Gutenberg component organisation update

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/ touches many areas of WordPress across multiple components. In preparation for merge proposal, separate 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/ milestones for the different component areas have been created. This helps clarify the remaining focus areas Gutenberg needs to tackle before merge, and also makes it easier for component maintainers and contributors to keep track of the remaining work.

Merge Milestones:

In addition to core components, there are now milestones for the following areas:

  • 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): https://github.com/WordPress/gutenberg/milestone/43
  • Documentation:  https://github.com/WordPress/gutenberg/milestone/50

What belongs in a merge proposal milestone?

These milestones are for the ‘must haves,’ and contain blockers for merge proposal. For additional feature ideas or future planned features, there are now the following milestones:

#gutenberg