Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why is the Add title "block" not a block ? #9575

Closed
polygbrl opened this issue Sep 3, 2018 · 3 comments
Closed

Why is the Add title "block" not a block ? #9575

polygbrl opened this issue Sep 3, 2018 · 3 comments
Labels
[Feature] Blocks Overall functionality of blocks [Status] Duplicate Used to indicate that a current issue matches an existing one and can be closed [Type] Enhancement A suggestion for improvement.

Comments

@polygbrl
Copy link

polygbrl commented Sep 3, 2018

For now (3.7.0 plugin version), the "Add title" component is displayed as if it was a block. In fact, it is more a document meta field than a block and I find it confusing having it there pretending to be a block. Let me explain my point of view.

The "Add title" component is a heading

The post name and a post title isn't quite the same. The first is some document data (like the publishing date) and is related to the post's permalink. The second is a heading (text), with maybe the same value as the post name, displayed or not in the post content.

How do I understand the "Add title" component now ?

The "Add title" component is displayed as a block, in the editor's post content. However, it can't be moved nor removed. It is also related to the permalink as it is where the permalink is shown. The editor seems to show us that the post name must be a post title starting at the very beginning of the post (no matter what) even if the theme isn't displaying it in the post content. This is breaking the idea of having a wysiwyg editor: the post name isn't the post title !

A post title is theme related

Having a post title at the beginning of the post is more theme related. It should never be Gutenberg's choice. Having the same post title and post name is good for SEO but remains the user's and his theme's choice. If not, why is the publishing date in the document "status and visibility" panel and not an irremovable block under the "Add title" component ?

What then ?

One thing for sure is that this component can't stay as somehow-a-block-but-not-really. I'm listing some ideas to make a good choice:

  • A post title should be optional.
  • A post name must be required and can be randomly generated if not provided.
  • A heading block acting as a post title could be automatically added when a post name is given in the document panel.
  • A post name block could be made. If not used, a randomly generated post name is given to the post.

My question is in the title, which is part of the content, because it is a post title.

@Soean
Copy link
Member

Soean commented Sep 3, 2018

Also see Give the title area a block description #8469

@designsimply designsimply added Customization Issues related to Phase 2: Customization efforts [Status] Duplicate Used to indicate that a current issue matches an existing one and can be closed labels Sep 6, 2018
@designsimply
Copy link
Member

Thank you for posting! Making the title into a block is a planned update. We can consolidate this to #4482 and note that it is in the To Do in Customization project which that means it will be looked at after Gutenberg has been merged into WordPress core.

@designsimply
Copy link
Member

Also see #11553

@designsimply designsimply added [Type] Enhancement A suggestion for improvement. [Feature] Blocks Overall functionality of blocks and removed Customization Issues related to Phase 2: Customization efforts labels Nov 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature] Blocks Overall functionality of blocks [Status] Duplicate Used to indicate that a current issue matches an existing one and can be closed [Type] Enhancement A suggestion for improvement.
Projects
None yet
Development

No branches or pull requests

3 participants