Housekeeping
- Attendance: @TC, @femkreations, @milana_cap, @basilh, @tacitonic, @muhammadfaizanhaidar, @ashiquzzaman
- Where: #docs channel on Slack
- Find the complete Transcript of the meeting on Slack.
- Meeting Facilitator: @TC
- Note Taker: @femkreations
- Next Meeting Facilitator: @muhammadfaizanhaidar
Project updates
@tacitonic: The WordPress Documentation Style Guide has been completed. This includes all the remaining articles, the word list, and the usage dictionary.
15 min repo triage:
Issue 1(labeled needs-discussion): Some end-user docs are too technical
@milana_cap: Agrees we shouldn’t have technical details in the end-user docs. But raises the question – where, in DevHub, should that info live?
End-user docs are for people who don’t code and most likely don’t deal with hosting/server issues but rather contact support. We need a place in DevHub that will be dedicated to tasks like .htaccess, internationalization, localization, etc that are shared throughout developing with WordPress. These are neither plugin/theme topics nor common APIs but also are not the end-user concerns.
She suggests we collect all the articles in the support section that are technical. This will help to get a better picture of the dedicated space we will need to create in DevHub.
@basilh – Suggests hyperlinks to a dedicated space on wordpress.org for topics related to Apache and Nginx, etc.
@milana_cap: Agrees to move all such info to another location on wordpress.org. And maybe say something like “For more advanced server settings take a check out this link”
ACTION ITEM: Please add your thoughts in the comments for the issue in GitHub.
Issue 2 (labeled good-first-issue): Update links inside the posts-screen DOC
- @muhammadfaizanhaidar is unable to recreate the issue and will update in the comments for that issue.
- @TC to take a look at the issue, if needed.