Yearly Archives: 2021

Jeff Ong 4:47 pm on October 11, 2021
Tags: , , ,   

Twenty Twenty-Two Chat Summary — 11 Oct 2021

In #core-themes, full transcript starts here. I (@jffng) facilitated the meeting. It was the first one!

Building TT2 for Full Site Editing

We discussed the approach to the theme’s development, which is developing this as a 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 and fixing as much in 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/ as possible. One of the goals is for the theme to have as little CSSCSS Cascading Style Sheets. and PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher as possible.

Our current development focuses are two-fold:

  1. Identifying the gaps / blockers in Gutenberg. There is an overview issue tracking what’s needed on the Gutenberg side: https://github.com/WordPress/twentytwentytwo/issues/75 We could use help testing various blocks and filing issues whenever they’re not looking or working as expected.
  2. Block patterns coming soon, @kjellr is leading that effort. We could use help with PR reviews and testing as those become available, follow along using this tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.).

Meeting Cadence

We plan to do meetings once a week at this time (Mondays, 15 UTC), aiming to keep them around 30 minutes as to be respectful of folks time and focus on async for inclusivity.

Open Floor Q&A

  • How do we decide what needs to be worked on?
    • Ideally everything that’s being worked on has an issue — so if you find something that needs fixing, please open an issue for it, and then work on a PR.
    • Keep an eye on the github milestones
  • Is there a mechanism for collaborating on an issue?
    • Comment on the issue, so it’s clear you’re working on it and if folks want to collaborate, they can communicate in the issue and slackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ if needed
  • Is the way fonts are enqueued going to change?
  • Are you looking for triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. help?
    • You can pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” @kjellr or me (@jffng) if you would like to help this way.
  • Will TT2 align with the 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) level AA like TT1 did? How do we make sure this gets addressed?
    • Short answer is yes, let’s use this issue to track
    • A lot of this lands on Gutenberg, and for what we can do on the theme side, we hope to make this as accessible as possible. For example, the color palettes have been designed to pass WCAGWCAG WCAG is an acronym for Web Content Accessibility Guidelines. These guidelines are helping make sure the internet is accessible to all people no matter how they would need to access the internet (screen-reader, keyboard only, etc) https://www.w3.org/TR/WCAG21/. AAA contrast.
    • Button states will be important too.
#bundled-theme, #summary, #twenty-twenty-two
Daniel Richards 9:11 am on October 11, 2021
Tags: , , ,   

Navigation Editor and Block Hallway Hangout

Date: October 13, 2021, 10:00 UTC

Format: Zoom (recorded). A link will be shared in the #feature-navigation-block-editor slackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ channel shortly before the meeting is due to commence.

Length: 60mins.

Goal: Discuss Navigation Editor and BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. goals for 5.9 and beyond.

Details: There are some recent proposed changes to the Navigation Editor and Block that would change some aspects of the project. See the post in slack for more information (https://wordpress.slack.com/archives/C01KDAZJMQ9/p1633512526250600). This hallway hangout will be assembled to discuss how the project should proceed.

Facilitator(s): 

Intended Audience: past and future contributors to the Navigation Editor and Block. Contributors to other related parts of WordPress.

Note Taker: any volunteers to be the official note keeper?

Agenda: 

  • Introduction
    • Facilitator and attendee introductions
    • Brief recap of Navigation Editor and Block projects to date
    • Recap of Navigation Editor goals to date
  • Discussion
    • Discuss the proposals for making the Navigation Block ‘reusable’. What are the block’s requirements for Full Site Editing?
    • How should the Navigation Block work with Classic Menu data for block-based themes (in a Full Site Editing context)?
    • How can the Navigation Editor can be made to work with this future Navigation Block?
      • Discuss the case of classic menu editing in the Navigation Editor for classic themes that do not support block-based menus.
        • Discuss backwards compatibility requirements and potential solutions.
      • Discuss the case of classic themes that could opt-in to showing block-based menus in their theme locations.
    • Have the goals for the Navigation Editor changed?
    • Discuss the proposed roadmap.
  • Summary
    • Briefly discuss next steps
      • Reworking the tracking issues / project board
      • Making WordPress post summarising results

#block-editor, #feature-navigation-block-editor, #gutenberg, #menus

Dion Hulse 7:30 am on October 11, 2021
Tags: ,   

X-post: WordPress.org Profiles now show GitHub activity

X-post from +make.wordpress.org/meta: WordPress.org Profiles now show GitHub activity

Paal Joachim Romdahl 4:48 am on October 9, 2021
Tags: , , , ,   

Editor chat summary: 6 October, 2021

This post summarizes the weekly editor chat meeting (agenda here) held on  Wednesday, October 6 2021, 04:00 PM GMT+1. in Slack. Moderated by @paaljoachim.

GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. releases

Gutenberg 11.7 RC Thanks to @zieladam for tackling the release.
What’s new in Gutenberg 11.6 release notes. Thanks to @ntsekouras for writing the notes and handling the release.

WordPress 5.9

October 14th is the date when the decision for “Go, no go” for Full Site Editing to be included in WordPress 5.9 will be decided.

Preliminary Road to 5.9. A quick overview of the main areas and features currently underway for 5.9 in Gutenberg.

What’s next in Gutenberg

What’s next in Gutenberg: Mid-September 2021.

Key project updates

Based on the scope for Site Editing projects.

Template Editor

  • No update currently mentioned. Check out the Full Site Editing label of current issues in the Gutenberg repo on GithubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/.

Global Styling

Patterns

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. & Navigation Editor

Update – 2021-10-06

  • Discussion is still continuing on the best way to ensure interoperability and compatibility between Nav block and Nav Editor.
  • Looks like there will be a Hallway Hangout on Wednesday 13th October (TBC). Agenda will be posted to Make Blogblog (versus network, site).
  • @talldan posted a nice summary of current state of things in Slack. There’s a lot of great energy in the team right now and we are looking to coalesce around a shared set of objectives.

Components squad

Shipping:

In Progress:

Mobile team

 Shipped:

  • Top 5 embeds blocks directly available in the block picker, Retry feature, specific embed’s icon and label in placeholder and bottom sheets.
  • Added a way to contact support from inside editor.
  • Added automated tests for editor onboarding.

Fixes:

  • Fixed an image block regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. causing the images to render with a fixed height and a bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. preventing the columns block from rendering in the editor in some occasions.

In Progress:

  • Embed block improvements.
  • GSS Font size, line height, colors.

Task Coordination

@annezazu

@ntsekouras

@amustaque97

Worked on Update Callers to handle when getBlockType return undefined (PR has been merged.)

@mamaduka

  • Helping with PR reviews and testing.
  • Merged the last PR for optimizing useSelect calls.
  • Started working on remaining items in the individual block locking feature.

Open Floor

@welcher

@mkaz

  • Any issues with switching Gutenberg examples repo (https://github.com/WordPress/gutenberg-examples) default branch to trunk? It’ll be nice to have it consistent.

@bph

  • This week’s Live Q & A is tomorrow at 16:00 UTC Going from classic to block-based theme building
  • Next week, Helen, Mark and Riad discuss how to make it easier to build custom blocks
  • On 10/28 LQA is with members of the BuddyPress Team discussion how to convert widgets to blocks.

Times and links are all available on Gutenbergtimes.com

@paaljoachim

  • Can someone create a WP 5.9 Github project board to where we can focus on Full Site Editing and general 5.9 issues/PR’s? As it has earlier been very useful to have the project board to check for issues related to a release.

    @priethor
    I can kick it off, sure. I was looking forward to the go/no-go demo next week so that we can have a more clear scope of the must-haves before creating it.

@talldanwp

  • The following PR needs some discussion: Use theme mods for templates and template parts
    “I was referred to this PR, and it seems like it had a lot of traction in 5.8 but didn’t make it in time. It’s still there needing reviews and possibly a decision for 5.9 and it seems like something that shouldn’t be left too late, otherwise the same will happen again.
    (I would review it myself, but I don’t really have the full knowledge required).”

    @get_dave
    It would be great if there was a recap summary which captures the current state of discussion. It seems pretty important for the utility of Template Parts. (Dave added a comment.)

@Gemini Labs

  • In Gutenberg 11.6 the ServerSideRender component was updated to display the existing content while the new response is fetched. There is bug with this change which I outlined here: https://github.com/WordPress/gutenberg/pull/28297#issuecomment-932723947. I thought it might be useful to bring it up again here in light of the recent Gutenberg 11.7 RCrelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). release (thanks @zieladam!).
    Bug issue opened here: Bug in ServerSideRender where the block disappears during render.
  • I would like to ask if anyone here had any concerns about adding a hook (or some other solution) to ServerSideRender which allows a plugin author to trigger something after a block has rendered.
    I opened a Feature Requestfeature request A feature request should generally begin the process in the ideas forum, on a mailing list, as a plugin, or brought to the attention of the core team, such as through scope meetings held for each major release. Unsolicited tickets of this variety are typically, therefore, discouraged. for this on Github here with a further explanation: https://github.com/WordPress/gutenberg/issues/35294

@get_dave

  • I found this forum post asking if there is a separate Read More block for use in 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? Currently it seems the Read more is locked inside the 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.. There is also a Gutenberg issue for it here: Could we have Read more link as a stand alone block?

@amustaque97

@zebulan

#core-editor, #core-editor-summary, #gutenberg, #meeting-notes, #summary

Birgit Pauli-Haack 2:29 pm on October 7, 2021
Tags: , ,   

Proposal: Gutenberg Developer Hours series of events.

  • Summary: Proposal for a new event: Every other week, invite WordPress developers to meet with 3 developers and discuss your 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/ development questions, code, ideas, and approaches. Follow-up w/ video and resources.
  • Start Date: Soon.
  • Trial period: 4 events.
  • Producer: Birgit Pauli-Haack + Gutenberg Developer Volunteers. 

Background: 

I used to do in-person walk-in clinics for a volunteer internet service provider, where we answered all kinds of questions. If there was a moment with no questions, I would pull a topic out of my hat, talk for five minutes and get another 10 questions that triggered in people’s heads. The place was always packed.

Not everyone is comfortable dealing with an unknown set of questions, but when done right, the panel format is quite fun and interesting. Of course, there were always questions that were too specific or too advanced. We would take note of it and answer them either the following week or via email directly to the attendee. 

I would like to try this in a remote setting with a panel of three developers from the community, who are experienced with working with blocks, and call it Gutenberg Developer Hours. 

About the show

I have heard from a number of people that despite the sheer volume of developer documentation that’s around, it’s hard to know where to start. And when developers hit roadblocks, it also takes a long time to troubleshoot errors and bugs. 

If you’re a developer who’s new to Gutenberg, I invite you to stop by, to get your questions answered or to get advice on architecture or approach. (You can also just lurk, of course!) Maybe you have a code issue: “I’ve been working on this project, but I hit a roadblock and I have no idea where to go from here.”

For the speakers, being on a panel lightens the load, opens the door to a wider range of topics and makes it much less likely any one person will get a question they might not be able to answer. 

As a moderator, I (at first; if the sessions go well, there can certainly be others) can jump in and ask questions to bridge the silence if the group runs out of audience questions. Plus, if a question gets too specific or too advanced, the moderator makes a note of it, discusses with the dev team and gets back to the attendee with a response after the event. That could be:

  • an invitation to office hours, 
  • a set of documentation, or 
  • a blogblog (versus network, site) post inspired by the question. 

It’s certainly part of the trial to find out where the boundaries of this support offerings are. 

At the beginning, I envision a frequency of every other week, once there is a pool of volunteer developer panelists available to schedule.

To get attendees interested, it might help to have a short educational segment that people are interested in for the first two or three shows.

The panelists could also pick a topic. Here are a few that come to mind:

  • How to tap into Gutenberg filters and hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same.?
  • How to add a button to the toolbar?
  • What is a store in ReactJS? 
  • How to add 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. Styles?

I propose promoting the series on Twitter and Facebook, and on make.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/. Would you like to see this on TikTok? Feel free to make one! Like FSE itself, these panels can be springboards to creative thinking and doing!

The producers will record and transcribe every show, and the moderator will make that clear in the opening moments. If an attendee wants to ask their question outside the recording, the moderator can hit the pause button. 

Reuse, Recycle, Repurpose

In post-production, the shows can generate a new stream of material for Learn, Marketing and Community, and everyone else in the community, to use however you like.

The show’s own producers and editors can cut the full session into smaller educational units and publish them on WordPress.tv. Did a specific question stump the panel? A producer can pull that out and write a separate tutorial about it.

Nuts and Bolts

The show is not a webinar but a normal Zoom meeting, so people can see each other and share their screens and code.

At least for the trial, registration is required. The producers will, of course, respect the attendee’s privacy and use email addresses only for communication regarding the specific Gutenberg Developer Hour session.

I have already approached a few developers to be our resident experts with the idea, and they want to try it. Depending on the feedback, they and I are ready to start soon. (It helps that this is a Zoom call and not a stage-set production!)

Are you a Gutenberg developer with some experience? Would you like to be on the panels? Irrespective of your Gutenberg experience, would you like to help produce the shows? Please let me know in the comments.

Production Process:

You do not have to be an experienced Gutenberg developer to help with production. In fact, it might be a great way to get your feet wet! And it is yet one more way to contribute to WordPress.

  • Schedule the Gutenberg Developer Hours, one at a time. 
    • Set-up Zoom space, with registration.
    • Announce the next session via social channels, Make/Project, Gutenberg Times, and other available channels. 
  • Connect with the volunteers on a regular basis so they can schedule themselves. 
  • Recruit volunteers as panelists, moderators and content producers. 
  • Published post with resources and solutions.

If you want to be part of the team working on this initiative, let us know in the comments and I will connect with you via WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. And as always, the team and I value your comments and questions immensely.

Please don’t hesitate to connect with me on WP Slack @bph if you have additional questions.

Thank You to @annezazu, @daisyo, and @sparklingrobots for collaboration and refinement of the initiative.
Props @jeffpaul and @audrasjb for peer review.

#developer-hours, #gutenberg, #new-contributors

Jb Audras 11:27 pm on October 6, 2021
Tags: , , , ,   

Dev chat summary – October 6, 2021

@audrasjb led the chat on this agenda. You can also read the Slack logs.

Highlighted blogblog (versus network, site) posts

Bringing to your attention some interesting reads and some call for feedback and/or volunteers:

Worth mentioning:

Thanks to the 21 contributors of the past week, including 4 new contributors! Kudos to the 3 coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. committers of the week, too.

A Week in Core – September 27, 2021

Upcoming releases updates

Next minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality.(s)

Please note that 5.8.2 was deferred due to the lack of ready-to-ship tickets.

Reminder: @desrosj and @circlecube are co-leading the 5.8.x releases. The 5.8.x point releases are coordinated in the #5-8-release-leads SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ channel. This channel is public and will be archived once 5.9 is released.

Next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.

Concerning the next major release —WordPress 5.9— a planning roundup was published some weeks ago.

@kjellr introduced the new bundled theme on Make/Core right before the devchat.

As usual, there is a public repository on GitHub so feel free to help testing the theme, and to contribute to this cool project

Introducing Twenty Twenty-Two

@chanthaboune wanted to clarify that the go/no go date was moved to October 14. It’s just for scheduling conflicts, there is not any worry over the release.

@audrasjb will run another bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrub on Thursday October 7, 2021 at 20:00 UTC.

Reminder: everyone is welcome to run a bug scrub on the #core Slack channel. If you are interested, please read this handbook post: Leading bug scrubs and get in touch with @audrasjb or @francina for details.

Component maintainers updates

Build/Test Tools – @sergeybiryukov

Last week, PHPUnit tests started failing on PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher 5.6 due to a combination of an older OpenSSL version and the DST Root CA X3 certificate that expired on September 30, 2021. This is now resolved by running the tests on the latest patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. version of PHP 5.6 (5.6.40 at the moment), instead of 5.6.20. See ticketticket Created for both bug reports and feature development on the bug tracker. #54223 for more details.

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. APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. – @sergeybiryukov

The expired DST Root CA X3 certificate is now removed from the WP core certificate bundle to resolve issues with OpenSSL 1.0.2. See ticket #54207 for more details.

CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. – @dlh

The Customize component could use a designer’s eye on #54211.

Upgrade/Install – @afragen

There have been issues with 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. installation/upgrade failures in plugins that have a large number of files. See #51857 (see comment 128 and below) and #54166.

@afragen thinks he have a solution in this pull request and would love some more testing and hopefully an early commit if appropriate.

Also, there are 2 different PRs for #22316 that take different approaches: PR1547 and PR1724.

It would be great to get feedback on which approach is preferred and work on getting that committed. Please test both and leave feedback.

@audrasjb noted that both PRs have detailed testing instructions. They are easy to test and any feedback is welcome.

@josvelasko raised a PR ready for review: PR#1688

Help/About – @marybaum

The Help/About component maintainers will hold a bug scrub on Monday, probably after 21:00. @marybaum will post an exact time in the next 24 hours.

Toolbar – @sabernhardt

@sabernhardt shared a draft of a Toolbar component update post.

He also pointed out that a docs update (#54191) was just committed today.

Script Loader – @clorith

The three tickets marked early about jQuery updates (37110, #51812, #52163) are almost ready to ship, so there are RCrelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta).’s in for testing at least.

Open Floor

@annezazu wanted to encourage everyone to attend the Pattern Party call for testing for the #fse-outreach-experiment. All are welcome to join in and she is always open to feedback to make participating even easier.

FSE Program Testing Call #10: Pattern Party

#5-8-x, #5-9, #dev-chat, #summary, #twenty-twenty-two

Dan Farrow 5:59 pm on October 6, 2021
Tags: ,   

CSS Chat Summary: 30 September 2021

The meeting took place here on Slack. @danfarrow facilitated and wrote up these notes.

Housekeeping

CSS Custom Properties (#49930)

  • @dryanpress suggested that, once all the PRs are merged, it would be very helpful to add a Table of Contents (TOC) to custom-properties.css. @ryelle agreed that it would help with reducing duplicates and with documentation.
  • @danfarrow asked about how the TOC sections would be broken down and @dryanpress suggested starting with a Theme and a General section, then adding sections for each file
  • We discussed following up on unfinished PRs. @dryanpress offered to gently nudge the relevant authors after which we would give them 5 days to respond before picking up / taking over their PRs. @wazeter agreed that applying a soft deadline is a good idea. UPDATE: By the end of the meeting all authors had effectively been nudged!
  • @danfarrow brought up the issue of rgba colour values and asked what the currently preferred approach is. After an interesting discussion the consensus was that the custom properties should be added for each distinct rgba value, for example --wp-admin--surface--box-shadow: rgba(0, 0, 0, 0.1);. We could then work on a second pass to reduce the number of distinct rgba values.
  • @joyously imagined a script that sequentially sets each custom property to hotpink, so the user can verify that the visual changes meet expections. UPDATE: Within a few hours @costdev pretty much delivered the goods – amazing!

Open Floor / CSS Link Share

  • @dryanpress shared a link to a tweet announcing that the ouline ring now automatically adapts to the element border-radius “in the latest releases of all major browsers”
  • @ryelle shared a link to WordCamp US [Now over, but there’s always next year!]
  • @dryanpress shared a link to Omatsuri, an essential collection of very useful browser-based HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers., CSS, SVG & other web related tools

Thanks everybody!

#summary

Kjell Reigstad 5:13 pm on October 6, 2021  

Introducing Twenty Twenty-Two

A collection of screenshots featuring the Twenty Twenty-Two theme

WordPress 5.9 will feature a brand new default theme named Twenty Twenty-Two. It arrives during an exciting time for WordPress themes. With the advent of Full Site Editing and Global Styles, themes are changing structurally and functionally to enable far more avenues for customization than users have come to expect in the past. To take advantage of these new abilities, Twenty Twenty-Two has been designed to be the most flexible default theme ever created for WordPress.  

A reliable starting point

To find inspiration for this theme’s design, I did not have to look far. Thanks to a bird feeder attached to the outside of our kitchen window, my family’s daily breakfast routine involves a rotating cast of cardinals, doves, finches, jays, and tufted titmice. The birds are always up to something interesting: Sometimes they’re lining up patiently to take turns eating, other times they’re playfully performing aerial gymnastics. 

While the birds’ exact behavior is unpredictable, they are remarkably reliable overall. The exact lineup changes somewhat, but every single morning there’s a group of birds eating breakfast with us. Throughout all of the tumult the world has seen in the past couple years, this consistent, entertaining routine has been a welcome starting point to my day. 

That routine is the inspiration for this years’ default theme. Like the birds, Twenty Twenty-Two is designed to be light and resilient, with a hint of playfulness. The theme uses the lightweight Source Serif Pro for headlines, paired with a sensible sans-serif for support. Its color palette is drawn from nature, and layout elements sit gently on the page.

Above all, the theme is designed to be reliable. Its design choices are intentionally subtle, and its foundation will be built strong. It’s our hope that this theme will suit your site through many seasons. 

Homepage and archive page mockups for the Twenty Twenty-Two theme.

Endlessly customizable

Twenty Twenty-Two will take advantage of a wide networknetwork (versus site, blog) of page templates, headers, footers, and other patterns so that users can easily make the theme their own. In another nod to the behavior of birds everywhere, these will offer a balance between fun and utility: some are irregular and unpredictable, while others are straightforward and traditional. Together, these patterns will act as a window into all of the possibilities that the theme enables.

A variety of page layouts and block pattern mockups for the Twenty Twenty-Two theme.

In addition, Twenty Twenty-Two will ship with a range of alternate color schemes so that folks can drastically change the appearance of their site. Users will also be able to change fonts, image treatments, and more on a site-wide level. These new controls open up a wide array of drastically different customizations for the theme:

Twenty Twenty-Two is designed with the acknowledgement that its default appearance is not most people’s endpoint. Everyone deserves a truly unique website, built on a solid, well-designed foundation, and Twenty Twenty-Two aims to help them achieve that.

Built for Full Site Editing

To take advantage of these new customization features, Twenty Twenty-Two will be built for Full Site Editing first. The theme aims to use as little CSSCSS Cascading Style Sheets. as possible: our goal is for all theme styles to be configured through 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. and editable through Global Styles. The theme development team will work closely with 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/ contributors to build design tools in 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. editor that enable this goal. 

As a block theme, Twenty Twenty-Two will likely require WordPress 5.9 to run. If the Twenty Twenty-Two and 5.9 release leads determine that there is need in the community for broader theme support, we will explore ways to bridge that gap.

Next steps

Kjell Reigstad (@kjellr) is leading design for Twenty Twenty-Two, and Jeff Ong (@jffng) is leading development. The two of us are looking forward to your involvement and support though the process!  If you are interested in contributing to Twenty Twenty-Two, make sure you are following this blogblog (versus network, site). 

Theme development will happen on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/. Once the theme is stable, it will be merged into CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and its GitHub repo will be deprecated. An empty repository has been created here that you can follow if you’d like: 

https://github.com/wordpress/twentytwentytwo

Starting on Monday October 11th at 3:00 PM UTC, there will be weekly SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ meetings in #core-themes to coordinate development of the theme.

The future of default themes

The community has produced a dozen best-in-class themes together, and we’ve come to look forward to a new one arriving at the close of each year. That said, themes are in a transition period today, and it seems like this may be a reasonable time to step back and to re-evaluate the annual cadence with which we build default themes. 

Innovations like theme.json, block templates, and block patterns are making theme development far simpler, and are providing new ways for users to customize their sites. There’s reason to believe that the community can leverage all this to build more frequent and diverse theme and customization solutions for our users in the coming years. 

We’re all still navigating these new opportunities (and in the meantime, we have a theme to build!) so let’s regroup after the 5.9 release to discuss future paths forward for default themes. 

Learn more

For information about about previous default themes, you can read the following posts:

If you’re interested in learning more about Block Themes and Full Site Editing, here are some resources for you:

annezazu 2:04 pm on October 6, 2021
Tags: , ,   

Core Editor Improvement: Continued progress on accessibility

Improving 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) requires ongoing effort and this post seeks to highlight some of the ways in which the project continues to make strides in this area. If you’re interested in helping with this work, please join the #accessibility channel in Make SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ and check out how you can get involved. There’s plenty of important work to be done including testing, giving accessibility feedback, and creating PRs to address feedback. 

Ensuring accessibility from the start with 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. [planned for 5.9]

The Navigation Block is a key milestone for the full site editing project that focuses on the experience of editing a site’s 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., both in terms of structure and design. This is a big effort that includes how to make it easy to add submenu items, how to create a responsive navigation experience, how to support multiple different inner blocks, and more. While work is underway to simplify the experience for all (ex: reducing the number of steps to add a page link), this section covers three big pieces of the work, thus far, that have had a particularly strong impact on accessibility:

  1. The first is that when implementing submenus it was intentional that they would open on explicit click rather than focus, when navigating with a keyboard and/or screen reader. The changes made ensure that screen reader users are better informed when tabbing submenus, and can choose whether to enter them or not. Previously it was necessary to tab through every submenu item to get to the next parent item. For a deeper look into the behaviors of the navigation block and submenu items, check out these visualizations that provide more context but have not yet been fully implemented. 
  1. When building the responsive navigation feature in the navigation block, work was done to ensure the hamburger menu was built using proper modal behavior from the start. This means that when you open the responsive burger menu, the tab is kept inside the responsive menu experience until you press Escape. A quick demonstration is shown in the video displayed in this section.
  1. Finally, the markup for the front end was changed to ensure that the Navigation block contains fully semantic markup, no matter what its contents are.

Accessibility benefits with the Gallery Block Refactor [planned for 5.9]

Ahead of WordPress 5.9, an update to the Gallery Block was shipped that essentially allows you to have all of the tools you’re used to with an Image Block for each image in the Gallery Block. Thanks to this change, the Gallery Block now benefits from improved keyboard navigation and the ability to add alt text right within the block 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.. This will make it easier to both produce accessibility friendly content and for those navigating what you create when viewing your site. To learn more about the Gallery Block Refactor, you can check out this WordPress News post dedicated to it. 

The new gallery block with an alt text field for each image within the gallery block itself.

Other noteworthy updates/fixes [in the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. today]

There’s a lot of high-impact changes that can be overlooked when not shown altogether. To help capture additional accessibility improvements, here are high impact changes in the editing experience: 

Thank you to @joen who helped provide wonderful insights about the navigation block, including the featured video. Thank you to @kellychoffman @priethor @daisyo for the content review. Thank you to @javiarce for the lovely Gallery Block refactor screenshot.

#core-editor-improvement, #gutenberg

Jb Audras 10:40 am on October 6, 2021
Tags: , , , ,   

Dev Chat Agenda for October 6, 2021

Here is the agenda for this week’s developer meeting to occur on October 6, 2021, at 20:00 UTC.

Please note that depending on your timezone, the time may have changed with the end of daylight saving time.

Blogblog (versus network, site) Post Highlights and announcements

Bringing to your attention some interesting reads and some call for feedback and/or volunteers:

Next releases status update

  • Next minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality.: WP 5.8.2
    👉 WordPress 5.8.2 Deferred
  • Next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.: WP 5.9
    👉 WordPress 5.9 Planning Roundup

Components check-in and status updates

  • Check-in with each component for status updates.
  • Poll for components that need assistance.

Open Floor

Do you have something to propose for the agenda, or a specific item relevant to the usual agenda items above?

Please leave a comment, and say whether or not you’ll be in the chat, so the group can either give you the floor or bring up your topic for you accordingly.

This meeting happens in the #core channel. To join the meeting, you’ll need an account on the Making WordPress Slack.

#5-8-2, #5-9, #agenda, #core, #dev-chat