Ways to keep up with Full Site Editing (FSE)

As work on Full Sitesite (versus network, blog) Editing continues, it’s important that communication around the project is made explicit so everyone can follow along appropriately. Each person will have their own unique needs in keeping up with a project of this scale so what follows is more of a catalogue of ways to keep up rather than a recommendation for how to do so. 

Yearly:

The 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/ Roadmap with Four Phases 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/ updated by @chanthaboune and/or @matt. This is the highest level overview of the changes coming to WordPress.

Quarterly: 

Quarterly Updates from Contribution Teams, coordinated by @chanthaboune. These updates give an overview on what each team is working on, struggling with, and how to get involved.

Monthly: 

“What’s Next In Gutenberg?” posts. These updates are wrangled by the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor team and highlight what’s planned for the coming month of work on Gutenberg. 

Block Based Themes Chat. These chats are currently wrangled by @kjellreigstad in the #themereview 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 and are dedicated to sharing FSE changes that will specifically impact themes. Agendas and summaries are shared on the make/themes blog

Biweekly: 

“What’s New In Gutenberg?” posts. These updates are wrangled by the Core Editor team and focus on what’s been released in each biweekly Gutenberg releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software.. Currently, they tend to mimic a changelog.

Weekly: 

Core Editor chats. These chats are wrangled by volunteer members in the #core-editor Slack channel. Agendas and summaries are shared on the make/core blog. They focus on task coordination and relevant discussions around Gutenberg releases. There is an Open Floor period in each chat where people can suggest topics to discuss.

Weekly Gutenberg Design Updates wrangled by @mapk. These posts capture the big discussions and work being done in the design of Full Site Editing and Gutenberg in general.

Weekly Theme Related Gutenberg Updates (new initiative) wrangled by @kjellr. These posts are focused on themes, including everything from current discussions to recent changes, as well as helpful resources for theme authors. 

Daily:

Checking in on FSE PRs and FSE issues 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/. This will give you a nearly real-time understanding of what’s being worked on by the developers and designers. 


Each of these are reliable ways of keeping up with the ongoing work on the new Full Site Editing feature coming to WordPress. A big thank you to everyone helping with these various initiatives!

Feedback welcome

What kinds of updates or communication might be missing? What might makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). these current updates and chats easier to follow? Share your ideas and feedback in the comments below! A next step to this work will be refining these communication pathways based on the feedback collected here and elsewhere.

Thank you to @itsjusteileen @andreamiddleton @paaljoachim @mapk for giving me feedback on this post.

#full-site-editing, #gutenberg

Editor chat Summary: 29 January, 2020

This post summarizes the weekly editor chat meeting agenda here. Held on Wednesday, 29th January 2020 held in Slack. Moderated by @youknowriad.

Weekly Priorities

@jorgefilipecosta
We are getting closer to the WordPress 5.4 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. releases.
ReleaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. dates:
11 February 2020 – Beta 1 – Deadline for new features (after this date, only 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. fixes for regressions in the release).
18 February 2020 – Beta 2
25 February 2020 – Beta 3
3 March 2020 – RC1
10 March 2020- RC2
17 March 2020 – RC3
24 March 2020 – RC4
31 March 2020 – 5.4 Release day

The main priority is making sure we don’t send an unfixed critical issue on the first WordPress 5.4 beta. To track the issues we have a project board:
https://github.com/WordPress/gutenberg/projects/39
We should give particular care to issues raised after 18th of September (date of the last 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/ release that was included in WordPress 5.3).

@youknowriad
Gutenberg 7.4 on Feb 5 (RC on Feb 3)
(Exceptional release) Gutenberg 7.5 on Feb 12 (RC on Feb 10)
Both will be included in WP 5.4.
What do you think about the current state of things?

@jorgefilipecosta
Currently it seems we are on track. Some new features like the custom gradient picker may need some focus to be polished and could benefit from tests/feedback. https://github.com/WordPress/gutenberg/issues/16662 and https://github.com/WordPress/gutenberg/pull/19582
I would also like to request everyone that implemented experimental 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.’s to think if they could be made stable before WordPress 5.4. It would be good to reduce experimental API’s as much as possible.

I will soon add a comment on https://github.com/WordPress/gutenberg/issues/17743 pinging the authors of API’s I think could be stabilised.

@gziolo
We are discussing with @mcsf 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. variations. It is nice to have for 5.4.
I believe that Social Icons is still not exposed for WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. so we only would include this new API paired with Social Icons block.

I also don’t feel that we can makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). the accessible toolbar for 5.4 but maybe it’s better to have it enabled together with the block toolbar redesign. In the gist, it’s change in the tabbing behavior where every toolbar is only one tab stop and you can navigate between items with arrow keys, home, end, etc. Super important from 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.

@mkaz
We started a draft PR iterating on Social Icons adjust implementation to allow for no-duplication of assets and making extendable, but there are some trade-offs being considered:
https://github.com/WordPress/gutenberg/pull/19888

Task Coordination

@karmatosed
I’ve had my head deep in Figma working on global styles. Focusing on the minimum version first. I also have been diving into controls. I also have been working on some iterations to color picker. Along the side there is as always a constant flow of triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors..

@youknowriad
Still working on the Dashicons and gathering all icons under the same package. Wrote some blogblog (versus network, site) posts about Gutenberg Extensibility APIs and Modularity. https://make.wordpress.org/core/2020/01/23/controlling-the-block-editor/
Reviewing, triaging as I can.
I’m hoping to continue on the icons and to circle back to the keyboards shortcuts package work as there’s still some improvements to make to allow third-party shortcuts to show up in the modal.

@jorgefilipecosta
Last week:
I started the work on the global styles, proposed the resolver system.
Iterated on the angle picker and merged it.
Triaged issues relevant for WordPress 5.4 & submitted bug fixes.
Next week:
Audit experimental APIs. Stabilize some API’s I proposed.
Audit 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. and create an issue summarizing all the dev notes needed.
Continue the work on global styles.
Continue the work on the custom gradient picker.
Continue the WordPress 5.4 preparations by triaging and fixing issues.
PR reviews.

@andraganescu
I am working on adding features to the author block.
https://github.com/WordPress/gutenberg/issues/19696 and
https://github.com/WordPress/gutenberg/pull/19894

@mkaz
We have some cool image editing tools we’d love to get in at some point, appreciate some feedback and guidance. Issue and details added here, 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 available for testing: https://github.com/WordPress/gutenberg/issues/13748#issuecomment-574903126

@aduth
Been working a fair bit around the LinkControl component and related implementations (Popovers, etc). I expect to be continuing this in the next week.
Discussing user preferences persistence using 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.. There’s been a lively discussion in https://github.com/WordPress/gutenberg/pull/19177

@nosolosw
I’ve also been diving into GlobalStyles (master issue at https://github.com/WordPress/gutenberg/issues/19611) pairing with Jorge and Q. My focus at the moment is accommodating the prototypes shared in the issue into the proper data structures, client side.
Need a tech review at https://github.com/WordPress/gutenberg/pull/14930

@gziolo
Merged create-block package for block scaffolding, still not published to npm until next Wednesday.
Landed Variations API integration with the inserter.
Some more work to improve the workflow for syncing Gutenberg and WP core.
I plan more work on the Variations API and smaller accessibility improvements I started earlier.

@mcsf
I have been focusing on the Block Patterns Variations API with @gziolo and exploring applying that to Social Links: https://github.com/WordPress/gutenberg/pull/19887
Discussing what @epiqueras initially proposed of server-side rendering support for parent attributes context:
https://github.com/WordPress/gutenberg/issues/19685
Improved the way RichText blocks do or don’t automatically transform content into another block: https://github.com/WordPress/gutenberg/pull/19727

@itsjonq
Continue with Global Styles work. Pairing with @karmatosed, @nosolosw, and @jorgefilipecosta for various parts. Also diving deeper into the technical aspects/flow and planning.
https://github.com/WordPress/gutenberg/issues/19611
Updates to the RangeControl component in wordpress/components at https://github.com/WordPress/gutenberg/pull/19916

@richtabor
Background color support for Columns block has landed: https://github.com/WordPress/gutenberg/pull/17813
Tidied up labels/titles to use sentence case formatting: https://github.com/WordPress/gutenberg/pull/19903 and https://github.com/WordPress/gutenberg/pull/19901

Open Floor

@SvenWeber asked about this issue: https://github.com/WordPress/gutenberg/issues/19898
@aduth added a comment to the issue.

@Munirkamal asked:
How can I replicate the “Add to Reusable Blocks” functionality on my custom Gutenberg Block which I need to allow users to save to a custom post typeCustom Post Type WordPress can hold and display many different types of content. A single item of such a content is generally called a post, although post is also a specific post type. Custom Post Types gives your site the ability to have templated posts, to simplify the concept.. So users will be able to save the block to a defined post type like core add to reusable functionality.
@epiqueras
I think he means saving the blocks to a different CPT.
https://github.com/WordPress/gutenberg/blob/5cb272724b30877217c9ec2d6ee0f4724deb4b51/packages/block-library/src/template-part/edit/index.js#L39
https://github.com/WordPress/gutenberg/blob/5cb272724b30877217c9ec2d6ee0f4724deb4b51/packages/block-library/src/template-part/edit/inner-blocks.js#L8-L21
@youknowriad
You just need to save a wp.blocks.serialize( block ) and save as “content” of your CPT.

@kjellr
A brand new recurring meeting in the #themereview channel. It’s dedicated to crafting the future of block-based themes in concert with the full-sitesite (versus network, blog) editing work happening in Gutenberg. It will be held bi-weekly on Wednesdays @ 16:00 UTC, beginning Feb 5th. Look for an official post about the meeting on make.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org//themes later today.

#agenda, #core-editor, #gutenberg

Core editor chat summary 4th December, 2019

This post summarizes the weekly editor chat meeting agenda here. Held on Wednesday, 4th December 2019 held in Slack. Moderated by @ellatrix.

Full Sitesite (versus network, blog) Editing and themes

@ellatrix
The idea here is to recap what’s being worked on, what has been discussed in #themereview yesterday’s meeting and provide some space for feedback and discussions about the next steps.
Must Read:
– Summary for yesterday’s #themereview meeting
https://make.wordpress.org/themes/2019/12/04/questions-about-the-future-of-themes/
– Documentation for the current state of 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 themes
https://github.com/WordPress/gutenberg/pull/18890

@youknowriad
The main takeaways/action items for me are:
– Let’s have theme authors experiment with these in 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//personal themes and provide feedback: Gather a list of Missing blocks?
– Potentially help build a demo theme in GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ in this folder https://github.com/WordPress/gutenberg/blob/master/lib/demo-block-templates/index.html
– From the editor side, continue on the current PRs/work https://github.com/WordPress/gutenberg/labels/%5BFeature%5D%20Full%20Site%20Editing

@williampatton
Sounds good to me, in addition we will also be doing more to get stuck in and help you all out with comments, PRs and testing as we all makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). time for it in the coming weeks.

@noisysocks
If I’m a theme author and read these incredibly helpful links and have some questions or comments, where should I put them?

@youknowriad
I think at the moment (only during experiment phase), it should be fine to ask here and raise Github issues for bugs. We should also take these as opportunities to document things as we move forward from both themers and devs.

Weekly Priorities

@youknowriad
I’d like to share the new priorities post for December in case you missed it https://make.wordpress.org/core/2019/12/03/whats-next-in-gutenberg-december/
An emphasize on Block content areas / Full site editing and also a push for Block Patterns APIs and usage across blocks and inserter in addition to a few tightening up items.

Task Coordination

@aduth
I’ve been focusing more on framework-y stuff:
– Get types checking in place https://github.com/WordPress/gutenberg/issues/18838
– A never-ending crusade to stabilize Travis build
Hoping in the next week to revisit some feature work:
– Better _fields handling in wordpress/apiFetch and/or wordpress/data
– Revisit spoken messages in Notice pull request
– Also been fixing up a few theme interoperability issues, notably around background colors for custom editor styles:
https://github.com/WordPress/gutenberg/pull/18732
https://github.com/WordPress/gutenberg/pull/18871
https://github.com/WordPress/gutenberg/pull/18873

@noisysocks
I’m somewhat looking at deprecating the wordpress/nux package but mostly reviewing PRs this week.

@ellatrix
I’ve been working on “Lighter block DOM: detached controls in popovers”, improvements on Popover, multi block selection, and paste on multi block selection.

@get_dave
I’ve been working on…
…a PR to allow parent blocks to capture the Block toolbars of all child blocks which is just waiting on a thumbs up from @jorgefilipecosta:
https://github.com/WordPress/gutenberg/pull/18440
…adding justification tools to the Navigation Block:
https://github.com/WordPress/gutenberg/pull/18909

@jorgefilipecosta
Past week:
– Reviewed some media-related PR’s, namely the refactor to the gallery, to increase reusability with the native mobile APP.
– Helped the enhancements to useColors and merged the PR that uses the hook in the paragraph.
– Finish the remove editor module usages in block-editor by applying changes to the reusable blocks, rich-text, and native inserter. Some PR’s are waiting for a review.
– Updated the releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. tool to move readme and changelog files to the Github repository.
– Submitted several 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. fixes.
– Continued the interactions/enhancements on the PR’s I have open e.g.: custom gradients.
Next week:
– Increase my involvement with the FSE work (by reviewing PR’s and working on a subtask — Suggestions for a possible subtask are welcome 🙂 ).
– Continue giving my support to some media-related PR’s by reviewing and testing them, and maybe submit follow up enhancements.
– Rebase Update the buttons block PR and try to unblock the PR.
– Address reviews Add a mechanism to set a width on withViewportMatch https://github.com/WordPress/gutenberg/pull/17085.
– Fix some 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. related issues.

@youknowriad
I’ve mostly trying to make sure everyone is not blocked and also worked on some PR’s related to the block toolbar/UIUI User interface (fixed toolbar, select/edit modes…) and some code quality refactorings.

@richtabor
I have a PR for adding background color support to the Columns block:
https://github.com/WordPress/gutenberg/pull/17813

@welcher
I have a small docs PR that explains how to work with the changes to serverSideRender location: https://github.com/WordPress/gutenberg/pull/18722

@gziolo
Last week:
– Worked on fixes for 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. introduced in the block toolbar.
– Refactoring towards using the new accessible version of Toolbar component.
CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 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. to simplify the process of updating Gutenberg packages after every 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 release.
Next week:
– Resume work on Patterns 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. once we decide which blocks should be integrated (Table?, Cover?).
– Resume work on block.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. transformation on the client side to allow automatic handling of translations.

Open Floor

@gziolo
Resume work on Patterns API once we decide which blocks should be integrated (Table?, Cover?)
We have Columns block integrate, we use some sort of setup step for Table block, should we integrate it with Patterns API as well?
The challenge is that it needs to allow the custom creator as well.

We tried Media & Text but we abandoned this idea
https://github.com/WordPress/gutenberg/issues/16283#issuecomment-508132004
Information here: https://github.com/WordPress/gutenberg/pull/18343

There was additional conversations about patterns and transforms during the open floor: https://wordpress.slack.com/archives/C02QB2JS7/p1575469981089100

#core-editor, #gutenberg

PHP Meeting Recap – November 12th

This recap is a summary of our previous PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 meeting. It highlights the ideas and decisions which came up during that meeting, both as a means of documenting and to provide a quick overview for those who were unable to attend.

You can find this meeting’s chat log here.

Chat Summary

  • @schlessera adapted the README.md in the Servehappy repository so that it just links to the Feature Project page, to avoid requiring both to stay in sync.
  • Adding support for PHP version requirements to themes was discussed (Meta Trac #3718). The current state of the requirement for themes to have a readme.txt file does not seem to be clearly defined, as the only source of truth is the combination of an old blog post from 2015 and its collection of comments.
  • @afragen proposed to split the individual next actions for theme support into separate tickets, just as we did with plugins.
  • We also initiated contact with one of the team leads of the #themereview team (@williampatton) to discuss the current state of the theme’s readme.txt requirements.
  • @schlessera noted that while it seems we need to help move some unrelated stuff forward to get around our own blockers, we should be careful to avoid taking on too much responsibility and wasting our time on unrelated efforts.

Next week’s meeting

  • Next meeting will take place on Monday, November 19th, 2018 at 15:00 UTC in #core-php.
  • Agenda: Open floor.
  • If you have suggestions about this but cannot makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). the meeting, please leave a comment on this post so that we can take them into account.

#core-php, #php, #servehappy, #summary

Dev Chat Summary: September 12, 2018 (4.9.9 week 5)

This post summarizes the weekly dev chat meeting held Wednesday, September 12, 2018 at 20:00 UTC. Agenda | Slack archive


4.9.9 Planning

We have a Road Map and she is gorgeous. Thank you @antpb and @schlessera for putting it together. Here’s a summary:

Suggested Timeline

We will reassess these dates after the three-week mark:

  • 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. : Monday October 22, 2018
  • 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).Monday October 29, 2018
  • ReleaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. Date : Monday November 5, 2018

Key Focuses

  • Internationalization (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.)
  • 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)
  • Sitesite (versus network, blog) Health Project (Servehappy)
  • 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/ Merge Prep
    • The Gutenberg team has proposed some tickets already:
      • #44758 user localeLocale A locale is a combination of language and regional dialect. Usually locales correspond to countries, as is the case with Portuguese (Portugal) and Portuguese (Brazil). Other examples of locales include Canadian English and U.S. English. support 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/. endpoints
      • #44862 endpoints to lock/unlock and release posts
  • Other potential inclusions

If you’re interested in helping out with these topics, hit up these 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/. channels:

*Not real but should be.

Bug Scrubs

  • The plan is to run them weekly in the #core Slack channel across multiple timezones. Schedule 👏 Coming 👏 Soon 👏

Focus Lead and Component Maintainer Updates

Notes and Summary Posts

Additional Updates/Requests

  • From PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 Servehappy: More testers are needed for the WSOD protection on real-life, complex sites to reveal edge cases. A “complex site” is basically any site running locally with random plugins and random code.

If you’re thinking about get all up in these Focus and Component Maintainer teams, try attending a chat. Here’s the comprehensive list.


Open Floor

Tickets

Anyone can submit a ticketticket Created for both bug reports and feature development on the bug tracker. for the Open Floor. Send your submission to @jeffpaul or moi (@whitneyyadrich), or comment on the agenda for that week’s chat.

  • #12563: New action on body open – Submitted via @welcher. Will be discussed in the #themereview meeting.
  • #32326: Improve Support for Structured Data – This one pairs nicely with the ticket above, so the conversation should be happening in the #themereview room and scheduled chat.
  • #25280: wp_localize_script unexpectedly converts numbers to strings – Submitted via @adamsilverstein and Ivan Kristianto. Lots of words about code were had in the chat, and then the conversation was moved to the ticket itself.

General Announcements

Dev Chat Schedule

@psykro published his proposal for a second <dev chat> and it’s open for your comments. I’m sure we’ll touch on this during tomorrow’s dev chat, too. 

As always, anyone is welcome to join <dev chat> every Wednesday at 20:00 UTC. As I said in the chat, to sorta quote the late, great Notorious B.I.G.

I’m goin’ go call my WP crew
You go call your WP crew
We can rendezvous in <dev chat> tomorrow around two (or Wednesday at 20:00 UTC)

#summary, #4-9-9, #core, #dev-chat

Dev Chat Summary: October 12 (4.7 week 8)

This post summarizes the dev chat meeting from October 12th (agenda, Slack archive).

Reminders

  • Schedule: We are just one week from the final chance to merge in major features. This includes Twenty Seventeen. We are just two weeks from 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..
  • Tickets: There are currently 145 tickets in the 4.7 milestone. This is 22 fewer than last week 🎉However, in just 4 short weeks, this needs to be zero. Of note, there are 57 tickets classified as enhancements or feature requests, which needs to be zero in order to qualify as beta. For any tickets you’ve moved into the milestone, please makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). sure these are active tickets, with some kind of activity in the last 7 days. Any tickets remaining without an owner on Friday will be punted.
  • Bug Scrubs: @jbpaul17, @desrosj, & @stevenkword to run scrubs over the next week covering at least Thursday from 9:30am-11:30am and 2:30pm-5pm CDT, Friday from 9:30am-11:30am and 1:00pm-3:00pm CDT, Monday from 11am-12:30pm CDT, and Wednesday from 2pm-3pm CDT. If you have interest in helping run a scrub and help ensure tickets move forward, please reach out to @jbpaul17 and we’ll find a time & scrub focus that works best for you.

Feature Proposals for 4.7

  • REST API: Content API (@kadamwhite)
    • REST API Team Update
    • Content 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. endpoints have been stable for some time and now have the missing functionality established at the start of this development cycle
    • We pitched merging in the OAuth 1 server alongside those content endpoints, to simplify the process of authenticating from remote applications
    • The auth method in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. right now is cookie/nonce-based, so it’s available to any code running within the same domain as the main WordPress install and leverages the existing login cookie
    • plugins and themes that utilize JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. to enhance the editing experience within their adminadmin (and super admin) UIUI User interface have full read/write access, restricted to the capabilities of the authenticated user
    • External applications, e.g. a mobile app, desktop app or external server, would have read-only access
    • readers, aggregators, etc are possible without authentication, and more complex read-write apps can be written by installing one of the available authentication plugins, of which OAuth is but one
    • Reference for options and when/how to use
    • 90 contributors for the 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
    • automated test coverage currently at 90.44%
    • 37 more open tickets
    • weekly meeting on Monday at 1400UTC in #core-restapi
  • Discovering and installing themes in the customizer (@celloexpressions)
    • Related Make/Design and Make/Flow posts, but best to post all feedback to the Make/Core feature proposal
    • Working through the accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) feedback, but it’s a bit unclear what’s specific to this feature versus 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. in general, and which issues are also present in the admin theme installer
    • Haven’t heard anything from polyglots, security (unlikely to have any issues), or docs
    • There is one known 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. concern where we’ll need a compromise until we have JS i18n in core
    • @celloexpressions to do a final iteration to pick up any remaining feedback on Thursday, then pass to @westonruter for the code review process
  • Custom CSS with live previews (@celloexpressions)
    • seems to have decent support as a feature, with the biggest question in the comments being how to store and output the CSSCSS Cascading Style Sheets.
    • CSS is output from the db via a style 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.), use of `style` tag is key for targeting for `postMessage` live preview
    • Post-based storage allows for 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. built in (ensuring that there are 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. for a plugin that wants to write a file would alleviate many concerns)
    • CSS is theme-specific in the proposal for this, with a post object for each theme that has CSS
    • Scheduling a meeting to go through these concerns and make a decision, coordination to occur in #core-customize
  • Customize Changesets (née Transactions) (@westonruter)
    • Technical Post (audience is developers who have extended the customizer significantly, as there may be impacts to any heavy customizer integrations since changesets touches some very low-level stuff in the customizer)
    • Users will be able to bookmark a customizer session since the changeset UUID will be part of the URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org
    • Theme switches will no longer result in changes being lost (no more AYS dialog)
    • a few other open questions and issues that have been noted

Components

  • Customize (@westonruter, @celloexpressions)
  • Twenty Seventeen (@davidakennedy, @melchoyce)
    • Latest theme update
    • Theme: This week, there has been a lot of testing after the initial design implementation was merged last week. One week to go and the focus is on three specific enhancements to come to a conclusion on: custom colors, SVGs for icons and more use of flexbox.
    • Multi-panel feature: a 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. exist, and it’s been iterated on a lot. This is close to being ready for being considered for merge. It needs more code review and a look by other teams (accessibility for one).
    • Video headers feature: we have an mvp defined,  a new patch started and @celloexpressions will work on the Customizer part of it. This is not as far along, but could be ready by the deadline.
    • A lot of issues need to be punted or moved on. Tracking everything toward merge for Twenty Seventeen via GitHub milestone.
    • Will generate a merge proposal for the theme by Monday if not sooner. Will have brief daily check-ins/meetings for the theme until the proposal is posted.
    • @celloexpressions: visual edit icons in the customizer (#27403) are probably happening but won’t need a proposal there since the implementation is straightforward.
    • @helen: will follow up on #38114
    • 29 contributors on Twenty Seventeen
    • Team would appreciate any PR reviews on the theme, eyes on the multi-panel ticketticket Created for both bug reports and feature development on the bug tracker., and testing with all kinds of devices and browsers.
    • Next steps: (1) Focus on feedback/iteration for these big enhancements: custom colors, SVGs for icons and more use of flexbox. (2) Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. necessary items into merge milestone. (3) Close as much as possible
    • Next meeting Tuesday, October 18, 2016, 1:00 PM CDT in #themereview
  • Media (@mikeschroder, @joemcgill)
  • i18n (@swissspidy)
  • Editor (@azaozz, @iseulde)
  • 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. (@johnbillion)
    • Next meeting Friday, October 14, 2016, 11:00 AM CDT in #core-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.

#4-7, #core, #dev-chat, #summary