Matias Ventura 9:10 am on January 26, 2022
Tags: 6.0 ( 76 ), gutenberg ( 475 ), gutenberg-next ( 23 ), release-roadmap ( 6 )

Preliminary Roadmap for 6.0 (Gutenberg Phase 2)

Yesterday, WordPress 5.9 Joséphine was released with the help of hundreds of contributors and achieving a big milestone for WordPress. It’s now time to start thinking about next steps and the general scope for 6.0. As before, this is meant to be a high level overview of the different areas of focus, not an exhaustive list.

The overall aim is to consolidate and expand the set of customization tools introduced in 5.9 for creating themes with blocks, with a special focus towards usability and refinement. This new release could be considered a conceptual wrap 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/: Phase 2. This doesn’t mean the customization phase would be concluded with it, but that its main features would have been established.

Tracking Issue to follow →

Editor

The introduction of the site editor marked a big milestone but also just a first step in the journey. There are various limitations that need to be lifted and features that didn’t make the cut that need to be revisited. We are also going to be learning a tremendous amount from users now that the initial work is out in the world to be experienced.

Refine the information architecture and template browsing experience. There’s work to be done to better organize the experience of interacting with the site editor, global styles, templates, and navigation as a whole. (36667)
Improve template creation (aiming at never showing disconcerting empty states) and allow the easy creation of more specific templates (i.e: category-$slug). The selection of new templates is artificially constrained right now in the interface. Opening that up should better express the power of the site editor as a web creation tool. (37407)
Expose site structure as “navigation” outside the navigation 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.. This is an important aspect to not limit site navigation editing exclusively to the site canvas, which for many reasons can be initially hidden from view. (36667)
Introduce browse mode to be able to conveniently follow links to different parts of the site. Conversely, the template editor that spawns when editing posts or pages also needs to establish better flows with the site editor. There’s a larger theme of connecting pages and templates to be explored. (23328)
Embrace style alternates driven by 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. This was teased in various videos around the new default theme and should be fully unveiled and presented in 6.0. One of the parallel goals is to create a few distinct variations of TT2 made just with styles. (35619)
Improve post settings design and organization. The 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. has gone without many updates for a while and could use improvements in clarity and design.
Complete the scope of global styles. Introduce easy export & import; support for 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.; etc. (27941)
Remove coupling of templates to specific themes. This is crucial for properly embracing the power of block templates. Switching themes should not cause the disappearance of your modified templates. This is also fundamental for offering more granular combinations instead of complete theme swaps, the ability to add new set of templates (relevant for plugins that introduce new templates), or changing individual parts of a site. (See also.)
Explore more advanced drafting and scheduling for the site editor. Some of this work is meant to happen more in depth during Phase 3, which will include more focus on editorial flows, but there’s still some paving steps to implement. (29575, 29388, 31456)
There should also be some room for some minor back to basics around the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. writing experience and further improvements to performance and usability. Areas to keep an eye on are the reliability of undo/redo, keyboard interactions, multi-selection, etc.

Patterns

It’s also time to expand the usability of patterns as a main ingredient when it comes to building pages and sites, now that most of the infrastructure has been established.

Prioritize pattern insertion on template building. This is a proposal to make patterns more central to the experience of creating theme templates and pages. (31153)
Simplify registration of patterns for themes. This might take the shape of a patterns folder with file headers that are automatically registered. All in all, it should be super easy for themes to provide a collection of patterns or to specify starter content as patterns. (36751)
Introduce page patterns for page creation. This has been on the horizon for a while and we should have enough building blocks to tackle it properly. It’s also an occasion to improve upon and align with the new “explore” modal that connects with the patterns directory.
Use patterns as possible transforms for offering “layout” options. Inserting new patterns is just a start, but often you want to change existing content or shapes into new ones. Patterns have some of those mechanisms but they need to be better presented and embraced. (27575)

Blocks

Finalize scope of navigation block and its overlay rendering. The navigation block introduced in 5.9 contains a whole world of customization and opportunities that needs to continue to expand and improve. In addition to the block itself, several flows need to be refined around transporting and initializing block menu data.
Introduce various new blocks to power the display of comments on themes. (34994, 38107)
Allow the featured imageFeatured image A featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts. to be an attribute of other blocks (like Cover, Media & Text, etc) to expand what designs can be achieved.
Allow Quotes and Lists to have child blocks. Some of the current limitations of the writing experience arise from this constraint. (25892)
Improve the Table block. There’s a good design direction to finally implement. (32400)
Explore the viability of inline tokens. This has come up repeatedly in the context of rendering dynamic strings (such as current date) in rich text blocks.
Migrate default block styles into proper style attributes. Continue the work put into global styles by making all systems understand each other.
Pick up the work done for a Table of Contents block.

Design Tools (33447)

A lot of progress was made in 5.9 around consolidating the set of design tools and introducing new ones to address major gaps in the experience and providing block authors with simpler ways to register them. For 6.0 there’d be a concerted effort around tightening consistency, introducing more responsive capabilities, and expanding the Supports & Elements APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways.. Another important goal is to continue to make it easier for third-party blocks to adopt these tools.

Layout:
- Address confusions and shortcomings of layout features (including mindbenders like “inherit layout”). (28356)
- Explore more convenient direct manipulation for height and width (alignment distribution) of blocks.
- Incorporate more definitive responsive handling (min/max containers) into the current flex-based tools. (34641)

Typography:
- Introduce responsive fonts with good defaults. (33543)
- Add a Web Fonts API connected with global styles. (37140)
- Explore paragraphs with indents and justification with hyphenation as global styles settings.

Elements:
- Introduce support for customizing block Captions.
- Investigate hover / focus effects and related problems.

Gradual Adoption

Full block themes are at the avant-garde of the WordPress evolution, but work continues to happen to improve how all themes can interact with blocks and make use of the new tools gradually and at their own pace.

Continue to adopt theme.json configuration for non-block themes as it aims to simplify and consolidate support for block properties and their capabilities.
With the “focused template part” editor established there are new opportunities for non-block themes to start incorporating specific areas for blocks using the site editor interface in a more gradual way, when ready to do so. (37943)
Utilize what we have implemented for the navigation block and site structure as the interface to eventually replace the navigation screen.
Explore the flows for creating some dynamic templates with blocks (for example, just the archive), similar to the custom page templates support in classic themes.

Please, help define the work to be done by joining the conversations listed in the issues above or giving feedback!

#6-0, #gutenberg, #gutenberg-next, #release-roadmap

Jessica Lyschik 10:59 am on January 26, 2022

Are there any plans to improve the available settings for the query loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. 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., for example allowing to exclude categories, tags, authors; selecting a single (or multiple) post(s) based on ID/title? There are so many possible parameters for the WP_Query function which the query loop block can‘t handle yet. I believe this would improve the adaption of FSE if there were more settings available.
- Carlos Bravo 12:03 pm on January 26, 2022
  
  Hi! I don’t know if there is a plan, but in this Github link there are a few improvements already done on the LoopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. 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. of 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/ 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.
  
  The first ones are adding custom taxonomies filtering and multiple authors support, for example, so I guess those updates will be in future releases.
  - Dozentis 11:33 am on January 27, 2022
    
    If you are involved there, could you add wp_query_random_post as feature requestfeature request A feature request should generally begin the process in the ideas forum, on a mailing list, as a plugin, or brought to the attention of the core team, such as through scope meetings held for each major release. Unsolicited tickets of this variety are typically, therefore, discouraged.?
- Matias Ventura 3:08 pm on January 26, 2022
  
  Yes! An updated project tracking issue for the query loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. should be ready soon.
  - Sallie Goetsch 7:03 pm on January 26, 2022
    
    So glad to hear that. Without proper tax queries and metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. queries, it’s really lacking vs PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher templates.
- Ulrich 5:19 pm on January 26, 2022
  
  Yes, I would interested in allowing developers to easily extend the query loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. 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. where needed. #38163
  - Sofia 9:48 am on February 23, 2022
    
    thanks Ulrich! this is a good start 🙂
    
    There is also a similar problem. Many times we need multiple WP_Query for one loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop.,
    
    For example in a list of people you want to have a CEO first, then 4 CTOs and then some managers and then employees. they needed four WP_Query and we merged them into a list.
    
    it is not currently possible to use multiple Query for one loop.
    
    I think you need a more functional solution. somehow bring all WP_Query and filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. the loop with whatever you need ?
    
    it would be great if we could do that!!
    
    thank you very much!!!
Nick Diego 12:51 pm on January 26, 2022

@matveb I would love to see an audit of all coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 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. controls for 6.0 and I am personally happy to work on this. For example, dimension and color support is inconsistent across blocks and some block simply haven’t been updated with newer supports. If this is something worth considering, I will put together a proposal on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/.
- Héctor Prieto 2:57 pm on January 26, 2022
  
  If I’m not mistaken, @karmatosed started working on a similar audit. I would love to see this effort consolidated in GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ to have a better overview and tracking as we add more 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. supports and design tools. It would greatly help us decide what controls make sense to be added to which blocks.
  - Tammie Lister 3:01 pm on January 26, 2022
    
    Hello! I did and I got it to a point where shared with docs team and in process of starting to see where that goes from there. I had made some issues from it, but more need making.
    
    I would love to see how we could collaborate together on things like this and even automate because the path I was taking was much more longer because of hand curating. Let’s plan together @ndiego. Thanks for connecting us @priethor.
    - Nick Diego 3:04 pm on January 26, 2022
      
      Absolutely, would love to.
- Matias Ventura 3:10 pm on January 26, 2022
  
  Indeed, that’d be a part of the work. We should ensure we are consolidating on what makes the most sense, though. That’s why a lot of work was put into more flexibility of design tool panels, so that a paragraph doesn’t become overwhelming with options.
  - Tammie Lister 3:14 pm on January 26, 2022
    
    +1 it’s easy to think everything needs all the things, however sometimes it only needs those rarely, it also might need to be combined with other things more, so those things should have them. It’s a balance.
Daniele Scasciafratte 2:47 pm on January 26, 2022

There are plans outside 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/? this post is talking about 6.0 for gutenberg or just plans for wordpress in 6.0?
- Matias Ventura 6:45 pm on January 26, 2022
  
  Since the main focus of the WordPress project right now are the 4 phases of 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/, the roadmap would overlap almost entirely. There’s some other ongoing work in other parts of the projects that is still prioritized by component maintainers. Those are generally on tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. and would be reflected once a squad is arranged for the 6.0 release.
Milana Cap 4:06 pm on January 26, 2022

Coming from #docs team and asking for some love for this teenager: https://core.trac.wordpress.org/ticket/4328

We need it for being able to redirect CPTs that WordPress documentation lives on. We have big plans in re-structuring docs but not being able to redirect it properly is a blockerblocker A bug which is so severe that it blocks a release. for a long time.

For more info see: https://meta.trac.wordpress.org/ticket/5519

I know it’s not attractive but we really need it. Thank you ❤️
Ulrich 5:21 pm on January 26, 2022

With the changes to the Quote 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., it might be good to look at #34454 too.
Ulrich 5:35 pm on January 26, 2022

Are there any plans to update the roadmap or publish a new release calendar for 2022 and 2023 like done previously.

@chanthaboune
- Josepha 6:54 pm on January 26, 2022
  
  Yes indeed! It’s on my list 🙂
  - Ulrich 6:55 pm on January 26, 2022
    
    Great 😀
Sallie Goetsch 6:38 pm on January 26, 2022

Looking forward to all of this, but the green in that button vibrates so much it’s about to trigger a migraine for me.
- Matias Ventura 6:47 pm on January 26, 2022
  
  Sorry! I brought it down a little.
Aurooba Ahmed 6:55 pm on January 26, 2022

I would really really love to see Custom CSSCSS Cascading Style Sheets. come to Global Styles in 6.0, as per this ticketticket Created for both bug reports and feature development on the bug tracker.: #30142. This aspect of 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. was heavily used by many people, and opens up the ability to easily add some customization to 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 in a powerful and low-code way. I personally do not have the experience and know-how (yet) to make this happen, but I would really really love to support the work on this anyway I can.
- Matias Ventura 8:39 pm on January 26, 2022
  
  Good thought! We had an exploration for the group 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. that could be repurposed in 25413.
westcoastdigital 4:47 am on January 27, 2022

As the focus for WP shifts to blocks and patterns, is there any plans to remove support for classic editor?
pmmueller 1:07 pm on January 27, 2022

Just an idea about the menu “Appearance > Editor 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.”:

Simply “Editor” is plain confusing.

It used to be called “Site Editor”, and even in this post Matias uses that term. I can understand that Site Editor is not the name of the menu as it’s about templates and global styles too.

How about “Theme Editor”?

Everything you do in there influences some aspect of a theme, doesn’t it?
- James Koster 12:26 pm on February 3, 2022
  
  Everything you do in there influences some aspect of a theme, doesn’t it?
  
  The functionality therein is not restricted to theme aspects, though. As of 5.9 you are already able edit the content of your home page, and in future updates other entries will likely become editable as well.
Miroslav Glavić 4:11 pm on January 27, 2022

I would really love to see an option in the settings to turn off updates, without having to use a 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. CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., themes, plugins.
cinza 9:01 pm on January 27, 2022

IMO the Layout part isn’t getting the attention it deserves. Site editor is good and all but you can’t really use it properly if there is no responsive settings for the columns/groups. I know there is an ongoing progress with the Flex 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. but I’m afraid it’s going to turn into the new Row block where you either have to pick vertical or horizontal but no proper wrapping based on child size.
Kingsley Felix 6:09 am on January 28, 2022

What about the IMPORT TOOL? when will that be updated? humanmade or 10up did a 2.0 that is far better when will that be adopted?
Jonny Harris 9:09 pm on January 28, 2022

No mention of the navigation editor. It was bumped from 5.9 but I thought we were working on it in 6.0?
- Andrei Draganescu 2:29 pm on February 3, 2022
  
  Hi! It is mentioned under Gradual adoption “Utilize what we have implemented for the navigation 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 site structure as the interface to eventually replace the navigation screen.”
TWD 2:28 am on February 3, 2022

I don’t know what the correct protocol is for making feature requests, but here goes.

I’ve lost count of the times when a 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 update has failed midstream for some reason (e.g. a 504 timeout) and I’m left with a site stuck in “maintenance” mode.
It’s no big deal for me to go in via FTPFTP FTP is an acronym for File Transfer Protocol which is a way of moving computer files from one computer to another via the Internet. You can use software, known as a FTP client, to upload files to a server for a WordPress website. https://codex.wordpress.org/FTP_Clients. and delete the “.maintenance” file but for newbies, it must completely freak them out.

Surely, it wouldn’t be hard to include some kind of link on the “Maintenance Mode” screen that authenticated Adminadmin (and super admin) level users could use to delete the .maintenance file and and return the website to an accessible state?
Destiny Kanno 7:32 pm on February 3, 2022

It’s been flagged that none of the FSE themes in the theme directory are `AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Ready`. Will there be any improvements to TT2 to make it `Accessibility Ready`?
- Kjell Reigstad 5:39 pm on February 4, 2022
  
  I’m pretty sure Twenty Twenty-Two is just missing the tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) actually. The theme was reviewed throughout its development, and found to pass WCAGWCAG WCAG is an acronym for Web Content Accessibility Guidelines. These guidelines are helping make sure the internet is accessible to all people no matter how they would need to access the internet (screen-reader, keyboard only, etc) https://www.w3.org/TR/WCAG21/. AA.
  
  https://github.com/WordPress/twentytwentytwo/issues/82
  
  The theme review guidelines go beyond WCAG in some areas, and there was one conflictconflict A conflict occurs when a patch changes code that was modified after the patch was created. These patches are considered stale, and will require a refresh of the changes before it can be applied, or the conflicts will need to be resolved. regarding the use of multiple H1s. But there was consensus that the rule would be updated in the guidelines side:
  
  https://github.com/WordPress/twentytwentytwo/issues/233#issuecomment-985756453
tinomueller 2:33 pm on March 10, 2022

Font family & design selection for all blocks with text content is mandatory. Since different webfonts are standard in nearly every project we often have to use css helper classes but this is not optimal for our customers. They do often have problems in understanding things like CSSCSS Cascading Style Sheets. / HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. and so on, which is normal.
woocomuser 10:26 am on April 10, 2022

Is there any word on the rollback feature for updates. It previously appeared to be gaining momentum but gone quiet recently.
illartista 9:46 pm on April 16, 2022

2021 Theme was amazing and had Light mode and Dark mode based on user’s system settings.

Now we lack that but with color palettes, it would be highly useful if we will be able to select one color palette for light theme and one color palette for dark theme. A toggle light/dark theme 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. would be also helpful.

I do not know if it would be technically difficult to implement but it will definitely help in making the internet more user friendly.