Summary of Gutenberg docs meeting 24 October 2018

Thanks to everyone who joined us for the kick-off 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/ docs meeting!

Below is a summary of last week’s meeting.

  1. Opened with introductions and hellos, and a description of @chrisvanpatten‘s goals for the group
  2. Set future meetings for 1pm ET/17:00 UTC on Tuesdays, in #docs on 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/.
  3. Discussion of where documentation would “live”
  4. Goal is to continue allowing docs to be prepared 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/
  5. @drewapicture raised some questions about what the Gutenberg handbook represents, suggesting it not exist as a mono-doc when merged into coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.
  6. @kenshino raised the idea of splitting into separate handbooks: auto-parsed documentation in DevHub, developer handbook in DevHub, and user handbook in HelpHub
  7. (@chrisvanpatten also added a contributor handbook to be considered too, likely to live on GitHub for now)
  8. Established next steps:
  9. Lock down high level documentation outline
  10. Open a PR to reorganise the documentation
  11. Determine list of holes in documentation
  12. Begin assigning writing tasks in GitHub issues/high level project/milestone
  13. Established next meeting for Tuesday, 30 October at 1pm ET/17:00 UTC in #docs
  14. </meeting>

I’ll post an agenda for our next meeting tomorrow a few hours before the meeting. Thank you everyone who joined us!