Title: Giving FSE a More User Friendly Name Author: Josepha Published: July 27, 2022 --- [ ](https://profiles.wordpress.org/chanthaboune/) [Josepha](https://profiles.wordpress.org/chanthaboune/) 4:02 pm _on_ July 27, 2022 Tags: [core-editor ( 761 )](https://make.wordpress.org/core/tag/core-editor/), [editor ( 223 )](https://make.wordpress.org/core/tag/editor/), [gutenberg ( 553 )](https://make.wordpress.org/core/tag/gutenberg/) # Giving FSE a More User Friendly Name **tl;dr**: The terms “full site editing” and “full site editor” (also abbreviated as FSE) were developed to easily refer to a collection of features and now that those features are integrated into our daily WordPress experience, how can we best update the wording to be more user friendly? _Not sure the difference between GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/), full site editing, and other terms here? _[_Check out this post for high level definitions_](https://wordpress.org/news/2021/04/become-an-early-adopter-with-the-gutenberg-plugin/)_._ ## What I know Many years ago when we started referring to some of the work going into Gutenberg’s Customization phase (Phase 2) as “full site editing” it was meant to differentiate from the work that had come out of Phase 1. Phase 1’s work was focused on bringing blocks to posts and much of the page surrounding posts, but Phase 2 was meant to move those blocks to the rest of the site editing experience—hence “full site editing”. There are some issues with the term “full site editing”, though. * It was already possible to edit every part of a WordPress site using code. The term “full site editing” differentiated between phases of a project, rather than a new capabilitycapability A **capability** is permission to perform one or more types of task. Checking if a user has a capability is performed by the `current_user_can` function. Each user of a WordPress site might have some permissions but not others, depending on their role. For example, users who have the Author role usually have permission to edit their own posts (the “edit_posts” capability), but not permission to edit other users’ posts (the “edit_others_posts” capability). in the CMS. * To us, “full site editing” implies the use of blocks, but for new users there’s no reason for them to expect anything else. The term isn’t descriptive of what makes it unique. As we continue the move toward a full-featured, true WYSIWYGWhat You See Is What You Get What You See Is What You Get. Most commonly used in relation to editors, where changes made in edit mode reflect exactly as they will translate to the published page. experience for WordPressers of all skill levels, we should have a way to refer to it that is immediately meaningful for new users of our software, while also being an easy to reference term for all of us building and supporting the software. ## What I see  There are a few existing conversations around renaming Full Site Editing (both from a UIUI User interface/UXUX User experience perspective as well as a development perspective). From what I have seen in my reading, there are two primary contexts from a big picture perspective: Users & Visitors of WordPress; Contributors & Extenders of WordPress. That leads me to think we have two primary use cases for terms as well. * **Users & Visitors of WordPress**: I’ve heard a lot of people outside of the WordPress ecosystem simply referring to this as “the WordPress editor”. That seems mostly applicable to folks building with WordPress, selling on WordPress, or otherwise not creating the CMS itself. * **Contributors & Extenders of WordPress**: I have primarily seen references to“ the BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor” with the understanding that work toward Full Site Editing is a suite of tools from within the Block editor, a framework that originated in the Post Editor but is extending to all areas of WordPress like the Site Editor, hence most editing interfaces evolving into “the Block Editor”. This seems mostly applicable to folks working in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., on Themes/Plugins, and by extension, also Training, Design, and Documentation. **What other contexts do you think we need to be aware of as we look toward making this more user friendly?** ## What I need As with any audacious journey, one of the things that will hinder our success is not knowing what stands in our way. I would love it if you’d share your thoughts on the following questions! 1. We’ve referred to it this way for a long time. How can we tackle renaming this together? 2. It’s in the codebase. How will we make sure people who aren’t regular contributors see this? 3. And repeating the in-line question from above: What other contexts do you think we need to be aware of as we look toward how to refer to our collective work in the future? [#core-editor](https://make.wordpress.org/core/tag/core-editor/), [#editor](https://make.wordpress.org/core/tag/editor/), [#gutenberg](https://make.wordpress.org/core/tag/gutenberg/) ### Share this: * [ Threads ](https://make.wordpress.org/core/2022/07/27/giving-fse-a-more-user-friendly-name/?share=threads) * [ Mastodon ](https://make.wordpress.org/core/2022/07/27/giving-fse-a-more-user-friendly-name/?share=mastodon) * [ Bluesky ](https://make.wordpress.org/core/2022/07/27/giving-fse-a-more-user-friendly-name/?share=bluesky) * [ X ](https://make.wordpress.org/core/2022/07/27/giving-fse-a-more-user-friendly-name/?share=x) * [ Facebook ](https://make.wordpress.org/core/2022/07/27/giving-fse-a-more-user-friendly-name/?share=facebook) * [ LinkedIn ](https://make.wordpress.org/core/2022/07/27/giving-fse-a-more-user-friendly-name/?share=linkedin) 1. ![](https://secure.gravatar.com/avatar/bf1bf4a08dcd6494ede244fd890adf356950d5e7d98c1a92c5f52371af3a7f2b? s=32&d=mm&r=g) 2. [turtlepod](https://profiles.wordpress.org/turtlepod/) 4:15 pm _on_ July 27, 2022 3. Maybe “Template Editor” ? 4. * ![](https://secure.gravatar.com/avatar/40af412e047db484173bc45e2f6ee4237e9697f5ede64f3e49f05e096bb44edb? s=32&d=mm&r=g) * [Adrian](https://profiles.wordpress.org/adrian2k7/) 8:21 am _on_ October 17, 2022 * Something like this was my first thought too… * “Theme Editor” or “Template Editor ” * -> the editor for the basic look of the website. * “Content Editor” * -> the editor for a specific content 5. ![](https://secure.gravatar.com/avatar/cd986a8dc1219161f53bc2ec6718ede9c50789eb96048ccd73fca2b49d0a8114? s=32&d=mm&r=g) 6. [dmccan](https://profiles.wordpress.org/dmccan/) 4:50 pm _on_ July 27, 2022 7. I like how you are thinking to clarify the terms. I see confusion sometimes between GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/)( the site editor) and the phases of the “Gutenberg” project. 8. I guess you could always edit the full site with code, aka create a theme, but that is not really an editor as people think of one. I think “Full Site Editor” accurately describes what it does as you can not only edit content, but also headers, footers, side bar, and all the content templates. As [@turtlepod](https://profiles.wordpress.org/turtlepod/) mentions, “Template Editor” is accurately descriptive also. For what it is worth, and maybe an option, most of the page builders now call this functionality “Theme Builder”. Now that we can export our own theme, that fits. Maybe “Theme Builder” suggests more of the creative side than “Template Builder” or “Full Site Editor”. What do you think? 9. * ![](https://secure.gravatar.com/avatar/3e78f487b817bc4d2e346731d508a3ec0595bd644ca0be7ea1d968a86e929206? s=32&d=mm&r=g) * [Dan Knauss](https://profiles.wordpress.org/dpknauss/) 3:03 am _on_ August 2, 2022 * It depends what you consider “content,” but when you’re in FSE mode you _can’t_ currently edit _all_ the content you can edit when you are in post or page edit mode. You’re presented with both options when you’re on an individual post-type screen. You can “Edit Site” or “Edit Page/Post.” The site editor is still more of a template/layout editor, and the page/post/GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/) editor is the content editor. That’s probably the main cause of the confusion and difficulty in naming things, just in cutting-edge FSE themes. Having “ classic,” “blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience.,” and “hybrid” themes in the mix complicates it all further — each is a different context where the same names don’t work to describe different experiences. * It’s worth paying attention to how the language being used reflects, even unconsciously, the user experience. “Full-Site Editing” (using a gerund/verb- as-noun) reflects the experience people are having of FSE as a comprehensive mode or state of action. It’s not a “thing” like “the [block] editor.” You can “go into the editor” as a different space associated with the back-end, but you “go into editing mode” without leaving the front-end space you’re in — you just gain the ability to change things there directly. * What feels comfortable for me currently for an FSDE theme is “Site/Template Editing Mode” and “the Content Editor.” * **Re. other contexts to worry about,** I think “Block Editor” might need to fade away like “Gutenberg” or be specifically attached to reusable block and block pattern editor screens — not content. Blocks are more about layout/presentation, even if they contain reusable content around the main content. 10. ![](https://secure.gravatar.com/avatar/b42bde7b57524c13154fefc75682b0d891b1b9ac3c3af6db153633312b786dd1? s=32&d=mm&r=g) 11. [the IceGluer](https://profiles.wordpress.org/anydog/) 5:03 pm _on_ July 27, 2022 12. It all started with GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/), then it has spread, over the years, to areas beyond the post/page editing, into a unified (more or less) system for creating sites. It seems from my perspective too, that there is a general confusion about naming all these new concepts, unified in “FSE”. FSE is a paradigm change in WordPress, so, maybe the change of the term “full site editing” should reflect that paradigm change? Something really bold? 13. ![](https://secure.gravatar.com/avatar/ec06da98bebb8a8eadba0f26b10797332ef270c505be28d216d167d8b24b86fe? s=32&d=mm&r=g) 14. [Adam W. Warner](https://profiles.wordpress.org/awarner20/) 5:18 pm _on_ July 27, 2022 15. First thought, why don’t we ask the average user via a carefully crafted survey in the Dashboard? How do THEY refer to editing their websites? 16. My hunch, like others have noted, is that “Template” or “Theme” Editor might resonate with how they think about “designing” their websites. 17. FWIW 🙂 18. * ![](https://secure.gravatar.com/avatar/947cd60adce308d5ba8772143832343bbec847703364425b696af78313f3f909? s=32&d=mm&r=g) * [leeshadle](https://profiles.wordpress.org/leeshadle/) 8:40 pm _on_ July 27, 2022 * I kinda love the idea of calling it “Template Editor.” * Since we’re editing templates/template-parts this seems to make it easier to create a mental model of what you’re doing in the “full site editor”… - ![](https://secure.gravatar.com/avatar/ee688e454076072936e2f07ceea1727351cda523c1c8925b90e5040a858463e1? s=32&d=mm&r=g) - [Carolina Nymark](https://profiles.wordpress.org/poena/) 2:50 am _on_ July 28, 2022 - There is already a screen that is called template editor, it is different from the site editor. It is when you edit templates from the Template section in the post or page. * ![](https://secure.gravatar.com/avatar/4357b58869cb50dc2899234aad25e08c747faf5a0b06393fc7e919b82a67cee4? s=32&d=mm&r=g) * [supernovia](https://profiles.wordpress.org/supernovia/) 10:16 pm _on_ August 17, 2022 * +1 to a survey or other research 🙂 19. ![](https://secure.gravatar.com/avatar/5d499534bfc21eaf9fa55506d50ffa01881d9a6cba58935552d3a8ac45944c29? s=32&d=mm&r=g) 20. [Nick Diego](https://profiles.wordpress.org/ndiego/) 5:21 pm _on_ July 27, 2022 21. This is an interesting question. Names seem to stick once introduced. Many still refer to the Editor as GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/). I would be hesitant to introduce a new name when “Full Site Editing”, now that it has been so publically talked about, will likely live on for years and years to come. 22. I kind of like the term “Full Site Editing”. For new users in WordPress, it implies that they will be able to edit their entire site, which is true. Of course, there are many Classic themes and page builders that also allow you to do the same thing, but a theme that supports FSE differentiates it from traditional Classic themes. 23. Long-time WordPress users and developers generally already know that FSE represents a shift in the way WordPress websites can be built and have become familiar with this terminology. 24. I think we need to keep reinforcing that FSE is a suite of features rather than a singular feature and nail down a clear and concise definition. I have generally described it based on the features that the initiative encompasses: Site Editor, theme blocks, blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. themes… 25. Under the umbrella of FSE, clearly defining and reinforcing the terminology of specific features is equally important, if not more so. As you mention, “Editor” is one that comes to mind. The Editor is referred to by all sorts of names even within our own documentation: Editor, Block Editor, Page/Post Editor, Gutenberg Editor, etc. 26. I would vote to keep the term “Full Site Editing” for now but strengthen and codify its definition. Then we should work towards clearly defining other areas of the WordPress interface and ensure all documentation is updated accordingly. I believe this will go a long way in reducing confusion. 27. * ![](https://secure.gravatar.com/avatar/d102a48e8cbffdae03c05c8f4409e6b97dcdafd3b879300ab6d7249a6ffd50a6? s=32&d=mm&r=g) * [Robert Lilly](https://profiles.wordpress.org/rclilly/) 8:57 pm _on_ July 27, 2022 * +1 * ![](https://secure.gravatar.com/avatar/1dba75a903be8eb13bae6f961d81a99e5c76d5ca8c327a18bc25e96df2417b99? s=32&d=mm&r=g) * [Hugh Lashbrooke](https://profiles.wordpress.org/hlashbrooke/) 10:52 pm _on_ July 27, 2022 * > I would vote to keep the term “Full Site Editing” for now but strengthen > and codify its definition. Then we should work towards clearly defining > other areas of the WordPress interface and ensure all documentation is updated > accordingly. I believe this will go a long way in reducing confusion. * Honestly, I like this idea – I actually like the term “Full Site Editing” as it is descriptive and accurate. If we double down on it and codify its definition, then it would make it more clear for people. - ![](https://secure.gravatar.com/avatar/b96b0d15a783789395cdef44e063be01558ee823a2cb8814aeaab245ba33a6cd? s=32&d=mm&r=g) - [Leo Gopal](https://profiles.wordpress.org/leogopal/) 9:12 pm _on_ August 17, 2022 - +1 * ![](https://secure.gravatar.com/avatar/1c07b42cbac37b466617475d535ed137372f620594c03e1bd81765d22e3066cf? s=32&d=mm&r=g) * [Gina W](https://profiles.wordpress.org/tacaha5/) 1:51 am _on_ July 28, 2022 * +1 * ![](https://secure.gravatar.com/avatar/165714348931b21b5ad76e84b2e1c407402d43162022e1a2149b49143a696dec? s=32&d=mm&r=g) * [Joao D - a11n](https://profiles.wordpress.org/johnlud/) 2:22 am _on_ July 28, 2022 * +1 * I also liked the ideas and questions raised. * “Full site editing” defines well what to expect from these features. From a support point of view, reinforcing this term seems to me like a good strategy, since other terms like “Site Builder, Site Editor, Theme Editor” can sound a bit generic and maybe confuse the customer thinking that other plugins and themes that have “Editor” in their name, are involved in this project. * The only consideration, that other colleagues mentioned, is that using a term that is easy to speak and remember in other languages would also be a plus. * ![](https://secure.gravatar.com/avatar/4dfad80d8f9d884b2c7c39d304c339b2ae573d178e2e5ec3e9150299b25fe744? s=32&d=mm&r=g) * [Damon Cook](https://profiles.wordpress.org/colorful-tones/) 11:14 am _on_ July 28, 2022 * +💯 - ![](https://secure.gravatar.com/avatar/3623efdc44943524c5828ff6ad90a30a217154846520082e0c4d7aa664e13708? s=32&d=mm&r=g) - [Sam Munoz](https://profiles.wordpress.org/samanthaxmunoz/) 3:45 pm _on_ July 28, 2022 - +1 I think “Full Site Editing” is an accurate description of the functionality. - **I strongly agree with this:** - > I would vote to keep the term “Full Site Editing” for now but strengthen > and codify its definition. Then we should work towards clearly defining > other areas of the WordPress interface and ensure all documentation is > updated accordingly. I believe this will go a long way in reducing confusion. - In some ways, the name itself is less relevant than the clarity and adoption by the community. * ![](https://secure.gravatar.com/avatar/f03c979ee6e36a4b7cbbe30f644f946afd7e68a097d5a334de15c344dea4e8fd? s=32&d=mm&r=g) * [sallijane](https://profiles.wordpress.org/sallijane/) 4:38 pm _on_ July 28, 2022 * AAbsolutely; changing names is simply confusing. It describes the function, has been in use, including in acronym form. Don’t create problems with extra, unneeded changes—enough changes fast as it is with software, most nonprofessionals have a hard time keeping up without an artificial change for marketing or some such reason. * ![](https://secure.gravatar.com/avatar/eb66d1655187ce7b2e3e22ee93a30d4f9657a505aa4a247c11c67b282164f60a? s=32&d=mm&r=g) * [Jessica Lyschik](https://profiles.wordpress.org/luminuu/) 4:52 pm _on_ July 28, 2022 * +1 for keeping the term “Full Site Editing”. Also, this thought from [@poena](https://profiles.wordpress.org/poena/) is very important (see further down below), especially when we look into the future: * > I think that as it becomes easier to navigate between the editors -all 3 > of them – and they merge more into one, and feel more like one… we will > naturally move towards only calling it “editor”. We are not there yet. * But for now it makes sense to stick with what we currently have. The term “ blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor” has not really replaced the term GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/) at all and tbh, I don’t think it will ever be. And the same would happen if a new term for Full Site Editing would be decided on. * ![](https://secure.gravatar.com/avatar/8df0935774c2077235436ffeb6637e021bff4e3b2810fd0dddc5a4e0918231d2? s=32&d=mm&r=g) * [Femy Praseeth](https://profiles.wordpress.org/femkreations/) 5:08 pm _on_ July 28, 2022 * +1 for keeping “Full Site Editing” I also love the idea by Adam to do a survey. * > Adam W. Warner Yesterday at 10:18 am > First thought, why don’t we ask the > average user via a carefully crafted survey in the Dashboard? How do THEY > refer to editing their websites? * ![](https://secure.gravatar.com/avatar/2002d4281b52a085b3248c89b21470d197453ff7c4a5a9f3bcbd7de72461881a? s=32&d=mm&r=g) * [SeReedMedia](https://profiles.wordpress.org/sereedmedia/) 5:16 pm _on_ July 28, 2022 * +1 * ![](https://secure.gravatar.com/avatar/5cd07f7bca6e9d0992c0635218e4aee9f65c674b45fbd8142b01a0e20b08363b? s=32&d=mm&r=g) * Anonymous User 6:17 am _on_ July 29, 2022 * +1 * ![](https://secure.gravatar.com/avatar/bb510c76886c4bf6fb743fd521691db49d49861bd099478cebb81b69771d971c? s=32&d=mm&r=g) * [Gurjot Singh](https://profiles.wordpress.org/gurjotsinghdev/) 8:25 pm _on_ August 3, 2022 * +1 for “Full Site Editing”. It describes the function fully. * ![](https://secure.gravatar.com/avatar/24a5ca8b960821795fd5f6c0f70ce94a84e0ee71fea4beeee394fa66995ae838? s=32&d=mm&r=g) * [Peter Wilson](https://profiles.wordpress.org/peterwilsoncc/) 12:27 am _on_ August 4, 2022 * I arrived intending to share my thoughts but [@ndiego](https://profiles.wordpress.org/ndiego/)‘ s already done so. After using the term for some time, I think it’s too late to rebrand. * It may be possible to drop the prefix “full” (it doesn’t appear in any of the docblocks within CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. as far as I can tell) but I think the most likely outcome is seeing it written as [Full] Site Editing when referred to elsewhere. * ![](https://secure.gravatar.com/avatar/2f3047dd0ab8cff7995f253c4190f0221dec5bb1d8d376d1c5f5746353521abf? s=32&d=mm&r=g) * [Carrie Dils](https://profiles.wordpress.org/cdils/) 9:50 pm _on_ August 8, 2022 * +1 [@ndiego](https://profiles.wordpress.org/ndiego/) 28. ![](https://secure.gravatar.com/avatar/a9b9c868096a582a9a9eec1199ea782cd219570b2d46936761ef5b7f56212b3d? s=32&d=mm&r=g) 29. [Davinder Singh Kainth](https://profiles.wordpress.org/idavinder/) 5:57 pm _on_ July 27, 2022 30. “Builder” or “Site Builder” would be more familiar words for the wider audience. 31. * ![](https://secure.gravatar.com/avatar/85b415147e01ce70ba2930cd87c672cccb6c6427470454c833dcc293ca657df2? s=32&d=mm&r=g) * [thedezzie](https://profiles.wordpress.org/thedezzie/) 2:44 pm _on_ July 28, 2022 * +1 32. ![](https://secure.gravatar.com/avatar/89e470d01e796cd2a0c01bec6b71b8183a6a6a176513e740e3ee29894e60711a? s=32&d=mm&r=g) 33. [robglidden](https://profiles.wordpress.org/robglidden/) 6:39 pm _on_ July 27, 2022 34. Future view, looking back from collaborative editing, what I would want to tell a user: 35. The Editor. 36. In the WordPress editor you and your team can edit posts, pages and themes in the same, consistent user interface. 37. A theme defines the style — the look and feel — of your site. A theme includes general style settings and templates that define the layout of particular posts or pages. 38. Once you and your team are satisfied with your work, you can “go live” and share it with the whole world or a particular community. 39. — This assumes collaborative editing extends to themes (why wouldn’t it?). 40. Some current terms are probably more shop-talk shorthand than useful descriptions—“ full site editing”, “FSE”, “GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/)”,“ template/site/blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor”. 41. Themes and templates are more high-level terms than blocks and patterns, but they are sufficient to communicate basic ideas to users. 42. * ![](https://secure.gravatar.com/avatar/2002d4281b52a085b3248c89b21470d197453ff7c4a5a9f3bcbd7de72461881a? s=32&d=mm&r=g) * [SeReedMedia](https://profiles.wordpress.org/sereedmedia/) 5:17 pm _on_ July 28, 2022 * +1 43. ![](https://secure.gravatar.com/avatar/c8091d1ddd1fb207bb9c5015c2869bae9a2f03bd1378d11cd5ec0edc076bb2cd? s=32&d=mm&r=g) 44. [Matt Cromwell](https://profiles.wordpress.org/webdevmattcrom/) 7:16 pm _on_ July 27, 2022 45. I think using GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/) as a codename for the project within the code is not really problematic. 46. But for users of the software, making the naming consistent and obvious (and dare I say boring) is best: Site Editor. Whether you’re editing your templates or your content, it’s an editor. 47. Or if we wanted to get fancy: 48. * Site Designer (for FSE) * Editor (for blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor) 49. * ![](https://secure.gravatar.com/avatar/2002d4281b52a085b3248c89b21470d197453ff7c4a5a9f3bcbd7de72461881a? s=32&d=mm&r=g) * [SeReedMedia](https://profiles.wordpress.org/sereedmedia/) 5:17 pm _on_ July 28, 2022 * +1 50. ![](https://secure.gravatar.com/avatar/e45bf14ef09437a9bf5231d92a08ecfcfc800402eb3ea68a82f8750d60ab815f? s=32&d=mm&r=g) 51. [Colin Chadwick](https://profiles.wordpress.org/colinchadwick/) 7:39 pm _on_ July 27, 2022 52. As WordPress has many non-technical users, I think it’s a good idea to keep it simple: Site Editor. 53. * ![](https://secure.gravatar.com/avatar/f03c979ee6e36a4b7cbbe30f644f946afd7e68a097d5a334de15c344dea4e8fd? s=32&d=mm&r=g) * [sallijane](https://profiles.wordpress.org/sallijane/) 4:41 pm _on_ July 28, 2022 * yes, dropping the “full” is not terrible, and avoids the “full-site editor vs full site editor” hyphen dilemma (one grammatically accurate, one in long- term use) for us copy editors, but I would not want to see any other change. Site editor is descriptive. 54. ![](https://secure.gravatar.com/avatar/89e470d01e796cd2a0c01bec6b71b8183a6a6a176513e740e3ee29894e60711a? s=32&d=mm&r=g) 55. [robglidden](https://profiles.wordpress.org/robglidden/) 8:44 pm _on_ July 27, 2022 56. — What to call a full-featured, true WYSIWYGWhat You See Is What You Get What You See Is What You Get. Most commonly used in relation to editors, where changes made in edit mode reflect exactly as they will translate to the published page. experience for WordPressers of all skill levels? 57. The Editor 58. With the editor, you and your team can edit posts, pages, and themes. 59. Before, it was same editor that edited both posts and pages. 60. Now, the same editor can also edit themes. 61. No need to call it a different editor every time it edits a slightly different thing. 62. What about editing patterns? Will we need to add a pattern editor? Or a navigation editor? No, same editor will edit a slightly different thing. 63. Distinguishing site/theme/template/pattern/blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience./page/post editors/builders as the definition of WordPress is too confusing. 64. One experience, one editor, one place for users to collaborate. 65. I think that is why users and visitors of WordPress are already simply referring to “the WordPress editor”. 66. — What other contexts do you think we need to be aware of as we look toward how to refer to our collective work in the future? 67. For terminology, I’d dare say better only one, unifying, context — the user context. 2 is already too many. 68. ![](https://secure.gravatar.com/avatar/e906028bee30f5b07463dfb2be84920db8d5016422c79b98cd93bbabfbaa4d48? s=32&d=mm&r=g) 69. [Benny](https://profiles.wordpress.org/bvl/) 9:02 pm _on_ July 27, 2022 70. I agree with robglidden. ‘The Editor’ encompasses all editing contexts. 71. ![](https://secure.gravatar.com/avatar/6f505c6be9a951929a99becb6b413dcfa583a5ca3dd0f7320766fee1481f0f82? s=32&d=mm&r=g) 72. [Jb Audras](https://profiles.wordpress.org/audrasjb/) 9:56 pm _on_ July 27, 2022 73. _Putting my GTEGeneral Translation Editor General Translation Editor – One of the polyglots team leads in a geographic region [https://make.wordpress.org/polyglots/teams/](https://make.wordpress.org/polyglots/teams/). Further information at [https://make.wordpress.org/polyglots/handbook/glossary/#general-translation-editor](https://make.wordpress.org/polyglots/handbook/glossary/#general-translation-editor) fr\_FR cap on to add my two cents._ 74. In the French translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see [localization](https://make.wordpress.org/core/2022/07/27/giving-fse-a-more-user-friendly-name/?output_format=md#l10n), [internationalization](https://make.wordpress.org/core/2022/07/27/giving-fse-a-more-user-friendly-name/?output_format=md#i18n). of WP, “Full site editing” would be literally translated into “Édition complète de site”, which is pretty long and sounds a bit weird. That’s why we decided to translate it to “Édition de site”, which would translate back to “Site editing” in English. 75. It’s short, simple, efficient 🙂 76. * ![](https://secure.gravatar.com/avatar/03fec775ba7bbccce7139a73dd5e741fbaa2069cf384cf2c5b328d391dd82266? s=32&d=mm&r=g) * [FX Bénard](https://profiles.wordpress.org/fxbenard/) 8:30 pm _on_ July 28, 2022 * Agree with [@audrasjb](https://profiles.wordpress.org/audrasjb/). We are fully happy with this translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see [localization](https://make.wordpress.org/core/2022/07/27/giving-fse-a-more-user-friendly-name/?output_format=md#l10n), [internationalization](https://make.wordpress.org/core/2022/07/27/giving-fse-a-more-user-friendly-name/?output_format=md#i18n). in French and no user seems to have any issue with it. * ![](https://secure.gravatar.com/avatar/46e579e5809af6c797613c207eb35f9b2ef06b2008e48c03e63e6d801ad048d6? s=32&d=mm&r=g) * [marybaum](https://profiles.wordpress.org/marybaum/) 6:09 pm _on_ July 29, 2022 * I like starting simple with Site Editor, then getting granular with the parts: the Template Editor, the Theme Editor (which would encompass a Template Editor, a Template Parts Editor, a Pattern Editor) in short, each of those would be the Editor for the particular thing a person is doing. * We do that already in other contexts for image editing, copy editing, code editing, and more. - ![](https://secure.gravatar.com/avatar/af98b4302728984cfc6255c7f94f7d6ba10e51787f68c0842d15d2005b57db57? s=32&d=mm&r=g) - [Benjamin Evans](https://profiles.wordpress.org/kaitohm/) 7:33 am _on_ August 2, 2022 - From the perspective of a new user interacting with WordPress for the first time, this thought process makes much sense. +1 ! * ![](https://secure.gravatar.com/avatar/823071bb01f306c6710ca48e28eaef885e700de5d9d005f0a5b6a29a6e987942? s=32&d=mm&r=g) * [Amit Patel](https://profiles.wordpress.org/amitpatelmd/) 3:53 am _on_ August 4, 2022 * I really like the word **“Site Editor”** because it makes more sense for the purpose of full site editing for any type of user (First-time user, Experienced one etc.). - ![](https://secure.gravatar.com/avatar/8e997e7b6570ba04b872e29f736ce77a396a6b024e434de7c82530456a253e65? s=32&d=mm&r=g) - [Courtney P.K.](https://profiles.wordpress.org/courtneypk/) 6:35 pm _on_ August 2, 2022 - Plus one from me as well. I also agree with “Site Editor” being quite simple and clear! 77. ![](https://secure.gravatar.com/avatar/13b3c2669c4f02f0684e72ae978ccda58ea137e1cddb9dafacf43967c841b96d? s=32&d=mm&r=g) 78. [James Giroux](https://profiles.wordpress.org/jamesgiroux/) 9:57 pm _on_ July 27, 2022 79. I also agree with Rob Glidden. The more we can demystify the experience for casual/ inexperienced users the better. 80. Advanced users and developers who follow the product development cycle will likely use terms like GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/), BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. Editor or Full Site Editor but it becomes irrelevant in the context of the job to be done by the user. 81. “I use the editor to update my site’s navigation.” “I use the editor to create beautiful blogblog (versus network, site) posts.” “I use the editor to update my footer’s copyright with the latest year.” 82. All those statements are correct and speak to a single unified experience by the user (again, as Rob has first said). 83. Thanks for asking Josepha, it’s a great question and I’m looking forward to how the conversation unfolds. 84. ![](https://secure.gravatar.com/avatar/325278bedbabb188c7a7fb9e919568efeca13fcab4302644406ceacf3614f9b6? s=32&d=mm&r=g) 85. [Jos Velasco](https://profiles.wordpress.org/josvelasco/) 11:19 pm _on_ July 27, 2022 86. Just drop the “Full”: 87. My vote is for “Site editor”. 88. * ![](https://secure.gravatar.com/avatar/09a19d6c3d35d136db80cd14757e532d95a3b54dd9aebded06dcee529ed3d285? s=32&d=mm&r=g) * [Nilo Velez](https://profiles.wordpress.org/nilovelez/) 11:53 pm _on_ July 29, 2022 * +1000 to this. Please, don’t overcomplicate things. * Post editor, site editor. 89. ![](https://secure.gravatar.com/avatar/d94bdc8e970ce9c05a299f54838f522dafcf3d9379cfbea2ca2c848497bb6732? s=32&d=mm&r=g) 90. [leemon](https://profiles.wordpress.org/leemon/) 11:39 pm _on_ July 27, 2022 91. I always hated the term “Full Site Editing” because, like Jb Audras said above, it doesn’t have a natural sounding translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see [localization](https://make.wordpress.org/core/2022/07/27/giving-fse-a-more-user-friendly-name/?output_format=md#l10n), [internationalization](https://make.wordpress.org/core/2022/07/27/giving-fse-a-more-user-friendly-name/?output_format=md#i18n). in Latin languages such as Spanish or Catalan. “Site editor” or “Site builder” would be better names. 92. * ![](https://secure.gravatar.com/avatar/aa89edf971372c035a02c633667412facd8b00fd6946fe4f208f7aed7f7bb524? s=32&d=mm&r=g) * [Naoko Takano](https://profiles.wordpress.org/nao/) 4:29 am _on_ July 28, 2022 * In Japanese too, a direct translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see [localization](https://make.wordpress.org/core/2022/07/27/giving-fse-a-more-user-friendly-name/?output_format=md#l10n), [internationalization](https://make.wordpress.org/core/2022/07/27/giving-fse-a-more-user-friendly-name/?output_format=md#i18n). of “Site Editor” (サイトエディター / pronounced like _saito editaā_) sounds less confusing than “Full Site Editor” (フルサイトエディター /_furu saito editaā_). * The abbreviation “FSE” can be difficult for non-English users since it doesn’t always represent the letters of the translated words. Whatever direction we are going, it’d be nice to have a short enough name that is less likely to be abbreviated. - ![](https://secure.gravatar.com/avatar/2f3047dd0ab8cff7995f253c4190f0221dec5bb1d8d376d1c5f5746353521abf? s=32&d=mm&r=g) - [Carrie Dils](https://profiles.wordpress.org/cdils/) 9:49 pm _on_ August 8, 2022 - +1 - That makes sense. Great call-out to consider how the name (and abbreviation) translate 93. ![](https://secure.gravatar.com/avatar/c2cdd42c640ba01f92cdefd35146b4d6f0df9a8d0d3f82cf82995feca6fbcc6c? s=32&d=mm&r=g) 94. [Elma Studio](https://profiles.wordpress.org/elmastudio/) 11:58 pm _on_ July 27, 2022 95. That is such an important question to ask. I think we are facing more and more complex new names as we are moving along the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/) project phases. I experience all the new names as confusing not only for users, but also for product developers like myself. 96. Right now, I personally find the differentiation between ‘Full Site Editing’ ( let’s keep the name for a second) and the post/page or blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor most confusing. 97. Additionally, as being said, the term ‘Full Site Editing (FSE)’ is already used, so we need to make sure not to cause more confusing changing it. 98. Taking this fact in consideration, I feel like dropping the ‘Full’ and calling it ‘Site Editor’ makes the most sense to me. To shorten the term is a big selling point in the long run I feel, ‘FSE’ was a needed abbreviation, but it’s not pretty nor descriptive, so hopefully it doesn’t stick around. 99. Thoughts on the term ‘Builder/building’: Personally, I like the word ‘builder’ but in the majority of user cases it seems more likely to be used as an editing experience vs. a building (from scratch) experience. Or I’m I wrong here? 100. Also, ‘builder/building’ is taking a strong reference to page builders, and I’m not sure if we want to confuse the experience we are building now with what page builders have already been doing for years. It should be a new/different name imo. 101. * ![](https://secure.gravatar.com/avatar/f03c979ee6e36a4b7cbbe30f644f946afd7e68a097d5a334de15c344dea4e8fd? s=32&d=mm&r=g) * [sallijane](https://profiles.wordpress.org/sallijane/) 4:43 pm _on_ July 28, 2022 * Stay away from builder! I avoid all page-builders where I can, and using that term for what is now called an editor will only add to confusion. 102. ![](https://secure.gravatar.com/avatar/3c2d35c70cfeb674f1fddcff8fdc6010f63d833d4ead58bba947d7578f039bd3? s=32&d=mm&r=g) 103. [Stephen Cronin](https://profiles.wordpress.org/stephencronin/) 12:16 am _on_ July 28, 2022 104. It’s probably worth considering the terms that have historically been used in the ecosystem, as the majority of users will mostly likely be used to those terms and the less confusing it is for them the better. 105. I think the most common term used to describe what the FSE does would be “Site Builder”. 106. The term “Editor” has historically been used to describe the post/page content editor. “Page Builders” were builders that generally only worked within the post/ page content editor area. Then along came “Site Builders” that worked outside that, across the whole of the site. 107. So, users will most likely understand the term “Site Builder” best. I personally don’t mind “Site Editor” (you are editing the site after all), but as mentioned above, that’s most commonly been used to reference to the post/page content editor. I can’t see any need for the “Full” part. 108. Whatever terminology is decided, the terms for related things should probably be reconsidered as well. Ie, would it be sensible to rename ‘blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. themes’( and all the things) to be more in line with the new terminology for the FSE? There’d be pain in changing the name of other things, but it would be better to consider this holistically and ensure consistent terminology throughout. 109. ![](https://secure.gravatar.com/avatar/a1a6b3b57272889d683058cc81b33bd1d232e55aff1e9288affa6f78d6df05b6? s=32&d=mm&r=g) 110. [Noumaan Yaqoob](https://profiles.wordpress.org/noumaan/) 1:26 am _on_ July 28, 2022 111. The editor allows users to edit their WordPress theme templates. Perhaps, a more apt term would be Theme Editor, which tells users that they are making changes to their WordPress theme and these changes will go away if they switched to a different theme. 112. * ![](https://secure.gravatar.com/avatar/f03c979ee6e36a4b7cbbe30f644f946afd7e68a097d5a334de15c344dea4e8fd? s=32&d=mm&r=g) * [sallijane](https://profiles.wordpress.org/sallijane/) 4:44 pm _on_ July 28, 2022 * I believe that the term _theme editor_ is already in use. 113. ![](https://secure.gravatar.com/avatar/e3f7160836a83aaac9c22e88cfaf7bbe9cd99e0f7b5c88bd16590d5b2bee42ff? s=32&d=mm&r=g) 114. [Rob Howard](https://profiles.wordpress.org/robhowarddc/) 2:13 am _on_ July 28, 2022 115. If we are sticking with simple, clear language (i.e. not a brand name like “Elementor” or a code name like “GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/)”), here’s how I would break it down: 116. The “Editor” is the tool that allows you to create and edit a mostly textual page or post, like the post I am commenting on right now. This is the primary functionality of WordPress, and I think saying this is the “Editor” allows us to continue to talk about the BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. Editor, Classic Editor, etc., in a way that is both intuitive and maps to how we’ve used this word in the past. I also think this maps to how others use this word – for example, the Medium editor is similar to the Substack editor is similar to the WordPress editor. 117. The “Theme” is the visual design of the site. The theme surrounds and affects the content you create in the editor, but you can feasibly swap themes and the content you created in the editor will still work. I think full-site editing is really a matter of “building” a “theme,” in terms of the most common and conventional language we can apply to these ideas. (There is also a “Theme Editor” in WP that allows you to view and edit the actual PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher/CSSCSS Cascading Style Sheets./HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. of your theme– but again that is using “editor” in the sense that you are editing text, which I think is reasonably consistent with the “editor” concept above.) 118. The word “Builder” is used by lots of third-party plugins (Beaver Builder, Elementor[ which describes itself as a Site Builder], etc.) and I think would be useful here. FSE could be called the “Theme Builder,” and we’d be using two words that are much clearer, and much more obvious in terms of meaning to a layperson. If you said, “use the Theme Builder to change how your site looks, but use the Editor to write a blogblog (versus network, site) post or create a new page,” I think that would instantly make sense even to a non-technical user. 119. Another possibility here is to use the word “CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings.,” which obviously is already used in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., but if we’re slowly deprecating the Customizer as it exists today, we could repurpose this word and call FSE the “Theme Customizer,” which in some ways is even more accurate than “Theme Builder.” That said, I think either of these options would be clear to the end-user and wouldn’t require any special further explanation or mental acrobatics. Other services (Squarespace, Shopify, etc.) use the word Theme in the same way, and the words “build” and “ customize” clearly describe how you would be modifying the look of your site ( i.e. the theme). 120. I agree with the other commenters who mentioned that “Full” is not really a useful adjective here. But I think the key thing is to distinguish clearly between Editor( posts/pages, mostly text) and Theme (visuals). From there, Theme Builder vs. Theme Customizer would really just be a matter of preference. I’d guess that “ Builder” comes off as a little simpler, but “Customizer” has the benefit of already being used in a similar way within WP core. 121. * ![](https://secure.gravatar.com/avatar/f03c979ee6e36a4b7cbbe30f644f946afd7e68a097d5a334de15c344dea4e8fd? s=32&d=mm&r=g) * [sallijane](https://profiles.wordpress.org/sallijane/) 4:46 pm _on_ July 28, 2022 * Don’t use a deprecated (or “being deprecated”) word for something else for at least 5 years (I would say 10, but computer time is compressed). It would totally confuse those who are not professionals or constantly involved. 122. ![](https://secure.gravatar.com/avatar/ee688e454076072936e2f07ceea1727351cda523c1c8925b90e5040a858463e1? s=32&d=mm&r=g) 123. [Carolina Nymark](https://profiles.wordpress.org/poena/) 2:52 am _on_ July 28, 2022 124. I think that as it becomes easier to navigate between the editors -all 3 of them– and they merge more into one, and feel more like one… we will naturally move towards only calling it “editor”. We are not there yet. 125. * ![](https://secure.gravatar.com/avatar/eb66d1655187ce7b2e3e22ee93a30d4f9657a505aa4a247c11c67b282164f60a? s=32&d=mm&r=g) * [Jessica Lyschik](https://profiles.wordpress.org/luminuu/) 4:43 pm _on_ July 28, 2022 * +1! * ![](https://secure.gravatar.com/avatar/2002d4281b52a085b3248c89b21470d197453ff7c4a5a9f3bcbd7de72461881a? s=32&d=mm&r=g) * [SeReedMedia](https://profiles.wordpress.org/sereedmedia/) 5:19 pm _on_ July 28, 2022 * +1 * ![](https://secure.gravatar.com/avatar/7a10376221a71d0539fedbcc58b816de195ecb6fd0898022ba6a46c9618b4c90? s=32&d=mm&r=g) * [franzaurus](https://profiles.wordpress.org/franz00/) 1:20 am _on_ August 2, 2022 * +1 126. ![](https://secure.gravatar.com/avatar/734b7b97667c20b489016c6980d84c92811356e7317617803f6585c40b72e383? s=32&d=mm&r=g) 127. [tanjoymor](https://profiles.wordpress.org/tanjoymor/) 4:14 am _on_ July 28, 2022 128. My thoughts on terminology: full site editing, FSE, Site Editor, BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. Editor and so forth, is that we need to look at the bigger picture of what the pieces actually are, what they’re capable of, and what their future will be. 129. As an action term, full site editing, isn’t that terrible and is accurate right now and will be accurate in the future. Right now it’s an action spread out among several different locations and tools within a site. In the future, maybe it will all be managed from one entry point. 130. I also don’t see anything wrong with the use of this term, as an action, when used properly and for the acronym of FSE to only be used as a replacement for this term but not as a noun for something else. 131. The term full site editing and FSE is not a “name”. 132. Interchanging FSE with Site Editor is not accurate. Categorizing themes as FSE themes is also not really accurate. 133. If you go to Appearance > Editor you cannot edit all of the content of your pages and posts. The Site Editor, as it is right now, does not provide an experience of full site editing on its own. However, it’s also not just a Template Editor because of Global Styles, and the way menus are now created. 134. Theme Editor would cause future limitations once content, templates, styles, and menus “can” be edited all in one location. Plus, we have a Theme Editor for accessing the code, so that would cause confusion. 135. In my opinion: 136. At the moment the Site Editor is more accurately a Designer. 137. When you edit a page or post you are taken into an “editor”. This is more accurately a Content Editor with a Classic and Block version, and a Visual or Code display. 138. Used in combination, all of these features create a full site editing experience. If we can get to the point when all of the features are merged together in a true Site Editor, it will still be an action of full site editing. 139. Code vs non-code editing? 140. > It was already possible to edit every part of a WordPress site using code. 141. I suppose this is technically true, though it feels as though that approach would be referenced as “code editing”, so is that really a concern? 142. Also, are the contributors and extenders actually confused by any of this? Or is it mostly the public who are confused? 143. I’d suggest that anyone deeply entrenched in WordPress has had enough time to wrap their head around what was meant by FSE and its the public that now needs to be addressed. 144. It should be easy enough to define and brand the action of full site editing to mean no-code-editing. 145. To pull away from using the wording of full site editing is going to be extremely difficult at this point, and stands a chance of creating a great deal of confusion with the public in general. Especially beginners. 146. My vote is that from a “name” perspective, under Appearance, we call it “Designer” whether we expand on that to be “Site Designer” or “Global Designer” doesn’t feel like big deal. 147. From an explanation perspective, it feels fine to be able to say: “the combined power of the Editor and the Designer now enables a no-code approach to full site editing” and allows educators to clarify that at the moment the Editor is intended for editing content and the Designer is intended for editing the visual look/ feel of a site. (Regardless of the fact that there is a bit of overlap that is possible. Just because something “can” be done, doesn’t mean it should be or that it’s the best approach.) 148. Then, if/when we get to the point of having one entry point location to manage it all we can remove Pages, Posts, and Designer as separate items and place one menu item for “Site Editor” at the top of the main dashboard that will then provide access to editing: content, templates, styles, menus. 149. Whichever way this goes, my hope is that consideration for the future direction and plans will be taken into consideration at this point, before even more public adoption occurs. 150. As a side thought, the time to consider the name for a new feature is before it’s released to the public. Perhaps something to keep in mind in the future. There’s a lot of work, documentation, videos, publicity, and education that has gone into this in many different places that is going to be a lot of work (and difficult) to undo as habits have already formed. 151. 1. We’ve referred to it this way for a long time. How can we tackle renaming this together? – Once a name, description, and explanation has been decided on, it’s going to need consistent application and high visibility. – All stakeholders will also need to buy-in to the decision for it to truly take effect with widespread adoption. 2. It’s in the codebase. How will we make sure people who aren’t regular contributors see this? – I’m an educator not a coder, so I honestly don’t know. Can the codebase be changed? That would be ideal or it will perpetuate confusion and mis-use. – But as above, broad and widespread high visibility is going to be important. Reaching out to vocal, high-traffic sites to ask for their help might be beneficial. No matter what, the decision needs to be prominent long term. 3. And repeating the in-line question from above: What other contexts do you think we need to be aware of as we look toward how to refer to our collective work in the future? – WIP names are likely always going to be a thing and a challenge. My recommendation is to adopt a more unified approach to utilizing BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. labels and link to that explanations that “beta names” are subject to change, simply from an angle of setting expectations. – Ideally, before public release, open discussion on naming choices should be thoroughly explored. Perhaps surveys, polls, and even contests could be considered. 152. In my writing circles, we like to make a caveat with opinion pieces like this comment: Everything here is my own personal opinion, take what you like, leave what you don’t 😊 153. * ![](https://secure.gravatar.com/avatar/f03c979ee6e36a4b7cbbe30f644f946afd7e68a097d5a334de15c344dea4e8fd? s=32&d=mm&r=g) * [sallijane](https://profiles.wordpress.org/sallijane/) 4:50 pm _on_ July 28, 2022 * Excellent analysis, I agree with your opinions. Naming should come early in process, not be changed unless absolutely necessary. The priority should be clarity for the public, ideally staying with what is already in place as much as possible to eliminate potential for confusion. * ![](https://secure.gravatar.com/avatar/2002d4281b52a085b3248c89b21470d197453ff7c4a5a9f3bcbd7de72461881a? s=32&d=mm&r=g) * [SeReedMedia](https://profiles.wordpress.org/sereedmedia/) 5:19 pm _on_ July 28, 2022 * +1 154. ![](https://secure.gravatar.com/avatar/80c838b93c23e1188834951292bef5eabd69d9f171f22841d643b94cc7970430? s=32&d=mm&r=g) 155. [Dave Loodts](https://profiles.wordpress.org/davelo/) 4:40 am _on_ July 28, 2022 156. I wouldn’t use the term ‘template’ cause there are still Page Templates to use; which is great; by the way. And “template’ is still a technical naming. Fill Site Editing is -in my opinion- mainly referring to the archives, tags, categorie pages. Yes, and also headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. and footer. 157. If you take a neutral look at it all these possibilities, it’s all gotta do with‘ layout’. So, keep it simple. I suggest if it needs to change: **The Layout Editor**. 158. Then we get two simple to understand terms: The BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. Editor and The Layout Editor. 159. ![](https://secure.gravatar.com/avatar/2fd9e571b4f17ef806dcff4014ffbfd46969ac837d5e23afe4837c6c8160b242? s=32&d=mm&r=g) 160. [Dozent.IS](https://profiles.wordpress.org/istag/) 6:30 am _on_ July 28, 2022 161. keep it simple, just: Content Editor and Layout Editor 162. and please keep away “theme blocks” from the page/post editor by default. It irritates ordinary users 163. * ![](https://secure.gravatar.com/avatar/2002d4281b52a085b3248c89b21470d197453ff7c4a5a9f3bcbd7de72461881a? s=32&d=mm&r=g) * [SeReedMedia](https://profiles.wordpress.org/sereedmedia/) 5:20 pm _on_ July 28, 2022 * +1 - ![](https://secure.gravatar.com/avatar/790863ada241f12306b63fba9f7785598e8b3f5d8a0ece595f68e7af08795f6f? s=32&d=mm&r=g) - [SpaceDragon](https://profiles.wordpress.org/spacedragon/) 9:54 pm _on_ July 28, 2022 - +1 164. ![](https://secure.gravatar.com/avatar/61090e2ef100818915e2ddf9d3d756a3be609bf4acd4264d92b14fdce7ae4e79? s=32&d=mm&r=g) 165. [Jaakko Pöntinen](https://profiles.wordpress.org/jpontinen/) 7:07 am _on_ July 28, 2022 166. Ditch the marketing attempts and go with something that’ll last by default and is completely unmistakable. 167. WordPress editor. Not capital E or “the” in the name or anything. 168. As in “open the editor” or “go to the editor -> HeaderHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes.” or “Fire up the editor, select your element”. If there are several editors of X kind in an installation, adding “WP” as in “WP editor” will single out the editor that came with the platform. 169. WordPress is what it is, there’s **no need** to make a brand within a brand. No mess, no fuss. 170. Problem solved. 🙂 171. * ![](https://secure.gravatar.com/avatar/cd9a7555ea561ad91adc1f90096adfff945025baacc986b8736ca6ad9e02b710? s=32&d=mm&r=g) * [Christian Sabo](https://profiles.wordpress.org/pixelverbieger/) 12:15 pm _on_ July 28, 2022 * +1 * ![](https://secure.gravatar.com/avatar/f03c979ee6e36a4b7cbbe30f644f946afd7e68a097d5a334de15c344dea4e8fd? s=32&d=mm&r=g) * [sallijane](https://profiles.wordpress.org/sallijane/) 4:51 pm _on_ July 28, 2022 * well said 172. ![](https://secure.gravatar.com/avatar/f2a0b5b107f3f1fb92d80ba2fb361ffae8333b2f5d9e8bd463d11ca7f1651bda? s=32&d=mm&r=g) 173. [mgarfath](https://profiles.wordpress.org/mgarfath/) 8:13 am _on_ July 28, 2022 174. WP Theme Maker or WP Theme Editor or WP Site builder or WP Template Builder 175. ![](https://secure.gravatar.com/avatar/b2c2030eafe7334589e9f60a3a16dbeab3ac1e3fe0b91bb99e91680eb64a3888? s=32&d=mm&r=g) 176. [ridesirat](https://profiles.wordpress.org/ridesirat/) 9:18 am _on_ July 28, 2022 177. I understand the idea of changing the name but I think WP is already in a turbulent time, no extra noise needed. FSE is in everybody’s mouth. And for newcomers it’s ok, it’s just a term. It describes it well. For oldcomers, they are above that. Just let it be. For the stable future.. WPD or WPDesign 🙂 178. * ![](https://secure.gravatar.com/avatar/f03c979ee6e36a4b7cbbe30f644f946afd7e68a097d5a334de15c344dea4e8fd? s=32&d=mm&r=g) * [sallijane](https://profiles.wordpress.org/sallijane/) 4:52 pm _on_ July 28, 2022 * agreed 179. ![](https://secure.gravatar.com/avatar/4dd5bf4d50cac5b0d15877b0abda25831e4382d6203e9debdc9daf493af6c421? s=32&d=mm&r=g) 180. [Doug Wagner](https://profiles.wordpress.org/desigstate/) 12:24 pm _on_ July 28, 2022 181. Going back to this article [https://www.nngroup.com/articles/direct-vs-sequential-access/](https://www.nngroup.com/articles/direct-vs-sequential-access/) I would recommend considering a generic term like “ (WordPress version) Settings” for FSE since the term “settings” is what mobile interfaces like iPhone and web interfaces like Chrome use to provide direct access to make changes to all the apps. I imagine this terminology would feel familiar to new users and versions terminology for developers. (To me, “editor” has always implied the need for a set of coding skills and a cautious warning. In reality, you are changing the theme or pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. “settings”.) My thoughts on WordPress 6 Settings 🙂 182. * ![](https://secure.gravatar.com/avatar/f03c979ee6e36a4b7cbbe30f644f946afd7e68a097d5a334de15c344dea4e8fd? s=32&d=mm&r=g) * [sallijane](https://profiles.wordpress.org/sallijane/) 4:53 pm _on_ July 28, 2022 * no, settings does not feel right to me; sounds like it would be more about preferences than editing/designing a site 183. ![](https://secure.gravatar.com/avatar/c9bb7b7837b7e5f0fedd2f77aa02f750e618d66eb8ef8c0e401db02108e29e09? s=32&d=mm&r=g) 184. [faazweb](https://profiles.wordpress.org/faazweb/) 12:36 pm _on_ July 28, 2022 185. We can call it simply “WP Full Editor” (WpFE) which also conveying it’s purpose. 186. ![](https://secure.gravatar.com/avatar/85b415147e01ce70ba2930cd87c672cccb6c6427470454c833dcc293ca657df2? s=32&d=mm&r=g) 187. [thedezzie](https://profiles.wordpress.org/thedezzie/) 2:49 pm _on_ July 28, 2022 188. I want to express empathy for the challenge of re-naming things that affect institutional, technical, and cultural systems, and share some take-aways from my own experience doing this. Realizing that something has the wrong name, or has outgrown its name, and gathering consensus around a path forward it is harder than most technical or design problems I’ve worked on. I don’t think this is a problem exclusive to open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL., and I wonder if it might actually be an edge for the community. 189. Generally, I’ve grown to not be too worried about how changing names affect users, so long as it is communicated in a way that is clear, gives them a heads up about how it’ll affect them, and empowers them to prepare and adapt. People mostly want to be able to create, manage, and achieve their goals on their site without it breaking, or paying and waiting for someone else to help them do it. Leaning on the power of documentation and help docs to support the transition really helps, and communicating it in places that users, not just developers, hang out. Names stick, but we often forget that we’re spending a lot more time in the project than users. 190. It’s a different story if you change names towards something that sets unclear or misleading expectations about features, but in this situation here it seems like you’re actually rectifying some confusion and disagreements. Closed source site building platforms will pull drastic changes without the level of care and consideration I see on this community all the time, so overall I don’t think rolling out the change is something that’s standing in your way! 191. * ![](https://secure.gravatar.com/avatar/85b415147e01ce70ba2930cd87c672cccb6c6427470454c833dcc293ca657df2? s=32&d=mm&r=g) * [thedezzie](https://profiles.wordpress.org/thedezzie/) 2:59 pm _on_ July 28, 2022 * I think it’s a really thoughtful way to help broader users of the WordPress community to feel invested by encouraging them to participate. Strategically though, I would not to use a survey for this, because that method invites a lot of input that might be hard to verify as coming from the users that need representation the most. You will end up with even more decision paralysis, and you will weaken the strength of the contenders that have already been thrown around. * What might be a more fruitful exercise in figuring out what users expect to call things is something you can all figure out pretty quick–looking at other site builders, and how things converge and diverge into different features. As a longtime user of WordPress that now uses multiple building platforms today, I’ve expanded my concept of FSE and have observed that irrespective of things like market share, people who are building sites for the first time also have more expectations of how a set of features work together to help them create their site, and it sadly leads them to not choose WordPress. It’s less about the power of WordPress or how awesome all of you are 🙂 and more about the internet ecosystem in which they’ve come up, and their first experiences of creating and publishing stuff. * Personally though, I wouldn’t overshoot a name and not deliver what it implies– I’ve learned that the hard way before. * The more localized the feature, the more reversible the name, and the more deliberate names for the ways you refer to groups of features that are used in concert and interoperably across the app. It’s fine if features have similar names across apps and platforms. I think about it from the lens of aligning with web standards, internationalization, and giving users a way to pick up new tools faster. - ![](https://secure.gravatar.com/avatar/f03c979ee6e36a4b7cbbe30f644f946afd7e68a097d5a334de15c344dea4e8fd? s=32&d=mm&r=g) - [sallijane](https://profiles.wordpress.org/sallijane/) 4:56 pm _on_ July 28, 2022 - aligning with standards makes sense; some of them are WordPress standards, some of standards from around the ’Net. How to do both. . . . * ![](https://secure.gravatar.com/avatar/f03c979ee6e36a4b7cbbe30f644f946afd7e68a097d5a334de15c344dea4e8fd? s=32&d=mm&r=g) * [sallijane](https://profiles.wordpress.org/sallijane/) 4:54 pm _on_ July 28, 2022 * Thanks; good post; maybe ensuring that the documentation uses both old and new names for quite a while so people can learn is enough. 192. ![](https://secure.gravatar.com/avatar/89e470d01e796cd2a0c01bec6b71b8183a6a6a176513e740e3ee29894e60711a? s=32&d=mm&r=g) 193. [robglidden](https://profiles.wordpress.org/robglidden/) 5:53 pm _on_ July 28, 2022 194. — What other contexts do you think we need to be aware of as we look toward how to refer to our collective work in the future? 195. The who-will-share-what of the upcoming phase of collaborative editing. 196. Or “workflow” as Matt called it at WordCampWordCamp WordCamps are casual, locally- organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. [Learn more](https://central.wordcamp.org/about/). EU: 197. * real-time coediting, much like Google Docs * for editing pages, sites, templates, etc. * version controlversion control A version control system keeps track of the source code and revisions to the source code. WordPress uses Subversion (SVN) for version control, with Git mirrors for most repositories. for as much as possible to roll back mistakes and edits 198. Feels like a publish-then-fix workflow will need to give way to more built-in preview/staging/sharing “sites” and broader community user roles. 199. And use cases beyond just two persons editing a post. 200. ![](https://secure.gravatar.com/avatar/2002d4281b52a085b3248c89b21470d197453ff7c4a5a9f3bcbd7de72461881a? s=32&d=mm&r=g) 201. [SeReedMedia](https://profiles.wordpress.org/sereedmedia/) 6:36 pm _on_ July 28, 2022 202. **1. We’ve referred to it this way for a long time. How can we tackle renaming this together?** 203. If we make the Official Names match the general/commonly adopted nomenclature, fit within the language of describing how the features are used, and provide consistent labeling within the UIUI User interface and documentation, then adoption will be natural. 204. **2. It’s in the codebase. How will we make sure people who aren’t regular contributors see this?** 205. I think the language in the UI is of the utmost importance to adoption, and I recently shared some related thoughts on the language in FSE/ GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/)/ Query BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. here: [https://github.com/WordPress/gutenberg/issues/31158#issuecomment-1191875000](https://github.com/WordPress/gutenberg/issues/31158#issuecomment-1191875000) 206. Some of the same sentiments apply here. Specifically:_ If the goal of FSE is to be useable for non-dev users, then the language needs to reflect that._ 207. The terms should be consistent across the project, for all audiences. 208. **3. And repeating the in-line question from above: What other contexts do you think we need to be aware of as we look toward how to refer to our collective work in the future?** 209. IMO part of the nomenclature problem within WordPress is that it has been done bit-by-bit as the features have expanded. Two major exceptions: There is a clear theme in naming each release (Jazz greats), and Gutenberg clearly invokes the printing press and its revolutionary impact. 210. But within the tools of the site, we are all over the place. This has roots in the dotcom-dotorg feature disparity, as well as spill-over from the developer- focused practice of code-naming features that are in development (i.e. Gutenberg, apparently). 211. There are many great comments on this post about keeping it simple and not rocking the boat with a new name. I agree with most of those, because calling something what it is (i.e. calling the area where you edit the layout of the site either the “Site Editor” or the “Layout Designer” or even the “Site Layout Designer”) removes a layer of abstraction, and anything that does that makes it one layer closer to intuitive for the user. (“How do I edit the layout of this site? Hmm, maybe I use the Site Layout Editor”) 212. However it ends up happening (and I’d love a clearer process outline for that), I propose that we do not just rename or not rename FSE and go about our business. We need to standardize the names for these various components, as was done to some degree with the Theme CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. (ten years ago!!), and define them in terms of their functions and their relationship to each other. 213. It’d be ideal to get to a point where we could make a chart that resembles the theme template hierarchy of yore ([https://developer.wordpress.org/themes/basics/template-hierarchy/](https://developer.wordpress.org/themes/basics/template-hierarchy/)), that would serve as both as a glossary and as a general benchmark of the skills that one needs to operate at each level. Sort of like a “you must be this tall to ride” warning on a roller coaster, but “you should have these skills to work in template parts). It could tie in with LearnWP’s efforts toward standardization as well, for example, including links from inside the template editor to Learn resources about that feature. 214. Those are #Goals. In the meantime, we still have a language problem. Some of the terms we need consider/standardize/define (again, not just a glossary definition, but especially *in relationship to one another*): 215. > Block and its variants > * CoreCore Core is the set of software required to run WordPress. The Core > Development Team builds WordPress. Block > * PluginPlugin A plugin is a piece of software containing a group of functions > that can be added to a WordPress website. They can extend functionality > or add new features to your WordPress websites. WordPress plugins are written > in the PHP programming language and integrate seamlessly with WordPress. > These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) > or can be cost-based plugin from a third-party. Block > * Theme Block > Block editor > Block Finder (for lack of a better term, i.e. the place where > you search for new blocks) Block inserter Block panel Builder Content Customizer( > or what is the FSE equivalent even just from a 301 redirect perspective) HeaderHeader > The header of your site is typically the first thing people will experience. > The masthead or header art located across the top of your page is part of the > look and feel of your website. It can influence a visitor’s opinion about your > content and you/ your organization’s brand. It may also look different on different > screen sizes. Header Block Heading Editor Footer Full Site Editing (verb) Full > Site Editor (noun) List View (or The List? SidebarSidebar A sidebar in WordPress > is referred to a widget-ready area used by WordPress themes to display information > that is not a part of the main content. It is not always a vertical column > on the side. It can be a horizontal rectangle below or above the content area, > footer, header, or any where in the theme.? Panel? Is there another View anywhere?) > Nav Block Navigation/Menus Page Editor (Is this the list of the site’s pages > or the actual page you are editing? And if it’s the page you’re editing, what > do you call the list of pages) Patterns Pattern Editor Pattern Finder (?) Post > Editor (same questions as pages, but posts 🙂 ) Theme Theme Editor Theme Finder(?) > Template Template part Site editor 216. There are more, this is just off the top of my head. 217. **TL;DR Across the project the terminology for new and legacy features and elements needs to be standardized, with a strong emphasis on how those features and elements are used and how they relate to one another.** 218. It’s all connected: [https://www.youtube.com/watch?v=f5FxRGhUv30](https://www.youtube.com/watch?v=f5FxRGhUv30) 219. * ![](https://secure.gravatar.com/avatar/2002d4281b52a085b3248c89b21470d197453ff7c4a5a9f3bcbd7de72461881a? s=32&d=mm&r=g) * [SeReedMedia](https://profiles.wordpress.org/sereedmedia/) 12:23 am _on_ July 30, 2022 * I just want to draw attention to the fact that in the new homepage redesign that is happening over here: [](https://make.wordpress.org/design/2022/07/27/project-update-wordpress-org-homepage-and-download-page-mockups/) [https://make.wordpress.org/design/2022/07/27/project-update-wordpress-org-homepage-and-download-page-mockups/](https://make.wordpress.org/design/2022/07/27/project-update-wordpress-org-homepage-and-download-page-mockups/) * … the design team has used the WordPress Editor as a key marketing message in the first section of the new website. * > It’s not magic, it’s the WordPress Editor. - ![](https://secure.gravatar.com/avatar/89e470d01e796cd2a0c01bec6b71b8183a6a6a176513e740e3ee29894e60711a? s=32&d=mm&r=g) - [robglidden](https://profiles.wordpress.org/robglidden/) 12:50 am _on_ July 30, 2022 - So much clearer than “It’s not magic, it’s Full Site Editing”. 220. ![](https://secure.gravatar.com/avatar/eb8a100b34072d5a5ba15cb247f8f55f56cf228b60e71d74303a4e6f6a0b081d? s=32&d=mm&r=g) 221. [Hauwa Abashiya](https://profiles.wordpress.org/azhiyadev/) 6:59 pm _on_ July 28, 2022 222. > I kind of like the term “Full Site Editing”. For new users in WordPress, it > implies that they will be able to edit their entire site, which is true. 223. Likewise and if we are looking for simplicity we can go with just Site Editor as that is easier to translate. 224. Equally, I would be interested to see what users call it and make a decision based on that. 225. > First thought, why don’t we ask the average user via a carefully crafted survey > in the Dashboard? How do THEY refer to editing their websites? 226. ![](https://secure.gravatar.com/avatar/d856f6ca8fa8d89f4b9d2f36c43c31f04b1a230e6a27ba7c700565ca1a7582cf? s=32&d=mm&r=g) 227. [Danny Cohen](https://profiles.wordpress.org/nebagakid/) 8:08 pm _on_ July 28, 2022 228. “Site Builder” 229. ![](https://secure.gravatar.com/avatar/0bf120fefff8e58b58bc56e223a6f6ac252104fa32caa3dfddd25523315e0643? s=32&d=mm&r=g) 230. [Viktor Nagornyy](https://profiles.wordpress.org/viktorix/) 3:23 am _on_ July 29, 2022 231. Since the main reason for GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/) was to help WordPress.comWordPress.com An online implementation of WordPress code that lets you immediately access a new WordPress environment to publish your content. WordPress.com is a private company owned by Automattic that hosts the largest multisite in the world. This is arguably the best place to start blogging if you have never touched WordPress before. [https://wordpress.com/](https://wordpress.com/) compete with Wix, Weebly, and others, it’s only right to complete the circle and call it what Wix, Weebly, etc. are – website builders. 232. ![](https://secure.gravatar.com/avatar/1bd692736861bd20949789e4a3d922736480efcacb0e44041616c5a79eaa54c0? s=32&d=mm&r=g) 233. [Darren Ethier (nerrad)](https://profiles.wordpress.org/nerrad/) 4:21 pm _on_ July 29, 2022 234. One thing I think needs considered with any improvement on naming this (which I am glad to see) is both what “FSE” has been used to describe now, and what is being worked towards. Essentially, the primary distinguishing feature for what has been called “full site editing” is _how the site and its content is edited_. Doing any significant customization or personalization of WordPress used to involve a number of disparate interfaces (including writing code) and we’re moving towards a _single coherent interface for designing your site via a no-code visual canvas_. 235. So whatever name we choose, I think it would be wise to land on something that captures the distinctiveness, and power behind what this enables for the user. 236. ![](https://secure.gravatar.com/avatar/6ddc525ae47cdce6c4d632d40ad0ebdfa590fdb36dfca0c85a4cbd5cccaf5351? s=32&d=mm&r=g) 237. [Fernando Tellado](https://profiles.wordpress.org/fernandot/) 10:50 pm _on_ July 29, 2022 238. IMHO I think that we could use a term already used in WordPress that serves for the same purpose with all themes: Theme CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. 239. Is a good name because: 240. * It’s a smooth transition from actual customizer for users * When an user changes from a no blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. theme to a block theme the change in the UIUI User interface is minimal while maintaining the meaning of the tool, from a simple customizer to the REAL theme customizer * The name is self explanatory and make use of terminology already known by end users and devs. The real change is internal but it don’t need to be moved to final users * When translated to other locales the typo changes are minimal. In Spanish would be from Personalizador to Personalizador de temas and would be easy to understand for users the significance of the change 241. 🙂 242. ![](https://secure.gravatar.com/avatar/89e470d01e796cd2a0c01bec6b71b8183a6a6a176513e740e3ee29894e60711a? s=32&d=mm&r=g) 243. [robglidden](https://profiles.wordpress.org/robglidden/) 12:07 am _on_ July 30, 2022 244. So far, the new but overnamed “full site editing” is just template editing (plus related stuff). It is awesome, I am very grateful for it, and I’m sure not going back. 245. But what we now think of as “site editing” will hopefully soon broaden substantially with the collaborative (or workflow) editing and multilingual stages soon upon us. 246. Real-time coediting of pages, sites and templates with version controlversion control A version control system keeps track of the source code and revisions to the source code. WordPress uses Subversion (SVN) for version control, with Git mirrors for most repositories. for it all, ultimately enabling even multilingual sites, will push today’s publish-then-fix workflow. 247. A “site” may well evolve into multiple collections of different versions of posts, pages, sites, and templates, each used for a different purpose by a different community. 248. From a user perspective, I think this will be much simpler and more natural and intuitive than it may sound. 249. And I hope these phases will empower new community editing uses. 250. That’s why I hope that rather than begetting more concern of unsettling change with broad metanames, the next phases stick to simpler, user-benefit-based naming. 251. * Multilingual website? I get it, just pick a different language. * Preview site with updated theme? Doesn’t sound overwhelming. * Share site subset with community members? Sounds as easy as Google doc sharing. 252. ![](https://secure.gravatar.com/avatar/33212bff2915bd72792772a2d3203abe0402352b6be6ba65081036f10560c6e6? s=32&d=mm&r=g) 253. [justlevine](https://profiles.wordpress.org/justlevine/) 11:48 pm _on_ July 30, 2022 254. I love the thought that’s gone into all the above comments and analyses, but here’s a probably radical idea. 255. What if instead of focusing on what parts of the site it can edit, or the underlying solution it implements, we referred to it by the value it offers to the user over whatever classic editing flows it’s replacing: the `Live Editor` 256. “The Live Editor allows users to make changes to their WordPress site, while previewing the changes in real time.” 257. Posts and pages and cpts can be edited in the Live Editor. WP recently added headers, footers, archives, and other template parts to the Live Editor. Basic nav menus can be built in the Live Editor, and they’re adding additional functionality every release. Even widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget- ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. content can be changed in the Live Editor! 258. * ![](https://secure.gravatar.com/avatar/46e579e5809af6c797613c207eb35f9b2ef06b2008e48c03e63e6d801ad048d6? s=32&d=mm&r=g) * [marybaum](https://profiles.wordpress.org/marybaum/) 1:10 pm _on_ August 3, 2022 * Oh wow. I like this approach a lot! Only, the Copy Commando in me would say,“ The Live Editor lets you make changes to your WordPress site and see the results in real time.” “In the Live Editor, you can: • Add and edit posts and pages• Build your design, including the headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes., footer, archives and other template parts • Add, fill, and edit widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. areas And more — even include common web functionality like event bookings and shopping!” 259. ![](https://secure.gravatar.com/avatar/ea5cf1a9df9bcd651321908528303a454c328977ac49b83465c61e850f4132b4? s=32&d=mm&r=g) 260. [Pieterjan Deneys](https://profiles.wordpress.org/nekojonez/) 1:34 pm _on_ August 3, 2022 261. Input from polyglot here… FSE is already backed in so many strings … So, apart from having all the translations needing to have an update, the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress. org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. & theme devs should get a notification about this so they can update their stuff as well. 262. Also, there are several articles & video’s now about FSE online… So, we need to have clear communication about this when changing. 263. But, I think that’s going to be not big of a problem when looking to all the comment already. These are just my two cents as a polyglot. 264. ![](https://secure.gravatar.com/avatar/a41989db8d0c06420b5042c3b3e10ddd496b0a9584897d1042499ebd6e467e6d? s=32&d=mm&r=g) 265. [DeveloperWil](https://profiles.wordpress.org/developerwil/) 2:10 am _on_ August 4, 2022 266. No particularly interested in what it’s called. More interested in how it makes WordPress easier to use and more accessible. Let’s call it “Kevin”. 267. * ![](https://secure.gravatar.com/avatar/1ccfcb1daa6c0b064e043799302012690fa5cfd4301d6e50bc08f2795cebe87b? s=32&d=mm&r=g) * [Gal Baras](https://profiles.wordpress.org/galbaras/) 6:28 am _on_ August 4, 2022 * Why not rename both blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editors “Block Page Editor” and“ Block Theme Editor”? That’s clear, descriptive and true. * But if we do go with “Kevin” for FSE, surely the post editor should be either“ Stuart”, or “Bob”. 268. ![](https://secure.gravatar.com/avatar/a7873a730eebbbf667e941eaefba2f3f16ee7fe49a5661507569ada7f46b94dc? s=32&d=mm&r=g) 269. [Birgit Pauli-Haack](https://profiles.wordpress.org/bph/) 11:44 am _on_ August 5, 2022 270. When the topic first came up, I wasn’t thrilled by the outlook to update lots of post, documentation etc, after discussing and writing about Full-Site Editing for over 2.5 years. I do must admit, it’s more the resistance to let go of something I am used to, then a good reason to not try for a more user-friendly name. 271. Considering, thoughts from polyglots teamPolyglots Team Polyglots Team is a group of multilingual translators who work on translating plugins, themes, documentation, and front-facing marketing copy. [https://make.wordpress.org/polyglots/teams/](https://make.wordpress.org/polyglots/teams/) members who feel it doesn’t translate well into other languages, and that they already started shortening it to something like site editor or layout editor, having the English name follow suit would be beneficial. 272. Personally, I would favor a name that ends in ‘designer’ rather than editor, ie: Layout designer, or Site designer. Template creation and modification need more a designer’s head, rather than an editor’s pencil. 273. ![](https://secure.gravatar.com/avatar/6845456dbc9056f20a4cd50a6b95db78f2ae31df5c0601c613ee5b8939c41a82? s=32&d=mm&r=g) 274. [Jon Brown](https://profiles.wordpress.org/jb510/) 1:24 pm _on_ August 11, 2022 275. I don’t see a strong reason to change it this late in the game. But if it were to change names, then I’d favor Template Editor which seems to me the most semantically accurate. 276. ![](https://secure.gravatar.com/avatar/53eb4d72178944e9bf5ae3f3b73b21ec5169628cff2c0b73cc655ce422967c40? s=32&d=mm&r=g) 277. [Alex Avalos](https://profiles.wordpress.org/alexavalos/) 9:25 pm _on_ August 23, 2022 278. It seems to me that Full Site Editing describes very well what a FSE theme does inside WordPress, because we have a blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor with which we can create content and some themes that from the customizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. include options to use blocks in specific places of the site such as the footer, headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes., etc. 279. But with the FSE we have a theme that allows us to build the entire site to pure blocks with a different interface to the customizer, where we build the structure of our entire site, what it will look like and how it will look on our website once it is published. For me it makes all the sense in the world: Full Site Editing. 280. Maybe, later when the current themes are the Legacy Themes it could be called: general structure or something like that… but for now FSE should stay. Comments are closed. # Post navigation [← Dev chat agenda, July 27, 2022](https://make.wordpress.org/core/2022/07/27/devchat-agenda-july-27-2022/) [Editor chat summary: 27 July 2022 →](https://make.wordpress.org/core/2022/07/27/editor-chat-summary-27-july-2022/)