Housekeeping
- Attendance: @estelaris @femkreations @milana_cap @bph @atachibana @tlc1206 @ibdz @mburridge
- Where: #docs channel on Slack. Find the complete Transcript of the meeting on Slack.
- Meeting Facilitator: @estelaris
- Note Taker: @femkreations
- Agenda: https://make.wordpress.org/docs/2022/04/18/agenda-for-docs-team-bi-weekly-meeting-19-april-2022/
- Next Meeting Facilitator (in two weeks): @tlc1206
Review of the design for documentation
The design team has reviewed the design. We are waiting on Josepha’s approval. The mobile version is not ready yet as there are a few items to be resolved.
- We now have 4 categories for the content and a submenu with the 4 categories, displayed at the top so users can easily navigate.
- The breadcrumbs are included as part of the left navigation (the blue square on the top left). The first 3 lines are the breadcrumbs, followed by the headings in the article. We also have another option (on the 3rd article example) where the breadcrumbs are horizontal, at the top of the TOC block.
Please add your comments here or in the slack channel.
Discussion 1: @femkreations: How are we handling the Changelog section since some of the Changelog entries are long?
@milana_cap: suggests not to delete the Changelog as it’s a history of the WP docs.
@bph: The Changelog is also used for translation and some locales might be behind on the pages.
@ibdz: We can have 2 different font sizes- one for the parent <li> (date) and one for secondary level <li> (content) to keep it aesthetically pleasing.
It was decided to add pagination to the Changelog. It is accessible and we can limit the number of entries per page, keeping the newest entries on page one and the oldest on page 2.
Discussion 2: @milana_cap: Would the definition list be semantic markup for the Changelog?
@mburridge suggests the details disclosure element
Discussion 3: @estelaris: What about the FAQs that are on some of the block articles? Are we going to keep them there or can we extract them and create a new FAQs section under resources?
@milana_cap: Thinks all FAQs should be in FAQs and articles that currently have them could link to them.
@atachibana: Suggests keeping it as is, to reduce the cost, and also create independent pages of the FAQ.
@ibdz: Thinks from the user’s point of view, it’s good to have the FAQ attached to the page.
Project updates
- Closed a few more 5.9 block editor end-user issues.
- All trac tickets are labeled for docs and GitHub project is ready.
- We have a new channel #docs-firehose for getting GitHub updates so that we keep the #docs channel clean
- Triaging the Google Doc and creating the Tracker issues for 6.0 end-user documentation.
- So far, 40 trackers have been added for 6.0 End User Documentation.
- Will complete the triage by the end of the week.
All the block editor articles listed in the inventory have been added to the new sitemap.
Open floor
@estelaris and @femkreations to review the following two pages: Block Editor and WordPress Editor to make sure they are not repetitive and if so, merge and delete one. @atachibana: Suggests renaming WordPress Editor to Classic Editor and keeping with TinyMCE.
@milana_cap gave a talk about Docs at WordCamp Athens in person.
@milana_cap to lead the Docs table at the Contributor Day for WCEU.