The Test Team helps manage testing and triage across the WordPress ecosystem. They focus on user testing of the editing experience and WordPress dashboard, replicating and documenting bug reports, and supporting a culture of review and triage across the project.
If you’d like to help test Full Site Editing, please join the FSE Outreach Program. You can find current calls for testing for this program here and you can join the fun in #fse-outreach-experiment.
The team gathers in #core-test. Please drop by any time with questions or to help out.
Core Editor Improvement: Smoother Site Editing: See some of the latest updates to the editor, including revisionsRevisionsThe 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. history for styles, templates, and template parts.
WP Briefing: Episode 56: What to Know About WordPress Playground: Learn more about experiments surrounding the ever-growing WordPress Playground, and what coding and testing accessibilityAccessibilityAccessibility (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) opportunities this exciting project is making possible.
What’s new in Gutenberg 15.8? (May 17): Get the latest scoop on what’s recently shipped in GutenbergGutenbergThe 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/.
WordPress 6.2.2 Security Release: This rapid-response security release addresses a shortcodes regression from 6.2.1, and further improves security around this feature.
FSE Program Testing Call #23: Rapid Revamp: Follow along with this #fse-outreach-experiment to test features planned for the 6.3 release. With clear instructions on setup and what to test, both experienced and new contributors to testing will find this an interesting way to test and explore new features.
And last, but not least:
WordPress’s 20th Anniversary: WordPress turns 20 this Saturday, 27 May! Celebrate this historic milestone with others from around the WordPress world!
@ironprogrammer drew attention to the recent release of wp-now (npm package), part of the WordPress Playground project. He noted that wp-now works with Node.js, and could be a possible replacement for wp-env. He gave an example of having navigated to a pluginPluginA 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 source directory and running wp-now start, which quickly launched a new WordPress site to test the plugin.
@ironprogrammer mentioned that the utility could be a fast way for contributors to get set up for testing or development, and referred to WCEU as a possible testing ground for test contributors to try it out.
@oglekler provided a link to a MeetupMeetupAll local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. event that featured Playground, occurring shortly after Test Chat.
@ironprogrammer then shared his plans to draft wp-now setup instructions to propose for addition to the Test Handbook, and asked the team to try out the utility and report any blockers or challenges they encounter.
@boniu91 asked if PRs and patches could be applied to sites running on wp-now. @ironprogrammer confirmed having tested with plugin repos, but that testing with the wordpress-develop repo would be important before recommending it for broader Test Team use.
WP Briefing: Episode 55: Happy Anniversary, WordPress!: Celebrating 20 years this month, take a look back on how WordPress has been shaped by its amazing open sourceOpen SourceOpen 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. community.
WordPress 6.2.1 Planning: This minor releaseMinor ReleaseA set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. brings an important bugfix to 6.2. Consider taking part in testing the RCRelease CandidateA beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. (today) or the final release next week.
Let’s talk: WordPress Core & Artificial Intelligence: Have you been following recent happenings in the world of AI and LLMs? Contribute to the discussion around how these important technologies fit with the WordPress open source project.
@ironprogrammer highlighted that the PR to prerelease Playwright test utils — aka @wordpress/e2e-test-utils-playwright — has been merged, and is slated for release with GutenbergGutenbergThe 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/ 15.8 🎉. He noted that this facilitates inclusion of the package in other test suites, and expressed hope that it would eventually contribute toward improved E2E coverage in WordPress.
@oglekler wondered how well Playwright worked in WP admin, outside of the editor context. She referred to reports of Quick Edit rows disappearing after an update, and whether an E2E test could help identify this.
@ironprogrammer clarified that the release of the @wordpress/e2e-test-utils-playwright package was in response to several requests from community members who wished to use it, and encouraged continued exploration regarding previous discussions about Cypress.
Phase 2 board: tracking the high level projects alongside medium projects that ladder into the larger work.
UX and Polish board: tracking smaller, developer ready items that help polish the experience. This is a great place for folks who want to dive in to help without needing to stay up to date on the larger projects.
From there, we discussed the larger topic of reintroducing content editing to the site editor, including where hints in the interface should be, the need to have strong user stories around using this functionality, and ensuring clarity between template and post editor. We very briefly touched on how there will be expanded Detail views of page, template, template part, styles without going into much detail.
With Ben on the call, we went over the focuses for 6.3 for navigation, including: adding back the navigation section to the Site Editor, improved link control, and using slugs to reference menus. We talked about the problem with how you can repeatedly import classic menus, leading to lots of extra menus, and discussed the need to see where menus are used when they are listed out so you know which to delete.
We ended on some interesting technical happenings that lead to some powerful UIUIUI 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./UXUXUX is an acronym for User Experience - the way the user uses the UI. Think ‘what they are doing’ and less about how they do it. options:
Simplified layout controls trying to bring together multiple tooling options into a more condensed interface.
Expose revisions (styles, templates, and template parts), including chatting about a current bug in the experience preventing us from testing in the outreach program. We went into some detail talking about Style revisionsRevisionsThe 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. and watched a demo of what that could look like to have visual revision history.
Add a command center option for ease of access to get where you want in WordPress.
Lots of work has momentum right now so stay tuned for much of it to be tested!
WP Briefing: Episode 54: A Bill of Rights for the Open Web: Dig into the four freedoms of open sourceOpen SourceOpen 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 how they relate to WordPress’s idea of a “Bill of Rights” for the open web.
Status update on the SQLite project: Learn more about how to test and provide feedback for this proposal to eventually offer SQLite support natively in WordPress coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress..
@ironprogrammer invited/reminded the team to consider submitting topics and/or applying to the 2023 WordPress Community Summit, emphasizing that ideas and input from underrepresented community members is especially important to summit discussions.
FSE Program Exploration: Build a block theme: In this latest #fse-outreach-experiment call for testers, approach blockBlockBlock 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 development with a design mindset, using only the editor and available tools (no code!) Accepting feedback through April 26, 2023.
Focal Groups 🧪
@ironprogrammer re-introduced this section as pertaining to Test Team discussions from 2021. Because contributorship has changed a lot since then, he asked that contributors interested in representing a particular focal group reach out to @boniu91 or @ironprogrammer (himself). He also noted that the team can adjust the focal groups to align with current needs, particularly if it would help inspire greater collaboration.
E2E
@oglekler noted their positive experience with Cypress, an open-source testing tool which uses Mocha and jQuery, and can be run headless. @ironprogrammer asked if it was compatible with the current WordPress E2E standard, Playwright, and suggested that discussion with other E2E contributors be held to discuss further.
@ironprogrammer suggested that a follow-up Make/Test post be considered to gauge interest on possible focal group rep interest, particularly for E2E.
Test Handbook
@ironprogrammer gave a brief update on the Test Handbook, noting that a new Contributor DayContributor DayContributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. page was under final review. The page will provide new Test Team contributors a good place to start at WordCampWordCampWordCamps 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. events. He encouraged contributors to share the page at future WordCamp Contributor Day events, and to raise suggestions for improvement in the #core-test channel, or to create a PR in the handbook’s official GitHub repo.
Are you interested in hosting a <test-scrub>? The Test Team needs you! Check out Leading Bug Scrubs for details, or inquire in #core-test for more info.
And while general release has been pushed to tomorrow, this post is a good refresher on the process leading up to and including release day: WordPress 6.2 Release Day Process.
@ironprogrammer pointed out that the release process helps ensure that issues like the regression noted above can be identified and resolved prior to general release.
PluginPluginA 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 Dependencies
@afragen requested UXUXUX is an acronym for User Experience - the way the user uses the UI. Think ‘what they are doing’ and less about how they do it. testing for the Plugin Dependencies feature plugin, noting that @azaozz was looking for “newish” user feedback for the plugin dependency activation workflow. The instructions provided by Andy included two steps: installing the feature pluginFeature PluginA plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins., and then installing a separate plugin with a dependency.
@costdev and @afragen explained that providing only basic instructions might better measure how easy or difficult the workflow is to users in discovering the process organically — i.e. how to successfully install the dependent plugin without outside guidance.
@costdev outlined the feedback desired from testers, and @ironprogrammer asked where the feedback should be provided. Additional discussion along with @afragen lead to the decision to create a new call for testing post. [Editor’s Note: The CFT for the above has been posted to Make/CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress..]
Are you interested in hosting a <test-scrub>? The Test Team needs you! Check out Leading Bug Scrubs for details, or inquire in #core-test for more info.
Announcements 📣
FYI: Navigation section of new Site Editor experienced removed for 6.2 RC 2 — after careful discussion, this feature has been removed from 6.2 in order to give it time to mature in the GutenbergGutenbergThe 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/pluginPluginA 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.
WP Briefing: Episode 51: Is Routine a Rut? — Josepha discusses the utility of consistency, how it can highlight notable changes, and allow us to spend more time on the important stuff.
WordPress 6.2 Release Candidate Phase — as a reminder, WordPress 6.2 is in the “release candidateRelease CandidateA beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge.” (RCRelease CandidateA beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge.) phase, and Tonya helps clarify the “dos and don’ts” in this post.
WordPress 6.2 Field Guide — check out the 6.2 Field Guide for important development and extender updates in this release.
@costdev mentioned that improved release testing has been discussed in #core, and asked if anyone had thoughts on how the number of testers might be increased during the Alpha/BetaBetaA 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./RC phases. @ironprogrammer noted that this has been suggested as a 2023 WordPress Community Summit topic, but that short term options are needed.
@costdev asserted that collaboration with MarComms (#marketing) would be key to finding ways to pull in more contributors for testing. He asked where we might extend reach/awareness, and what motivates users to become testers.
@afragen suggested that managed hosting providers, such as WordPress.comWordPress.comAn 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/, might facilitate RC testing by working with opt-in site owners. @costdev agreed that this would help environment testing, but that there is a lack of feature-specific testing and reporting. He asked what tools might be offered to make this easier.
@afragen offered the WordPress Beta Tester plugin as a place to experiment with the “Report an issue” concept. [Editor’s note: This plugin currently reflects 3000+ active installs.]
Admin bar link: “Report an issue”.
On plugin activation/update, add a tooltip to the admin bar link: “Found an issue? Report it here”, to promote awareness.
The link leads to a new tab in Beta Tester, which displays basic — but important — environment information consistent with what is suggested for test reports, some of which has been written/tested by @costdev in a separate plugin. The information would be formatted for inclusion in a TracTracTrac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. or GitHubGitHubGitHub 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/ ticket.
Provided this initial scope, users would be able to copy this information for use in a new issue or reproduction report.
@afragen also noted updates may be needed for Apple Silicon support.
Jeff Ong, Ellen Bauer, Nick Diego, and Edwin Cromley
Video Recording:
Topics:
We covered a wide variety of topics: the outreach program’s future, updates for the 6.1 release, aspects of phase 2 to wrap up, the current experience of developing and maintaining blockBlockBlock 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 more.
What will happen to the outreach program now that 6.1 is out?
The outreach program is continuing as is! When it comes time to wind it down, it will be heavily communicated and, ideally, continued in some form or another. As with “gradual adoption” of FSE features, expect a more gradual phasing out.
The discussion around 6.1 feedback led to a conversation about managing updates for block themes. In particular, there were some layout changes that needed to be managed. Keeping up with these changes for each release can lead to a feeling of “Why did we build these themes already?!” when there’s so much to keep on top of with each release. It still is taking a lot of work with each release.
@bph the idea was brought up to have a compressed set of links to follow based on audience perhaps for the Developer blog, inspired by Rich Tabor’s twitter roundup. We discussed how there were also 2x the number of dev notes for this release compared to 5.9 and 6.0.
In general, there seems to be a cycle of finding a solution to work around current limitations > the gap getting filled in coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. > needing to update > cycle repeats. There are questions around when this process will get less intense.
Themeshaper
Questions around themeshaper came up with folks wanting to see more there and reminiscing on the kinds of posts that were shared previously as being quite illuminating. Speaking personally, I’m now trying to share more directly in Core when posting but it is an “outlet” that would be great to see revived.
Pixl theme discussion
After Matt tweeted about the Pixl theme, this led to questions around: “Is this the direction we’re heading in? Is it meant to be super simple block theme? Am I overcomplicating it somehow?” We talked about how it was likely just a note about a cool, quirky theme and that ultimately block themes are for all cases (or will be in the future as functionality grows). The goal is to do everything, from very simple to very high level. Nick shared that he’s, “Taking a lot of block themes and throwing them away. I took what was available and took it to the next level, like custom classes or custom code, that block themes couldn’t do at that time. Now, I’m stripping it out and refreshing it with a much simpler architecture.” Ellen is doing the same and it’s a lot of work. From there, you have to consider propagating updates. While this is a big part of being an early adopter, it’s still worth noting and it becomes intimidating to step into eCommerce considering.
Stability for maintenance & stability for UXUXUX is an acronym for User Experience - the way the user uses the UI. Think ‘what they are doing’ and less about how they do it. of block themes
We talked about how there’s a split when talking about stability: stability of block themes in terms of less maintenance and stability of the UX for end users of block themes. We discussed how patterns are a big deal for UX in general and shared some examples of using starter patterns, with Nick sharing a great resource he wrote.
Latest Phase 2 Update
We went through the latest phase 2 overview issue update, talking at a high level about what’s to come and how work is progressing. This included a lot of discussion around the ability to save, import, and export variations. Feedback was given that style variations are often ignored for clients and that it would be more useful to be able to copy style variations/copying block styles. At the same time, being able to import/export your own branding via style variations would also be wildly helpful.
We ended by talking about the betaBetaA 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. label, how it’s likely slated for 6.2, how another update will need to be done to ensure the issue is up to date, and how the label itself might change away from just “editor”.
Attendance: Rich Tabor, Damon Cook, Courtney Roberston, Paal Joachim Romdahl, Jeff Ong, Nick Diego, Vagelis, Sé Reed, Piermario Orecchioni.
Video Recording:
Topics:
The main topic centered around the work underway to wrap phase 2 gathered in this overview issue. Expect regular updates to this issue and know that other work will continue but there’s a big emphasis to complete the tasks outlined there.
As of last week, the following was in place:
Work has been completed (1)
Dev work is underway (9)
We’re in the design stage still (3).
Dev is assigned but hasn’t started (3).
Means work is stuck but there’s follow up to try to get unstuck (1).
Means work is stuck, either due to a problem or a time lapse of 14+ days, and unclear how to unblock (11).
From there, we dug into the following individual issues to chat through at a high level what we were seeing. At a high level, it stuck out to folks how many different explorations there are, conflicting designs at times, etc. By doing this work concurrently, these differences can be resolved and the solutions refined together.
We talked about how this was a change in the entrance to the site editor just as much as it was for navigating between content. There was a desire to be able to click on the site title in the nav component to take you to the front end of the site. We discussed the important of accessibilityAccessibilityAccessibility (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) testing for this change and it’s top of mind to test for the FSE Outreach Program.
Overall, this would be a great way to get a sense of how changes impact the entirety of the site and in creating a more unified approach.
When looking at this issue, various folks commented on how it feels like there’s a number of different modes and it isn’t always clear how they relate and don’t relate. Part of this is due to designs being in progress at various stages and including some work but not others.
We chatted about how the IA needs to improve around right/left sidebars. Is there a best practice for when to put things in left vs right sidebarSidebarA 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. in the design library? Are we at a critical point in that convo right now? What about RTL when it comes to moving where things “live”?
We discussed what consolidation of the various editors might look like and how the current work seeks to make everything more unified, with the option to edit content in the site editor for example.
Media library getting the “FSE treatment”
Previously, the outreach program had an exploration around media and site building leading Courtney to bring it up!
Feedback on the Quick Inserter prioritizing patterns in certain circumstances
We discussed some pain points around when the quick inserter prioritizes patterns, especially the struggle to be able to add a blockBlockBlock 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.!
Talked about having it be a user preference to start with blocks vs patterns.
There are generally two different mindsets when working with blocks vs patterns.
Could the slash inserter work with patterns? There’s already an open issue here.
Other topics and questions
Folks shared that responsiveness is still a big topic along with navigation block. Multiple people echoed both. Damon shared in the chat: “The Navigation block has SO much complexity, but tackling the challenges will likely surface many great ideas that can be rolled out to other blocks that have complete UIUIUI 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./interaction”. Finally, we chatted at the end about the history of the Query LoopLoopThe 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. block naming (why not loop?), where folks can report issues when 6.1 is out in the wild, and what’s next for the FSE Outreach Program.
Attendance: Carolina Nymark, Daisy Olsen, Manuel Esposito, Rich Tabor, Herb Miller, Ellen Baeur, Ana Segota, Evan Mullins, Damon Cook, David Bowman, Jessica Lyschik, Ed Beck, Courtney Roberston, Amy L, Rita Best.
Video Recording:
Topics:
Apologies for the lack of timestamps – this conversation was vast and deep, making it hard to separate out into specific sections.
Pain points with blockBlockBlock 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, including naming conventions for color palettes/mapping colors, managing updates to the theme, oddities with switching between style variations/losing styles, and keeping up with all the various changes to CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress..
Pain points from users including “how can I change fonts”, using the navigation block, and confusion around the split between the post editor vs site editor (ie have to go into the site editor to manage styles).
Theme switching and the UXUXUX is an acronym for User Experience - the way the user uses the UI. Think ‘what they are doing’ and less about how they do it. around picking/choosing parts of Styles from a theme, which ties into this prior exploration.
Discussion around “Who are our users?” and how there’s a spectrum of use cases to cover from those who want a ready made theme to those who want to dig into the details. How do you build for each or all?
Discussion around having a pattern library/pool as a way to speed up development for themes with a note around how there are so many ways to build smarter for block themes and how much more accessible it is for designers compared to classic themes.
Discussion around using Figma and design tokens to create a system for updating/working with theme.jsonJSONJSON, 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.. The following links were shared: Figma Tokens & Style Dictionary (What’s used to transform the output for theme.json). This is currently being used by the VIP team at Automattic.
Discussion around custom blocks, when to build them, and why they are often times preferable due to the ability to completely manage updates rather than chasing after changes to Core. This led to a conversation around why themes aren’t able to require custom blocks (it breaks a users site when they switch away).
A follow up idea was shared after the hangout from Damon Cook to consider: “It would be super helpful to have a single Figma file with all blocks, colors, and properties that could go in a theme.json. It would undoubtedly be high maintenance and would have to be under active updates alongside new GutenbergGutenbergThe 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/ features being merged into core, but it could also have a webpage equivalent to markup/output. A WordPress theme Style Guide: Figma file with the equivalent of block output on a site for users to copy/paste the code into their theme and see everything on a page… kinda deal.”
Overall, while there is both excitement and interest in what block themes unlock, it’s also clear that there are a build up of pain points to address, whether through clearer resources or changes to Gutenberg itself. These conversations are just one way to start surfacing these themes (get it) and to begin finding ways forward.