Test Chat Summary: 27 February 2024

On Tuesday, February 27, 2024 at 04:30 PM GMT+5:30, <test-chat> started in #core-test facilitated by @webtechpooja Agenda can be found here.

1. Attendance and Looking for Volunteer

Attendees: @oglekler, @bph, @shiponkarmakar, @huzaifaalmesbah, @sumitbagthariya16, @hasanuzzamanshamim, @webtechpooja, @nazmul111, @ankit-k-gupta, @devmuhib, @narolainfotech, @lumiblog, @tapan29bd, @hage, @krupajnanda, @rcreators, @ironprogrammer, @freewebmentor

Note-taker and facilitator for the next meeting:

Facilitator – Looking for volunteer (@webtechpooja will be traveling during the next meeting to attend WCAsia.)
Note taker – @freewebmentor

Looking for Volunteer

We are looking for a volunteer to work on user calls for testing (for more detail, check out the guide: How to facilitate a Call for Testing).

@webtechpooja asked for more insight from @bph. She added that the recent outreach program restart revealed positive feedback, highlighting the effectiveness of this approach in engaging non-coders. Test Team seeks collaborators for the regular creation of no-code user testing calls, catering to site builders and owners. Join us 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. Asia Contributor DayContributor Day Contributor 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/. for discussions, or connect asynchronously to plan and schedule Hallway Hangouts.

2. Announcements 📣

  • WordPress 6.5 Beta 2, released on February 20, 2024, extends thanks for your contributions. Asked to join the upcoming WordPress 6.5 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. 3 release party in the #core channel.
  • Exciting update: WordPress 6.5 introduces AVIF support, a cutting-edge image format delivering superior quality and compression, up to 50% smaller than JPEGs. Explore and test this feature in the latest release!
  • WordPress developer live stream: testing WordPress 6.5 If you want to know what is upcoming in WP 6.5. @psykro is hosting an online workshop. Do join the workshop.

3. Test Team Announcements

4. Focal Group Updates

@ankit-k-gupta is extending the opportunity to host the Test Team Triage biweekly meeting. If anyone is interested, please express your willingness.

@hage asked, Is there additional AVIF information beyond Specifically, I’m curious if existing JPEGs can be converted to AVIF without using 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.

@ironprogrammer replied, The update introduces support for new AVIF uploads and auto-conversion upon upload via the ‘image_editor_output_formatfilterFilter 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., but it doesn’t alter existing images. @hage suggests that to modify existing images to AVIF in bulk, installing a corresponding plugin may be necessary.

@oglekler has a proposal that she would love to see working groups between developers and testers. @bph replied they just created 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/ group WordPress/Outreach that developers can pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” for feedback and testing. She also drafted the announcement on Google Doc.

@oglekler replied – @bph, I’m not just suggesting casual pings; I’m advocating for close collaboration from project inception. Testers can contribute valuable insights on project architecture right from the start, applicable not only to the Editor but across WordPress. @bph replied – Yes, of course, the ping is the first step for the developer when they are ready to connect.

@hage added – The background to my question: I would like to test this in more detail. @webtechpooja replied – you’re on the right track! @oglekler and other Test Release leads are crafting a post set to release this week. It will contain comprehensive details and testing instructions, so stay tuned for updates.

5. Call for testers/visibility

6. Open Floor

@rcreators think we should create high priority testing tags for features that need more testing. Or we can have quite a separate list for testing for this part.

@bph asked – why in the list of things to testing issues from Gutenberg repo are not listed. Just want to know the history of the decision. @ironprogrammer is seeking clarification on areas where we might have overlooked pointing out issues related to GB (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/).

@bph replied I only noticed it on This week of Test where new tickets are listed under Reproduction tests. They seems to be all trac tickets. @ironprogrammer mentioned the omission of highlighting Gutenberg issues in WiT posts wasn’t intentional. Challenges arose due to labeling inconsistencies and filtering issues, making it difficult to categorize “small/medium/large” ticket types accurately. The dilemma lies in triage/labeling, and the suggestion is to explore using the “Needs Testing” label for potential solutions.

@rcreators added – Also, if we can add something like a deadline for testing task that would be great. @webtechpooja replied – In our open-source, volunteer-driven project, imposing deadlines is not feasible.

@krupajnanda requested to change the weekly meeting time. But rest of the people are happy with the current time and suggested her to join asynchronously.

7. Next Meeting 🗓

Next meeting will be on Tuesday, March 12, 2024 at 04:30 PM GMT+5:30, held on #core-test! </test-chat>

If anyone wants to facilitate the next meeting, please feel free to comment in this thread.

Thank you, @webtechpooja, for the peer review and for helping me write this post. 

#core-editor-improvement, #meeting-notes

Test Chat Summary: 13 February 2024

On Tuesday, February 13, 2024 at 04:30 PM GMT+5:30, <test-chat> started in #core-test facilitated by @webtechpooja Agenda can be found here.

Attendees: @ankit-k-gupta, @rcreators, @JavierCasares, @mahbubmr500, @anandau14, @huzaifaalmesbah, @vipuljnext, @zunaid321, @devmuhib, @sakibsnaz, @shiponkarmakar, @krupajnanda.

Note-taker and facilitator for the next meeting:

Facilitator – @krupajnanda
Note taker – looking for volunteer

1. Announcements 📣

  • Bug scrub schedule for WordPress 6.5 – This post lists bug scrub sessions dedicated to moving things forward toward the next major WordPress release, 6.5, slated for March 26, 2024. Read the full 6.5 Release Schedule.
  • Important milestones for WordPress 6.5 – The WordPress 6.5 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. 1 was scheduled for release on February 13th, which was yesterday. Be ready for the Beta and get started for testing soon.
  • Core Editor Improvement: Power in the Details – These “CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor Improvement…” posts (labeled with the #core-editor-improvement tag) are a series dedicated to highlighting various new features, improvements, and more from Core Editor-related projects. Take a moment to learn more about them—and explore how the power of details in 6.5 can transform your current workflows.
  • Improving block development documentation: 2023 recap and a look ahead – Over the last year, a group of contributors has been working to improve 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. development onboarding experience within the Block Editor Handbook. In this post, you can find the highlights of the updates made, pinpoint areas for further refinement, and outline our focus for the next few months and ways you can help.

2. Test Team Updates

  • Week in Test Post: Wondering where you can contribute and learn? The Test Team’s got you covered. Check out this post and pick any issue mentioned in it.
  • Test Team Update: Metrics for overall team progress

3. Focal Group Updates

  • We are working on some easy way to provide a badge to Test team contributors, so we worked on a handbook page where all the details are mentioned. Please Review Test team badge criteria and share your feedback.

4. Open Floor

  • @rcreators discussed that 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 nightly build does not work with the Gutenberg regular plugin. Along with that we received the feedback from @JavierCasares  who shared updates on improving the WordPress test results tool, inviting questions on reviewing fails, accessing support for failed tests, and expanding testing capabilities like WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/ integration and pre-installed plugins for hosters.

Next Meeting 🗓

The next scheduled meeting is on Tuesday, February 20, 2024 at 04:30 PM GMT+5:30 for <test-triage> in #core-test.

Are you interested in helping write Test chat summaries like this one? Volunteer at the start of the next <test-chat> and earn some props!

Thank you, @webtechpooja, for the peer review and for helping me write this post. 

#meeting-notes

Test Chat Summary: 16 January 2024

On 16 January 2024 at 11:00 UTC<test-chat> started in #core-test facilitated by @webtechpooja. Agenda can be find here.

Attendees: @ankit-k-gupta, @sumitbagthariya16, @shiponkarmakar

1. Announcements 📣

  • Call for Mentees & Mentors: Contributor Mentorship Program Cohort #2 (2024 Q1) – Community team is thrilled to announce the launch of the second WordPress Contributor Mentorship Program cohort for the first quarter of 2024! This initiative is a fantastic opportunity for experienced WordPress contributors and those looking to get involved for the first time.
  • A Year in Core – 2023 – Check out some aggregate data for 2023 about WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. contribution on TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/..
  • Incident Reports 2023 Recap – The Incident Response Team (IRT) receives and handles incident reports following the Community Code of ConductThis handbook page includes information about the Incident Response Team, its members, and insight into their processes.
  • WordPress End of Year Celebrations! – The updates were submitted by team reps and are just a selection of the projects that their teams are proud of. Give it a read to see a few hidden projects and celebrate how much we did together in 2023!
  • Thank you and bye (for now), Jill! – Jill has been a key player in our community as the leader of the Diverse Speaker Training (#WPDiversity) working group and as the co-creator & maintainer of the Diverse Speaker Training Workshop. This post expressing our collective thanks to Jill Binder for her remarkable contributions to the WordPress 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. project. If you ever worked with Jill Binder, Please show your gratitude to her by commenting on this post.
  •  2024 Global Sponsors: Announcement – We extend our gratitude to all the sponsors who have played a pivotal role in supporting various WordPress community programs, including WordCamps, new events, and WordPress Chapter MeetupMeetup All 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. groups.
  • A Look Ahead at WordPress in 2024 – Curious about WordPress’s big-picture items for 2024? Phase 3, Data Liberation, new meetups, and more, get the spotlight in this episode. Join Executive Director Josepha Haden Chomphosy for all this, plus a small list of big things coming up in the next two weeks.
  • Data Liberation in 2024 – Imagine a more open web where people can switch between any platform of their choosing. A web where being locked into a system is a thing of the past. That’s why Matt announced a new initiative called Data Liberation for 2024. Migrating your site to WordPress, or exporting all your content from WordPress, should be possible in one click. He want WordPress’ export format to become the lingua franca of CMSes, whether coming to WordPress or moving within WordPress.

2. Test Team Announcements

3. Focal Group Updates

4. Open Floor

  • Call for testers/visibility –
    • Early Opportunities to Test WordPress 6.5 – Ahead of 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. 1 for WordPress 6.5 on February 13th, this is an early opportunity to provide feedback as features are rapidly underway. Of note, this is intentionally just a selection of what’s ready to test and doesn’t include everything mentioned in the roadmap. Expect a broader testing post, like this for 6.4, for the release once beta 1 is out in the world.

Next Meeting 🗓

The next scheduled meeting is on 23 January 2024 at 11:00 UTC for <test-triage> in #core-test.

Are you interested in helping write Test chat summaries like this one? Volunteer at the start of the next <test-chat> and earn some props!

#meeting-notes

Hallway Hangout: Let’s chat about the experience of building a block theme

This is a summary of a Hallway Hangout that was wrangled in the #fse-outreach-experiment and #accessibility channels as part of the FSE Outreach Program. Huge props to @alexstine and @joedolson for demoing.

Attendees:

There were enough folks who I don’t know so am going to leave out WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ usernames on this!

@annezazu @elmastudio @greenshady @arrayhq @luminuu @richtabor @jffng, Nahuai Badiola, Sonia Gaballa, Jeffrey Pearce, Henriette Stewart, Jason Crist, Kafleg, Sarah Norris, Jos Velasco, Digamber, Arkadiusz Salek, Patrick Posner, Gravnetic, Vikas Singhal, Jeremy Techtmann.

Video Recording:

Notes/Links:

Context setting

Mike reached out to @annezazu to share some feedback about his recent 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 building experience and they decided together to turn it into a hallway hangout in order to have it benefit the wider community and gather more insights.

Mike’s high level thoughts

Point 1: The elements that you need to build a block theme are solid, reliable, and they aren’t changing everyday. You can build a block theme for broad use a lot faster and in a better way. If you’ve had hesitations about that, get in there and try it again. Have an open mind. 

Point 2: Folks expect to intuitively know this stuff but you do have to treat it as a new tool to learn. You put a page builder on your site, you don’t expect to just know it. Take this new experience with a fresh perspective and learn it in the same way.

Point 3: Follow people who have been building themes and learn with them.  

Thoughts on current adoption blockers

Ellen chatted about her experience jumping into the experience early on and how they felt the different pain points. From her perspective, the biggest issue is that adoption from users is way behind the potential of what’s available partially due to the reputation 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/. How can we change this?

We no longer have a technology problem in WordPress. It’s capable of whatever you want it to do. Now, we need people building on it. 

Mike

We discussed how we can show off what’s being built and how TT4 is a way to do that, especially since full page patterns are coming to this new default theme and the theme in general matches a more real life use case outside of blogging.

Highlighting block themes

Block themes are the introduction to the new WordPress and highlighting them more feels blocked by various CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets. For example, folks talked about wanting an introduction video for themes and a better option for demo content. Seeing a preview of patterns is nice but there’s a desire for more.

@richtabor mentioned trying out a playground blueprint where you can pick patterns, templates, post content, image sources, and have folks dive into the theme to try it out. Perhaps it could reuse the starter content 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. and extend what’s already there. 

This naturally led to a conversation bout the refresh of the Theme Showcase and the ways that can help highlight block themes more. This is especially important since block themes pave the way to use the site editor. 

“The themes page is really better these days. but we have to improve it even more.  The main thing is we need Block theme users, we need to show them the importance of using it. If we have users, we will get more beautiful themes.” –

Kafleg in the zoom chat.

We talked about wanting a built in way to demo using WordPress.org that’s so good that theme authors link to that instead of their own demo on their own site. @luminuu shared the idea of “A separate multisiteMultisite Multisite is a WordPress feature which allows users to create a network of sites on a single WordPress installation. Available since WordPress version 3.0, Multisite is a continuation of WPMU or WordPress Multiuser project. WordPress MultiUser project was discontinued and its features were included into WordPress core.https://codex.wordpress.org/Create_A_Network. for theme demos so you can fully customize that demo to the theme’s needs.”

Exporting theme

Mike touched on his experience of using the Create Block Theme plugin and how the overall workflows needs to be refined, including in exporting the theme. This would help make it a defacto tool for now until more functionality can be added into Core itself.

Pattern management

We discussed the potential and power of patterns alongside the overall pain points in managing/maintaining them. Mike talked about the early days before you could create them in the interface and how cumbersome the process was (had to create in the page, export the content, put it into a file, figure out the image, etc). Maintaining patterns is immense still: have to manually put in a file, translate the strings again, change the image tags, etc.

“If you were to tell this to a new user for distribution, they would say no way.”

Mike

We talked about incorporating this more into the Create block theme 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 folks, some of whom were on the call, and they haven’t had the bandwidth to add it in yet. However, it’s clear that this is a part of the UIUI 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. that isn’t covered well anywhere right now and definitely needs attention. We talked about the broader discussion kicked off here.

Interoperability

We talked about the long term aim to have things be interchangeable between patterns, templates, style variations, etc. Ellen shared a vision of how simple it would be to upload patterns to the directory and easily reference them in new themes she’s creating. During this conversation, we touched on a wide range of issues:

“My idea was always how can be get components like patterns and style variations out of one theme and maybe/possibly make them interchangeable and usable within multiple themes. So maintaining patterns of a theme from the patterns library would be amazing…I feel so much that the seeds are all there we just need it together.”

Ellen reflecting ont his topic.

There’s a draft PR for TT4 to include patterns via 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. which helps also push this forward. We ended talking a bit about nailing a color system for a theme without needing to repeat yourself with @richtabor talking about his “colorways” idea.

Theme documentation call out

@greenshady is doing a ton of work to overhaul the theme handbook and folks are welcome to share feedback along the way as we all continue to help push block theme and adoption forward.

Action items

I’ll follow up on this early next week.

#fse-hallway-hangout

FSE Program Final Touches Summary

This post is a summary of the Final Touches call for testing for the FSE outreach program, the twenty-sixth and final effort. As always, I want to highlight those who helped to bring others along with them in this latest effort: 

  • InstaWP for allowing the outreach program to use their tooling for free, enabling more folks to jump into this call for testing and for more creativity in what we are able to test. 

As mentioned on the Evolving the FSE Outreach Program post, thank you to everyone who has helped from the start with these feedback efforts.

High level summary 

This testing call spanned numerous planned WordPress 6.4 features, including a focus on the Font Library (which is no longer planned for 6.4). Most feedback pertained to feature requests and usability concerns, highlighting the following common themes:

  • A desire for improved visibility of current and CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. categories in pattern creation.
  • Requesting additional controls, similar to the Cover 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 adding background images to a Group block.
  • A need for more informative error messages in the Font Library, especially when deleting fonts.
  • Enhancing the discoverability of the Font Library.

Instead of breaking down feedback into bugs, feature requests, and general usability feedback, everything is broken down into groupings of features with extra quotes. This decision was driven by the limited volume of feedback received (only three responses) and the evident recurring themes within the feedback itself. 

Command Palette 

The Command Palette was featured throughout this call for testing, including to navigate to a page with a similar name to a pattern. This quickly reinforced a need for more context when searching for items and running commands:

Using the Command Palette. I write Portfolio and get up two Portfolios that have two different icons. One that looks like a post/page and the other as if it is a template part. Hovering over both it would be nice if it said something like: Portfolio page and the other Portfolio template part. To strengthen the meaning of the icons I see.
@paaljoachim in this comment.

It would be awesome to have more information about the current state of a toggle, “Disable distraction free mode” instead of “Toggle distraction free mode.” Or maybe make the icon of the active toggle reflect its state by adding a black background like the Settings or Styles buttons do.
@josvelasco in this comment.

I like that the command palette now includes site editor navigation like list view toggle, distraction free toggle, and code view toggle. However, I agree with you and the folks here that suggest that the command name having a clearer context of what each will do.
@franz00 in this comment.

Patterns 

While adding categories to patterns works, the ability to see current categories, core provided or otherwise, would make it much easier to stay organized:

When creating synced patterns, it is great that now we can put them into categories. However, I’ve also learned that WordPress has its own default categories for patterns from this URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org https://github.com/WordPress/gutenberg/blob/c20350c1d246163201375f090b0b7b4ab49b1dad/packages/block-editor/src/components/inserter/block-patterns-tab.js#L35 (‘custom’, ‘featured’, ‘posts’, ‘text’, ‘gallery’, ‘call-to-action’, ‘banner’, ‘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’). Personally, I want my patterns organization to be as much closer to WP default categories as possible, but I can’t find those predefined categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. names being listed somewhere in the Site Editor interface. Perhaps we could have categories checkbox for those, like the post page have?
@franz00 in this comment.

Since there was a pattern called “Portfolio,” it was kind of confusing to find where to edit the page with the same name. The command palette would be more verbose and say “Edit template Portfolio” instead of just “Portfolio.”
@josvelasco in this comment.

I see that I can add a category, but I can not see which categories already exist. As I might want to place this into a pre existing category.
@paaljoachim in this comment.

Font Library 

The following specific items were raised with a particular note around the need for better error messaging both when uploading and deleting fonts:

I clicked the “Aa” icon to open up font management just because I followed your instructions, but I couldn’t have found the font management easily without them. I love icons, but this is only visible with a label.
@josvelasco in this comment.

I tried to upload a .zip on purpose but got no errors. It may be nice to have or suggest allowed font formats and a confirmation notification when one gets uploaded.
@josvelasco in this comment.

However, I found that the activation/deactivation and deletion of fonts somewhat confusing. Why would fonts deletion be offered on active, check marked, fonts? Would it make more sense to only offer fonts deletion to the inactive (unused) ones? Because deleting an active font directly impact the pages that use them, which will cause the page to automatically fall back to the default font. Besides, this is done without any warnings.
@franz00 in this comment.

I see the Fuggles uploaded above the Theme Fonts. There is a heading for Theme fonts but no heading for the fonts above it. It would be nice to have an “External Fonts” etc heading for the ones that are not Theme fonts.
@paaljoachim in this comment.

Other

Of the following items, the desire for more controls in adding a background image to the Group block was mentioned by all three responses. In particular, folks wanted to see the ability to change focal point. 

I find the rename feature taking too many steps and feels cumbersome. I would like to double click it just as if I was on a Mac to rename. I am happy the feature is in even if it kinda feels half baked.
@paaljoachim in this comment.

Color adjustments are fine, but having the same background adjustments available as the cover block would be great. Focus point, at least.
@josvelasco in this comment.

I also noticed that when navigating blocks in list view, the up arrow key sometimes cannot traverse back up when it encounters synced patterns, or a footer template part.
@franz00 in this comment.

#fse-outreach-program, #fse-testing-summary

Test Chat Summary: 29 August 2023

On 29 August 2023 at 16:00 UTC<test-chat> started in #core-test.

Announcements 📣

  • WordPress 6.3.1 Maintenance Release: This update fixes a handful of CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and 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 items, details of which can be found in the previous RC1 announcement.
  • 6.4 Release Parties Schedule and Hosts: The release squad is looking for volunteers to fill various roles required for each milestone’s <release-party>. Raise your hand, or be kind and share this post with folks you think can help out. Thanks!
  • The Future of WordPress & What’s Next for Gutenberg: Watch these presentations from WCUS 2023 to see what’s in store for 6.4 and beyond.

Focal Group Updates 🗣️

Handbook

There is an open PR to add a Test Team Rep page to the handbook. Reviews are welcome, which can be comments/reviews on the PR, or a pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” in #core-test if something needs more discussion.

Open Floor 💬

FSE Outreach Program Update

[This discussion started here.]

It has been proposed that the #fse-outreach-experiment begin the process of spinning down its user testing aspect (i.e. the program’s calls for testing) by the time WordPress 6.4 ships. In place of testing efforts, focus would shift to emphasize wider adoption of the Site Editor through hallway hangouts, dev documentation efforts, and other adoption-focused initiatives on the path toward wrapping up Phase 2 of the WordPress Project Roadmap.

Because the FSE Outreach Program has considerable overlap with Test Team efforts, program leadership has requested input from Test Team contributors with questions or concerns around the proposed shift. This follows other shared feedback from current program participants.

It was stressed that changes in the outreach program be handled carefully and slowly, and to capture opportunities for feedback. The next step is to compile initial feedback and thoughts around this change to share in a Make/Test post for wider input.

Calls for Testing

Current contributors in the #fse-outreach-experiment have expressed a desire to continue testing in a format adapted from or similar to the outreach program. Structured ad hoc calls for testing from within the Test Team are similar, and would provide an opportunity for continued contribution through testing. [Ed. note: the Test Team should also consider adopting things that worked for FSE CfTs to improve the experience for all testers.]

A possible source for CfT topics could be pulled from roadmap posts (for example), or otherwise collected in an ideas backlog (for example). Some pertinent links for CfTs can be found at:

Work is ongoing for documenting processes in the Test Team. The Handbook project can be found at https://github.com/wordpress/test-handbook.

Test Team RepTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. Nominations

[This discussion started here.]

The Call for Nominations for the next Test Team Reps is underway. Test Team members’ help is needed to nominate or volunteer for this role, to help represent the team to the wider project.

If you have a nominee in mind, or questions about the role, please comment on the post, ask in #core-test, or reach out directly to @ironprogrammer in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

@ironprogrammer stepped forward with an offer to help mentor volunteers for this role. It was also noted that serving as a rep offers an excellent opportunity to gain a broader perspective of how Test Team interacts with other teams, and that while it isn’t a “lead” role, there are some leadership-focused skills that reps develop in the process.

Please submit nominations by Thursday, August 31 Friday, September 22, end of day (UTC).

Next Meeting 🗓

The next scheduled meeting is on 5 September 2023 at 16:00 UTC for <test-triage> in #core-test.

Are you interested in helping write Test chat summaries like this one? Volunteer at the start of the next <test-chat> and earn some props!

Props @annezazu for peer review of this post.

#fse-outreach-experiment, #meeting-notes

FSE Program Let’s Start From The Beginning Summary

This post is a summary of the Let’s start from the beginning call for testing for the FSE outreach program, the twenty-fifth effort. As always, I want to highlight those who helped to bring others along with them in this latest effort: 

Shout out to @mdquer @olein @foosantos as first time contributors for this call for testing. Expect a badge on your WordPress profiles for your contribution! 

High level summary 

This call for testing focused on a “from scratch” experience using the big pieces from WordPress 6.3 without detailed instructions for maximum exploration, which is reflected in the lack of new bugs found and in a fair amount of usability feedback and feature requests. In particular, folks struggled immensely with figuring out how to change the sync status of an already created pattern and fumbled through using the Command Palette, with some left confused on how best to use this new tool. While no new bugs were found, Synced Patterns losing their alignment attribute and the Table of Contents 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.’s links not working on an initial save were noted by a few folks. Here’s what some folks had to say overall:

“The only thing to mention is for me is the command palette: The command palette is not satisfying for me. It works , but for me the problem are the keywords. I could not find > top toolbar or list view. As a normal user i would expect a keyword like – list view – should open the list view, or keyword – top toolbar – , should open top toolbar, that does not work for me. I like the new patterns section with synced and unsynced patterns.” @mdquer in this comment.

I’ve been trying to use the new command palette, but I honestly don’t know what to do there. I’ve used it successfully to switch to different pages, but I don’t know what the primary purpose of the command palette is supposed to be so I have no idea if I’m leveraging its capabilities at all…In general I feel like all aspects 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/ have been improved by recent updates. @beckej in this comment.

Bugs 

No new bugs were found and replicated with the following known items raised instead:

Each of these touch on items planned for 6.4 and, in particular, the alignment attribute with synced patterns remains a repeated and well established pain pointPain point Pain points are “places where you know from research or analytics that users are currently getting hung up and have to ask questions, or are likely to abandon the site or app.” — Design for Real Life

But it looks like the block does not work on previews only after the page has been published. As the preview does not have the correct structure. https://bluewinddesign.com/?page_id=385 (previewed page). Clicking one of the headings in the Table of Contents block the link anchor looks like this: https://bluewinddesign.com/resume/#head-3 . It went to a 404 page. @paaljoachim in this comment.

Feature Requests 

Many of these feature requests centered on the Command Palette, a feature new to 6.3 and slated for improvements for 6.4, with one request already completed for adding a Toggle List View command. With the growing number of design and styling options, two folks noted a desire to see the Style Book elevated and more readily discoverable, which aligns nicely with a currently open design issue on that exact topic. 

New

Previous

I found the autosuggest/listings to be varied in their accuracy. Some of them didn’t make much sense in their order compared to the actual search query. @jordesign in this comment.

The ‘View Page’ button exists in the old block editor, so it would be nice to have a similar experience. (My apologies if this has already been raised in an Issue). @olein in this comment.

After checking further, I realized that Style Book does something like that. In my opinion, Style Book should be the default option with a site preview alternative. Or at least highlight Style Book a bit more somehow. @foosantos in this comment.

Media & text block didn’t apply the border when I edited the image styles. The Media & text could be composed of sub-blocks to inherit the properties of a single image block like the Gallery block does now. @josvelasco in this comment

General usability 

Out of all of the usability feedback, a few themes emerged:

  • Changing just the H2 styles was hard to find, with folks going to the Styles > Blocks > Heading rather than Typography. 
  • Switching a sync status of a pattern after it’s been created proved to be nearly impossible to figure out. 
  • Writing in the Site Editor > Pages section has a few points of friction with the locked blocks experience. 

None of these tasks are necessarily niche to do yet prove to be tricky to navigate, with cumbersome steps or unclear UXUX UX 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. to navigate, like being unable to see the blinking cursor in a new page in the Site Editor.

New

Previous

Using the Style Book – I was hoping to be able to make changes to the H2 specifically while viewing a preview. It wasn’t made clear anywhere what the hierarchy of editing headings was to edit the ‘Heading’ element for styles that go across all headings, but could then make individual changes to different headings under Typography > Headings. @jordesign in this comment.

I typed into the Width box where it said Auto and wrote 100. The image is now smaller. I am wondering where the size drop down is? To select full, large, medium, small, thumbnail. Instead these options are inside the Resolution dropdown and that can be very confusing. @paaljoachim in this comment.

After checking for about 2-3 minutes, I really couldn’t find a way to change from Synced to Unsynced. Both for the original and duplicated. @foosantos in this comment.

I wanted to insert the table of contents block between the title and the first block, so I moved the cursor to the page title with the mouse and pressed enter, but could not move it to the content area. @olein in this comment.

After creating the page from the Site editor, clicking the Type / to choose a block does not make the vertical text cursor | start blinking. You see it only after you start typing or pasting something like the Google Doc’s content. @josvelasco in this comment

#fse-testing-summary

Test Chat Summary: 15 August 2023

On 15 August 2023 at 16:00 UTC<test-chat> started in #core-test.

Announcements 📣

  • Test Team at WCUS 2023: The WCUS 2023 Contributor DayContributor Day Contributor 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/. is less than a week away! Check out this post for information, and to share your questions and thoughts.
  • Admin Design Kickoff: The Design Team share early thoughts on how WP admin could be reimagined. Join the discussion to help shape this important part of WordPress.
  • What’s new in Gutenberg 16.4? (9 August): Download and test the latest feature updates in 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/ or can be cost-based plugin from a third-party, and get a peek at what the future holds for editor updates to WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..
  • FSE Program Testing Call #25: Let’s start from the beginning: Get in on this latest call for testing before the feedback window closes on August 23.
  • WordPress 6.3 “Lionel”: And finally, WordPress 6.3 was released last week. When submitting bug reports, please consider the official test report guidelines, and remember that the WordPress Beta Tester plugin has a handy “Report a Bug” button that works even if you’re running the 6.3 release version 🎉.

And we received one participant-submitted announcement:

Open Floor 💬

WCUS 2023 Contributor Day

Volunteers were asked to step forward to help facilitate the Test table, both in person and remotely on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.. @ironprogrammer volunteered to help lead in person at the event, but at the time of this writing there was no clear lead for coordinating contributors online in Slack. Contributors wishing to help are asked to comment below or raise their hand in Slack.

The remote session for Contributor Day is scheduled to begin at 2023-08-24 10:00 EDT in the #contributor-day channel. For more details, see the Test Team at WCUS 2023 post.

Test Team RepTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. Nominations

It was shared that the nomination process for the next Test Team Reps would begin soon, and team members were encouraged to help identify and nominate individuals who might be a good fit for the role (even themselves). [Ed. note: the 2023-24 call for nominations has been published.]

Next Meeting 🗓

The next scheduled meeting is on 22 August 2023 at 16:00 UTC for <test-triage> in #core-test.

Are you interested in helping write Test chat summaries like this one? Volunteer at the start of the next <test-chat> and earn some props!

Props @boniu91 for peer review of this post.

#fse-outreach-experiment, #meeting-notes

FSE Program Momery Makeover Summary

This post is a summary of the Momery Makeover call for testing for the FSE outreach program, the twenty-fourth effort. As always, I want to highlight those who helped to bring others along with them in this latest effort: 

  • InstaWP for allowing the outreach program to use their tooling for free, enabling more folks to jump into this call for testing and for more creativity in what we are able to test. 
  • Thank you to @bph and @ndiego for covering for two weeks of this call for testing when I was out on vacation. Your coverage made my break possible!

High level summary 

Since this call for testing took place during the early stages of an iterative process, several aspects of the feedback provided have already been swiftly addressed, thanks to ongoing development for WordPress 6.3. The relatively limited amount of bugs received and feedback aligning with feature development reflects a level of solidness in the direction of recent improvements. These improvements encompassed a range of features, such as the ability to rename menus in Site View, add template parts directly from the Site View, publish pages, and introduce additional interface enhancements to improve the template vs content editing experience. Notably, Style 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. proved to be significantly more intuitive compared to the code view available for Templates and Template Parts.

@paaljoachim shared a video of his experience going through the call for testing if you’re looking to get a sense of a test contributor’s experience in more detail:

Bugs 

The following bugs were all reported before this call for testing, reflecting known issues and showing a level of stability in the breadth of new features added to the Site Editor experience: 

Right now we can use a Post ExcerptExcerpt An excerpt is the description of the blog post or page that will by default show on the blog archive page, in search results (SERPs), and on social media. With an SEO plugin, the excerpt may also be in that plugin’s metabox. or Post Content. Post Content is the whole entire post in the Editor, but the post up to the “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.” on the front end. This is the behavior that I expect on the front end. But I would really like the Editor to not show the entire post! It just makes the Queries too long.

@antigone7 in this comment.

When I created a new page by way of creating a draft page. I found that a draft page creation option was missing if I tried to create it under the Menu 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. https://s.id/1Nh2y. However, it showed up if I tried to add a non-existent page link via the Navigation block https://s.id/1NgZg.

@franz00 in this comment.

Feature Requests 

Many of the feature requests tie in nicely with work either completed or currently underway (marked as “In the 6.3 board”). Across most of the following issues, the ability to access exactly what one wants in the Site Editor as a whole acts as a through point, whether when clicking “Edit Site” from the admin bar or trying to search for specific things with the Command Palette. Building into phase 3, the Template Part and Template revisions were seen as subpar in comparison to the new experience offered by Style revisions.

New: 

Previous:

I went out of the site editor and found the blog page in the Pages screen. Viewed it. Then clicked Edit Site. I expected to have the Home template open up but instead clicking Edit Site on the frontend will only open the Front Page template, and not the template related to the specific page I am on.

@paaljoachim in this comment.

I feel uncomfortable to roll-back template changes using the provided revision states located at the bottom of a particular template tab. The reason for this discomfort is that the revision states appear to be too raw. Since we rarely used the Code editor in building a site/pages in the Site Editor, seeing loads of HTMLHTML 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. block codes as reference points to roll back to feels unfamiliar within our current workflow.

@franz00 in this comment.

I had to go to the side menu to change the Page template why from the About page I didn’t see the option to Edit the template page. I found the option when I changed to Contact page by chance. The solution? I don’t know which is the better option. Maybe that open right side bar by default when we change a page or template. Or open and close to see that this appears here. Or in the wizard (I don’t saw the wizard).

@soivigol in this comment.

When typing in ‘page’ into the command centre – I didn’t expect ‘add new page’ to be the first item – rather than the ‘page’ template. Is this weighted in some way? It may just be me.

@jordesign in this comment.

General usability 

Part of the call for testing instructions included replacing a template part and creating a new menu, both of which caused some confusion. Each experience has improved with additional functionality added to the Site View for each respective section (Patterns, Menus). Outside of that, it’s worth noting that with Reusable blocks being consolidated into Patterns overall, a bug with Reusable blocks now has a wider spread impact. Currently, if you convert a set of blocks into a Pattern, the align full or align wide options are removed, leading to what feels like a broken experience by design since the alignment/flex position depends on the container. This is likely to come up as a broader piece of feedback. The Navigation block continues to receive feedback around the desire to have an easier and more consistent way to rename, regardless of where you are editing a menu (sidebar, in editor, in Site View). 

Finally, a few folks mentioned issues with the Post Content block that wasn’t replicable in later versions released after the call for testing. 

I think creating a reusable block or a template part from the Site editor should be possible. People using the Site editor probably will know the difference. I like the idea of making things clear, but I’m not 100% convinced. I prefer to have a place to be able to edit everything, including content, and the other just for content.

@josvelasco in this comment.

I first tried to “Replace the Footer”, and while it added a new footer in the Home Template, it had a different name in the Library > Manage All Template Parts. It didn’t change the existing Footer into the new one which was what I expected from “Replace Footer”. Later I realized that this did exactly what it was supposed to do – create a new Footer to use.

@antigone7 in this comment.

Create a reusable block. NB! Before creating a Reusable block I had a full width block. After the conversion to a Reusable block the alignment controls went away and it seems that the block went to a no alignment. How do I have the Reusable block in full width alignment?

@paaljoachim in this comment.

When I go to add three columns with the Columns block, I have the option to give the gap space between columns and I have the padding default left and right padding in each column. I am confused. I think that if I have gap option, should not have padding or reverse.

@soivigol in this comment.

When searching for pages in the command centre – there was a slight delay before they showed as results – but there was no visual indicator that anything was happening.

@jordesign in this comment.

#fse-outreach-program, #fse-testing-summary

FSE Program Rapid Revamp Summary

This post is a summary of the Rapid Revamp call for testing for the FSE outreach program, the twenty-third effort. As always, I want to highlight those who helped to bring others along with them in this latest effort: 

  • InstaWP for allowing the outreach program to use their tooling for free, enabling more folks to jump into this call for testing and for more creativity in what we are able to test. 

Shout out to @poojabhimani @oncecoupled @josvelasco @krupalpanchal as first time contributors for this call for testing. Expect a badge on your WordPress profiles for your contribution! 

High level summary 

Once more, bug wise, the call for testing was quite contained, reflecting a solid state in the experience considering how many new features are being built upon. Overall, the feedback mostly centered on iterating upon 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 previewing, improving template vs content editing clarity, confusion around which revision tool to use, and some more minor usability pain points, like poor drag and drop for the Details block or inconsistent triggering of the command center. There was plenty of positive feedback around how much smoother and cohesive the experience feels, with easier access to high level items thanks to the Site Editor additions of top level items in 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. for Pages, Styles, and Navigation.

The newly added details block is wonderful. I used it to create an FAQ section, which contained paragraphs, list of items, code, and quote blocks. When I rearranged the blocks, I found it incredibly easy to drag and drop them at any level of block hierarchy. This snap ability turned out to be a significant improvement for GB 15.8. Awesome…I noticed that we now have Pages in the Site Editor, which has made transitioning between editing page templates and editing page/post contents much more easy. However, I still feel the tension between them are still strong. This is mainly because the right sidebar of the template and page/post content still display their respective details and options.

@franz00 in this comment.

I love how everything is becoming more fluent.

@josvelasco in this comment.

@oncecoupled offered a recording of the experience that’s worth watching for an overall look at one person’s journey through this call for testing.

Bugs 

Despite a variety of new features to test, the bugs remained fairly tame in number and severity:

New:

Previous:

After adding content to About page and leaving the cursor in a paragraph block, when I click on the CMD + K, not open the command center. In this case, open a Search to add a link (the popup that appears when a link is inserted). I have to click in the parent block to work fine in the command center. @soivigol in this comment.

Feature Requests 

With a strong emphasis on block theme previewing and the feature itself being in an early state, numerous feature requests came up to polish that specific experience, alongside requests for more styling options for the Details block and an easier to find pathway for Style 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.. Block theme previewing is a game changer and the feedback provided here offers some solid iteration opportunities. 

New:

Previous:

Once I clicked on the Live Preview link and entered the Site Editor with the Navigation Sidebar (the dark grey menu area) on the left, I was expecting to be able to navigate between all the installed block themes and WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ block themes, similar to how the preview of classic themes work.

@poena in this comment.

General usability 

Outside of more specific issues, feedback was repeated around the confusion between editing a template and a page, which aligns nicely with the already shipped next call for testing that focuses on some improvements there. Beyond the following, two folks mentioned that the “Work with me” link showed up twice as there was a Page list block present in the Navigation menuNavigation Menu A theme feature introduced with Version 3.0. WordPress includes an easy to use mechanism for giving various control options to get users to click from one place to another on a site., causing the item to automatically be added after publishing. This caused some confusion and wasn’t intuitive to understand what was happening.

Adding “Work with Me” again, I figured out why it appears twice on the outside navigation. I also see it twice on any template or the Header template part after the “Work with Me” page is published, if I leave the Editor and open the Editor again. The menu in the Twenty Twenty-Three theme is a “Page List”. When I add the additional Item, it always adds below or outside of the Page List. I couldn’t see how to add it to the Page List. But then when the Work with Me” page is published, it’s automatically added to the Page List, but it’s also outside where it was added originally.

@antigone7 in this comment.

When I made some revisions to the site design and clicked “Reset to defaults,” I expected to be taken back to the default settings of the active style (grapes), but instead the Editor presented me with TT3 default theme.

@franzaurus in this comment.

I was confused initially that the style revisions are stored together, not individually by block. I guess I expected this because they were on different “pages” and because I’m used to existing post/page revisions being separate.

@oncecoupled in this comment.

Clicking into the Post Content group it acts just like 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. block. There is no page inserter but the inserter is at the bottom right of the Post Content. To me that feels strange. I expected to see the standard page inserter.

@paaljoachim in this comment.

With the Details Block I felt very frustrated. In a first moment, I tried to drag and drop to move the selected content to “Type / to add a hidden block”, but it’s impossible why the Details block is closed when lost the focus. I had to use the keyboard (CMD + X) to cut the content and paste it. Additionally, I tried to click in the arrow to close the block (by intuition), but don’t occur anything. Only close when lost the focus and open when get the focus.

@soivigol in this comment.

#fse-testing-summary