Anthony Burchell 3:22 pm on December 6, 2018
Tags: , ,   

Media 5.0 Guide

The block editor in WordPress 5.0 brings a much needed refresh to how we interact with media in the editor. 5.0 has provided new features designed to make complex content easier to create, and is built in a way that is now truly “what you see is what you get”! There are some big changes to where things are, new methods of accessing `classic` functionality, as well as new features you may not even know about. Let’s highlight a few of those!

Where is the add media button?

If you are looking for the add media button for any reason, this can be found in the classic block TinyMCE toolbar labeled “add media”. This button will trigger the media modal.

Gallery Block:

We have improved the Gallery experience with a new block that gives users a truly real time interactive Gallery.

If you need to utilize dynamic galleries that are based on post ID, or if you need to use the `post_gallery` filter, this can still be achieved using the `add media` button located in the classic block TinyMCE toolbar.

Wide Alignment Theme Support:

Some blocks, such as the image block, have the ability to define a “wide” or “full” alignment in the new editor. This is accomplished by adding the `.alignwide` or `.alignfull` classes, respectively, to the image’s wrapper element. A theme can opt-in for this feature by calling: 

add_theme_support( 'align-wide' );.

For more information on Wide Alignment, or if you would like to explore the potential markup of images in this context, the documentation has more details.

#5-0 #dev-notes

#media

Robert Anderson 7:07 am on December 6, 2018
Tags: , ,   

5.0 / Gutenberg Status Update – Dec 6

Current PRs for review:

Open issues in 5.0.0: 1 (=)
Open issues in 5.0.1: 28 (-1)
Open issues in 5.0.x (fast follow): 123 (+1)
5.0 status: RC3, released December 4.
Current plugin: 4.6, released November 30.
Next 5.0 milestone: WordPress 5.0, to be released December 6. 

In Trac:

  • Ready to commit:
    • N/A
  • Has patch, needs review:
    • N/A
  • Opened bugs:
    • N/A
  • Opened tasks:

#core-editor, #editor, #gutenberg

laurelfulford 4:01 am on December 6, 2018
Tags: ,   

Block Editor Support in Existing Default Themes

The default WordPress themes are a great way for even the most novice of site owners to quickly get up and running with a WordPress site that speaks their unique message. WordPress 5.0 will ship with the brand new Twenty Nineteen theme that fully showcases everything the new block-based editor has to offer. But, what if you aren’t ready to abandon your site’s current default theme?

New versions of all default WordPress themes will ship at the same time as WordPress 5.0 with full block editor support. For each theme:

  • Front-end and editor styles have been added for the new block-based editor.
  • Editor color palettes have been added based on the theme’s existing color settings. To best mesh with its accent color picker, Twenty Seventeen uses the block based editor’s default color palette.
  • In Twenty Thirteen, support has been added for wide alignments — they will be applied when no sidebar is present.

If default themes are not updated, they will still work with WordPress 5.0, but the editor may not accurately reflect how the post or page will look to users. As always, you are strongly encouraged to always run the latest version of all themes. Below are the versions of each default theme that add full block editor support:

  • Twenty Seventeen: 1.8
  • Twenty Sixteen: 1.6
  • Twenty Fifteen: 2.1
  • Twenty Fourteen: 2.3
  • Twenty Thirteen: 2.5
  • Twenty Twelve: 2.6
  • Twenty Eleven: 2.9
  • Twenty Ten: 2.6

#5-0, #dev-notes

Heather Burns 8:24 pm on December 4, 2018
Tags:   

Core-Privacy Office Hours Summary, 21 and 28 November

Ticket and coding issues

  • Gutenberg 11999, Fix the Privacy Policy Help Notice – merged into Core r43920. There is an open PR on the Classic Editor that will reverse the changes in r43920 and preserve the current placement of the notice (below the post title, above the editor) when that plugin is active.
  • As far as the contributors are aware, Gutenberg 11648 is the only remaining 5.0 related privacy ticket.
  • Quantcast advertising tracking has been removed from the .org footer. Props @ocean90. Matt has also approved replacing the social networking links with non-tracker links.
  • There are some potential privacy issues regarding Google Captcha 3.0. @idea15 to research.
  • #45395, which added the “shield” illustration to the admin dashboard privacy page, has raised the issue of the currency and accuracy of the text under it.
  • The 26 November bug scrub examined several new tickets: #45416 #45154, #45136, #44952, #44940, and #44876.
  • The needs-privacy-review tag in Trac (#3896) has been marked commit. @garrett-eclipse will add a link to the “needs-privacy-review” page on the main component page when there are active tickets.
  • There are 46 privacy tickets awaiting review.

Conference talks

Team issues

  • @javorszky has had to step away from contributing due to time constraints. @allendav is also unable to contribute at pre-4.9.6 levels. The team is always looking for new participants and contributors.
  • @riankinney and @idea15 are meeting with the Joomla! Core privacy team after WCUS to identify potential areas for mutual cooperation and to also learn more about their consent and logging work.
  • @idea15 wrote a post about the component’s work for the Marketing team.
  • The attendees agreed to use our 12 December office hours meeting, after WCUS and our contributions to Gutenberg are out of the way, to kickstart the V2 core privacy work.

Reminder: our weekly office hours are now at Wednesdays at 1900 UTC while bug scrubs remain Mondays at 16:00 UTC. The next office hours will take place on Wednesday, December 5, 2018 at 19:00 UTC

#core-privacy

Andrew Duthie 3:26 pm on December 4, 2018
Tags:   

JavaScript Weekly Chats – WordCamp US & Holiday Scheduling

As discussed in today’s chat, the following meeting dates for the JavaScript Weekly Chat will be cancelled due to WordCamp US travel and in observation of upcoming holidays:

  • December 11
  • December 25
  • January 1

#javascript

Robert Anderson 6:23 am on December 4, 2018
Tags: , ,   

5.0 / Gutenberg Status Update – Dec 4

Current PRs for review:

Open issues in 5.0.0: 1 (=)
Open issues in 5.0.1: 34 (+1)
Open issues in 5.0.x (fast follow): 122 (+1)
5.0 status: RC2, released November 30.
Current plugin: 4.6, released November 30.
Next 5.0 milestone: RC3, to be released today

In Trac:

  • Ready to commit:
    • N/A
  • Has patch, needs review:
    • N/A
  • Opened bugs:
    • N/A

#core-editor, #editor, #gutenberg

Alain Schlesser 3:30 pm on December 3, 2018
Tags: , ,   

PHP Meeting Recap – November 26th

This recap is a summary of our previous PHP 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 introduced the idea of using the concept of “feature flags” to be able to commit experimental code to be tested into trunk without immediately affecting everyone by default. Features hidden behind these feature flags would be opt-in through a mechanism like a setting in wp-config.php. The WP Beta Tester plugin could maybe be updated to provide a graphical interface to enable such feature flags.
  • The general format for feature flags in the wp-config.php could be something like the following: 
    define( 'WSOD_PROTECTION', getenv( 'WSOD_PROTECTION ) || false );
  • This allows for direct hardcoding of the value, as well as for passing it in via the server environment.
  • Discussion revolved around whether such a “feature flag” system would actually improve anything. For code to be considered “committable” to trunk under a feature flag, conditions would probably be the very same than for it to be committable to trunk directly.
  • @nerrad is concerned about the code churn that such feature flags could add to Core development.
  • @sergeybiryukov is concerned that feature flags would create a new precedent in WordPress and would prefer to have us either commit the required hooks into Core to provide WSOD protection through a plugin, or to iterate directly in trunk as this has been done before the advent of feature plugins.
  • An alternative approach would be to make branches available through the WP Beta Tester plugin. However, branches are hard to keep in sync with trunk, especially in SVN.
  • @afragen will experiment with changes to the WP Beta Tester plugin to see how feature flags or branches could be handled.

Post-meeting update

Next week’s meeting

  • Next meeting will take place on Monday, December 3rd, 2018 at 15:00 UTC in #core-php.
  • Agenda: WCUS in-person opportunities planning.
  • If you have suggestions about this but cannot make the meeting, please leave a comment on this post so that we can take them into account.

#core-php, #php, #summary

Matias Ventura 11:28 pm on November 30, 2018
Tags: , ,   

What’s New in Gutenberg? (30th November)

This should be the final “what’s new” installment for 5.0 — the 46th overall — accompanying the second release candidate which is also just released.

The Gutenberg plugin has also been updated to match core. The changelog here is a bit longer as it updates from 4.5.1:

4.6 ⌛️

#core-editor, #editor, #gutenberg

Josepha 11:12 pm on November 29, 2018
Tags:   

Dev Chat Summary: November 28th (5.0 Week 9)

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

5.0 Planning and Updates

  • We started with a reminder that RC1 is out and moved quickly into a lively discussion about remaining blockers, timing, and general logistics. I’ve summarized them the best I could below.
    • There was a request for review on one outstanding item in the default theme.
    • There were requests for consideration on 11973, 6177, and 45407 in media. These tickets are largely about how to best handle responsive images, specifically some nuance around the sizes attribute.
    • There are no automated tests for expected vs actual behavior
    • This affects only new posts, or newly edited posts.
    • It’s related to full-width images in the new editor and further complicated by the lack of any way to filter for block alignment width.
    • There are concerns about high data usage and negative impacts on search engines (esp for mobile)
    • Q: If we fix this in 5.0.x, what happens to content published in between 5.0 and 5.0.x? Will content need to be updated to correct? It was suggested that fixing the insertion of full size images in content and incorrect width attributes would let us ship and then iterate. Insertion is already fixed, so it’s just the second one!
    • Q: What would need to be fixed or added to content to allow it to be fixed post-release? Ensure we have correct default height and width attributes on inserted img elements.
    • We started running low on time, but additional clarifications were offered in #core-media. Additional discussion can take place on https://github.com/WordPress/gutenberg/issues/6177
  • There were a number of questions that got interjected during the discussion, that I’ve collected the best I could below.
    • Are we proceeding with the January slip date as identified in the launch post?
      • A January date was seconded by the docs team and a collection of others.
      • Many mentioned concerns around predictability and user trust.
      • Data is still being gathered about how RC1 is being received, and once enough is available, a Core P2 post will be made to help people plan. RC2 is next on the horizon.
      • How much time will there be between the announcement of the release date and the actual release date?
    • Are there any dev notes that need to be posted prior to release? And if so, is there a list? And how can we help?
    • Should we prep a 4.9.9 in order to be prepared for PHP7.3 support?
    • There were multiple offers to help gather necessary data to determine how close we are to a release date.

Component and Focus Updates

  • The PHP team shared last week’s meeting recap which included some discussion of Tide, whether to expose PHP compat on plugins/themes, and best ways to identify those with compatibility concerns. https://make.wordpress.org/core/2018/11/26/php-meeting-recap-november-19th/
  • The JavaScript team shared this week’s meeting recap which included discussion of Contributor Day at WordCamp US, work on docs parsing for devhub, and ESLint configurations. https://make.wordpress.org/core/2018/11/27/javascript-chat-summary-november-27-2018/
  • Design has a new research channel in the works. A lot of their initial work will be around user research for Phase 2+ of Gutenberg. Not much going on, but worth knowing about for sure. 🙂 https://make.wordpress.org/design/2018/11/19/two-ways-to-get-involved-in-gutenberg-user-research/

Next meeting

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

#5-0, #a11y, #core, #core-editor, #core-js, #core-media, #core-php, #core-restapi, #dev-chat, #gutenberg, #summary, #team-reps

catehstn 2:34 pm on November 29, 2018
Tags: , ,   

5.0 / Gutenberg Status Update – Nov 29

Current PRs for review:

Open issues in 5.0.0: 15 (=)
Open issues in 5.0.1: 52 (-1)
Open issues in 5.0.x (fast follow): 105 (-1)
Current beta: RC 1, released November 23.
Current plugin: 4.5.1, released November 21.
Next release: RC 2, November 30.

In Trac:

#core-editor, #editor, #gutenberg