This post summarizes the weekly editor chat meeting agenda. Held on 2020-08-12 14:00 UTC in Slack. Moderated by @paaljoachim.
WordPress 5.5 was released on 11th August.
Gutenberg 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/ 8.7
The latest release of Gutenberg, version 8.7 was released 5th of August.
The Monthly Priorities
The monthly plan for August.
Navigation block 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. chat.
Scroll back to Navigation block chat.
- I’ve been working on the server-side support for Block API 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. support flags.
- I’m planning to focus more deeply on the “Editor controlling APIs”
- I’ll probably spend some time on the forums to check 5.5 feedback and issues.
- This week I’ve been working on prep work regarding block styles and FSE/Global-Styles: Removing hardcoded colors from block-styles, separating editor & front-facing styles, converting absolute units to relative etc.
- Accordion block. I’ll have some style variations up this week.
- Topbar labels for icons with @tellthemachines.
- New icons for Post blocks.
- Widget 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.-block editor designs (Figma file).
- Catching up and reviewing. Always happy to review.
- Helped @ntsekouras land his changing of Embed blocks to block variations.
- Been reviewing PRs such as refactors or Global Styles-related items.
- Triaging issues.
- Team support.
- Focus on experiments on evolving the Editor UI.
- Taking a deep look into wordpress/components, and seeing how it can be improved to address many pain-points + missing features we have today, and setting up the UI User interface layer for success for the future. One of the many drivers for this is my involvement in improving editor Design Tools, which relies very heavily on the UI layer. I’ve started sharing some of these updates with folks via Zoom sessions, Github 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/ posts, and most recently, a dedicated blog (versus network, site) (published yesterday) https://g2components.wordpress.com/
- I’m planning on hosting another collab Zoom session today.
- Working on moving Global Styles forward and how that looks/feels within the editor (will be getting these into an issue soon) [Full Site Editing]
- Moving the first iteration of Multi-Entity Saving forward with engineering [Full Site Editing]
Comment by @paaljoachim
- Let’s be sure that any Full Site Editing UI adjustments are also reflected back to the regular Gutenberg content creation where it is applicable to do so.
From the agenda post.
@zebulan brings focus to the work done by @aristath on the usage of relative units (rem, em) in relation to block styles in themes and removing hardcoded colors. PRs.
Getting workshops up on learn.wordpress.org. One of the workshops is a beginners guide to block development, following by a group discussion. It would be helpful to have Gutenberg developers present. We need feedback. The group discussion details (including date and time) are on the meetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. event – https://www.meetup.com/learn-wordpress-discussions/events/272503390, the actual workshop you can watch any time on learn.wordpress.org.
Supporting prefers-color-scheme queries.
Gutenberg has no option to set a Dark scheme in relation to user preference and a11y 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) issues. Discussion:
Check the experimental design tools by @q as color schemes is one of the areas he is experimenting with.
“Remove Embeds for Facebook and Instagram”
Basically Facebook is changing the FB and Instagram embeds on Oct 24, so older embeds will no longer work. So at what point should we remove from WP?
Brought up the above issue during the Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Dev chat in the #core channel on Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.. Link to discussion: https://wordpress.slack.com/archives/C02RQBWTW/p1597265852021400
Andrei are there notes or follow up on the Nav meetings?
The idea being theme authors need to look at building progressive enhancements, and keeping up with this feature even if it is exploratory would have benefit to FSE and communicating with the theme team. I can take a look at today’s meeting then and go from there.
Back scroll link to Navigation meeting held in #core channel on Slack.