Facilitated by @kjellr
Gutenberg 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/ + Themes Updates
- 10.0.0 was just released
- If you’ve defined
customTemplates as noted in this PR.
- Gutenberg will now enqueue the comments reply script automatically when the comments block 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. is used.
- The Query block should now properly interpret the global query when used on single pages.
- Here is a PR that lets folks try a hybrid template hierarchy — using both HTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites. and PHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. http://php.net/manual/en/intro-whatis.php. templates.
Discussion: Bridging the gap between traditional themes and block themes
A healthy discussion ensued about how to transition between traditional / classic themes and block themes. You can read the full discussion starting here.
- Hybrid Themes
- Ari and other folks have been discussing how template hierarchy could involve both block-based and PHP templates. There’s a PR to try out a similar idea.
- @pbking had discussed the idea of pulling blocks into standard templates, and now has a PR here, as well as a Gutenberg issue filed.
- “The templating system and using a mix of PHP & HTML files is easy on the frontend… The problem is mostly focused around the “what happens in the editor if A/B/C” questions.”
- Blocks can be used in traditional templates with
echo do_blocks( '<!-- wp:post-title /-->' ); or
echo do_blocks( file_get_contents( 'block-templates/page.html' ) ); — this could make it easier for theme developers to convert their PHP templates to block templates while keeping their same templating structure.
- Global Styles Now
- It seems like themers should want to use theme.json / global styles without changing any of their templates. How do we give users access to the global styles, without forcing them to be using a completely FSE Short for Full Site Editing, a project for the Gutenberg plugin and the editor where a full page layout is created using only blocks. ready theme?
- “Finding the perfect place/UI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. for it may be hard, but I think it’s very important to have GS be somehow decoupled from FSE”
- “If a theme has a
theme.json file then yes,I think we should hide the customizer 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. link and instead point them to the global-styles UI (wherever that may be). Having 2 interfaces to edit styles would be confusing.”
Are you interested in helping out with the future of themes? We need folks to lead this meeting and help compile weekly updates, reach out to @kjellr if you’re interested!