Information Sources for WordPress 6.2

Welcome

The WordPress Training Team helps people learn to use, extend, and contribute to WordPress through learn.wordpress.org.

Are you new to the team?

Getting Started – Join the team through this self-guided onboarding program

Current Focus Areas – What we’re currently focusing on

Already onboarded and ready to get involved?

See How we use GitHub to get started on one of our 6 project boards

Meetings (Calendar)

You can join these meetings from the #training Slack channel:

Weekly meeting: Thursdays 00:00 UTC

Dev-squad GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ triage: Thursdays 07:00 UTC

See Meeting Details for more information.

These are sources of information when assessing what content will need to be updated and revised for LearnWP.

CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Announcements:

GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ Labels

Not all of these are related to

Core DevNotes

DevNotes tracking GitHub Issue
More to come

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/

Changelogs (on Core)

TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/.:

Docs team:

Docs WP 6.2 GitHub Project Board

Training / LearnWP Project

RevisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. Extended

We revise content ahead of release while preserving the current content until release. Think of it as a Pull Request that ships on release day. Here’s how we do that:

Jonathan Bossenger 6:12 pm on January 13, 2023

Thanks for posting this @courane01. In 2023 I want to focus on keeping these sources at the top of my mind and help with surfacing this content for the training team.
annezazu 5:42 pm on January 18, 2023
Hey folks! I wanted to drop a list of what I already see as big changes coming for 6.2 to help get on the same page:

Interface:
- Browse mode which reorganizes the site editor experience: https://github.com/WordPress/gutenberg/issues/36667
- Pathway to import widgets when switching to 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 from a classic theme: https://github.com/WordPress/gutenberg/issues/39270
- Removing 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. label (TBD): https://github.com/WordPress/gutenberg/issues/39293
- Change in the block settings icon: https://github.com/WordPress/gutenberg/issues/46851
Blocks:
- Sticky positioning with some follow up happening: https://github.com/WordPress/gutenberg/issues/47043
- Change in the navigation block 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. with an editable list view: https://github.com/WordPress/gutenberg/issues/41549
- Split block settings between styles and settings: https://github.com/WordPress/gutenberg/issues/40204
- Colorise template parts and reusable blocks 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.: https://github.com/WordPress/gutenberg/issues/32163
Patterns:
- New design of the pattern Inserter, along with (hopefully) headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. & footer patterns bundled and potentially new categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. names: https://github.com/WordPress/gutenberg/issues/41379 & https://github.com/WordPress/gutenberg/issues/44501
- Openverse integration in the Inserter (this is TBD still): https://github.com/WordPress/gutenberg/issues/46222
Styles:
- In line preview of blocks when working with Styles: https://github.com/WordPress/gutenberg/issues/42919
- Add option to apply local changes to a block to your entire site: https://github.com/WordPress/gutenberg/issues/44361
- Style Book that allows you to see all blocks on your site as you style them: https://github.com/WordPress/gutenberg/issues/44420
- Add option to copy and paste block styles: https://github.com/WordPress/gutenberg/issues/44418
- Input for Custom CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. for Styles https://github.com/WordPress/gutenberg/issues/30142 and for individual blocks https://github.com/WordPress/gutenberg/issues/44412 Both are a work in progress.
To see some of this working together, here’s a YouTube video I made comparing things from 5.9 to 6.2 in progress items and here’s a core editor improvement post going through how they work together to evolve the experience.

I’m aiming to share the source of truth for 6.2 on February 21st where more solid info and resources can be viewed.