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

Full Site Editing: Block group label #26639

Open
jameskoster opened this issue Nov 2, 2020 · 8 comments
Open

Full Site Editing: Block group label #26639

jameskoster opened this issue Nov 2, 2020 · 8 comments

Comments

@jameskoster
Copy link
Contributor

@jameskoster jameskoster commented Nov 2, 2020

Many blocks that are most likely to be used in the Site Editing context are currently grouped in to a "Design" category in the Inserter:

Screenshot 2020-11-02 at 17 05 46

While I understand the intention behind this label, it doesn't feel quite right looking at this group of blocks holistically. Dynamic blocks like Post Title / Site Tagline, and more technical blocks like the Query Loop transcend what I think the average user would interpret as "Design".

Framing the Site Editor as a visual theme builder, we might consider renaming this group to "Theme", or "Template". This would feel like a natural evolution given that many of the Site Editing blocks are direct ports of theme Template Tags.

Another option would be to split these blocks in to multiple groups – there are a great number of template tags for us to create... Perhaps there is scope for separate "Template – post", "Template – category", "Template – comment", and "Template – site", etc. block groups?

My instinct tells me a single "Theme" or "Template" group would be a good starting point from which we can refine over time. What do y'all think?

@mtias
Copy link
Contributor

@mtias mtias commented Feb 4, 2021

I'd be fine with a "Theme" category, though how would we describe the difference between "Widgets" and "Theme"? Maybe we could merge everything on widgets and rename the title to "Widgets & Theme".

@priethor
Copy link
Contributor

@priethor priethor commented Feb 4, 2021

I feel "Widgets & Theme" gives a better context without being too long, as I believe "Theme" can lead to confusion and users may understand "Theme" blocks are specific to the current theme.

@kjellr
Copy link
Contributor

@kjellr kjellr commented Feb 4, 2021

I believe "Theme" can lead to confusion and users may understand "Theme" blocks are specific to the current theme.

Yeah, I could see that point of confusion too. Maybe the category would be called "Site"? Or Even "Site Building" or "Site Editing"?

@priethor
Copy link
Contributor

@priethor priethor commented Feb 4, 2021

I was also thinking of the "Site" term, especially since some of these blocks are Site title and Site logo. However, "Site Editing" sounds too similar to "Full Site Editing" and might cause even more confusion. I think grouping them with "Widgets" ("Site & Widgets", maybe?) can help users conceptually differentiate between classic site-building, even if with blocks, and Full Site Editing.

@mtias
Copy link
Contributor

@mtias mtias commented Feb 4, 2021

Also relevant #26316 and #27822.

We already have "Latest Posts" in widgets so it makes sense to combine "Query" there.

@carolinan
Copy link
Contributor

@carolinan carolinan commented Feb 6, 2021

I would prefer "Site & Widgets" over "Theme"

@overclokk
Copy link

@overclokk overclokk commented Feb 19, 2021

My 2 cent, I think "Site" is good, not widget because they are different kind as I can see.

@aurooba
Copy link
Contributor

@aurooba aurooba commented Feb 22, 2021

In general, I find the term 'widgets' awkward within the Block Editor context.

Widgets are often a way to display content dynamically – latest posts, categories, calendar, archives, search, RSS, etc – these are all dynamic content blocks. The exception would be the Social Icons block, which I don't see as dynamic. Personally, I'd prefer to see a term like 'Dynamic' or 'Dynamic Content' encompass both the FSE specific blocks and the Widgets.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
7 participants