Attendance
@chaion07, @milana_cap, @wpza, @sasiddiqui, @nao, @ibdz, @audrasjb, @nobnob, @bph, @mantismamita, @mapk, @estelaris, @sukafia, @tomf, @usmanaliqureshi, @marcio-zebedeu, @pmbaldha, @kenshino, @Felipeloureirosantos, @atachibana, @themiked
Notetaker & Facilitator selection
Notetaker: @chaion07
Notes Reviewed by: @sukafia
Facilitator for the next meeting: @sasiddiqui
Next Meeting will be held on: April 06, 2020
Project Updates
@leogermani had updated the ‘home page’ and ‘welcome message’ of the Handbook and stressed on the fact that we should define pages for the next deadline.
@milana_cap reported that In Serbia they are organizing “Translate Thursdays”, every Thursday from 6-8PM on zoom where people gather and translate whatever they want.
@bph updated, Upon request from Support Team had created a section for the 5.4 default Full screen Mode https://wordpress.org/support/article/wordpress-editor/#the-editors-workspace
Updating sprint for 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. documentation: Adding missing blocks within the next 2 weeks.
Community Team: documentation on how to set-up a website for virtual events (Crowdcast, Live Captioning).
@Felipeloureirosantos also didn’t have updates for HelpHub translation to pt_BR. He was surprised that people actually get really excited about contributing because of the badges and so he emphasized to highlight it more.
@atachibana had 2 updates re-routing from Codex ‘Function’ to Code Reference, 431 of 1069 have been done which is 40.3% & translation of HelpHub to Japanese, 50% have been completed and they hope to keep the momentum going.
Handbook Revamp
- Homepage update
- Deadline for next 2 or 3 pages
- @milana_cap suggested that we work on drafts until next Monday, then we review and discuss, fix what’s needed and publish it another 7 days later (so the actual deadline would be 14 days). Which @estelaris, @marcio-zebedu, @chaion07 and @ibdz showed support to.
Categorization Project, Alterations Workflow (discussion)
- @sukafia shared the link of the spreadsheet for the project. https://docs.google.com/spreadsheets/d/1_Ea2yeF5Rfy_YDk7pBRJ4rdljhMjygXFqBq8gWwhbaE/edit#gid=1762929540
- @estelaris addressed the 2 goals agreed upon last week:
- better search
- improve usability (in mobile)
- @estelaris also mentioned that Roles and Capabilities is under categories Installation, Basic Administration and Getting Started
- @milana_cap pointed out that there was no mention of User
- @sukafia asked, if there was a 3rd goal and urged to suggest if any
- @estelaris suggested, if we think of the menu like this: getting started > Roles and Capabilities
- @estelaris said, and then when we go back, the system may go Roles and Capabilities > Installation. The user will go back to a different category The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. then when he/she started. that is not good. then we have the title
- @Kenshino gave 2 examples of User stories:
- “As a first time user, I should be able to figure out whether WordPress is adequate for my needs easily”
- “As a user, I should be able to figure out which articles to look at without knowing WordPress terminologies”
- @mapk added to the point made by @estelaris that revisiting some of those titles could help with the latter
- @tomf said that it’s good to define a number of steps also in terms of ultimately finding information from a start point and use that as a scaffolding target. It’d be good to have a user stories doc as we really will probably keep having more of these that fit into a theme to identify areas of improvement
- @sukafia outlined the goals:
- Better discoverability
- Improve usability
- @estelaris said that she will add the stories to the working document and write a few for next week we can move from there
- @kenshinoo Called on volunteers to help write user stories and suggested that if everyone could target writing 3 based on our understanding of how people want to access user docs, we’d have a lot!
- Due to time running out for the meeting we had to move to the next topic.
Open Floor
- @adamsilverstein expressed his thanks to the ‘Docs Team’ for everything we do. He introduced the team to the recently announced “Season of Docs”, a Google’s effort to help open source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. projects with documentation and pointed out that it may be a good opportunity to get some additional resources towards tackling documentation goals or projects. : https://opensource.googleblog.com/2020/03/announcing-season-of-docs-2020.html. https://developers.google.com/season-of-docs/docs/admin-guide
- @nobnob asked on the changes to HelpHub articles, for example the one indicated by @bph were automatically updated on Rosetta sites or, conversely, how we translators can be informed.
- @milana_cap answered, unfortunately, rosetta sites are not notified
- @Bph replied to @nobnob that there aren’t any notifications. The best would be to have an RSS feed RSS is an acronym for Real Simple Syndication which is a type of web feed which allows users to access updates to online content in a standardized, computer-readable format. This is the feed. for articles enabled and send out notifications. @bph also asked @nobnob would a post in the #polyglots channel help? She would make a note of that, to include it when there are updates on support/articles.
Transcript of the meeting can be found here on slack
Thank you all & please stay safe!
#meetings
