Daisy Olsen 12:46 am on January 7, 2021
Tags: , , ,   

What’s next in Gutenberg? (January 2021)

This is a monthly update containing the high-level items that 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 are focusing on for January. Please join us in our efforts and let us know in the comments if anything is blocking you from doing so. 

How to follow along with Gutenberg: 

Here’s an overview of different ways to keep up with Gutenberg and the Full Site Editing project. There is also an index page of Gutenberg development-related posts and a Site Editing Milestone overview issue that breaks down the upcoming work into more concrete next steps. 

Global Styles

Global Styles refers to the system that defines and manages global aesthetics, allowing overall site styles, theme styles, and blocks to work well together. Global Styles focus areas for January include:

  • Determining what 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. and infrastructure functionality (not user facing) to include in WP 5.7
  • Support for translation theme.json strings

Follow along:

You can follow the progress for this overall system in this overview issue and by reviewing the Global Styles label. 

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.-based 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. Editor

Work on the Block-based widget editor (Widgets Screen) is a continued focus for the month ahead. The purpose of this effort is to bring the flexibility of block-based editing to the widgets and 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. screens.

Blocks in the Widget Screen

Adding block support for the widget editor is an ongoing focus. Progress toward this effort can be accessed via the Block-based Widget Editor project board. The emphasis for January will be eliminating bugs.

Blocks in the Customizer

An exploratory phase to find the best path for adding blocks in the customizer. If this interests you, please review this previous discussion and check out the current plan for exploration. For greater context, you can also watch this hallway hangout focused on managing blocks in the customizer. 

Follow along:

You can follow the progress of this work on this project board and you can join #feature-widgets-block-editor in 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/ 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/. for future widget screen focused meetings post 5.6 launch. 

Full Site Editing

As with the prior months, work on this major focus for phase 2 is ongoing and is expected to continue iterating over the coming months. Work this month will include the following focus areas:

Milestone 1 – Site Editing Infrastructure and UI

Work toward infrastructure and UIUI User interface improvements including:

Milestone 5 – Query Block 

This work includes the following Query Block design explorations:

  • A pagination block with different style variations to work alongside the Query Block. 
  • Query Block toolbar controls 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. to make it easier to show the content you want.
  • Exploring the idea of a Query Block builder UI to scale the experience for advanced users. 

Milestone 6 – Navigation Block

Work on the Navigation Block is an ongoing effort and focus for January. An overview of the work in progress can be found in the Navigation Block tracking issue.

In addition to the above, the Theme Experiments repo is being monitored to see how theme developers are building block-based themes. Please continue to share there, it is appreciated!

Follow along:

You can follow the progress of this project with this overview issue showing key milestones for site editing. For each major milestone, there are related issues you can follow if you want a more granular look at each next step (example from Query Block).

As a reminder, if you’re interested in being a part of testing Full Site Editing, check out the experimental outreach program to learn more. 

Important Note:

If you were previously following this project board, it has now been closed in order to use the milestones issues more consistently and to prevent people from needing to follow the progress in two places. 

Areas to be aware of:

Block & 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 Developers

PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8 has been released please review the Dev Notes in the 5.6 Field Guide with a particular focus on preparing your plugins for PHP 8. 

Theme Developers

Those interested in learning more about block-based themes may wish to read the comprehensive article @frankklein wrote on what he learned while building a block-based theme. 

Ways to Get Involved:

While the above items are our focuses, don’t forget that you can always help with triage, needs testing issues, good first issues, and reviewing PRs. In particular, for this month, focusing efforts around testing the Widgets Screen would be very helpful and high impact. 

If there’s anything we can do to make contributing easier, let us know in the comments or in #core-editor chats. While we can’t promise to fix everything, we’d appreciate being aware of any blockers.

Meetings to join:

While you can view all meetings here, here are specific meetings to join depending on your interest. Remember that you need a WordPress.org slack account to participate: 

  • CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor weekly @ 14:00 UTC on Wednesday in #core-editor focused on all things Gutenberg. 
  • Block-Based Themes meeting twice monthly Wednesday @ 16:00 UTC on Wednesday in #themereview focusing on preparing for Full Site Editing enabled theme development. 
  • Block-Based Widget Editor meeting weekly @ 07:00 UTC in #feature-widgets-block-editor on Wednesday focusing on implementing the ability to manage blocks in widget areas.

#gutenberg-next

Jb Audras 9:47 pm on January 4, 2021
Tags: , ,   

A Week in Core – January 4, 2021

🌟 Happy New Year! 🌟

Welcome back to a new issue of Week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Let’s 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 December 28, 2020 and January 4, 2021.

  • 12 commits
  • 19 contributors
  • 39 tickets created
  • 9 tickets reopened
  • 46 tickets closed

As expected, Trac has been fairly quiet last week ❄️⛄️

Ticketticket Created for both bug reports and feature development on the bug tracker. numbers are based on the Trac timeline for the period above. The following is a summary of commits, organized by component.

Code changes

App Passwords

  • Ensure the Add New button isn’t hidden on mobile – #51980
  • Correct authorize app action names and signatures – #52013
  • Only attempt auth if the username and password are set – #52003

Build/Test Tools

  • Change the frequency of code coverage reporting – #50401, #52141

Bundled Themes

  • Twenty Twenty-One: Make sure filtering attachment image attributes only affects front end and not the adminadmin (and super admin) area – #52212
  • Twenty Twenty-One: Remove extra brackets from :last-child CSSCSS Cascading Style Sheets. pseudo-class – #52176

Canonical

  • Check if the post type exists when attempting a canonical redirect – #40309

REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/.

  • Move the WP_Query args filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. after the tax_query is setup – #42762
  • Only include the controller’s own taxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies. in it’s schema – #51940
  • Properly display 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. encoding errors – #52106
  • Expose all themes in the themes controller – #50152

Site Health

  • Use a front-end URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org for loopback tests – #52097

Props

Thanks to everyone who contributed to WordPress Core on Trac last week:

@johnbillion (3), @engahmeds3ed (2), @TimothyBlynJacobs (2), @mukesh27 (2), @jorbin (1), @munyagu (1), @Clorith (1), @technosailor (1), @atimmer (1), @iamfriendly (1), @MadtownLems (1), @vladytimy (1), @denisco (1), @Krstarica (1), @hareesh-pillai (1), @bobbingwide (1), @lpawlik (1), @spacedmonkey (1) and @activecoder (1).

Please welcome our 3 new Core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. of the week ♥️
@engahmeds3ed, @vladytimy and @activecoder.

Core committers: @timothyblynjacobs (8), @sergeybiryukov (3) and @desrosj (1).

#5-6-1, #5-7, #week-in-core

Jb Audras 12:15 pm on December 31, 2020
Tags: , ,   

DevChat meeting Summary – December 30th, 2020

@lukecarbis and @audrasjb led the weekly meetings of the WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team, respectively at 05:00 UTC and 20:00 UTC.

Announcements

The WordPress 5.7 Development Cycle has been posted. The core team is targeting a final release date of March 9, 2021. More information available on the milestone page.

@hellofromtonya published the incoming bug scrubs schedule for 5.7.

The FSE (Full Site Editing) Outreach Program has its first call for Testers, specifically designed to explore the interaction between the two editing experiences (post vs. template editing) to make sure it’s clear when users are editing each. If you’d like to help test and provide feedback, please comment on the related post.

Another Week in Core blogpost was published. Most of the tickets of that timeline relate to Twenty Twenty-One and Twenty Nineteen bundled themes. Core team reps added a new props section to highlight contributors who made their very first contribution to WordPress Core.

A weekly Gutenberg update was also published on Make/Core.

Twenty Twenty-One and Twenty-Nineteen bundled themes recently had version updates. @desrosj published a recap on Make/Core. Indeed, bundled themes can iterate independently from Core releases. Of course, WP Core next point 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. will ship these changes.

Upcoming WordPress releases

WordPress 5.7

Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Lead @hellofromtonya shared some insights:

  • We’ve had 4 early scrubs in Dec: with one in APAC and the other for EMEA/AMER
  • Participation has been light due to the year end and holidays
  • In January, we’ll shift focus to early, high priority, features, and enhancements

And also TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. stats:

  • 200 tickets in the milestone
  • 33 closed tickets
  • 31 tickets marked early
  • 86 defects
  • 68 enhancements
  • 6 features
  • 18 tasks

200 tickets for a 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. is quite light. @hellofromtonya will be looking for other opportunities as well as talking with component teams/maintainers to see if there are other tickets we might be able to land in the milestone. @sergeybiryukov pointed out that with 4 releases a year instead of the usual 3, it’s expected that the number of tickets in each could be a bit lower. 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 is coming quickly. So the quantity of tickets needs to be balanced with time and capacity.

@hellofromtonya shared a link to tickets marked as early + needs-testing. Everyone is invited to test them and provide feedback.

WordPress 5.6.1

There is currently 49 tickets in milestone 5.6.1. 23 are already closed as fixed, mostly related to Bundled themes.

As WP 5.6.1 may probably be released around mid-January, it would be nice to schedule few 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 next week. Please get in touch with @audrasjb if you want to run a scrub. @marybaum, @metalandcoffee and @hellofromtonya raised their hands during the chat. An agenda will be published by the beginning of January.

Component maintainers updates

From @sergeybiryukov:

Build/Test Tools: Random unit testunit test Code written to test a small piece of code or functionality within a larger application. Everything from themes to WordPress core have a series of unit tests. Also see regression. failures in REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. 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 controller tests due to external 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. request timeouts should now be resolved with [49913].

General: A second pass was made at replacing Codex URLs with a corresponding HelpHub or DevHub article in [49912].

I18Ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill., Date/Time, Permalinks: No major news this week.

From @afragen:

Upgrade/Install: If you have access to a resource poor, shared hosting server we could use your testing experience on #51857. Specifically the goal is to determine if there might be a timeout issue for the zipping/unzipping processes.

@pbiron proposed to move #51928 to milestone 5.6.1. The attendees agreed to prioritize this ticketticket Created for both bug reports and feature development on the bug tracker. to get it ready for 5.6.1 release mid-January. @davidbaumwald raised some concern about moving an enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. to 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. milestone and about making final decision during devchat. The ticket was changed from enhancement to blessed task as this is not an enhancement for end-users but mostly something related to 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/ Updates APIs. @audrasjb pointed out that changing the milestone and the type of a ticket is not a final decision. Final decision will be the commit action. @dd32 was also mentionned for final decision, as WP Lead Developer and Updates 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. maintainer.

#5-6-1, #5-7, #devchat

Jb Audras 12:26 am on December 29, 2020
Tags: ,   

A Week in Core – December 28, 2020

Welcome back to a new issue of Week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Let’s 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 December 21 and December 28, 2020.

  • 18 commits
  • 32 contributors
  • 48 tickets created
  • 12 tickets reopened
  • 53 tickets closed

Most of the tickets that landed last week relate to Twenty Twenty-One and Twenty Nineteen bundled themes. A new version has been released for both themes, independently from the next WordPress 5.6.1 point 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.. Indeed, even if there is already a number of tickets slated in the related milestone, WordPress 5.6.1 is not planned at the moment since none of the tickets seem to be urgent or critical.

Except concerning bundled themes and… as expected, Trac has been fairly calm these days ❄
The WordPress 5.7 Alpha Cycle should regain its develop-test-commit pace after New Year’s Eve.

Ticketticket Created for both bug reports and feature development on the bug tracker. numbers are based on the Trac timeline for the period above. The following is a summary of commits, organized by component.

Code changes

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)

  • Add more contrast to input borders during installation – #51854

Build/Test

  • Send Code Coverage reports to Codecov – #52141
  • Use shared post fixture in comment template tests – #51802

Bundled Themes

  • Twenty Nineteen: Add the block-patterns 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.) to the appropriate SASS file – #52159
  • Twenty Twenty-One: Set a maximum width on inputs – #52083
  • Twenty Twenty-One: Improve strings found in post navigations for easier translating – #52047
  • Twenty Twenty-One: Only load IE specific polyfills when actually using Internet Explorer – #52098
  • Twenty Twenty-One: Improve striped table styling in Dark Mode – #52129
  • Twenty Twenty-One: Do not specify loading=“eager” for single post thumbnails – #52139
  • Twenty Twenty-One: Allow local anchor links to be used in primary navigation – #52006

Docs

  • Correct the type of the $user parameter in WP_REST_Users_Controller::prepare_links() – #52175

Editor

  • Align 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/ the name of generated asset handle for core blocks – #50328

Export

  • Add post_modified and post_modified_gmt fields to the generated WXR export file – #52180

Posts, Post Types

  • Correct the check for term IDs to be queued for lazy-loading term 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. – #52144

Site Health

  • Add WP_MEMORY_LIMIT constant to debug info – #51680
  • Detect HTTPSHTTPS HTTPS is an acronym for Hyper Text Transfer Protocol Secure. HTTPS is the secure version of HTTP, the protocol over which data is sent between your browser and the website that you are connected to. The 'S' at the end of HTTPS stands for 'Secure'. It means all communications between your browser and the website are encrypted. This is especially helpful for protecting sensitive data like banking information. support and encourage switching – #47577

XML-RPC

  • Emit an appropriate 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. status code when an error is returned in response to an XML-RPC request – #48213

Props

Thanks to everyone who contributed to WordPress Core on Trac last week:

@poena (7), @audrasjb (2), @flixos90 (2), @ryelle (2), @aristath (2), @peterwilsoncc (2), @basscan (1), @kjellr (1), @sabernhardt (1), @SergeyBiryukov (1), @jmdodd (1), @ismail.elkorchi (1), @melchoyce (1), @celendesign (1), @ericmann (1), @macmanx (1), @danfarrow (1), @swissspidy (1), @sanketchodavadiya (1), @desrosj (1), @westonruter (1), @miinasikk (1), @Clorith (1), @akabarikalpesh (1), @denishua (1), @mukesh27 (1), @iviweb (1), @Maigret (1), @noisysocks (1), @talldanwp (1), @nre (1) and @t-p (1).

Please welcome our 7 new Core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. of the week ♥️
@celendesign, @sanketchodavadiya, @denishua, @iviweb, @Maigret, @nre and @t-p.

Core committers: @sergeybiryukov (6), @desrosj (6), @flixos90 (1), @jorbin (1), @ryelle (1), @johnbillion (1) and @gziolo (1).

See you in 2021 for the next Week in Core issue! 🌟

#5-7, #week-in-core

annezazu 1:14 am on December 22, 2020
Tags: , ,   

Core Editor Improvement: Video Subtitles

While some people might think of the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor as being focused on the writing experience, it’s so much more than that, especially with what’s now possible thanks to numerous core blocks and the future site editing world. This post is about one of these new content tools that you might have missed in the last few months of recent releases: the ability to add video subtitles. With more and more people venturing into the video space thanks to them being easier than ever to create, this new feature packs powerful capabilities for content creators and their viewers alike. 

To take advantage of this new feature, just upload a video and use the Text Tracks setting to upload your subtitles as shown below: 

The Text Tracks setting options now included in the Video 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..

People viewing your site can enable captions through the settings of the video player. Here’s a screenshot of a video with captions on to get a sense of the experience: 

Example of a paused video with subtitles enabled.

Now you can engage with your audiences so they can catch what you’re up to whether they might have limited hearing, don’t want to wake a sleeping baby/pet/person nearby, or prefer reading along while watching your video. Happy creating! 

If you’re interested in working on features like this, make sure to join #core-editor, check out the current focuses, and attend the Core Editor weekly meeting @ 14:00 UTC in core-editor. 

#core-editor-improvement #core-editor #accessibility

Jb Audras 11:50 pm on December 21, 2020
Tags: , 52071XML-RPC,   

A Week in Core – December 21, 2020

Welcome back to a new issue of Week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Let’s 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 December 14 and December 21, 2020.

  • 41 commits
  • 57 contributors
  • 81 tickets created
  • 12 tickets reopened
  • 90 tickets closed

Now that WordPress 5.6 « Simone » was smoothly delivered to millions of people, the WordPress Core Team is quietly moving to WordPress 5.7.

Ticketticket Created for both bug reports and feature development on the bug tracker. numbers are based on the Trac timeline for the period above. The following is a summary of commits, organized by component.

Code changes

Build/Test Tools

  • Build/Test Tools: Support the use of MariaDB in the local Docker environment – #51744
  • Build/Test Tools: Run the Ajax test group for multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site – #46567
  • Build/Test Tools: Generate a code coverage report using 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/ Actions – #52034

Bundled Themes

  • Twenty Twenty-One: Do not specify `loading=“eager”` for single post thumbnails – #52139
  • Twenty Twenty-One: Allow local anchor links to be used in primary navigation – #52006
  • Twenty Ten: Correct `$post_title` variable name in `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.-attachment.php` – #52121
  • Twenty Twenty-One: Clarify a sentence in `readme.txt` – #52120
  • Twenty Nineteen: Add “Continue reading” link for post excerpts – #46177
  • Twenty Twenty-One: Correct `since` inline documentation tags – #51958
  • Twenty Twenty-One: Make text within code blocks readable in Dark Mode – #51985
  • Twenty Twenty-One: Prevent `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.` embeds from being too narrow – #52004
  • Twenty Twenty-One: Fix typos in some inline comments – #52071XML-RPC: Emit an appropriate 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. status code when an error is returned in response to an XML-RPC request – #48213

Docs

  • Use a canonical form of “knowledgeable” in `readme.htmlHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers.` – #52125
  • Fix typo in `getCursorMarkerSpan()` DocBlockdocblock (phpdoc, xref, inline docs) in `js/_enqueues/wp/editor/base.js` – #52128

Editor

  • Fix improper triggering of the “Are you sure” prompt when navigating away from the old, “classic” Edit Post screen and there are no changes. Was
  • Blocks: Align 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/ the name of generated asset handle for core blocks – #50328

Feed

  • Replace `join()` with `implode()` for safety – #51056
  • Merge multiple 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. values to avoid fatal error – #51056

Mail

  • Introduce a `pre_wp_mail` filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. to allow short-circuiting the `wp_mail()` function without having to override the pluggable function – #35069

Media

  • Editor: Fix improper triggering of the “Are you sure” prompt when navigating away from the old, “classic” Edit Post screen and there are no changes. Was triggered when there is an instance of TinyMCE in 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. postbox – #52038
  • Enable lazy-loading of iframes by adding the `loading=”lazy”` attribute to iframe tags on the front-end – #50756
  • Uploads: Introduce the `{$action}_overrides` filter that allows the overrides parameter for file uploads and file sideloads to be filtered – #16849
  • Fix the template for the “Align” and “Link To” fields in the media modal when inserting an image from URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org

Query

  • Respect post-type specific capabilities when querying for multiple post types – #13509, #48968, #48556
  • Ensure the author archive title always shows the name of the queried author, regardless of whether there are results – #44183

Props

Thanks to everyone who contributed to WordPress Core on Trac last week:

@mukesh27 (5), @poena (5), @SergeyBiryukov (4), @audrasjb (2), @johnbillion (2), @Mte90 (2), @azaozz (2), @sabernhardt (2), @flixos90 (2), @westonruter (1), @justinahinon (1), @slaFFik (1), @leogermani (1), @helen (1), @thorlentz (1), @laurelfulford (1), @ericmann (1), @kevin940726 (1), @rodrigosprimo (1), @jonathanstegall (1), @alex27 (1), @noisysocks (1), @david.binda (1), @litemotiv (1), @inc2734 (1), @NicolasKulka (1), @hellofromTonya (1), @mbabker (1), @skithund (1), @desrosj (1), @timothyblynjacobs (1), @mdrockwell (1), @davidbaumwald (1), @metalandcoffee (1), @swissspidy (1), @ryelle (1), @macmanx (1), @t-p (1), @aristath (1), @iandunn (1), @jakub.tyrcha (1), @nacin (1), @wonderboymusic (1), @DvanKooten (1), @jtsternberg (1), @ocean90 (1), @ericlewis (1), @birgire (1), @ayeshrajans (1), @Tkama (1), @subrataemfluence (1), @shahinsid07 (1), @voboghure (1), @gkibria69 (1), @garrett-eclipse (1), @netweb (1) and @manzurahammed (1).

Core committers: @desrosj (8), @sergeybiryukov (5), @johnbillion (4), @azaozz (2), @iandunn (2), @gziolo (1), @boonebgorges (1) and @flixos90 (1).

Thanks @annezazu for proofreading this post.

#5-7, #week-in-core

annezazu 8:12 pm on December 21, 2020
Tags: , ,   

Core Editor Improvement: Text Only Icons for the Toolbar

A lot of work has been done to improve the infrastructure of the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor and expand what’s possible technically. It is also important to pause and highlight improvements that make creating with the core editor easier than ever before. This post seeks to highlight one of those recent features that might have been missed in the flurry of recent releases: the ability to have descriptive text icons instead of an icon only view of the Block Toolbar. Since the Toolbar is currently one of the main ways we all interact with the Core Editor this is a big change that should have big benefits. Text icons unlock the ability for you to tailor your experience of the Toolbar and helps more people have the flexibility to create with the Core Editor. In particular, these icons improve settings from an 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) standpoint for those relying on tooltips.

To get a sense of just how much of a difference this makes, check out the following screenshots showing the different options available: 

Icon Only: 

Icon Only view in the Core Editor Toolbar

Text Only: 

Text Only view in the Core Editor Toolbar

How to find this option

Here’s a helpful GIF that illustrates where you can easily find this setting in the Options menu under the Appearances section:

Settings can be adjusted under the Options menu in the Appearance section by toggling “Display Button Labels”.

Try out both and see which works best for you. If you’re like me, you might find times when it’s helpful to use each. Perhaps you’re teaching someone about the Core Editor for the first time, and they find the text-based options easier to understand! Or, you are trying to write a lengthy post and find Icon Only to feel less distracting. No matter the circumstance, the option is there for you to experience the toolbar in the way that works best for whatever you’re trying to do. 

If you’re interested in working on features like this, make sure to join #core-editor, check out the current focuses, and attend the Core Editor weekly meeting @ 14:00 UTC in core-editor. 

#core-editor-improvement #core-editor #accessibility

Paal Joachim Romdahl 5:55 pm on December 21, 2020
Tags: , , , ,   

Editor chat Summary: 16 December, 2020

This post summarizes the weekly editor chat meeting (agenda here) held on 2020-12-16 14:00 UTC. 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/ 9.6.0 RC release

Gutenberg 9.6.0 RC was released 16th December. It will have one week of testing before general release.

WordPress 5.6 release

WordPress 5.6 was released on 8th December.
Be sure to check the forums as well as the Gutenberg repository for user feedback.

Monthly Priorities

December monthly priorities. Along with Key Project updates.

Full Site Editing

@annezazu
Full Site Editing Outreach program is starting up with the launch of Gutenberg 9.6: https://make.wordpress.org/core/2020/12/11/the-fse-outreach-program-is-officially-starting/ Join (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)
#fse-outreach-experiment to take part in the exploration.

@aristath
Working on blocks assets loading for FSE themes. Finding ways to address styles for blocks that will be loaded asynchronously via infinite-scoll or other mechanisms. Experimenting with inlining & minifying assets on the fly when 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. gets loaded.

Global Styles

@jorgefilipecosta
Global Styles Project: We made sure Font Weight and Style can be used independently on Global Styles.
Changes: Font Weight, Style and decoration are not presets anymore.
Box control now supports custom units .
Implemented border radius support.
A few bugs were fixed Fix: Block crashes if font family is not found.

Widgets Screen and the 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.

@andraganescu
Widgets screen: Nothing notable on the widgets screen or on adding blocks in customizer. Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. sessions for both Widgets and Navigation will restart in 2021.

Task Coordination

@youknowriad

  • Drag and drop from the inserter.
  • Some 5.6 documentation follow-ups.
  • Some refactorings around Popover/Dialogs (reusable 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.).
  • More FSE related work on the next week(s).

@ntsekouras

@annezazu

  • Prep work for the launch of the #fse-outreach-experiment, 5.6 Q&A follow up, triage of 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/ repo, launched the overhaul of the new https://make.wordpress.org/core/features/ page (now with coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. editor items!) with the teamwork of @noisysocks, and doing various FSE testing with different block themes.

@get_dave

  • Adding an experimental Gutenberg REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. endpoint to allow us to get data about a remote URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org for use in the editor (eg: contents of <title> 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.) or favion…etc). Potential use cases:
  • 1. Showing an embed preview for generic links when pasted into editor (a la Slack).
  • 2. Showing details about a link being added using LinkControl.
  • Making some tweaks soon and then should be ready to merge: Add URL Details endpoint to REST API to allow retrieval of info about a remote URL.

@tug

  • Good progress on porting the Audio block.
  • Improving our CI tests and working on performance tweaks.
  • Porting Audio and Code blocks related to the RN v0.63 upgrade.
  • Link picker integrations in blocks. 

Open Floor

@Settimo Augusto Vittorio

  • Needs help with Post title block: Enabling the link changes the position of the block.
  • Proposed a ServerSideRenderedDataDrivenBlock, to enable developers who don’t know js to write blocks. A toggle to enable a preview.
    @joyously
    The shortcodeShortcode A shortcode is a placeholder used within a WordPress post, page, or widget to insert a form or function generated by a plugin in a specific location on your site. block could be extended to use the expected attributes as inputs in 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.. (like ShortCake 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 was trying to do)
    Link to additional discussion on Slack.

@joyously

  • There are usually some forum topics about coding blocks, but no one to answer them.

@daisyo

  • Starting the “What’s Next” post for January. If you have specific focus areas (issues, PRs, etc) planned for the month please feel free to share them with me. Hearing from you all helps to make this post really useful for those outside of the core editor contributor team.

@paaljoachim

  • The 16th December Core Editor chat was the last before the holidays. 23rd and 30th December there will be no official chats. The next chat in the new year will be 6th January.
  • Merry Christmas and a Happy New Year! Have a beautiful and relaxing holiday! See you in the new year!

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

Dan Farrow 12:14 pm on December 21, 2020
Tags: ,   

CSS Chat Summary: 17 December 2020

The meeting took place here on Slack. @notlaura facilitated and @danfarrow (me!) wrote up these notes.

Housekeeping

We discussed the meeting schedule over the next two weeks. There was general agreement that we should take the next two weeks off, so the next meeting will be 07 January 2021. Happy holidays!

CSSCSS Cascading Style Sheets. Audit (#49582)

@danfarrow reported that we can now add a note to the !important audit ticketticket Created for both bug reports and feature development on the bug tracker. #26350 with a link to the !important audit section of the report (update: this note has now been added here).

Thanks to @sabernhardt‘s comprehensive audit spreadsheet we can see that the number of !important declarations has dropped from 142 at the start of this year to the current 106.

@ryelle reported an issue with the colour counts which means they are slightly off, however in order to fix it would require a major overhaul of the audit process. However, the discrepancy is minor.

@ryelle also noted that colours defined in colour schemes are not currently included in the numbers and suggested that they should be included.

Color Scheming (#49999) & Visual 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. Testing (#49606)

@ryelle has pushed a PR for reduced colours in core which is one step in her plan outlined in this comment.

She also shared her excellent before & after comparison page built to enable comparison between current & reduced colours.

We agreed that the next step is to bring this up in the first dev chat in January.

For visual regression testing, @isabel_brison suggested that the next step would be to separate the test config from the e2e config to enable them to be run independently.

Open floor & CSS link share

@danfarrow shared an enlightening article on The Surprising Things That CSS Can Animate, from the UI Animation newsletter.

@notlaura shared an excellent CSS Tricks article from Jeremy Keith on “the enjoyment of building a website with plain ol’ HTML, CSS, and JavaScript” which inspired an exchange of thoughts & feelings about web tools.

The conclusion was that our favourite web tool platform is of course ❤️ WordPress ❤️, and on that note the meeting concluded.

Thanks everybody and see you in 2021!

#core-css, #summary

Lara Schenck 7:53 pm on December 17, 2020
Tags: ,   

CSS Chat Agenda: 17 December 2020

Note: 1 hour before the meeting this week, @sabernhardt will lead the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. CSSCSS Cascading Style Sheets. 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. triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors.!

This is the agenda for the upcoming CSS meeting scheduled for Thursday, December 17, at 10:00 PM UTC. This meeting will be held in the #core-css channel in the Making 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/..

If there’s any topic you’d like to discuss, please leave a comment below!

  • Housekeeping
  • Updates
    • CSS Audit (#49582)
    • Color Scheming (#49999) – Visual 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. Testing (#49606)
  • Open floor + CSS link share
#agenda, #core-css