WP Updates

.travis.yml

@@ -1,5 +1,3 @@
-sudo: required
-
 dist: trusty
 
 language: php
@@ -19,11 +17,6 @@ cache:
     - $HOME/.npm
 
 before_install:
-  - |
-    git diff --name-only $TRAVIS_COMMIT_RANGE | grep -qvE '(\.md$)' || {
-      echo "Only docs were updated, stopping build process."
-      exit
-    }
   - nvm install && nvm use
   - npm install npm -g
 

CONTRIBUTING.md

@@ -104,11 +104,11 @@ For example, `add/gallery-block` means you're working on adding a new gallery bl
 
 You can pick among all the <a href="https://github.com/WordPress/gutenberg/issues">tickets</a>, or some of the ones labelled <a href="https://github.com/WordPress/gutenberg/labels/Good%20First%20Issue">Good First Issue</a>.
 
-The workflow is documented in greater detail in the [repository management](./docs/reference/repository-management.md) document.
+The workflow is documented in greater detail in the [repository management](./docs/contributors/repository-management.md) document.
 
 ## Testing
 
-Gutenberg contains both PHP and JavaScript code, and encourages testing and code style linting for both. It also incorporates end-to-end testing using [Google Puppeteer](https://developers.google.com/web/tools/puppeteer/). You can find out more details in [Testing Overview document](./docs/reference/testing-overview.md).
+Gutenberg contains both PHP and JavaScript code, and encourages testing and code style linting for both. It also incorporates end-to-end testing using [Google Puppeteer](https://developers.google.com/web/tools/puppeteer/). You can find out more details in [Testing Overview document](./docs/contributors/testing-overview.md).
 
 ## Managing packages
 
@@ -238,7 +238,7 @@ Choose the correct version based on `CHANGELOG.md` files, confirm your choices a
 
 ## How Designers Can Contribute
 
-If you'd like to contribute to the design or front-end, feel free to contribute to tickets labelled <a href="https://github.com/WordPress/gutenberg/issues?q=is%3Aissue+is%3Aopen+label%3ADesign">Design</a>. We could use your thoughtful replies, mockups, animatics, sketches, doodles. Proposed changes are best done as minimal and specific iterations on the work that precedes it so we can compare. If you use <a href="https://www.sketchapp.com/">Sketch</a>, you can grab <a href="https://cloudup.com/cMPXM8Va2cy">the source file for the mockups</a> (updated April 6th).
+If you'd like to contribute to the design or front-end, feel free to contribute to tickets labelled [Needs Design](https://github.com/WordPress/gutenberg/issues?q=is%3Aissue+is%3Aopen+label%3A%22Needs+Design%22) or [Needs Design Feedback](https://github.com/WordPress/gutenberg/issues?q=is%3Aissue+is%3Aopen+label%3A"Needs+Design+Feedback%22). We could use your thoughtful replies, mockups, animatics, sketches, doodles. Proposed changes are best done as minimal and specific iterations on the work that precedes it so we can compare. If you use <a href="https://www.sketchapp.com/">Sketch</a>, you can grab <a href="https://cloudup.com/cMPXM8Va2cy">the source file for the mockups</a> (updated April 6th).
 
 ## Contribute to the Documentation
 

CONTRIBUTORS.md

@@ -119,3 +119,5 @@ This list is manually curated to include valuable contributions by volunteers th
 | @luehrsen | @luehrsen |
 | @getsource | @mikeschroder |
 | @greatislander | @greatislander |
+| @sharazghouri | @sharaz |
+| @jakeparis | @jakeparis |

docs/contributors/scripts.md

@@ -50,13 +50,12 @@ The editor also uses some popular third-party packages and scripts. Plugin devel
 | [React](https://reactjs.org) | react  | React is a JavaScript library for building user interfaces |
 | [React Dom](https://reactjs.org/docs/react-dom.html) | react-dom | Serves as the entry point to the DOM and server renderers for React, intended to be paired with React |
 | [Moment](https://momentjs.com/) | moment| Parse, validate, manipulate, and display dates and times in JavaScript |
-| [TinyMCE Lists](https://www.tiny.cloud/docs/plugins/lists/) | tinymce-latest-lists| The `lists` plugin allows you to add numbered and bulleted lists to TinyMCE |
 | [Lodash](https://lodash.com) | lodash| Lodash is a JavaScript library which provides utility functions for common programming tasks |
 
 ## Polyfill Scripts
 
 The editor also provides polyfills for certain features that may not be available in all modern browsers.
-It is recommened to use the main `wp-polyfill` script handle which takes care of loading all the below mentioned polyfills.  
+It is recommened to use the main `wp-polyfill` script handle which takes care of loading all the below mentioned polyfills.
 
 | Script Name | Handle | Description |
 |-------------|--------|-------------|

docs/designers-developers/developers/block-api/block-registration.md

@@ -233,8 +233,8 @@ transforms: {
                 // An attribute can be source from the shortcode attributes
                 align: {
                     type: 'string',
-                    shortcode: function( named ) {
-                        var align = named.align ? named.align : 'alignnone';
+                    shortcode: function( attributes ) {
+                        var align = attributes.named.align ? attributes.named.align : 'alignnone';
                         return align.replace( 'align', '' );
                     },
                 },

docs/designers-developers/developers/data/data-core-editor.md

@@ -1292,19 +1292,21 @@ Returns the permalink for the post.
 
 *Returns*
 
-The permalink.
+The permalink, or null if the post is not viewable.
 
 ### getPermalinkParts
 
-Returns the permalink for a post, split into it's three parts: the prefix, the postName, and the suffix.
+Returns the permalink for a post, split into it's three parts: the prefix,
+the postName, and the suffix.
 
 *Parameters*
 
  * state: Editor state.
 
 *Returns*
 
-The prefix, postName, and suffix for the permalink.
+An object containing the prefix, postName, and suffix for
+                 the permalink, or null if the post is not viewable.
 
 ### inSomeHistory
 

docs/designers-developers/developers/themes/theme-support.md

@@ -202,7 +202,9 @@ This flag will make sure users are only able to choose colors from the `editor-c
 
 Gutenberg supports the theme's [editor styles](https://codex.wordpress.org/Editor_Style), however it works a little differently than in the classic editor.
 
-In the classic editor, the editor stylesheet is loaded directly into the iframe of the WYSIWYG editor, with no changes. Gutenberg, however, doesn't use iframes. To make sure your styles are applied only to the content of the editor, we automatically transform your editor styles by selectively rewriting or adjusting certain CSS selectors.
+In the classic editor, the editor stylesheet is loaded directly into the iframe of the WYSIWYG editor, with no changes. Gutenberg, however, doesn't use iframes. To make sure your styles are applied only to the content of the editor, we automatically transform your editor styles by selectively rewriting or adjusting certain CSS selectors. This also allows Gutenberg to leverage your editor style in block variation previews.
+
+For example, if you write `body { ... }` in your editor style, this is rewritten to `.editor-styles-wrapper { ... }`.  This also means that you should _not_ target any of the editor class names directly.
 
 Because it works a little differently, you need to opt-in to this by adding an extra snippet to your theme, in addition to the add_editor_style function:
 
@@ -212,6 +214,8 @@ add_theme_support('editor-styles');
 
 You shouldn't need to change your editor styles too much; most themes can add the snippet above and get similar results in the classic editor and inside Gutenberg.
 
+### Dark backgrounds
+
 If your editor style relies on a dark background, you can add the following to adjust the color of the UI to work on dark backgrounds:
 
 ```php
@@ -221,6 +225,16 @@ add_theme_support( 'dark-editor-style' );
 
 Note you don't need to add `add_theme_support( 'editor-styles' );` twice, but that rule does need to be present for the `dark-editor-style` rule to work.
 
+### Enqueuing the editor style
+
+To make sure your editor style is loaded and parsed correctly, enqueue it using the following method:
+
+```php
+add_editor_style( 'style-editor.css' );
+```
+
+It is enough to paste that in your `functions.php` file, for the style to be loaded and parsed.
+
 ### Basic colors
 
 You can style the editor like any other webpage. Here's how to change the background color and the font color to blue:

docs/designers-developers/developers/tutorials/block-tutorial/block-controls-toolbars-and-inspector.md

@@ -171,7 +171,7 @@ Note that `BlockControls` is only visible when the block is currently selected a
 
 ## Inspector
 
-<img src="https://raw.githubusercontent.com/WordPress/gutenberg/master/docs/blocks/inspector.png" with="281" height="527" alt="inspector">
+<img src="https://raw.githubusercontent.com/WordPress/gutenberg/master/docs/designers-developers/developers/tutorials/block-tutorial/inspector.png" with="281" height="527" alt="inspector">
 
 The inspector is used to display less-often-used settings or settings that require more screen space. The inspector should be used for **block-level settings only**.
 

docs/designers-developers/developers/tutorials/block-tutorial/writing-your-first-block-type.md

@@ -30,6 +30,8 @@ Note the two script dependencies:
 - __`wp-blocks`__ includes block type registration and related functions
 - __`wp-element`__ includes the [WordPress Element abstraction](https://github.com/WordPress/gutenberg/tree/master/packages/element) for describing the structure of your blocks
 
+If you were to use a component from the `wp-editor` package, for example the RichText component, you would also need to add `wp-editor` to the dependency list.
+
 ## Registering the Block
 
 With the script enqueued, let's look at the implementation of the block itself: