WordPress 5.7 Planning Roundup

After a successful WordPress 5.6 release, this post aims to provide a round-up of planning done so far for WordPress 5.7.

Proposed WordPress 5.7 Schedule

This cycle will have a similar timeframe than 5.6:

  • Alpha, 78 days – 5.6 had 84 days
  • 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., 21 days – same as 5.6
  • RC, 14 days – same as 5.6

Based on the tentative schedule and experiments from the past twelve months, this is the proposed schedule for the first of the four planned releases for 2021:

  • Alpha: 17 November 2020 trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. is open for 5.7 alpha contributions
  • Kickoff: 15 December 2020 first 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 of the new cycle
  • Planning roundup: 21 December 2020 (that’s this post!)
  • Betas: 2 February 2021 (eleven weeks from branching off trunk, seven weeks from kickoff)
  • Release Candidates: 23 February 2021 (three weeks from beta 1)
  • General Release: 9 March 2021 (two weeks from release candidaterelease 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). 1)

Proposed WordPress 5.7 Scope

The main goal for 2021 is Full Site Editing via 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/ (edited for clarity: this is not THE scope for 5.7 but an ongoing effort 😊).
You can read the status report, join the FSE Outreach program, check the progress on the GitHub issue used to overview to progress, and dive into contributing to it from there!

For WP5.7, these are some of the features that will be likely worked on:

  • Update WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. to include current releases of the Gutenberg pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party.
  • Gutenberg: ship additional blocks, refine the UIUI User interface, add tools for themes and design, and continue working on the widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. screen.
  • Continue work on auto-updates and jQuery.

We might add more items in the upcoming weeks, and we will reconfirm the above-proposed list after the end-of-Gregorian year holidays.

As with every release, all component maintainers and teams are invited to prioritize their bug-fixes and enhancements for 5.7. Look out for the 5.7 report in Trac to see what is getting milestoned and help the project gets those tickets to the end line!”

In addition, all components and teams are invited to continue polishing current interactions and making the UIs more user-friendly.

JB and I are collecting all the proposals from the open call for tickets: we will submit them to the relevant component maintainers so they can evaluate if there are enough resources to address them during this release cycle and update their status. If they are, they will be milestoned for 5.7, so turn on your notifications if you haven’t already.

Please bear in mind, if a ticketticket Created for both bug reports and feature development on the bug tracker. is still waiting for review, has no 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., or no owner, it is unlikely (not impossible) that it will land in 5.7. This shouldn’t stop you from continuing to work on it, gather feedback, and ultimately polish it enough to have it in a future release. Shepherding tickets is as vital as submitting patches.

Proposed WordPress 5.7 Leads

This area is intentionally incomplete. JB, Josepha, and I are reaching out to people that have expressed interest in being part of 5.7. 

You can read about each role in our handbook. If you are interested, leave a comment on this post, and we will reach out to you too.

  • Release LeadRelease Lead The community member ultimately responsible for the Release.: Matt
  • Release Co-ordinator: Ebonie Butler
  • Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. PM: Tonya Mork
  • Core Tech: Sergey Biryukov
  • Editor Tech: Robert Anderson
  • Design: Tim Hengeveld 
  • Docs: JB Audras
  • 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): Sarah Ricker
  • Test: Monika Rao

Release specific leads

Once we have final confirmation of scope, we will annouce additional focus leads, if needed.

Thanks @chanthaboune and @audrasjb for the help with the post.
Edited for clarity about scope (FSE is not THE scope, it’s an ongoing effort) and tickets in milestone (unlikely to happen vs. impossible to happen)

#5-7, #planning

Dev Chat Summary Dec 16th 2020

Hello! Here’s what happened in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. dev chat on Wednesday, December 16, 2020, 05:00 UTC, and Wednesday, December 16, 2020, 20:00 UTC. Both chats followed this agenda.

05:00 UTC core dev chat
@thewebprincess facilitated the meeting and took notes. Find the full Slack archive here.

20:00 UTC core dev chat

@laurora facilitated the meeting and @thelmachido took notes. Find the full Slack archive here.

Announcements

Reminder – State of the Word is today. Set your alarm for the time Thursday, Dec 17th, 2020 at 1600 UTC so you don’t miss it!!

The 5.6 retrospective has started! We’d love as many of you as possible to share your feedback with us via the form linked in this post

The Full Site Editing Outreach program is officially underway. It will start with the release of GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ 9.6 around December 23rd with plenty of time to be involved. If interested in joining the fun, please head on over to #fse-outreach-experiment. There is a comprehensive status update on Site Editing, view the post from Matias.

@abhanonstopnewsuk would like to inform us that the questions and answers on the release have had some updates thanks to a number of comments from user experience, to further help non-technical users. These updates will be posted on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can 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/.

Highlighted Posts

Component maintainers and focus leads

Build/Test Tools
Work has continued on GitHub Actions in this ticketticket Created for both bug reports and feature development on the bug tracker. #50401. There are also 3 relevant commits to take note of. r49781 Disable GitHub Action workflow runs triggered on push for forks and mirrors. r49782  Use NodeJS 14 in GitHub Action workflows. r49783  Enable reporting of results to WordPress.org

Site Health
A small ticket for 5.6.1 came in today, so it’s looking manageable

@clorith pointed out that jQuery updates got flagged early

Comments Component
@imath updated the 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. on this ticket #33717, feedbacks welcome

@flixos90 is planning to commit iframeiframe iFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser. lazy-loading today #50756

Upgrade and Install
There is a plan to have error stats for 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/theme updates failures sent to dotorg #51928 in 5.7

Open Floor

  • @iandunn would like to get some broader feedback on #51966 – please review and leave comments on tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress..
  • A question was raised during chat, does a theme upgrade require being tied to a core upgrade?. The issue was raised because of this ticket #52040 @audrasjb said that this issue can be fixed in a TT1 release because a theme upgrade doesn’t need to be tied to a core upgrade. You can follow the full conversation here.
  • Learn WordPress was launched yesterday and a big cross teams effort including contributors from community, training, marketing, polyglots, design, metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress., core and more. There are some more fun promotions in store too. Social videos have been produced for the promotion of Learn WordPress. Here is an example, the team would like to encourage contributions in other languages.  They’re also exploring how to support older audiences to use WordPress through the resources on Learn WordPress. Any hands to help with this? 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.” @nalini on slackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..
  • @annezazu worked to redo the core feature projects page. Project owners where contacted for the latest status, description/intro paragraphs where updated, core editor items where added, and inactive projects where hidden to make the page more focused.

Next Dev Chat Meeting

The next meetings will take place on Wednesday, December 23rd 2020, 05:00 UTC and Wednesday, December 23rd 2020, 20:00UTC in the #core Slack channel. Please feel free to drop in with any updates or questions. If you have items to discuss but cannot make the meeting, please leave a comment on this post so that we can take them into account. 

#props to @thelmachido for consolidating both sets of notes together prior to publishing.

#5-7, #summary

Dev Chat Agenda: 16th December 2020

Here is the #agenda for this week’s meetings happening at:
Wednesday, 16 December 2020, 0500UTC and Wednesday, 16 December 2020, 2000UTC .

The #dev-chat meetings will be held on Wednesday, 16 December 2020, 05:00UTC and Wednesday, 16 December 2020, 2000UTC. These meetings are held in the #core channel. To join the meeting, you’ll need an account on the Making WordPress Slack .

#5-7, #agenda

Call for Volunteers – Early bug scrubs for WordPress 5.7

In preparation for WordPress 5.7, tentatively scheduled for a March 9th, 2021 release, it would be beneficial to start running weekly 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. scrubs around the tickets flagged as early.

Tickets marked with the early workflow keyword are a priority and should be committed as soon as possible in the release cycle. Indeed, tickets that are committed early can be tested during the alpha cycle, and other tickets may depend on them to be committed.

Alpha has been open for business since November 17th, so there are already some tickets in the report.

Who?

Leading a Bug Scrub is something any interested community member can do! Please comment below if you’re interested in running one bug scrub or two 🙂

When?

To make sure we have at least some dates in the books, Let’s schedule two sessions on the same day, to allow for maximum participation across the globe.

If more scrubs are going to be needed before we formally kick-off the cycle, they will be added along the way.

Call for volunteers

If you are interested, please pick a date and a time and say it in the comments. Thank you.

#5-7, #bug-scrub

Dev Chat Summary: December 9 2020

Hello! Here’s what happened in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. dev chat on Wednesday, December 9, 2020, 05:00 UTC and Wednesday, December 9, 2020, 20:00 UTC.

05:00 UTC core dev chat

@thewebprincess facilitated the meeting and took notes. Find the full Slack archive here.

20:00 UTC core dev chat

@francina & @johnbillion facilitated the meeting and @laurora took notes. The full Slack archive can be viewed here.

Announcements

WordPress 5.6 aka “Simone” was released yesterday (8 December 2020). The release squad was entirely made of people identifying as women and non-binary folx. You can read more about the release in this blog post. At the time of the meeting, @helen shared that it’s already exceeded 3 million downloads.

The annual State of the WordState of the Word This is the annual report given by Matt Mullenweg, founder of WordPress at WordCamp US. It looks at what we’ve done, what we’re doing, and the future of WordPress. https://wordpress.tv/tag/state-of-the-word/. will be taking place Thursday 17 December at 1600 UTC. If you’d like to submit a question, the deadline is Friday 11 December! This post has more information.

Updates from Component Maintainers/Focus Leads

Build/Test Tools:

@desrosj is continuing to work on the GitHubGitHub GitHub is a website that offers online implementation of git repositories that can 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/ Action workflows and backporting the local Docker environment to the remaining older branches.

@desrosj has been working one repo at a time to convert the Travis configurations to workflows. If you maintain any repositories under the WordPress GitHub organization and want to help with the transition, feel free to DM him.

Open Floor

@afragen requested some extra eyes on #51976. If you’re able to help out, please add your comments to the ticketticket Created for both bug reports and feature development on the bug tracker.. And also added that if you’re after a larger challenge to take a look at #51928, noting that 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. might need to be moved to #51857.

Next Dev Chat meetings

The next meetings will take place on Wednesday, December 16, 2020, 05:00 UTC and Wednesday, December 16, 2020, 20:00 UTC in the #core 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. Please feel free to drop in with any updates or questions.

#5-6, #5-7, #dev-chat, #summary

Dev Chat Summary – 2 December 2020

The meeting was facilitated by @peterwilsoncc and @thewebprincess while @mikeschroder and @johnbillion took notes. Full meeting transcript on Slack. Both groups followed this pre-prepared agenda.

Announcements

Highlighted Posts

  • A Week in Core – November 23, 2020
  • What’s next in Gutenberg? The monthly report is out
  • Discussion: Update the updater
  • Dev Notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include: a description of the change; the decision that led to this change a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. are continue to be updated ready for final release, here’s the latest dev-notes.
  • Release cycle discussion post – we need your feedback!
  • WP Notify project review

Component maintainers and focus leads

@peterwilsoncc reminded everyone that these components are in need of maintainers:

If you’re wondering what being a maintainer involves, @markparnell linked this guide from @francina.

Open Floor

@noisysocks requested review on #51612, which aims to make the  render_block_data, pre_render_block and render_block_context filters run on nested blocks. The PR with the latest approach can be found here.

The 2000 UTC group discussed #51913 and #51918 which led into a general discussion about the level of PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8 support in 5.6 and how to communicate it. @marybaum asked for clarity to ensure all the marketing messaging is accurate.

The current consensus is that coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. is “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.-compatible”, which means 5.6 works on its own with PHP 8, but that any given site may not work due to the plugins and themes in use and that more defensive programming is needed in core.

Next Dev Chat Meeting

The next meetings will take place on December 9, 2020 at 0500UTC and December 9, 2020 at 2000UTC in the #core 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. Please feel free to drop in with any updates or questions. If you have items to discuss but cannot make the meeting, please leave a comment on this post so that we can take them into account. 

Apologies

Apologies from @johnbillion for the late posting of this summary. The post sat in draft until today when I was reminded of it.

Onwards!

#5-6, #5-7, #core, #dev-chat, #summary

Dev Chat Summary – 25 November 2020

The meeting was facilitated by @thewebprincess while @thelmachido took notes. Full meeting transcript on slack. Both groups followed the pre-prepared agenda

Highlighted Posts

  1.  A week in Core. Take a look at what changed on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between November 16 and November 23, 2020
  2. On November 24 the Field Guide was updated with new  Dev notes
  3. WP release cycle. If you work for a company whose product is influenced by WordPress releases, you are encouraged to join the discussion about aligning the WP release cycle with industry standards
  4. PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party and themes developers releases depend on CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., so it’s important that extenders reply.
  5. With the 5.6 release scheduled for December 8th, let’s start planning for 5.7. What’s on your wish-list for version 5.7
  6. The marketing team are starting working on ‘the Month in WordPress in their weekly meeting, please reach out if you have any contributions to share.
  7. Last but not least, the PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8 dev notedev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include: a description of the change; the decision that led to this change a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. is now published. Folks are reminded to continue testing PHP 8

Component maintainers and focus leads

 PHP 8 Dev Notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include: a description of the change; the decision that led to this change a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. @sergeybiryukov advised that PHP 8.0 release is scheduled for November 26. The dev note does a great job summarizing the changes and challenges PHP 8.0 brings for WordPress core and plugin or theme authors, so give it a read. There are a few components without a maintainer, and some that could use more maintainer support, a challenge was raised to people to consider contributing in this way, it’s not as hard as you might be thinking! See the discussion here and pick a component to dive into.

Open Floor


The Marketing Team is working on a social media pack on version 5.6, if anyone would like to support this, please let @lmurillom or @abhanonstopnewsuk know. Follow the conversation on slack 

Questions and answers for version 5.6
Where uploaded yesterday on GithubGitHub GitHub is a website that offers online implementation of git repositories that can 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/. @abhanonstopnewsuk – “ l would like to thank everyone who has already helped with this from the release squad, core and marketing, and a big shout out to @vimes1984 and  @meher who have led these questions and answers work with me over the last month.”

There are a number of tickets coming in since 5.6 RC1. @hellofromtonya will be scheduling a pre-RC2 Scrub Scheduled: Nov 30th @ 1900 UTC and will drop tickets into #core channel over the next few days to escalate.

The theme/theme directory teams have two requests for feedback on the make blogblog (versus network, site)https://make.wordpress.org/themes/2020/11/18/theme-previews-in-the-time-of-blocks/ and https://make.wordpress.org/themes/2020/11/19/feedback-requested-resolution-process-for-issues-found-in-live-themes/  please review and add your thoughts.

Mike asked for more testing assistance with https://github.com/WordPress/phpunit-test-runner/issues/121 in the hopes we can get this across the line. Finally, Paal posted a note that he’s going to be focusing on improving the structure of the handbooks, watch this space to see how that develops

Next Dev Chat Meeting

The next meetings will take place on Wednesday, December 2, 2020, 07:00 AM GMT+2 and Wednesday, December 2, 2020, 10:00 PM GMT+2 in the #core 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. Please feel free to drop in with any updates or questions. If you have items to discuss but cannot make the meeting, please leave a comment on this post so that we can take them into account. 

#5-6, #5-7, #dev-chat, #summary

WordPress 5.7: What’s on your wishlist?

With the 5.6 release scheduled for December 8th, let’s start planning for 5.7!

We always aim to fix bugs, add new tools, and make WordPress better than ever for users. Components of Full Site Editing are still at the top of the WordPress goals list; what other tickets do you think need some attention in this release cycle?

Share Your Feedback!

  • What do you want to see included in 5.7?
  • What are the current UXUX User experience pain points?
  • What features can we add or iterate on?
  • Component Maintainers: what tickets do you think will be ready to ship by late January and need some review/feedback/approval/etc?

Note: Adding your ticketticket Created for both bug reports and feature development on the bug tracker. here won’t necessarily guarantee inclusion. But no one can fix things they can’t see, so bravely share your thoughts!

Deadline December 15, 2020

#5-7

Widgets Screen Not Shipping in 5.6

The Widgets Screen project was pencilled in for 5.6, but as of BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1, work on its major features was not complete, so Release LeadRelease Lead The community member ultimately responsible for the Release. @chanthaboune, CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech Lead @helen, Editor Tech Lead @isabel_brison and some of the contributors working actively on the project — @noisysocks, @talldan and @kevin940726 — decided to exclude it from 5.6. Thank you to everyone who tested and gave feedback as it helped inform this decision! 

The Reasoning

Making the Customizer work with the block editor is a challenging process, and one that needs  substantial and thoughtful work to make sure that we deliver the best possible user experience. At the current stage of this project a bulk of that work is done, but more focused testing revealed notable concerns for overall usability (including 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. interactions, some confusions between 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. & legacy widgets, and UXUX User experience disparities between the old and new screens). You can read more in the ticket.

Next Steps

We will continue working on the Widgets screen, and will keep the new screen as the default option when using 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 to encourage more feedback.  At the top of the year, we’ll explore where this fits in the larger roadmap for future releases. For those looking to get involved until then, check out the options below: 

  • It’s been tentatively added to the WP5.7 milestone, with an early 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.) so that it comes up in scrubs as quickly as possible.
  • If you’re interested in following the status of the project, you can find the top priority issues and current focuses on the Widgets Editor project board in GitHub
  • If you can help with development, we encourage you to attend or review the weekly triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. sessions in the #core Slack channel on Wednesdays at 7am UTC.
  • If you can help with testing, please feel free to leave comments on the Call for Testing for us to review or to open issues directly in GitHub. In particular, we’d love to hear from plugin and theme authors. 

Thanks in advance for everyone’s help making sure that this key element is a success!

#5-6, #5-7