@estelaris, @chaion07, @bph, @harishanker, @tacitonic, @veralee, @justinahinon, @paaljoachim, @cguntur
Thanks to @estelaris for facilitating the meeting.
@bph is planning to do a guided documentation sprint for the BEE-Docs starting this Wednesday through Friday (25 to 28 November). The extensive list of the changes in WordPress 5.6 that needs to be triaged and categorized, compared to the current pages and transformed into a contributor task list. Birgit will be online every morning 9 to noon EST. Please join her at your convenience during these times and contribute to BEE-Docs. Birgit will be posting an announcement p2 later on.
@justinahinon is collaborating with @paaljoachim for Gutenberg 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/ Developer Documentation in order to improve it. Justin hinted that there might be a bit more progress than the past weeks.
New Member Mentoring
6 new members joined #docs in the week between 16 and 23 November 2020. Thanks to @prubhtej for the information.
Due to the general confusion with the time-zones a new Doodle was created by @kenshino. Everyone is requested to cast their votes.
Monthly Coffee Break
The November Coffee Break was hosted by @estelaris with 5 participants joining. @chaion07 will be posting a summary in a p2 later on.
@tacitonic is reported the following:
@estelaris mentioned that the classification project will start reviewing the block Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. articles and coordinate with the BEE-docs team to figure out how to move forward.
The GSoD team would love to hear from the Docs team on the Do’s and Dont’s including comments related to the Style and Tone section.
@bph informed everyone that we need to enable discussion per page since the feedback section that’s now available on HelpHub. Users will be able to leave comments for the Admins and Moderators to be able to view them using wp-admin. Also in the works is a way to revise an article without taking the existing page offline or update unfinished. We will be able to work on revisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. and then schedule making them public.
@paaljoachim asked if there been any talk about going through the structure of the handbooks and suggested that creating a flow chart of how docs are linked together can help improve on the user experience. @estelaris mentioned that there has been discussion on this in the past and advised everyone that any idea or a proposal on the topic is welcome. Paal will be bringing this topic next week since majority of the team is unavailable for this meeting.