Summary for Docs Team Meeting on 11 January 2021

Attendance

@milana_cap, @estelaris, @paaljoachim, @atachibana, @tacitonic, @shitalmarakana @chaion07, @bph, @justinahinon, @aurangajeb, @themiked

Thanks to @milana_cap for Facilitating the Meeting.

Notetaker & Facilitator Selection
Project Updates
  • 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 Handbook by @themiked: Minimal changes, need to ratify the external linking policy document. According to Mike, all previous owners have just made changes as appropriate without asking, and nobody noticed.
  • Design for Documentation by @estelaris: Planning on finishing the design for documentation in the first quarter. Need to gather the final results from the reclassification project, other requirements I picked up from diverse meetings and put together my recommendation for final design. You will see a few discussion posts before the design proposal, aimed between the last week of March- first week of April.
  • BEE-Docs by @bph: Caught up on our articles to make them current with 5.5 and started working on 5.6 updates and create new pages. Started to open up the feedback for more pages. Definitely need instructions, how we would like to handle things. The team is now working via TrelloTrello Project management system using the concepts of boards and cards to organize tasks in a sane way. This is what the make.wordpress.com/marketing team uses for example: https://trello.com/b/8UGHVBu8/wp-marketing., Google Docs. Kudos to all who keep working away on the to-do lists. The ‘Thanksgiving Sprint’ which was a great way to get a lot of things done and connect with contributors, especially new ones. This will definitely be repeated and hopefully can be an ongoing team exercise. Kudos to @geheren for taking up a quite a few pages and work on them.Challenges: We don’t yet have a fluid system on keeping pace with the rapid development 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/ and for adoption of FSE for 2021 the team needs help from the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-editor team to at least have a rough draft of documentation coming from the developers, that we can follow and extend for End-User.
  • External Linking Policy by @milana_cap: Finally made some visible progress even though it was rather slow at the beginning
  • Google Season of Docs by @estelaris: One project finished and another is due to finish by Q1 2021 by @tacitonic. He finished the lengthiest section in the style guide – the Formatting section, started writing a spinoff section on Linking and encouraged team members to review and discuss articles in discussion tab 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/.
Goals for Next Quarter

Milana thinks that The Team can start with some rough ideas where each project should be in March. Not just projects but processes as well. Plugin Handbook should finish the second phase: https://make.wordpress.org/docs/2020/12/01/external-linking-policy-1st-review-of-plugin-developer-handbook/ The main idea here is to think about direction for each project and some sort of measurable progress at the end of each period.

It’s Birgit’s first year on the team, so she’s not sure what’s the ‘usual’ process is. On Community team, there is a post asking for suggestions from the whole community, like the wishlist for the new release and then the team organizes the suggestions and translate them to goal statements, and picks their priorities.

Estela points out the goals for Design: Documentation design proposal – Q1

  • P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org/. new requests – Week 03
  • P2 new classification – Week 05
  • P2 on final navigation – Week 07
  • P2 on templates draft – Week 10
  • P2 proposal new design for documentation – Week 13
Open Floor

@estelaris feared to collaborate with the #meta team but at the same time is planning to annoy them until they reply. @bph mentioned that #Meta team is working on a Pattern Directory that is exciting for a lot of us.

@tacitonic was looking at ways to insert an icon inline to indicate that a link is going to an external site. Reference: https://developers.google.com/style/cross-references#out-page

#meeting-notes, #meetings, #summary