Title: 2021 – Make WordPress Test

---

#  Yearly Archives: 2021

 [  ](https://profiles.wordpress.org/annezazu/) [annezazu](https://profiles.wordpress.org/annezazu/)
4:47 pm _on_ December 21, 2021     
Tags: [fse-hallway-hangout ( 31 )](https://make.wordpress.org/test/tag/fse-hallway-hangout/),
[fse-outreach-program ( 110 )](https://make.wordpress.org/test/tag/fse-outreach-program/)

# 󠀁[Hallway Hangout: Let’s talk about WordPress 6.0](https://make.wordpress.org/test/2021/12/21/hallway-hangout-lets-talk-about-wordpress-6-0/)󠁿

This is a summary of a Hallway Hangout that was wrangled in the [#fse-outreach-experiment](https://wordpress.slack.com/archives/C015GUFFC00)
channel as part of the [FSE Outreach Program.](https://make.wordpress.org/test/handbook/full-site-editing-outreach-experiment/)
The intent was to have a fun and open ended chat about what we each would like to
see for WordPress 6.0 as 5.9 continues to take shape. This was not a call to make
decisions or set priorities as a result but just to swap ideas, review various issues,
and more. Overall, this chat really showed how the foundation being set for 5.9 
is leading to great excitement about future WordPress releases and the features 
that might come.

As a friendly reminder, [please help test WordPress 5.9](https://make.wordpress.org/test/2021/11/30/help-test-wordpress-5-9-features/).

**Attendance:** Thanks so much to everyone who took the time to join. It was so 
neat to see folks before the year ends. cc [@poena](https://profiles.wordpress.org/poena/)
[@fabiankaegy](https://profiles.wordpress.org/fabiankaegy/) [@overclokk](https://profiles.wordpress.org/overclokk/)
[@courane01](https://profiles.wordpress.org/courane01/) [@anoopd](https://profiles.wordpress.org/anoopd/)
[@thakurtech](https://profiles.wordpress.org/thakurtech/) [@annezazu](https://profiles.wordpress.org/annezazu/)
[@azhiyadev](https://profiles.wordpress.org/azhiyadev/)

**Video Recording:**

**Topics Covered:**

 * We started the call talking about responsive controls after [@thakurtech](https://profiles.wordpress.org/thakurtech/)
   shared some great insights around the current experience with clients missing
   the ability to have more options, specifically with the columns blockBlock Block
   is the abstract term used to describe units of markup that, composed together,
   form the content or layout of a webpage using the WordPress editor. The idea 
   combines concepts of what in the past may have achieved with shortcodes, custom
   HTML, and embed discovery into a single consistent API and user experience.. 
   [This overview issue](https://github.com/WordPress/gutenberg/issues/34641) was
   identified as a great place to share this kind of feedback.
 * A lovely and well deserved shoutout was giving to [@poena](https://profiles.wordpress.org/poena/)
   about all of her excellent work with https://fullsiteediting.com/.
 * Keeping up with WooCommerce changes related to FSE were mentioned with the best
   advice being to check out the [WooCommerce GitHub repo](https://github.com/woocommerce/woocommerce)
   and reviewing their latest changelogs.
 * We briefly chatted about the [Comments Loop block](https://github.com/WordPress/gutenberg/issues/34994)
   and excitement for more robust comment abilities for 6.0, including integrated
   patterns.
 * The current experience of the Layout settings were brought up as an area that
   refinement and iteration is needed, from [how it’s currently named/described](https://github.com/WordPress/gutenberg/issues/31950)
   to how to make it easier for folks to find.
 * The need for having more consistency with the [“Preview Site” feature](https://github.com/WordPress/gutenberg/issues/29398#issuecomment-988859368)
   and/or implementing a [Browse Mode ](https://github.com/WordPress/gutenberg/issues/23328)
   was then discussed after [@paaljoachim](https://profiles.wordpress.org/paaljoachim/)
   raised the topic ahead of time. Folks are going to expect similar functionality
   for Preview as the Post Editor and we still see folks viewing the front end of
   their site to see how changes are impacting the site, rather than being able 
   to rely on what’s in the Site Editor. There was also a request to be able to 
   drag around the current Preview in the site editor similar to what one can do
   with the template part focus mode. This is under discussion!
 * This led to a discussion around both [expanding what templates](https://github.com/WordPress/gutenberg/issues/37407)
   can be created and unifying the experience with template editing mode and the
   site editor. For example, folks already are wanting the ability to add a custom
   template for a specific categoryCategory The 'category' taxonomy lets you group
   posts / content together that share a common bond. Categories are pre-defined
   and broad ranging. of posts and there’s not a way to do that now with 5.9.
 * Generally speaking, there are still some discrepancies between the post editor
   and site editor. It’s a tough balance to strike to have both familiar tooling
   in both while also making it clear how the changes in the Site Editor are more
   global.
 * [@fabiankaegy](https://profiles.wordpress.org/fabiankaegy/) brought up how in
   the post editor the break points are no longer applying correctly due to post
   editor not being iframed yet! This is a big issue for custom builds when list
   view and 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. are open so there’s excitement for iframing coming to the post editor 
   in the future.
 * We then dove into how the post editor experience might be improved for 6.0 by
   looking at an exploration from [@shaunandrews](https://profiles.wordpress.org/shaunandrews/)
   on [improving the post editor sidebar](https://shaunandrews.com/2021/09/the-wordpress-editor-document-status-and-visibility/).
   A suggestion was made to include auto-detection of post formats!
 * We had a fairly lengthy discussion about all things 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](https://codex.wordpress.org/The_Loop)
   block including everything from wanting to see expanded functionality, more patterns,
   more variations, a revamped building experience, etc. This included talking about
   how folks who aren’t as technical might interact with it (likely through patterns
   and variations).
    - [Consider creating a builder for the Query Loop block.](https://github.com/WordPress/gutenberg/discussions/35760)
    - [Add filters to extend the block](https://github.com/WordPress/gutenberg/issues/36504)
      and help prevent the need to fork it.
    - Add new functionality like no results found, sticky post, etc.
    - Change the category of the Pattern inserter to be more user friendly rather
      than relying on “Query”.
    - Consider having a welcome guide for the block.
    - Make it easier to change the number of posts displayed and clarify the concept
      of “offset”.
 * [We touched on the Webfonts API](https://github.com/WordPress/gutenberg/pull/36394)
   and the excitement there to see this implemented, especially so testing doesn’t
   have to happen in three editors (amongst other things).
 * We dove deep on the topic of block theme switching, being able to schedule changes,
   have style variations, and the possibility of a style directory! This included
   checking out [@critterverse](https://profiles.wordpress.org/critterverse/)‘s 
   design [explorations on block theme switching](https://critterverse.blog/2021/10/19/block-theme-switching-mvp/)
   and [style variation switching](https://github.com/WordPress/gutenberg/pull/35619).
 * This led to a big topic around naming! What are users typing into Google already?
   What should folks call this experience far into the future? How can we communicate
   these concepts now? We had more questions than answers. From [@overclokk](https://profiles.wordpress.org/overclokk/):“
   About the editor naming, I made a video for Italian people to explain the difference
   about content editor, template editor and site editor because it is not so easy
   to understand which one to use when do things. Most of the search are about “
   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/](https://wordpress.org/gutenberg/)
   editor”.
 * The oEmbed block was briefly discussed in terms of is needing accessibilityAccessibility
   Accessibility (commonly shortened to a11y) refers to the design of products, 
   devices, services, or environments for people with disabilities. The concept 
   of accessible design ensures both “direct access” (i.e. unassisted) and “indirect
   access” meaning compatibility with a person’s assistive technology (for example,
   computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) improvements.
   I’m going to track this down.  
 * The modal for the pattern explorer was raised as a topic with an idea around 
   whether there could be more visual overlap between the modal and the directory
   itself potentially. Either way, it would be excellent to have better organization
   for 6.0.
 * We ended chatting about the [WordPress Photo Directory](https://wordpress.org/photos/)
   and possible future integration. It’s unlikely for 6.0 just due to the lack of
   photos but there was lots of excitement around the possibilities of integration
   in the future regardless! Consider this a nudge to [submit your photos](https://wordpress.org/photos/submit/)(
   especially cat photos!).

[#fse-hallway-hangout](https://make.wordpress.org/test/tag/fse-hallway-hangout/),
[#fse-outreach-program](https://make.wordpress.org/test/tag/fse-outreach-program/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Ftest%2F2021%2F12%2F21%2Fhallway-hangout-lets-talk-about-wordpress-6-0%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/annezazu/) [annezazu](https://profiles.wordpress.org/annezazu/)
11:32 pm _on_ December 16, 2021     
Tags: [fse-outreach-program ( 110 )](https://make.wordpress.org/test/tag/fse-outreach-program/),
[fse-testing-summary ( 27 )](https://make.wordpress.org/test/tag/fse-testing-summary/)

# 󠀁[FSE Program Site Editing Safari Summary](https://make.wordpress.org/test/2021/12/16/fse-program-site-editing-safari-summary/)󠁿

This post is a summary of the eleventh call for testing for the experimental FSE
outreach program. Once again, I want to highlight the fantastic broader contributions
surrounding this call for testing that enabled even more people to be a part of 
this work: 

 * [@atachibana](https://profiles.wordpress.org/atachibana/) launched a [Japanese translation of the call for testing](https://ja.wordpress.org/team/2021/11/12/2381/).
 * [@piermario](https://profiles.wordpress.org/piermario/) shared an [Italian translation of the call for testing](https://it.wordpress.org/team/2021/11/25/chiamata-per-il-test-del-programma-fse-11-un-safari-nella-modifica-di-un-sito/).
 * [@courane01](https://profiles.wordpress.org/courane01/) ran a lovely group testing
   session with GoDaddy.

Shout out to the following folks as first-time contributors to a call for testing:
[@colorful-tones](https://profiles.wordpress.org/colorful-tones/) [@anjchang](https://profiles.wordpress.org/anjchang/)
[@mburridge](https://profiles.wordpress.org/mburridge/) [@paulbigai](https://profiles.wordpress.org/paulbigai/)
[@luminuu](https://profiles.wordpress.org/luminuu/). Get excited – you now have 
a testing contributor badge on your WordPress profile! Thank you too to [@piyopiyofox](https://profiles.wordpress.org/piyopiyofox/)
for kindly reviewing this post.

**High-level summary**

Here’s what a few folks had to say about the experience that can help frame the 
following more specific feedback. Overall, folks found the exploration to be easy
enough to use with some minor enhancements and a few surprises. However, once most
folks got beyond the basics, they found pitfalls in understanding how things might
work together and how to accomplish different, slightly more complex tasks. This
included everything from wanting more granular control of different link states 
with the Styles system (hover, active, etc) to confusion around how to change the
width settings for new templates. This was the first time the Styles system was 
explored in a call for testing as well and, beyond a 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. issue mentioned by four folks and some feature requests, the
feedback was generally uneventful and positive. 

> _This very much feels like where the state of 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. and site editing is
> overall. Many pieces are exceptional, but after digging beneath the surface, you
> find that you need workarounds for some essential design needs. _
> @greenshady in this [WP Tavern article](https://wptavern.com/fse-outreach-round-11-going-on-a-site-editing-safari).

> _As usual, with WordPress, also with bleeding edge experiments, it seems there
> is almost always a way to achieve the same result using different paths…Not had
> any crash or unattended interruption, so the current developing stage is showing
> a robust application. The improvements on each area done so far are impressive,
> sure we have tons of things and features to come. _
> @paulbigai in [this comment](https://make.wordpress.org/test/2021/11/08/fse-program-testing-call-11-site-editing-safari/#comment-2219).

[⌊Image of a homepage with black and white images arranged in a three column layout.⌉⌊
Image of a homepage with black and white images arranged in a three column layout
.⌉[

**Confirmed bugs**

Listed below are confirmed bugs that break expected functionality or the experience
of different features. Thanks to this test running during the 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. cycle for 5.9, many of these are already fixed.
**
Fixed

 * [Color naming conflict](https://github.com/WordPress/gutenberg/issues/36360) 
   with theme variables (fixed in 12.1 and backported).
 * [Consolidate two dimension panels](https://github.com/WordPress/gutenberg/issues/36536)
   for Post 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. block (fixed in 12.1 and backported).
 * [Duotone bug in selecting custom color](https://github.com/WordPress/gutenberg/issues/37069)(
   fixed in 12.1 and backported).
 * [Custom color palettes applied inconsistently](https://github.com/WordPress/gutenberg/issues/36979)
   with Styles (resolved with 5.9 beta 3).
 * [Featured category and various patterns](https://core.trac.wordpress.org/ticket/54623)
   missing from the Inserter (fixed).

New Reports or previously reported

 * [Setting color for List block impacts Post Template block](https://github.com/WordPress/gutenberg/issues/37388)
   with Styles.
 * [Align center doesn’t work with the Site Logo](https://github.com/WordPress/gutenberg/issues/36606)(
   previously reported). 
 * [Converting Group block to Cover block removes content](https://github.com/WordPress/gutenberg/issues/37342).

> _This resulted in the entire background of the posts list to change the background
> color. I was expecting that only the actual lists blocks would change when adjusting
> this setting, instead the entire page background of the query block changed. _
> @luminuu in [this comment](https://make.wordpress.org/test/2021/11/08/fse-program-testing-call-11-site-editing-safari/#comment-2254).

> _The biggest, ahem, hiccup that I ran into wiped all of my progress when editing
> my 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.. I tried to transform one of the outer Group blocks
> into a Cover to give it a background. It wiped everything in the header area clean,
> and the “undo” button did not seem to work. I just started over. _
> @greenshady in this[ WP Tavern article](https://wptavern.com/fse-outreach-round-11-going-on-a-site-editing-safari)_._

**Feature Requests**

As folks dug in, there were numerous enhancements that quickly came to mind as awesome
nice to haves. These desired enhancements not only underscores the potential of 
various full site editing pieces when put together, but also highlights the frustration
around the current limitations:

 * [Add a max number option](https://github.com/WordPress/gutenberg/issues/37340)
   to the Page List block.
 * [Add image size controls](https://github.com/WordPress/gutenberg/issues/33789)
   to the Post Featured Image block.
 * [Allow for more granular options](https://github.com/WordPress/gutenberg/issues/29388#issuecomment-969585680)
   for saving Styles changes.
 * [Consider adding patterns to Quick Inserter](https://github.com/WordPress/gutenberg/issues/36350#issuecomment-969605441).
 * [Desire for a way to export Styles](https://github.com/WordPress/gutenberg/issues/27528#issuecomment-970357823).
 * [Add ability to create custom general templates](https://github.com/WordPress/gutenberg/issues/37407)
   and [rename slug](https://github.com/WordPress/gutenberg/issues/32861) (related
   requests). 
 * [Ability to keep custom templates cross themes](https://github.com/WordPress/gutenberg/issues/31954).
 * [Desire for more advanced customization options](https://github.com/WordPress/gutenberg/issues/22071#issuecomment-993026495)
   for the Search block.
 * [Change excerpt length](https://github.com/WordPress/gutenberg/issues/34757) 
   for the 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. block.
 * [Style the “read more” section](https://github.com/WordPress/gutenberg/issues/33288)
   in the Post excerpt block 
 * [Add ability to add borders directly from the Image block](https://github.com/WordPress/gutenberg/issues/21540#issuecomment-993032825).

> _I started by removing the Page List block from 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. in the header. I have 90+ pages on my install, and
> it is always irritating when themes list them all by default. _
> @greenshady in [this WP Tavern post](https://wptavern.com/fse-outreach-round-11-going-on-a-site-editing-safari).

> _Post Featured Image selected I expected to see to see similar options as the 
> Image block. Example Image size: Full Size, Large, Medium or Thumbnail_.
> @paaljoachim in [this comment.](https://make.wordpress.org/test/2021/11/08/fse-program-testing-call-11-site-editing-safari/#comment-2218)

> _I miss a way for Global Styles to have more granular control over the links states,
> for color and the style in general. We have only one setting for link color, nothing
> for hover, active and visited state, neither the possibility to change the style
> applied, with TT1 Blocks we have the theme default text-decoration-style: dotted;
> for instance. _ 
> @paulbigai in [this comment](https://make.wordpress.org/test/2021/11/08/fse-program-testing-call-11-site-editing-safari/#comment-2219).

**General Usability Feedback**

Thanks to videos from a few folks as part of this call for testing, I’m including
less issues and quotes and more descriptions in order to capture the great feedback
that was shared. 

In [@courane01](https://profiles.wordpress.org/courane01/)‘s wonderful testing session,
the Navigation block placeholder proved to be quite confusing when it comes to WYSIWG(
what you see is what you getWhat You See Is What You Get What You See Is What You
Get. Most commonly used in relation to editors, where changes made in edit mode 
reflect exactly as they will translate to the published page.), especially if you
haven’t yet set a menu. There are improvements to [this placeholder setup that are being iterated upon as I write this](https://github.com/WordPress/gutenberg/pull/37144).
Tied to this, switching which menu is shown after selecting one also felt tricky,
likely because there were a number of empty menus. Thankfully, this is a likely 
rare occurrence with a limited number of likely switches. Regardless of the rarity,
an issue was opened to refine the language from “Select Menu” to “Switch Menu” or“
Replace”.

In [@paaljoachim](https://profiles.wordpress.org/paaljoachim/)’s video, he touched
on confusion around Styles and how best to both communicate global changes as you’re
editing and when you’re saving with multi-entity saving lacking granular options.
While there is a [welcome guide to help with](https://github.com/WordPress/gutenberg/issues/32844#issuecomment-960113269)
explaining Styles customization, it very much brings to the forefront how these 
new concepts will take some getting used to for WordPress users and how much needs
to be done in 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. to clearly communicate what is happening.

Beyond these high level themes, there were some specific issues raised:

 * [Update language for switching menus](https://github.com/WordPress/gutenberg/issues/37068)
   when using the Navigation block. 
 * [Add nudge to include name for Custom Color Palette](https://github.com/WordPress/gutenberg/issues/36473)(
   fixed in 12.1 and backported). This was brought up four times! 
 * [Simplify layout concept](https://github.com/WordPress/gutenberg/issues/36082#issuecomment-968358335)
   in order to make it more intuitive to set the width for all blocks within a template.
 * [Improve Post Featured Image block placeholder](https://github.com/WordPress/gutenberg/issues/36136#issuecomment-969590328)
   to make it easier to know what adjustments are being made (fixed in 12.0 and 
   backported). 
 * [Can’t remove group block margins](https://github.com/WordPress/gutenberg/issues/36797),
   making certain designs hard to accomplish. 

> _I actually missed that I needed to add a name to the color at all. Since there’s
> no placeholder text in the area where the color name should be added, I completely
> overlooked it and assumed I would just add the color, click Done, and voilà! However,
> it looks like not adding a color name at all means the colors won’t get saved.
> Adding some directive placeholder text next to the colors – or even an error message
> after clicking Done – might have helped me move past that.  _
> @evarlese in [this comment](https://make.wordpress.org/test/2021/11/08/fse-program-testing-call-11-site-editing-safari/#comment-2217)**.**

> _After applying the template to my post, it didn’t look like those changes or 
> settings were applied, since everything appeared at max width, and I wasn’t really
> sure of how or where to fix that. _
> @evarlese in [this comment](https://make.wordpress.org/test/2021/11/08/fse-program-testing-call-11-site-editing-safari/#comment-2217)**.**

> _I found it a bit strange adding a featured image block and a duotone filterFilter
> Filters are one of the two types of Hooks [https://codex.wordpress.org/Plugin\_API/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. without seeing what the result would look like. _ 
> @paaljoachim in [this comment.](https://make.wordpress.org/test/2021/11/08/fse-program-testing-call-11-site-editing-safari/#comment-2218)

> _Adding a suggest a second button, is showing it is not using the format of the
> already present one, which should be more logical. The differences are in the “
> Border Radius: 50%”” and “Width settings: 50%”” not applied on the new one. Of
> course this is not an issue, and if you need the same button its easy to achieve
> this duplicating the existing one. _
> @paulbigai in [this comment](https://make.wordpress.org/test/2021/11/08/fse-program-testing-call-11-site-editing-safari/#comment-2219).

> _The biggest issue I hit was with the Group block. By default, the Twenty Twenty-
> Two theme adds an 8rem (that’s pretty big) bottom margin to one of the Groups 
> within the header area. _
> @greenshady in [this WP Tavern post](https://wptavern.com/fse-outreach-round-11-going-on-a-site-editing-safari).

[#fse-outreach-program](https://make.wordpress.org/test/tag/fse-outreach-program/),
[#fse-testing-summary](https://make.wordpress.org/test/tag/fse-testing-summary/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Ftest%2F2021%2F12%2F16%2Ffse-program-site-editing-safari-summary%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/thehenrybyrd/) [Alicia](https://profiles.wordpress.org/thehenrybyrd/)
9:42 pm _on_ December 14, 2021     
Tags: [make.wordpress.org/mobile ( 139 )](https://make.wordpress.org/test/tag/make-wordpress-org-mobile/),
[p2-xpost ( 400 )](https://make.wordpress.org/test/tag/p2-xpost/)   

# 󠀁[X-post: Call for Testing: WordPress for Android 18.9](https://make.wordpress.org/test/2021/12/14/xpost-call-for-testing-wordpress-for-android-18-9/)󠁿

X-post from [+make.wordpress.org/mobile](https://make.wordpress.org/mobile/): [Call for Testing: WordPress for Android 18.9](https://make.wordpress.org/mobile/2021/12/14/call-for-testing-wordpress-for-android-18-9/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Ftest%2F2021%2F12%2F14%2Fxpost-call-for-testing-wordpress-for-android-18-9%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/annezazu/) [annezazu](https://profiles.wordpress.org/annezazu/)
9:32 pm _on_ November 30, 2021     
Tags: [5.9 ( 2 )](https://make.wordpress.org/test/tag/5-9/),
[fse-outreach-program ( 110 )](https://make.wordpress.org/test/tag/fse-outreach-program/),
[full-site-editing ( 63 )](https://make.wordpress.org/test/tag/full-site-editing/),
[release-field-guide ( 14 )](https://make.wordpress.org/test/tag/release-field-guide/)

# 󠀁[Help test WordPress 5.9 Features](https://make.wordpress.org/test/2021/11/30/help-test-wordpress-5-9-features/)󠁿

With WordPress 5.9 slated to ship on January 25th, 2022, this post seeks to consolidate
ways for folks to help test specific features that will be included in this release.
This is meant to bolster and support overall 5.9 testing efforts. As a result, expect
that FSE Outreach Program calls for testing will be on pause ahead of the FSE related
features landing in WordPress 5.9.

**Important note: **Anything marked as [Technical] is best for those comfortable
with more advanced testing steps. 

## Testing environment

Please only test on a development siteDevelopment Site You can keep a copy of your
live site in a separate environment. Maintaining a development site is a good practice
that can let you make any changes and test them without affecting the live/production
environment. and not on a production/live site. You can [follow these instructions](https://make.wordpress.org/core/handbook/tutorials/installing-wordpress-locally/)
to set up a local installLocal Install A local install of WordPress is a way to 
create a staging environment by installing a LAMP or LEMP stack on your local computer.
or use a[ tool like this to set up a development site](https://localwp.com/). 

Once a development site is set up, please install and activate the [WordPress Beta Tester Plugin](https://wordpress.org/plugins/wordpress-beta-tester/)
before setting it to: 

 * Update channel to “Bleeding edge”
 * Stream options to “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./RCRelease Candidate A beta version of software with the potential
   to be a final product, which is ready to release unless significant bugs emerge.
   only”

If you need more specific steps, [here are more detailed instructions you can follow](https://make.wordpress.org/core/handbook/testing/beta-testing/).

## Testing Tips

At a high level, there are a few tips to keep in mind to get the most out of helping
to test:

 * Try testing across different browsers.
 * Try testing in different languages. 
 * See what features look like on different screen sizes.
 * Try using just your keyboard or a screen reader.
 * Explore using both blockBlock Block is the abstract term used to describe units
   of markup that, composed together, form the content or layout of a webpage using
   the WordPress editor. The idea combines concepts of what in the past may have
   achieved with shortcodes, custom HTML, and embed discovery into a single consistent
   API and user experience. and classic themes. 

## Features to test

**Twenty Twenty-Two Default Block Theme**

When picking a theme to use for your test site, please try out the Twenty Twenty-
Two theme. It’s the very first theme that’s block based and needs thorough testing
as a result. Here’s where you can [read more about this theme](https://make.wordpress.org/core/2021/10/06/introducing-twenty-twenty-two/).
You can test the theme by installing the Beta and activating Twenty Twenty-Two from
Appearance > Themes. To report issues with the theme, [you can do so here](https://github.com/WordPress/twentytwentytwo/issues).

**Block theme flows** 

Since Block Themes open up the opportunity to edit more parts of your site, new 
flows have been added to make it more intuitive to access items, like a template
editor, where you can make the changes you want to your homepage or 404 page. These
workflows and new features need your help to test! 

For detailed testing steps around how best to test these workflows, [please follow this call for testing](https://make.wordpress.org/test/2021/11/08/fse-program-testing-call-11-site-editing-safari/)
that covers using Styles, Template Part focus mode, and more.

**Theme blocks with a focus on the Navigation block**

As Full Site Editing is a collection of features that allows more items to be easily
edited without knowing how to code, new blocks were created to cover more parts 
of your site. These blocks are generally called “Theme Blocks” as they match the
functionality that used to be in themes. While a number of theme blocks were introduced
in WordPress 5.8, there’s always more work to be done, including shipping even more
theme blocks in future releases!

For detailed steps around how to test the navigation block, [please follow this call for testing](https://make.wordpress.org/test/2021/08/11/fse-program-testing-call-9-handling-highered-headers/)
that covers creating two different menus. 

For detailed steps around how to general test theme blocks and a complete list of
blocks, [please follow this call for testing](https://make.wordpress.org/test/2021/09/29/fse-program-testing-call-10-pattern-party/).

**List View**

List view has a few enhancements to keep in mind, including the ability to drag &
drop blocks, and the ability to collapse sections to make it easier to navigate 
complex content. As you explore 5.9, try using List View in various situations to
ensure it’s performant and easy to use. 

**Design tools**

The effort to bring better and more consistent design tools continues to progress
with new options added, a more intuitive interface, and more. With just a few combinations
of these settings, you can create vastly different layouts from a few simple slight
changes to more radical and complex options. 

While a ton of tools have been added to various blocks, there are just a few to 
focus on for testing:

 * Buttons block: block gap, border controls, dimension controls (padding).
 * Columns block: block gap, dimension controls (padding).
 * Navigation block: flex layout, block gap, layout controls (vertical and horizontal,
   alignment).
 * Group block: layout controls, dimension controls (padding)
 * Cover block: duotone, dimension controls (padding, min height).
 * Social Icons block: layout controls (vertical and horizontal, alignment), block
   gap, dimension controls (margin). 
 * 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. block: duotone, dimension controls (width, height, margin, padding).

**Gallery block **

Thanks to a Gallery Block refactor, you can now use the same tools that are available
for individual image blocks on each image in the Gallery Block! This added flexibility
means you can do more customization – from adding links to each individual image,
inline cropping to edit on the fly, apply unique styles for more visually compelling
images and apply an array of duotone filters. [You can read more about this change](https://wordpress.org/news/2021/09/upcoming-gallery-block-improvements/).

The following items are a high priority to test:

 * [Technical] If you are 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/](https://wordpress.org/plugins/)
   or can be cost-based plugin from a third-party. or theme author that has used
   the Gallery block previously, [please follow the instructions here](https://make.wordpress.org/core/2021/08/20/gallery-block-refactor-dev-note/)
   to ensure you’re prepared for 5.9.
 * Test backwards compatibility by creating a Gallery Block with WordPress 5.8.2
   and switching to early releases of 5.9. 
 * Explore using the Gallery Block tools itself. Try cropping images, rearranging,
   adding alt text, and more. 
 * Test against third party plugins that you might use for galleries and ensure 
   the transformations work. If they don’t, it’s best to contact the third party
   plugin to let them know.

For additional context, please note that the new Gallery block is included in Beta
1, but the auto migrationMigration Moving the code, database and media files for
a website site from one server to another. Most typically done when changing hosting
companies. of existing Gallery blocks will be in Beta 2. As a result, for Beta 1,
you’ll be able to test the new Gallery block by adding a new Gallery, but, in order
to migrate an old format Gallery block, you’ll need to do so manually using the `
Update` button in the block toolbar.

**Block pattern explorer**

The experience of adding patterns from the Inserter just got a refresh with the 
[introduction of a new modal](https://github.com/WordPress/gutenberg/pull/35773)
that allows you to see patterns in a more organized way with larger previews. In
terms of testing, the items to cover are quite simple:

 * Select and add patterns to your content. 
 * Scroll through different pattern options.

**General updates coming to CoreCore Core is the set of software required to run
WordPress. The Core Development Team builds WordPress.**

Outside of these more specific features, there are also some general updates coming
to this release that would be advantageous to have tested:

 * Use the new [language switcher shown on the login screen](https://core.trac.wordpress.org/ticket/43700).
 * [Technical] [Properly enqueue wp-embed](https://core.trac.wordpress.org/ticket/44632)
 * [Technical] [Try out the new function wp_list_users()](https://core.trac.wordpress.org/ticket/15145)
   to create a list of users.
 * [Technical] [Explore the new visibility field](https://core.trac.wordpress.org/ticket/54055)
   for the REST post type controller.

## Where to report feedback

If you find any issues, it’s best to share them on the [alpha/beta forums,](https://wordpress.org/support/forum/alphabeta/)
or [Trac](https://core.trac.wordpress.org/) if you are more technically savvy and
comfortable. Please share feedback as soon as you can [before the release on January 25th, 2022.](https://make.wordpress.org/core/5-9/)

_Thank you to [@justinahinon](https://profiles.wordpress.org/justinahinon/) [@boniu91](https://profiles.wordpress.org/boniu91/)
[@cbringmann](https://profiles.wordpress.org/cbringmann/) [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/)
and [@webcommsat](https://profiles.wordpress.org/webcommsat/) for reviewing and 
contributing to this post._

[#5-9](https://make.wordpress.org/test/tag/5-9/), [#fse-outreach-program](https://make.wordpress.org/test/tag/fse-outreach-program/),
[#full-site-editing](https://make.wordpress.org/test/tag/full-site-editing/), [#release-field-guide](https://make.wordpress.org/test/tag/release-field-guide/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Ftest%2F2021%2F11%2F30%2Fhelp-test-wordpress-5-9-features%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/thehenrybyrd/) [Alicia](https://profiles.wordpress.org/thehenrybyrd/)
8:39 am _on_ November 30, 2021     
Tags: [make.wordpress.org/mobile ( 139 )](https://make.wordpress.org/test/tag/make-wordpress-org-mobile/),
[p2-xpost ( 400 )](https://make.wordpress.org/test/tag/p2-xpost/)   

# 󠀁[X-post: Call for Testing: WordPress for Android 18.8](https://make.wordpress.org/test/2021/11/30/xpost-call-for-testing-wordpress-for-android-18-8/)󠁿

X-post from [+make.wordpress.org/mobile](https://make.wordpress.org/mobile/): [Call for Testing: WordPress for Android 18.8](https://make.wordpress.org/mobile/2021/11/30/call-for-testing-wordpress-for-android-18-8/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Ftest%2F2021%2F11%2F30%2Fxpost-call-for-testing-wordpress-for-android-18-8%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/meaghanthompson/) [meaghanthompson](https://profiles.wordpress.org/meaghanthompson/)
3:50 am _on_ November 30, 2021     
Tags: [make.wordpress.org/mobile ( 139 )](https://make.wordpress.org/test/tag/make-wordpress-org-mobile/),
[p2-xpost ( 400 )](https://make.wordpress.org/test/tag/p2-xpost/)   

# 󠀁[X-post: Call for Testing: WordPress for iOS 18.8](https://make.wordpress.org/test/2021/11/30/xpost-call-for-testing-wordpress-for-ios-18-8/)󠁿

X-post from [+make.wordpress.org/mobile](https://make.wordpress.org/mobile/): [Call for Testing: WordPress for iOS 18.8](https://make.wordpress.org/mobile/2021/11/30/call-for-testing-wordpress-for-ios-18-8/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Ftest%2F2021%2F11%2F30%2Fxpost-call-for-testing-wordpress-for-ios-18-8%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/meaghanthompson/) [meaghanthompson](https://profiles.wordpress.org/meaghanthompson/)
7:06 pm _on_ November 16, 2021     
Tags: [make.wordpress.org/mobile ( 139 )](https://make.wordpress.org/test/tag/make-wordpress-org-mobile/),
[p2-xpost ( 400 )](https://make.wordpress.org/test/tag/p2-xpost/)   

# 󠀁[X-post: Call for Testing: WordPress for iOS 18.7](https://make.wordpress.org/test/2021/11/16/xpost-call-for-testing-wordpress-for-ios-18-7/)󠁿

X-post from [+make.wordpress.org/mobile](https://make.wordpress.org/mobile/): [Call for Testing: WordPress for iOS 18.7](https://make.wordpress.org/mobile/2021/11/16/call-for-testing-wordpress-for-ios-18-7/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Ftest%2F2021%2F11%2F16%2Fxpost-call-for-testing-wordpress-for-ios-18-7%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/thehenrybyrd/) [Alicia](https://profiles.wordpress.org/thehenrybyrd/)
10:08 am _on_ November 16, 2021     
Tags: [make.wordpress.org/mobile ( 139 )](https://make.wordpress.org/test/tag/make-wordpress-org-mobile/),
[p2-xpost ( 400 )](https://make.wordpress.org/test/tag/p2-xpost/)   

# 󠀁[X-post: Call for Testing: WordPress for Android 18.7](https://make.wordpress.org/test/2021/11/16/xpost-call-for-testing-wordpress-for-android-18-7/)󠁿

X-post from [+make.wordpress.org/mobile](https://make.wordpress.org/mobile/): [Call for Testing: WordPress for Android 18.7](https://make.wordpress.org/mobile/2021/11/16/call-for-testing-wordpress-for-android-18-7/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Ftest%2F2021%2F11%2F16%2Fxpost-call-for-testing-wordpress-for-android-18-7%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/annezazu/) [annezazu](https://profiles.wordpress.org/annezazu/)
9:52 pm _on_ November 8, 2021     
Tags: [fse-outreach-experiment ( 20 )](https://make.wordpress.org/test/tag/fse-outreach-experiment/),
[fse-outreach-program ( 110 )](https://make.wordpress.org/test/tag/fse-outreach-program/),
[fse-testing-call ( 28 )](https://make.wordpress.org/test/tag/fse-testing-call/),
[full-site-editing ( 63 )](https://make.wordpress.org/test/tag/full-site-editing/)

# 󠀁[FSE Program Testing Call #11: Site Editing Safari](https://make.wordpress.org/test/2021/11/08/fse-program-testing-call-11-site-editing-safari/)󠁿

This is the eleventh call for testing as part of the [Full Site Editing Outreach Program](https://make.wordpress.org/core/2020/12/11/the-fse-outreach-program-is-officially-starting/)!
For more information about this outreach program, [please review this FAQ](https://make.wordpress.org/test/handbook/full-site-editing-outreach-experiment/faq-for-fse-outreach-experiment/)
for helpful details. To properly join the fun, please head to [#fse-outreach-experiment](https://wordpress.slack.com/archives/C015GUFFC00)
in [Make Slack](https://make.wordpress.org/chat/) for future testing announcements,
helpful posts, and more. 

As a reminder, if you’d like to suggest an idea for a call for testing, it’s very
welcomed and all ideas will be weighed against current project priorities to figure
out what makes the most sense to pursue. You can share ideas directly in the slackSlack
Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/).
The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/)
channel or via DM to me ([@annezazu](https://profiles.wordpress.org/annezazu/)).

## Overview

_Feel free to jump straight to the [testing steps](https://make.wordpress.org/test/2021/?output_format=md#testing-steps)
if you’d prefer to get started right away. _

This is the final call for testing before WordPress 5.9, which makes it a wonderful
and high impact one to be involved in as it’ll help improve the experience for a
large portion of the web before it ever launches. In order to get the most out of
this call for testing, the instructions are going to change as the test goes on 
and as we move forward in the release cycle. For example, at the start of this test,
folks will be encouraged to use TT1 and, by the end of the test, Twenty Twenty-Two
will be recommended. For now, here’s a high level overview of what is going to be
tested:

**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
template and template part editing 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.**

While certain calls for testing have ventured into the Site Editor, that experience
as you’ve known it is shifting for 5.9 in order to offer a more refined and scaled
down experience to manage templates and template parts within a block theme. With
a condensed browsing tool and a new placement in wp-admin under Appearance, this
might feel more like a taste than the full experience of the Site Editor as you’ve
come to know it.  

**Styles Interface**

While 5.8 laid the groundwork for a cohesive style system, 5.9 sees the introduction
of a beautiful user interface that allows folks to interact directly with various
style properties. You might have heard of this work under the project name “global
styles”! While we’ve had calls for testing around 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., one of the mechanisms related to the overall Global Styles project, this
is the first time Styling itself is being explored. Currently, this interface displays
two large groups of design focuses: blocks and elements. Elements represent things
that can be styled globally and across blocks (such as “text”, “links”, “captions”,
etc). This is a fancy way of saying you can easily change the typography of your
entire site or the unique coloring of your buttons block all from the same interface.

**Patterns Explorer**

With block patterns on the rise, [a new explorer modal has been shipped](https://github.com/WordPress/gutenberg/pull/35773)
to make it easier to navigate between patterns and find the exact one you want to
use. This sets the groundwork for future integration with the Pattern Directory.
This test will briefly explore this new experience.

**Twenty Twenty-Two**

Twenty Twenty-Two is the latest in a long line of default themes with a twist — 
it’s a block theme first and foremost built for the various site editing tools. 
As a result, midway through this call for testing, folks will be encouraged to test
using this theme and report back their findings. Read more about this [groundbreaking default theme here](https://make.wordpress.org/core/2021/10/06/introducing-twenty-twenty-two/).

## Testing Environment 

_This will adjust as the test goes on and the release cycle progresses to ensure
folks are testing the latest and greatest. _

Here are the steps to follow to properly set up your testing environment for this
specific all for testing. If you’re already ready to go, jump to the testing steps
below.

 1. Use a test site with the latest version of WordPress. Right now, that’s 5.8.2. 
    It’s important this is not a production/live site. 
 2. Install and activate 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/](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/](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 12.0](https://github.com/WordPress/gutenberg/releases/tag/v12.0.0).
 3. Install the [TT1 Blocks theme](https://wordpress.org/themes/tt1-blocks/) by going
    to Appearances > Themes > Add New. Once installed, activate the theme. 
 4. Create a few posts with featured images of your choosing. Alternatively, you can
    download and import the [demo Gutenberg content](https://cloudup.com/cARY6x8T1Dc)
    created previously for these kinds of tests via the WordPress importer under Tools
    >  Import. You can also follow [this lesson for how to use demo content](https://learn.wordpress.org/lesson-plan/how-to-add-demo-content-in-wordpress/).
 5. Go to the website’s admin.
 6. You should now see a navigation item under Appearance titled “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.)”. If you don’t see that, your
    environment isn’t correctly set up. If you get stuck here, just comment on this
    post or ask in [#fse-outreach-experiment](https://make.wordpress.org/test/tag/fse-outreach-experiment/)
    for help!

Generally speaking, please use the latest versions of each part of the setup and
keep in mind that versions might have changed since this post was shared.

## Testing steps

Personalize your homepage

1. Go to Settings > Reading and set “Your homepage displays” to show “Your latest
posts”.
2. Once set, go to Appearance > “Editor (beta)”. This will open up to show
a template that displays your homepage.3. From there, change your homepage to your
liking! This could mean adding in a navigation block, changing the font size of 
your Post Title Blocks, adding a duotone filterFilter Filters are one of the two
types of Hooks [https://codex.wordpress.org/Plugin_API/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 your Post 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. blocks, removing blocks, adding blocks, and more. 4. Once
you’ve adjusted everything to your liking, click “Save” and go through the saving
experience. 

Set your styles 

5. From there, click on the [Styles icon](https://cloudup.com/cTXfCLwf7iJ) in the
upper right corner to access the Styles interface. 
6. Once open, personalize the
four sections as much or as little as you’d like: Typography, Colors, Layout, and
Blocks (to customize individual blocks). For example, you can click on Colors > 
Palette > Use the + sign to add your own custom color option for use throughout 
your content. 7. Once you’ve adjusted everything to your liking, click “Save” and
go through the saving experience. 

Add a buttons pattern and use layout controls

8. From there, open up the Inserter and switch to the Patterns tab.
9. Select the“
Explore” option, navigate to the Buttons section, and pick the “Simple call to action”
pattern.10. Once added, use the + option to add in a second button. 11. From there,
select the overall parent Buttons block and open 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. settings to customize the layout
to your liking. [Here’s a quick video](https://www.dropbox.com/s/uuorot3u5yvjsu2/button%20layout.mov?dl=0)
in case you get stuck.12. Save the changes. 

Add a duotone filter to your Archive template

13. Click on the W menu in the upper left hand corner > Under Editor select “Templates”
> Select “Add New” > Select “Archive” ([currently not possible to create a General template from here](https://github.com/WordPress/gutenberg/issues/36741)).

14. In the content, add in the Post Featured Image block and add in a duotone filter.
15. Add in any additional blocks you’d like and save the changes when you’re ready.
16. Head back to your dashboard by clicking on the W icon in the upper left corner
before heading to Posts > All posts. 17. Edit one of your posts with a featured 
image and assign your updated “Archive” to this post. [Here’s a quick video](https://www.dropbox.com/s/htwy6dubrnqxghd/duotone.mov?dl=0)
in case you get stuck.18. Save and view the post to see the filter applied!

Edit your 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.

19. Return to Appearance > Editor (beta) and, using List View if you need to, select
your Header template part. 
20. Select the three dot menu in List View or in the
block toolbar and select “Edit Header”. This will take you to the focused template
part mode. 21. From there, make a few changes to the template part (add items to
the navigation block, change the size of your Site Title, etc) and use the horizontal
drag handles to see how your header will look at different sizes! 22. Save the changes.

## What to notice:

 * Did the experience crash at any point?
 * Did the saving experience properly save your changes? 
 * Did you find any features missing? 
 * What did you find anything 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 in the editor matched what you saw on your
   site?
 * How did your content look on a smaller device or screen size? 
 * How do you think this will impact your current workflows? 
 * Did it work using Keyboard only?
 * Did it work using a screen reader?

## Leave Feedback by December 7th, 2021

Please leave feedback in the comments of this post. If you’d prefer, you’re always
welcome to create issues [in this GitHub repo directly for Gutenberg](https://github.com/WordPress/gutenberg/issues).
If you leave feedback in GitHubGitHub GitHub is a website that offers online implementation
of git repositories that can easily be shared, copied and modified by other developers.
Public repositories are free to host, private repositories require a paid subscription.
GitHub introduced the concept of the ‘pull request’ where code changes done in branches
by contributors can be reviewed and discussed before being merged by the repository
owner. [https://github.com/](https://github.com/), please do still comment below
with the link. If you see that someone else has already reported a problem, please
still note your experience with it below, as it’ll help give those working on this
experience more well-rounded insight into what to improve.

_Props to [@kellychoffman](https://profiles.wordpress.org/kellychoffman/) for helping
review this call for testing._

**Changelog**

Nov 10th: updated instructions to use Gutenberg 11.9 RC4.
Nov 12th: updated instructions
to use Gutenberg 11.9.Nov 13th: updated instructions to use WordPress 5.8.2.Nov 
24th: updated instructions to use Gutenberg 12.0, to change the phrasing around 
the browsing component, and to update the due date.

[#fse-outreach-program](https://make.wordpress.org/test/tag/fse-outreach-program/),
[#fse-testing-call](https://make.wordpress.org/test/tag/fse-testing-call/), [#full-site-editing](https://make.wordpress.org/test/tag/full-site-editing/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Ftest%2F2021%2F11%2F08%2Ffse-program-testing-call-11-site-editing-safari%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/designsimply/) [Sheri Grey](https://profiles.wordpress.org/designsimply/)
12:31 am _on_ November 4, 2021     
Tags: [make.wordpress.org/mobile ( 139 )](https://make.wordpress.org/test/tag/make-wordpress-org-mobile/),
[p2-xpost ( 400 )](https://make.wordpress.org/test/tag/p2-xpost/)   

# 󠀁[X-post: Call for Testing: WordPress for iOS 18.6](https://make.wordpress.org/test/2021/11/04/xpost-call-for-testing-wordpress-for-ios-18-6/)󠁿

X-post from [+make.wordpress.org/mobile](https://make.wordpress.org/mobile/): [Call for Testing: WordPress for iOS 18.6](https://make.wordpress.org/mobile/2021/11/04/call-for-testing-wordpress-for-ios-18-6/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Ftest%2F2021%2F11%2F04%2Fxpost-call-for-testing-wordpress-for-ios-18-6%2F%23respond&locale=en_US)

# Post navigation

[← Older posts](https://make.wordpress.org/test/2021/page/2/?output_format=md)