6.3 Live Product Demo Q&A

Honoring a WordPress tradition, this post will recap the question-and-answer segment of the 6.3 Live Product Demo.

6.3 release squad members, Anne McCarthy and Rich Tabor, prepared a live product demonstration, moderated by Nathan Wrigley, to highlight aspects of this monumental release. You can read some of the highlights or watch the recording below.

6.3 Live Product Demo

The panelists answered a number of questions for attendees.

Q1: It felt like Phase 2 went on longer than expected, producing ongoing quality-of-life improvements to the Site Editor. It’s been, in a word, wonderful. While I’m excited for Phase 3 and what lies ahead, is it possible Phase 2 aspects will continue to be revisited and refined concurrently with Phase 3, or is this expect to be a more thorough wind-down — meaning the Site Editor in 6.3 is roughly where it is expected to be going forward?

A1: There’s more to come, and the work isn’t over. Check out this overview GitHub issue here for what’s already planned for iteration.

Q2: Can you assign Patterns to Categories?

A2: Not yet. More info here for anyone interested in the details within this GitHub issue.

Q3: But there are no revisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. at the style book, or did I miss this?

A3: The revisions show changes for all of styles, including changes made when viewing the style book.

Q4: Is this doc you created accessible? The one with the different uses for the Reusable Blocks, Patterns, etc?

A4: For more information, read the overview on comparing patterns template parts, and reusable blocks (now synced patterns.)

Q5: For classic themes, will it be possible to access the pattern editor? Either directly or indirectly?

A5: Classic themes can create patterns, and the reusable 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. management screen is reused to store them. More info on the Patterns section, specifically in the Site Editor being exposed for Classic Themes here in this GitHub issue. Great spot to share feedback!

Q6: There are no revisions in the style book, or did I miss this?

A6: The revisions show changes for all of styles, including changes made when viewing the style book.

Q7: Are footnotes finalized, and will they be released in WP 6.3?

A7: Yes, they will.

Q8: Do we have any rough ideas of previewing a theme, working on it, saving that, but NOT activating or scheduling when it goes live

A8: Some rough ideas here from prior design efforts.

Q9: From my testing, I found that you don’t need to highlight anything to add a footnote number, just place the cursor behind the word where the footnote numbrt should go… Is that a hidden feature or a bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority.?

A9: It’s a feature! Though I find selecting more intuitive.

Q10: Is there any option to apply global styles (theme.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. variations) to different templates separately? btw new aspect ratio input is cool!

A10: Not yet, but on the radar. I’d love to be able to apply variations to templates, even patterns. Calling them Theme.json Partials (partially applied theme.json). 

Q11: With 6.3, CSSCSS Cascading Style Sheets. Grids come to query builder. But what is the plan for CSS grids in the group block (Row, Stack, and Grid)? And will it be a full implementation or a limited one (as the current limited Flexbox implementation in Row features)?

A11: Here is some additional info on layout updates in the editor.

Q12: Is there any information about the possibility of applying multiple block styles to blocks? Also info about block styles to be applied just to block variation, not the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. block? Struggling with creating styles and variations.

A12: Not multiple block styles, but you can design a block variation within the Style Book.

Q13: Is there any news regarding native multilingual support in Core?

A13: Not quite as multilingual support is slated for Phase 4 on the WordPress roadmap.

Q14: Regarding the rollback of failed manual plugins and theme updates. This will happen even if the updates break and make the website fails with a fatal error like some kind of recovery mode.

A14: For more information on failed manual 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/ or can be cost-based plugin from a third-party and theme updates, check out this Core post.

Additional references mentioned during the live product demo

#6-3, #live-product-demo