FSE Program Category Customization Summary

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

  • @courane01 for running a group testing session and reporting feedback.
  • @mimitips and @atachibana for creating a Japanese translation.
  • @piermario for creating an Italian translation.
  • InstaWP for allowing the outreach program to use their tooling for free, resulting in a much lower barrier to entry to help test and more room for creativity in coming up with the test itself. The features focused on for this test would have been much harder for individuals to set up without the tooling offered. 

Shout out to @clubkert @chopinbach @franz00 @osamunize @eboxnet for being first time contributors. Expect a badge on your WordPress profiles for your contribution!

High-level summary

As with prior calls for testing that centered on using the Query LoopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience., the current experience remains equal parts magical and clunky to configure exactly as one wants. When combined with the fact that when creating a new template, you’re met with an empty view, this call for testing mainly weights towards feature requests to ease the experience rather than outright bugs. Of all of what’s shared here, these are the most repeated items of feedback: unclear UX for how to get out of a locked block with headings & paragraph blocks, improve the verbiage around the Query Block settings and revise Query Block controls, edit site link should open the current template, and add fallback template content on creation.

The addition of starter patterns with locked blocks when creating a new post offered a peak at how streamlined and curated the experience can be while also revealing that more visual cues are needed to better understand what exactly is happening, particularly with locked blocks and layout controls. Most of what was discussed matches what has been previously found which underscores the impact resolving these repeated key problems will have.

For any designers and developers who want to see someone walk through the experience, I want to also mention the following videos to check out to see the call for testing in action:

To help ground the following feedback, here are some quotes about the overall experience to keep in mind: 

It’s so smooth and easy. The fact that you can create template overrides for specific categories is brilliant. I can’t wait to use that on a custom theme with custom blocks. Post patterns are also great!

@eboxnet in this comment.

So cool to see how far FSE has come and all of the improvements related to templates. We’re getting closer to the power of the template hierarchy of traditional themes!

@bgturner in this comment.

Selecting “categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging.” from the “Add new” template menu was unintuitive for me. That 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. implies to me that I could add many “category” templates, which is not true. That confused me as to whether I would be creating a “category” template for every type of category, or choosing which categories to assign the template to. When I realized I couldn’t add another “category” I figured out what was going on…I enjoyed playing around with the featured imageFeatured image A featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts. / cover interaction and the “inner blocks use full width” feature. At the end of the test it was also cool to see the category template in use. 

@arturgrabo in this comment.

Maybe I am too used to classic WordPress themes with 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. and footer pretty much always there. But it was very easy to create the template without a footer or header. Which obviously is cool that you can do that, but for whatever reason my brain was expecting header and footer to be auto included by default.

@chopinbach in this comment.

Confirmed Bugs

Previously reported:

New issues:

Locked heading blocks in the provided templates were super, duper frustrating. With normal heading blocks, if I press “return” at the end of a heading I get a paragraph block. With the locked headings I got stuck in the heading blocks. This felt like a major departure from typical interactions in the block editor.

@arturgrabo in this comment.

Feature Requests 

As reflected in the high level summary, most feature requests have been mentioned before with a particular focus on various refinements, like adding a “view site” link in the editor or renaming “default template” in the template panel to match what one would see in the template list. While these are listed as feature requests, the lack of each adds up quickly creating an experience that accomplishes what you want but not without repeated moments of confusion. 

New issues:

Previously reported:

Another thing that feels a bit bumpy is when saving the template, there’s no way to quickly access your site again.

@luminuu in this comment.

It sometimes feels like I am “trapped” in the site editor without an easy way to get back to the dashboard. One suggestion would be having a dropdown to select whether I want to go back to the dashboard vs. see Site/Template/Template part editor. Similarly, I sometimes wish there was a “view site” option from the site editor. Again, I feel trapped.

@clubkert in this comment

I would prefer to have the same experience each time. It’s confusing to suddenly see patterns when I was expecting blocks. I would like to always see blocks first with a button or such to switch to the patterns.

@antigone7 in this comment.

I found that a different role will have a slightly different saving experience. Under administrator role, after I clicked publish for a new event or a new event recap, a suggestion menu to assign a category appeared. But this didn’t happen under an author role. So, author will have to go back to post tab, if she just remembered that she hasn’t assigned an event category to the post.

@franz00 in this comment.

It works very well, as long as you remember to select “Inherit query from template” when you add the Query Loop. (I forget sometimes.) So I had different templates for one category over all the others.

@antigone7 in this comment.

So I would prefer if it said “Template Single” instead of “Template Default Template”. Or maybe “Template Single (Default)”, though I don’t see how being shown Single is the default is really helpful at that moment.

@robglidden  in this comment.

General Usability

Feedback from this experience centered heavily on the Query Loop block and template creation experiences, rather than using block locking or post patterns or the featured image in the Cover block, despite those being newer features. As with every call for testing where a new template is being created, the experience of being dropped into an empty template to build from scratch is underwhelming. Determining when and how to use various settings for controlling both layout and query options continues to be a major 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. This will likely be eased when better defaults are available (Query loop block automatically added with “inherit query by default” set to true) rather than needing to create more from scratch, even with patterns. 

Please ensure to read the quotes below as they help give context to what’s shared below as simple issues. 

I really liked the “Inner blocks use full width” option, but I could not figure out what the “Wide” setting did. Changing the value didn’t do anything, and both the icon and description were unclear.  

@arturgrabo in this comment.

In the template editor, I was expecting the center-top dropdown (which said home initially) to allow me to easily switch to different templates.

@clubkert in this comment.

When using the query loop block, it isn’t immediately obvious how to view other design options. One suggestion would be to have the grid view displayed by default and allow someone to choose the single view as an option.

@clubkert in this comment.

I don’t mind curated blocks or locked blocks at all… I only wish that the visual editor will prepare me (or the common user as the intended user of a bespoke theme) when dealing with curated blocks…Perhaps giving the curated block a different color? Or any sign that it is not your usual kind of block?

@franz00 in this comment.

When selecting an “Event Recap” pattern, the caption was not visible in the preview because the pattern was too long vertically, and had to scroll to confirm it.

@osamunize in this comment.

Editing the layout of a group is a little tricky. I think getting more comfortable with 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. would help, but having additional feedback around what is selected and where I can move things would be helpful.

@bgturner in this comment.

This blur is too strong/too much contrast. It would be helpful with a much more subtle blur. As the current background blur is exhausting on the eyes.

@paaljoachim in this comment.

The Inherit query from template toggle is not obvious for the average non-dev to enable.

@courane01 in this comment.

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

X-post: Test Team Update: 26 July 2022

X-post from +make.wordpress.org/updates: Test Team Update: 26 July 2022

X-post: Call for Testing: WordPress for Android 20.4

X-post from +make.wordpress.org/mobile: Call for Testing: WordPress for Android 20.4

X-post: Call for Testing: WordPress for iOS 20.4

X-post from +make.wordpress.org/mobile: Call for Testing: WordPress for iOS 20.4

X-post: Rollback Feature: Testing Call to Action

X-comment from +make.wordpress.org/core: Comment on Rollback Feature: Testing Call to Action

X-post: Call for Testing: WordPress for iOS 20.3

X-post from +make.wordpress.org/mobile: Call for Testing: WordPress for iOS 20.3

X-post: Call for Testing: WordPress for Android 20.3

X-post from +make.wordpress.org/mobile: Call for Testing: WordPress for Android 20.3

FSE Program Pattern and Template Part Usability Testing Summary

This post is a summary of the usability testing done as a joint collaboration between design contributors and FSE Outreach program participants. For starters, big thank you to everyone who contributed both as designers and participants. Having watched each of the following videos, I’m really struck by how seriously everyone took this effort and how much kindness existed in each interaction, even when sharing tough feedback or stumbling over the experience. This was an experiment and it was a success because of how each of you engaged.

Before digging into the videos themselves, I want to note that I had to scale down many, if not all, of the videos in order to get them to upload properly to Make Test. For full access to the highest quality recordings, you can view them in this Google Drive folder that was set up for this series of tests. Separately, the intent was to have an equal split between both flows but that wasn’t always followed for each participant.

Finally, everyone who participated, whether as a design contributor or participant, will get a Test Contributor badge added to their profile as soon as possible if you don’t already have one!

Overall takeaways

High level summary

Across each experience, the following commonalities stood out:

  • Lack of awareness around List View and, even for those who do use it, frustration around dragging and dropping items.
  • Desire for more visual indicators of where content would be added, whether when adding patterns or trying to create a new template part without it being baked inside another one. This caused repeated placing of patterns within patterns or template parts within template parts.
  • Missing knowledge around patterns, including discovering them to begin with or finding how they are sorted by categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging..
  • Great difficulty using the navigation blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience., whether to do something more advanced like create a different experience on mobile or as simple as understanding how to add items to the menu based on the current placeholder state.
  • Easier to replace a template part while creating from scratch proved painful, even if folks went into the isolated template part mode. This is due to things like confusion around building simple layouts, details around setting the correct template part area, the impact of duplicating template parts, and restrictions in what can be done to edit a template part in isolated mode.
  • Clear confusion around the various sidebars, where to find settings, what impacts a site globally (like Styles), etc.

Bugs

Feature requests

Template Part Testing

Level listed under each video reflects a self reported level of comfort with FSE with 1 being not all familiar and 10 reflecting expertise. For any listed as N/A, the participant was not asked.

Video 1

  • Level: 2-3
  • Didn’t use list view.
  • Replaced the template part but wasn’t able to create a new one from scratch.
  • Navigation block was identified as a major pain.
  • Went back to the overall template list to apply the template part to another template but it felt like the wrong place even though it was the right spot to go to (around 7 minutes in).
  • Unable to complete the final task of applying a template part to another template.

“It’s definitely different than the WordPress I’m used to. I’m more used to operating through the dashboard than a visual editor which I think is why I was unsure of what I was doing. Otherwise, as far as changing the 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., was absolutely quick and painless. Once I learned what some of the other options did it was an easy way to align it how I wanted it to.”

Video 2

  • Level: 6 or 7.
  • Didn’t use list view.
  • Created a template part within the editor to start.
  • Created a template part within a template part within a template part, causing the final template part to be smushed within the editor.
  • Left to go to template part focus mode to try to add navigation since the + button for the new template part looked so different than what he was used to (5:10-6:00).
  • The navigation block placeholder felt unusable and it wasn’t clear how best to add items to it with the + button being so far removed from the experience.
  • He tried to use “Manage menus” thinking that would allow for a way to add items only to reach a dead end.

Video 3

  • Level: 7 or 8
  • Didn’t use list view, except with the navigation block’s list view.
  • Went to template parts > add new to add a new template part.
  • Couldn’t edit background or basic colors in isolated template part mode. Instead he used Styles which changed the whole site, not just the template part without realizing it would do that (around 6 minutes). This touches on a closed issue.
  • Isolated template part mode has an easier flowFlow Flow is the path of screens and interactions taken to accomplish a task. It’s an experience vector. Flow is also a feeling. It’s being unselfconscious and in the zone. Flow is what happens when difficulties are removed and you are freed to pursue an activity without forming intentions. You just do it.
    Flow is the actual user experience, in many ways. If you like, you can think of flow as a really comprehensive set of user stories. When you think about user flow, you’re thinking about exactly how a user will perform the tasks allowed by your product.Flow and Context
    to see bounds of a template part, assign an area, etc but then has huge limitations in terms of customization.
  • Wants the ability to create a sticky header and a way to add all new pages to the navigation block.

“It’s a little bit confusing, what you’re really changing and where it works…It’s a lot of understanding that’s needed. I think for an ordinary user it’s very difficult.”

Video 4

  • Level: N/A
  • Used List View.
  • Went back to template parts immediately to create a new one and noted that he usually creates template parts with code.
  • At first, duplicated the template part, which runs into this issue. Later, he made a template part by converting a group block using list view. 
  • He found the header within a header for Twenty Twenty-Two confusing to navigate.
  • He shared that he uses a hack where he adds two navigation blocks: one with mobile always on and one with it always off. From there, will mobile always on, uses custom CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. so it only displays on small screen sizes. 
  • New header template part was only available when adding a generic template part and not in the Replace modal. This is because when he originally set up the template part (6:54), he selected general rather than header. He couldn’t find a way to assign the right area for the template part (change from General to Header) within the isolated template part mode.

“This is something that is really annoying to me in the full site editor… moving blocks into different groups…I find it very hard to get to the correct hierarchical level…it’s very flimsy and hard for me to get to the right place.”  

“The navigation block for me is really weird to me. If I click on Manage Menus, it’s empty. There’s nothing to do. I really don’t understand it.” 

Video 5

  • Level: N/A
  • Used List View.
  • Went back to the list of template parts to create a new template part and correctly assigned the area.
  • Ran into this issue where the navigation toolbar overlaps with the experience of adding a link, making it nearly impossible to figure out what you’re doing.

“The more helper things you have open (ie: sidebars) I think sometimes it could be hard, especially with full site editing. So maybe you need to use a big screen or remember to close out some of the sidebars”.

“Being able to go through the block navigation (list view) is where I can usually find out if I put something in a container that didn’t belong in that container”.

Video 6

  • Level: N/A
  • Used List View.
  • Went back to template parts and then edited a current header, rather than creating a new one.
  • Converting page list items in the navigation was confusing in order to edit each link.
  • Ran into the experience of menu items merging when deleting, which has been reported before and was noted as intended functionality.
  • When adding a template part into template part focus mode, a template part was not created, matching this currently open issue. In theory, this should create a template part within a template part.

Video 7

  • Level: 8
  • Used List View.
  • Used replace to switch out template part.
  • Use of group within a template part feels really odd to him. Feels like it’s only there to help control the layout but feels unnecessary in general. 
  • Struggled to drop something into a cover block that had a row block inside of it. It wasn’t clear how to add something else to the row block.
  • Finds it limiting which blocks are able to be added to the navigation block. Wants mega menu options and ways to display things based on screen size. 
  • Expressed a desire for a middle ground between solely relying on what’s defined by a theme vs getting into the nitty gritty details with Styles.

“I have trouble a lot of times with the list view and getting blocks precisely where I want them to be.”

From around 3:25 in the video

“I don’t make my own headers. Just because I found it completely frustrating and I rely on templates to make all my headers that come with the themes because I’ve found I just can’t manipulate it enough no matter how much time I spend on it. I can’t make things that look better than the pre-made templates so I only do small changes from the pre-made templates… Headers are incredibly challenging. I just don’t know how to do it.”

Video 8

  • Level: 1 or 2
  • Didn’t use List View. 
  • Icons for theme blocks feel very confusing and don’t feel similar to other software he uses. 
  • Used replace to switch template part out but, because there is a header within a header for Twenty Twenty-Two, this was a bit confusing.
  • He wanted to access different header options using the transform menu. Noted the feedback in a related issue.
  • Wanted to duplicate the header at first to have a base to start with which would have run into this problem with duplicated headers.
  • Eventually, went into the isolated template part mode where he found the slash inserter to be “very tech-y”.
  • Ran into an issue in isolated mode where the toolbar blocks the current blocks.
  • Struggled to understand that he needed to select the overall navigation block to customize it in the way he wanted as he expected to find customization options within individual navigation links.
  • When asked about saving, he expressed that he expected autosave to work/be happening.

“As a kind of a first time user of the interface, I found this very difficult. It doesn’t remind me of anything I’m used to with other applications I’m using…it’s just not easy for a novice…This was a bit of a learning curve just to get to a header…I was quite uncertain on my choices. I wasn’t sure if I was doing the right thing.”

Pattern Testing

Level listed under each video reflects a self reported level of comfort with FSE with 1 being not all familiar and 10 reflecting expertise. For any listed as N/A, the participant was not asked.

Video 1

  • Level: 6-7
  • Didn’t use List View. 
  • When asked to add a pattern with columns, just added the columns block itself.
  • She didn’t know that you could filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. by columns for patterns and remarked that “it’s not obvious they are columns” when glancing at patterns.
  • Only used patterns from the Inserter.
  • Found the layout settings to be very confusing and px dropdown to be very small/hard to see.
  • Wanted to be able to create a new post/page from within site editor rather than needing to go to the post editor.

Video 2

  • Level: 8
  • Used List View.
  • Repeatedly felt that visual cues were missing, especially when wanting to see what was a whole pattern rather than a piece of one.
  • Didn’t use drag and drop as it’s not clear where a pattern might go.
  • Added a pattern by accident into 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. causing it to appear throughout the loop rather than outside of it.
  • Noted that the font size labeling felt very confusing with the different numbers. There’s an effort underway to improve this experience with “t-shirt” sizing.
  • Wants consistent dimension controls.

“My main problem with the editor is that I don’t always get visual cues on where I can add blocks or patterns.”

Video 3

  • Level: 6
  • Didn’t use List View until prompted.
  • When asked to add a pattern with columns, proceeded to add a Columns block rather than adding a pattern. Later, it was clear that this was due to a lack of awareness around patterns in general.
  • Tried repeatedly to find patterns in the quick inserter by searching “patterns” leading to this new issue.
  • Participant noted she has tried to make at least 10 WordPress sites and regularly struggles with getting the layout to look correct across different screen sizes. 
  • In List view, expected to find mover controls rather than relying on drag and drop and didn’t understand why they weren’t there.
  • The browser/site randomly crashed (unclear why).
  • Noted that she wanted autosave.

Video 4

  • Level: N/A
  • Used List View and noted that she “always has it open”.
  • Once pattern was added into the site editor it was hard to reposition it where she wanted it to go.
  • Wanted a way to change hover colors for buttons.
  • Learned about patterns from Nick Diego’s SLS about patterns. Otherwise, did not know they exist and doesn’t feel anything clarifies that they are there.

“Having to go to the + sign and then browse all and that’s the only way I know how to get to patterns is super cumbersome” 

Video 5

  • Level: 5
  • Used List View. 
  • Drag and drop totally didn’t work as expected for adding a pattern. Tried to place it within a query loop and the pattern ended up below it in an unexpected way. Realized later that it was a query loop and it made sense that the pattern was placed below but it proved confusing at the time.
  • Added a query loop pattern to the template and was expecting from a user’s point of view to be able to edit the text. The experience felt broken when he wasn’t able to until he realized it was a query loop which he was familiar with. 
  • Lack of feedback in being unable to edit the query loop content was jarring. Kept wanting to edit the content itself. 
  • Felt that the block settings are very hidden for deeper customization and that it’s hard to know how to get to those options when looking at just the editor itself. 
  • Added another pattern as an example that ended up chunkily within another pattern.

“I was thinking I could drop it right above this text…when I grabbed it I saw the hand icon so I knew it was draggable. I didn’t have the clearest ever – I didn’t see like a line showing me it’ll drop here. I didn’t think it would work… it dropped below what I was expecting.” 

“I still am not totally sure if I went and looked at the page on the front end what would be there”.

Noted at the very end of the test.

Next Steps

Going forward, I’ll look to facilitate this kind of usability testing experience again, especially since this time I had to turn folks away.

#fse-usability-testing, #fse-usabilty-summary, #usability-testing

Week in Test: 11 July 2022

Welcome back to Week in Test, where contributors of any skill level can find a handy list of links and opportunities to start testing WordPress. Join the Test Team in #core-test for questions and thoughtful discussion.

Did you know that contributions with the Test Team are also a fantastic way to level up your WordPress knowledge and skill? Dive in to contribute, and gain coveted props 😎 for a coming release.

Reproduction Testing 🔁

Who? Any contributor.
Why? It is helpful to show an issue exists for other users in order to move a ticket forward for patching.

The following new tickets are awaiting review, and need testers to attempt to reproduce the reported issue (aka “repro”), and then provide a reproduction test report with the results:

  • #56169: 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. menu navigation in FSE visibility issue.
  • #56178: Mobile menu link in FSE visibility issue.
  • #56184: register_block_type does not recognize ancestor 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. setting in block.json.

Patch Testing 🩹

Who? All contributors (not just developers) who can set up a local testing environment.
Why? It is necessary to apply proposed patches and test per the testing instructions in order to validate that a patch fixes the issue.

The following tickets have been reviewed and a patch provided, and need testers to apply the patch and manually test, then provide feedback through a patch test report:

  • #56167: Post title block alignment with RTL languages in Twenty Twenty theme.
  • #54677: Alternate option names for default widgets cause unnecessary DB queries.
  • #51812: Third (and final) step in removing jQuery Migrate 3.3.x from coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..

And as this week’s bonus 🌟, here are some tickets that are almost there and need a little more exposure to testers:

  • #54394: Add functions for form required field indicators and messages.
  • #51170: Update FTPFTP FTP is an acronym for File Transfer Protocol which is a way of moving computer files from one computer to another via the Internet. You can use software, known as a FTP client, to upload files to a server for a WordPress website. https://codex.wordpress.org/FTP_Clients. updates to be RFC 959 compliant. Needs thorough testing across a variety of server environments.
  • #53816: Refactor widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. read/write logic.

PHPUnit Tests 🛟

Who? Any QA or PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. http://php.net/manual/en/intro-whatis.php. developer contributors who can (or are interested in learning how to) build automated PHPUnit tests.
Why? Automated tests improve the software development feedback loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. for quality and backward compatibility.

The following tickets need PHPUnit tests built to accompany their respective patches:

  • #56068: Send HTTPHTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. headers after querying posts in WP::main().
  • #21650: Replace serialize() with print_r() in stats() function.
  • #56180: Add header_image filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. to header_image() function.

Read/Watch 📖

Meetings This Week 🗓

#build-test-tools, #core-test

FSE Program Testing Call #15: Category Customization

This post is the fifteenth call for testing as part of the Full Site Editing Outreach Program. For more information about this experimental program, please review this FAQ for helpful details. To properly join the fun, please head to #fse-outreach-experiment in Make Slack for future testing announcements, helpful posts, and more will be shared there. 

Overview

This call for testing focuses on what, on the surface, feels like a common task you might have done in the Site Editor: creating a new template and applying it to some posts. As you go through the tasks though, the way the following features align will hopefully surprise you and show you a greater layer of depth in the site editing experience. 

More template options

Expanding what templates can be created from the Site Editor continues to be a high priority with a number of new options to explore. This test in particular will focus on the general CategoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. template but stay tuned for Gutenberg 13.7 (the next version) when you’ll be able to create a template for a specific category. This means you could have a different template for all your posts categorized as “WordPress” for example! Depending on when you participate in this call for testing, that means you might have access to this new option to explore too. 

New template picker design

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/ 13.6 offers a new, streamlined template picker design that helps both conserve space and more naturally align with other post details:

Visual of the new template part selection experience.

More descriptive layout controls

If you’ve been left confused by every mention of “Inherit Default Layout”, the recent update to the description of this feature will be welcomed

(Semi locked) Starter patterns when creating a new post

Both the patterns and the fact that various blocks are locked are all part of some of the features one can use to curate the editor experience. Even though these might not be incorporated out of the box with a new WordPress site, they are still important to test so that those who do rely on them have a great experience. In this case, the test goes through the new starter patterns that were first introduced in WordPress 6.0 with pages and are now available for any post type with Gutenberg 13.6. As a bonus, a few blocks are locked in each pattern to help explore more granular ways to control the experience. 

Using a featured imageFeatured image A featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts. in a 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.

Another feature from WordPress 6.0 is making an appearance in this test, alongside some subsequent improvements to the placeholder when the featured image is in use and the easier discoverability of the option itself in the media replace option.

Visual of the cover block feature where you can use the featured image.

Testing Instructions

Helpful Hint: As you go through this test, you might find the List View helpful while navigating between content.

Note on InstaWP

The folks behind InstaWP have granted the outreach program an account that we can use for these calls for testing. This means if you want to skip setting up your own test site and instead use a temporary one, you can do so. When you set up a site with InstaWP, no email addresses will be collected which means you’ll need to save the link to access the site again. Big thank you to the InstaWP team! 

Launch test site or setup test environment

To use a prebuilt test site: 

  1. Open this link only once: https://app.instawp.io/launch?t=fse-fifteenth-call-for-testing Please do not repeatedly open this link as it creates a new site each time and there’s a limit of 50 sites that can be created. 
  2. This will launch a site for you to use for up to 24 hours. Select “Access Now” to log in to the wp-admin dashboard. 
  3. Save the link to your site so you can access it again during the test. 
  4. Navigate to Appearance > Editor (betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process.). This will automatically open the site editor to the template powering your homepage. 

To set up your own test site: 

  1. Have a test site using the latest version of WordPress. It’s important this is not a production/live site. 
  2. Install and activate the Twenty Twenty-Two theme by going to Appearances > Themes. Add a patterns folder to your Twenty Twenty-Two theme and add these two files: new-event-announcement.php and event-recap.php. Here’s more information about this functionality. 
Visual of what the files for your test site should look like with a new patterns folder and two patterns placed within it.
  1. Install and activate the 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 from Plugins > Add New. If you already have it installed, make sure you are using at least Gutenberg 13.6.
  2. From there, navigate to Appearance > Editor (beta). This will automatically open the site editor to the template powering your homepage. 

Create a category template 

  1. Once there, open the W menu > Templates. This will open up the template list. If you have a set site icon, you will see that instead of the big W. 
  2. Choose “Add New” > Select “Category”. This will open up a new blank template. 
  3. As you’d like, add any 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. or Footer template parts. You can do this by searching directly for “Header” or “Footer” or by adding the template part block and selecting the one you’d like. 
  4. Add a 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 and select whichever design option you’d like.
  5. While selecting the Query Loop block, open the block settings 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. and ensure the option “Inherit query from template” has been selected. This will ensure that the right posts appear. 
  6. Customize the template further as you see fit keeping in mind that this template will be used when viewing a specific category of posts. When done, hit save to publish the new template.

Create two new posts to explore patterns

  1. Open the W menu (if you have a set site icon, you will see that instead) and select “Dashboard” to return to your wp-admin dashboard.
  2. Under Posts > Add New to create a new post. 
  3. Select the “New Event Announcement” pattern and fill in details as you’d like. For inspiration, in your post lists, there’s an example post titled “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. Museum” using this pattern. Note that a few blocks are locked! Explore what this experience is like (lock more blocks, unlock current ones, etc).
  4. Set a featured image and notice how it also appears in the Cover block of the pattern. Feel free to customize this further.
  5. Before publishing, open the post settings, assign the category “Events”, and under “Template” feel free to select a different template with the new pop over interface.
  6. Return to the dashboard and create another new post.
  7. Select the “Event Recap” pattern and fill in details as you’d like once more. For inspiration, in your post lists, there’s an example post titled “WordCamp Museum Recap” using this pattern. Note that a few blocks are locked! Explore what this experience is like. 
  8. Under the “Attendees” heading, select the Group block that contains the various names. Open the sidebar settings and, under “Layout”, explore the “Inner blocks use full width” option and customize to your liking (change colors, font size, dimensions, etc).
  9. Before publishing, open the post settings, assign the category “Events”, and under “Template” feel free to select a different template with the new pop over interface.

View your category template

  1. Once done, view the “Event” category to see your template and posts on full display. You can find the category template by going to yoursiteurl.com/category/events/

What to notice:

Remember to share a screenshot of what you created if you’re up for it!

  • Did the experience crash at any point?
  • Did the saving experience work properly? 
  • What did you find particularly confusing or frustrating about the experience?
  • What did you especially enjoy or appreciate about the experience? 
  • What would have made this experience easier?
  • Did you find that what you created matched what you saw on your site?
  • Did it work using Keyboard only?
  • Did it work using a screen reader?

Leave Feedback by August 1st, 2022

#fse-outreach-program, #fse-testing-call