-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Update template descriptions with more detail #48290
Comments
Related: #36000 |
I think there is a HUGE opportunity here for the copy to help with clarity around some of the potential confusion around the use of Home/Index/Front Page - and other things like that. |
We might want to consider grouping this task with one or two others, or at least having some designs prepared. With longer descriptions the Add Template menu is going to become very noisy: If we introduce some grouping for templates (as discussed in #44302) then perhaps we can omit the description in the Add Template menu, and defer the description to the pattern selection modal, something like: It's important to keep such grouping in mind for this task as well because it might affect the description. For example when the Home template exists within the 'Blog' group, it's purpose is more inherently apparent. Just for completeness, the template description also appears in the Inspector, the document details popover, and the template management table. But a change in description length probably won't affect these too badly. |
Related: https://core.trac.wordpress.org/ticket/57562
|
Is 6.2 the right time to introduce template drill-down? Might be a little redundant without extra details, including which pages are using a particular template. It also means extra clicks for quickly previewing different templates. Perhaps a dedicated |
The drilldown is key to actually showing the edit button in context, so I think we do need it for 6.2 yes. |
Here's an initial take on this, inspired partially by existing documentation:
|
Perhaps @WordPress/block-themers has some thoughts on these descriptions? 🙏 |
High level, looks good. A few quick ones:
A few meta comments about this issue, and about for anyone reviewing:
|
Towards consistency of wording... Front Page: Displays your site’s front page.... Page: The template used to display all static pages.... Privacy Policy: Displays your site’s Privacy Policy page. |
I don't think so 👍
Sure!
Haha, I took that from the wp.org documentation, but yes it stood out to me as well. Updated descriptions:
|
a few suggestions for clarity. For others, I would need to think some more...
|
One thing I've been personally confused about while designing block themes is the difference between Front Page and Home, so any additional context that could be added here could be really helpful. |
I've made several adjustments to the table above, primarily cleaning up some of the copy. Some of it I have simplified by just making descriptions consistent. Others, I added a couple of different takes. There were also some inconsistencies with the usage of uppercase, and I wasn't sure how to proceed. So, I used my best judgement, preferring uppercase only when referencing a specific title or template name. One important note on the earlier text: "e.g." should be followed by a comma (e.g., something). It's the same as "for example, something." I'm not sure if we have a stylebook mention of this, but it is in both the Chicago and AP stylebooks. We could also really shorten the taxonomy template description if we left out the definition of what a taxonomy is. Otherwise, it's just long. Are links to support documents possible here?
|
Thanks for taking a look, this seems like a nice iteration to me. A couple of minor comments: 404The 'typo' part is a little ambiguous... when the user makes a typo where, adding a comment, logging in, searching? Should we embellish that, or maybe get rid of it? AttachmentIt feels a little overly technical / jargony. Do we need that "uploaded to a post" part at the end?
Home
Should 'for' be 'as'?
|
My gut instinct was to get rid of it when I first read it, but I was trying to incorporate some of the existing text. Should've went with my gut. Either option would work, though. Agreed that it's ambiguous.
We can drop that bit. Technically, it doesn't have to be uploaded to a post, so it'd be more accurate.
Yes, that would be better. |
I recommended a few changes to WordPress/wordpress-develop#4204, which probably would need to be in the plugin, too.
The longer descriptions also move the icons further down, away from the template name. Align these icons to the top:
If the style is appropriate for all of the similar buttons, |
@sabernhardt this one should already be fixed in the plugin: See: #48710 |
It would be the same in WP 6.2 after package updates are merged. |
Landed here after this forum issue thank you for looking into this. Confusing issues:-
Is it possible to change the description for the index template and the name of the blog(alternative) template |
The blog (alternative) template is available in Twenty Twenty-Three. It is a custom template. |
This was closed by #48934 |
Now that the 6.2 Site Editor is introducing a drill-down for individual templates, let’s revisit the current descriptive text for each template type. These don't have to be limited to small bits — but rather provide details, and context, on the workings of the selected template.
We'll need to update the descriptions in get_default_block_template_types() — referencing content from the template hierarchy.
Visual
The text was updated successfully, but these errors were encountered: