Team Goals for Quarter 1, 2021

Biggest challenges from previous periods:

  • Slow processes, mainly in making decisions, even with simple things.
  • Lack of response from other contributors (e.g. commenting on p2 posts)

This post should serve as a rough (or not so rough) focus plan and set of goals for the Docs team in the first quarter of 2021.

Content team

@atachibana – Contents migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. team will complete the task (hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same. and classes migration) within a Q1.

End User BlockBlock 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. Editor team

@bph – 

  • We are triaging 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/ Changelogs 9.3 – 9.9 for End-User relevant changes in “Features” and “Enhancements” coming to 5.7
  • Beginning of February – A team sprint to prepare next set of tasks
  • Replace “More Options” section with link to “More Options”-page
  • Outline of Full-Site-Editing documentation for 5.8
  • Ongoing recruiting and onboarding of new contributors
  • Team checking on current workload. 
  • Fielding Feedback from readers. 

Design team

@estelaris – design proposal:

  • 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 reqs – week 4
  • p2 new classification – week 6
  • p2 on final navigation – week 8
  • p2 on templates draft – week 10
  • p2 proposal new design for documentation – week 13

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 Developer Handbook

@themiked – Based on the discussion here (1), the Plugin handbook will develop a way to indicate obsolete docs on both a page-level and a section-level. This will be done with an eye towards it being used elsewhere.

The modernization of the handbook is ¼ of the way done. There are four primary steps in this process:

  1. Convert content to blocks – done
  2. Edit content for clarity and consistency of tone
  3. Confirm that every code snippet conforms to best practices (phpcs, phpcbf, proper naming, good use of comments, and that it actually does what it says it does)
  4. Revisit of the writing to conform to the style guide, whenever that is finished.

(1) What to do with old/obsolete documentation – Make WordPress Documentation 

Block Editor Handbook

@justinahinon – improving the structure of the block editor handbook: https://make.wordpress.org/docs/2020/08/13/plan-proposal-for-a-new-better-structured-gutenberg-developer-documentation/

Plan

  • Improve the structure and the design of the homepage – done
  • Reorganize the handbook table of content (in progress – https://github.com/WordPress/gutenberg/issues/28460)
  • Find a place for FSE documentation
  • Overall, add design improvements were needed in the handbook

Keep up with Gutenberg: https://make.wordpress.org/core/handbook/references/keeping-up-with-gutenberg-index/ 

More Info (DevHub)

@juliobox – 

User Notes (DevHub)

@audrasjb, @crstauf – stay on top of pending user notes: check regularly and optimize process for handling feedback for doc changes.

They also regularly open TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets when the comments raise issues located in WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. docblocks.

Common APIs Handbook

@leogermani – 

External Linking Policy

@themiked, @milana_cap – Finish first and the second phase of reviewing Plugin Developer Handbook: https://make.wordpress.org/docs/2020/12/01/external-linking-policy-1st-review-of-plugin-developer-handbook/ 

Documentation Handbook

This project was neglected in the past quarter. We should make some time to review it and pinpoint spots that need updating.

Contributing Videos

After having two videos published we neglected this project as well. Perhaps we could plan for a couple of more in this quarter.

Google Season of Docs

@tacitonic 

  • Finalize and complete the Style Guide by March 1, 2021.
  • Write the project report.
  • Parse the 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/ repo to make.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org//docs/style
  • Initial public release of the Style Guide.

Onboarding New Members

@sukafia

  • Set up an automated slackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. bot to welcome new members with links to relevant resources.
  • Add the mentorship team to the handbook
  • Call word for mentorship (a word people can use in the slack channel that automatically pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” members of the team)

HelpHub Localisation

Locales updates

@audrasjb: the French Documentation Team nominated two team leads (@jdy68 and @chaton666) and we’re now at 50% of coverage. In early 2021, we started to create our own original contents.

#q1, #q1-2021

Summary for Docs Team Meeting on March 1, 2021

Attendance

@chaion07 @ashiquzzaman @justinahinon @bph @zzap @tacitonic @atachibana @geheren @reachmazharul @harishanker @themiked @deadpool76 @atiktonmoy

Housekeeping

Project Updates

HelpHub Redesign

Update from @estelarisThere are no updates on the HelpHub redesign project yet but estelaris still need help with articles link review. All the articles must be reviewed, most are fine and few are not, and those few are the cause of plenty of fix-link requests. If anyone wants to review, pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” @estelaris. The task is only to identify the wrong links and there is a team in charge of approving and updating the links. @ashiquzzaman showed interest to review the articles

BlockBlock 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. Editor Developer Doc

Update from @justinahinon – The table of content pull request (https://github.com/WordPress/gutenberg/pull/28665) is ready to be merged.

End User Block Editor team

Update from @bph  –
@geheren and Mathew McCabe had their sprint; @poena had also participated. Discussed the end-user documentation for Full Site Editing. The plan is to wait until the Prototype is released, and then again until BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. of 5.8 to see what will make it into coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. WP 5.7 changes are now available in our Spreadsheet and 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. board. 

The team is also getting ready to touch almost all pages to implement More Options link/page enable comments and add a note to the change-log as with which WordPress version a page is currently. @Geheren added that to all the pages in the Trello board. Once @collinsmbaka publishes his page, all contributors can start working on it. A plan is in place to welcome new contributors to the team.

Full Site Editing Documentation

Skipped for this meeting.

Codex to HelpHub MigrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies.

@atachibana was unavailable to provide an update on this.

New Member Monitoring

@chaion07 reported that 10 new members joined the Docs channel in the past 7 days. The team welcomed all of them. Here is the Slack thread with the list of members.

Monthly Coffee Break

There is a new p2 you can all check out: Docs Team Coffee Break February 2021 Summary.

@chaion07 reported that there have been a total of 5 contributors joining in for February 2021 Coffee Break. Thanks to @thisisyeasin, @Gtarafdarr, @atiktonmoy & @reachmazharul for making time. For those who couldn’t make it you can definitely join the March Coffee Break. Anyone who is willing to host it can ping either @chaion07 or @sukafia

Google Season of Docs

Update from @tacitonic:
Completed 15/28 articles in the Word list and usage dictionary. Parser will be completed by Monday, i.e. today. The project finalization phase for Google Season of Docs begins from today. He’ll start writing a 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/. on make.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org//docs after the final project report. Google Season of Docs 2021: The organization application phase has also begun for this year’s program.

Open Floor

The team discussed using 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/ as opposed to other tools, as GitHub would also reduce the use of Trello to some extent. 

#meeting-notes, #meetings, #summary

Docs Team Coffee Break February 2021 Summary

The February Coffee Break took place on the 24th instant at 11 AM UTC timing which saw the presence of 5 contributors from the Global Documentation Team. Kudos to @chaion07 for hosting!

Docs Team Coffee Break for February 2020

I came online at the scheduled time but did not see anyone joining. So I waited and sent a message across my workplace, weDevs which resulted in a few of my colleagues joining instantly.

We mostly talked about how to become a Documentation Contributor and what projects are there to contribute. I tried to answer various questions ranging from the Handbook to the weekly meeting. All contributors were encouraged to attend the weekly meetings.

We thank @atiktonmoy, @thisisyeasin, @reachmazharul & @gtarafdarr for joining the Docs Team Coffee Break for 2021. We invite all of you to join the coffee break for March 2021 as it progresses from planning to execution.

#coffee-break, #meeting-notes, #meetings

Agenda for Docs Team Meeting March 01, 2021

The next meeting for the Make WordPress Global Documentation Team is scheduled with the following details:

When: Monday, March 01, 2021, 14:00 UTC

Where: #docs channel on Slack.

Meeting Agenda

  1. Project Updates
  2. Full Site Editing Documentation
  3. New Member Mentoring
  4. Monthly Coffee Break
  5. Google Season of Docs
  6. Open Floor

Please feel free to suggest agenda items by commenting on this post or raise during the open floor.

Thank you!

#agenda, #meetings

Summary for Docs Team Meeting on February 22, 2021

Attendance

@estelaris @atachibana @sasiddiqui @deadpool76 @bph @chaion07 @sukafia @tacitonic @justinahinon @aurooba

Housekeeping

Project Updates

End User BlockBlock 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. Editor team

Updates by @bph

  • Huge thanks for @geheren for working through the upcoming change with WordPress 5.7 and added it to the spreadsheet. Release is scheduled for March 9th, 2021.
  • Some line items are already claimed/assigned to contributors. Thank you @bizanimesh @collinsmbaka @cguntur @geheren to charge ahead!
  • If you’d like to work on some of it add yourself to the card on the 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. board in the “need changes” column. (If you are not part of the Trello board yet, use this link)
  • Sprint is this week Thursday Feb. 25 – P2 post. If you want to learn more about the Full-site editing, also join this sprint.
  • The metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. team is working on a scheduled update feature, so we can work on our pages on the site, without overwriting existing pages. It’s now in alpha-test and if you want to test it contact  @Corey McKrill to get you access. 

HelpHub Redesign

Updates by @estelaris

Changing the anchor # from documentation. As of now, if you are to read a title with a screen reader, for example “New to WordPress #” it will read “new to WordPress number” ,
The accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) issue plus the visual noise caused by that # and the images are the reasons of changes. Will write up a post this week explaining this.

HelpHub issue

@deadpool76 found the wrong descriptions about PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. http://php.net/manual/en/intro-whatis.php. requirements. Though they were already fixed, multiple pages should not have the duplicate information. @atachibana will integrate duplicate requirement articles.

New Member Mentoring

🎉 Four new members joined the Docs channel in the past 7 days and were welcomed by @tacitonic.

Monthly Coffee Break

February’s Coffee break is scheduled for Thursday, February 25th, being planned by @sukafia and @chaion07; Find details here: https://make.wordpress.org/docs/?p=11101

Google Season of Docs

Updates from @tacitonic

  • Completed 12/28 articles in the Word list and usage dictionary.
  • Still waiting for the parser implementation – 1 week till I have to send a final project report to Google.

Open Floor

n/a

🐝-Docs Team Sprint Feb 25, 2021

🐝-docs stands for Block-Editor End User documentation.

What makes Contributor Days at WordCamps such a great event is the concerted focused time and working alongside of each other in person. You meet teammates from around the world, you can get instant answers to questions, help when you get stuck and have short discussions on important issues. It does wonders to motivation, productivity and camaraderie. Just because there aren’t any in-person WordCamps, doesn’t mean we can’t have remote Contributor Days, I call ’em a Team Sprints. It might be the next best thing.

So, dear team members, Contributors, current and future once, you are invited to join us for our next sprint on February 25, 2021. To accommodate different time zones, there will be two 2-hour sessions, starting at

The Team Sprint will be held on Zoom and the URLs will be published on Thursday in #meta-helphub channel an hour before the session. The accompanying chat will also take place in #meta-helphub, so contributors joining us asynchronously can leave comments and questions, too. Follow-ups can then happen in #meta-helphub threads.

Topics

The topics will mostly be determined by the people able to join us, and what we would want to work on the next two hours. These are only suggestions, covering all four projects and more.

  • Onboarding of new contributors
  • Virtual walk through our tools and documents (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., Make blockBlock 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., Handbook, Google Docs, using a test site etc)
  • Early peak on Scheduling updates to published posts on WordPress.org (demo)
  • Process of updating existing documentation with changes from new versions.
    • 1st iteration for 5.6,
    • 2nd iteration for 5.7.
  • Creating end-user documentation for Full-Site Editing
  • “More Options” project
  • Handling Feedback / Comments

What else do you want to talk about? Leave questions and suggestions in the comments or on #meta-helphub

Hope to see many teammates on Thursday.

PS: Yes, there is also a coffee break scheduled for Thursday. It gives you an opportunity to hang out with the rest of the docs team! It’s way too early for me, though.

February 2021 Docs Team Coffee Break Announcement

The next Coffee Break for Docs Team is scheduled for Thursday, February 25, 2021, 11:00 UTC. The details for joining the Zoom call are as follows:

The details will also be posted in #docs channel on the day. If you wish to get a calendar invite then please pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” @chaion07 or @sukafia. Take care and stay safe!

#coffee-break, #meetings

Agenda for Docs Team Meeting February 22, 2021

The next meeting is scheduled with the following details:

When: Monday, February 22, 2021, 03:00 PM GMT+1

Where: #docs channel on Slack.

Meeting Agenda

Project Updates
Full Site Editing Documentation
New Member Mentoring
Monthly Coffee Break
Google Season of Docs
Open Floor

Please feel free to suggest agenda items by commenting on this post or raise during the open floor.

Thank you!

A home and a name for Site Editor Documentation (Full Site Editing Feature)

As you may know, the “Full Site Editing via Gutenberg” is the main goal for 2021. We still don’t know when exactly it will become the part of coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. but to avoid missed opportunities (as we had them in the past with 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/) let’s start preparing documentation space for this new feature’s arrival. 

We want to join efforts with other teams already working on Site Editor. Namely, the Test team has an ongoing Outreach Program (lead by @annezazu), Themes team (mostly @poena) is explaining what this feature is and how it’s working, Core and Design teams are building it: pull requests and issues

Our job is to document it. 

First things first

Before we start with anything else, we need to know two things: the name and the place.  

The name

It’s been called “Full Site Editing” throughout the community but, as history teaches us, this is most likely to stay around only as the code name for the project, used among people working on it. 

We will probably have a different name facing documentation consumers so, to avoid confusions and to have a proper Handbook slug from the beginning, we might want to spend some time on thinking it through. This is not a task only for the Documentation team, of course, and we hope to get input on this post from all teams involved.

It’s been suggested in #docs chat, that “Site Editor” might be an appropriate name (just as Gutenberg became BlockBlock 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. Editor) so we’ll use it as a starting point. Please leave your opinions and suggestions in the comments below.  

The home 

The whole user facing documentation is roughly divided into end user documentation (HelpHub) and developer documentation (DevHub). Obviously, Full Site Editing feature should be explained to both, in a way that is useful to each group. 

@bph is already doing an amazing job in organising and creating content for end user Block Editor documentation and she has a plan for Full Site Editing feature.

The problem we are facing is the home for developer part of Full Site Editing feature documentation. It doesn’t fully belong to any existing Handbook as it requires features from different areas (it needs to be enabled in theme but it assumes template post types, it doesn’t create new blocks but it does use blocks specifically created for it, it can use global styles etc).

Majority of the Documentation team agrees that Full Site Editing feature shouldn’t be buried in any one existing Handbook but it should be mentioned where relevant. Also, we agree that the full concept should be explained in one place from and to where we can easily inner link relevant places in other Handbooks. 

Considering there might be much more to Full Site Editing feature in the future and we might need more space for it than, say, one page, the Documentation team propose a new Handbook under DevHub. 

The slug for this Handbook depends on the name we settle with. Also, it would be a good time to decide if we want to have this Handbook built and generated from 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/ (like WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/, REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/., Block Editor and Coding Standards are) or do we want to publish content directly from WordPress. 

Please leave your feedback in comments below by 25th February. Thank you.

#fse, #site-editor

Summary for Docs Team Meeting on February 15, 2021

Attendance

@collinsmbaka, @bph, @aurooba, @estelaris, @tacitonic, @atachibana, @chaion07, @crstauf, @sukafia, @poena, @themiked, @nahidsharifkomol

Housekeeping

Project Updates

End User BlockBlock 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. Editor team

Updates by @bph

Scheduled Sprint

February 25th, 2021 with two time slots, 14:00 – 16:00 UTC (9 to 11 EST) and 21:00 – 23:00 UTC (6 to 8pm EST)

  • To get the task list together, onboard new contributors, update 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. Cards, and progress follow up with experience contributors.. There will be a Zoom call with demos, screen sharing, and Q&A.

Updates for 5.7 release

  • @geheren and @bph have been working on identifying user facing changes and cluster them per section.
  • Updates are happening for existing pages with a link to the More Options page, and to reduce the duplicate content. When touching all pages, the feedback section is also opened up on all pages. @collinsmbaka and @bph will rally the troops on #meta-helphub
  • To Do: We need to come up with a process for the comments to tally them and see the nature of the problem and how to solve them.

Design

Updates by @estelaris

The comments for the requirements for a new design for user documentation were closed yesterday. There was a discussion with the design team about the anchor icon, in particular, and a decision was made to design a new icon to replace the current ‘#’ icon, further explanation can be found here.

@estelaris is working on the new navigation and post about that part, but needs help. There are many articles (at least 170) that need to be reviewed for old/broken links. To help review them:

  • View the list of articles in this Google doc, in the “List of Pages” tab. The results of the review should go into the “Link Review” tab.
  • Please do not fix any links, that is the job of @atachibana and his team, and any changes need to be approved by them
  • If you have any questions, pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” @estelaris in Slack.

Full Site Editing Documentation

Transcript bookmark

Planning of Full-Site Editing (FSE) documentation is ongoing (for the 5.8 release). Contributors are needed who know FSE deeply and can teach the rest of the team how it’s supposed to work. Thanks to Tom Rankin for working on the outline. @bph will be publishing a blog post with a call for contributors.

Before the meeting, @milana_cap mentioned, “As a team, considering the way documentation is structured currently, we have to come up with our proposal where FSE (Full Site Editing) documentation should live.”

There was a healthy discussion around how the FSE documentation should be structured and how FSE should be defined. As @bph described, there are 3 parts to FSE documentation:

  1. Themes need to be built for it. A theme must support FSE for it to be available. This information needs to be available in the Developers Handbook.
  2. There is the user facing site for those who have access that should be in the User facing documentation on Help Hub.
  3. Documentation for site builders who build sites for others. There is no current space for this yet.

@poena pointed out there are a lot of overlaps between these 3 aspects, since users, site builders, theme developers, and theme designers all will use the editor to assemble blocks.

@themiked felt FSE should be a single page with links pointed towards discussions on how to use it within the desired context: theme handbook for themes, user handbook for users, etc. Ultimately, we can link to respective spaces when needed and create a bridge pages to interlink the different areas. The key issue here is to make the documentation easy to discover. @bph brought up the Fireside chat at WordCamp India, where @chanthaboune and @matt talk about FSE.

This is an undecided topic, which needs a dedicated post for feedback.

@bph will have a post out about user-facing documentation for FSE before February 25.

New Member Mentoring

🎉 Five new members joined the Docs channel this past week and were welcomed by @sukafia.

The mentorship team met last week Thursday on Zoom to plan and set goals for the year.
(If you’re not familiar with the team, you can read the initial proposal here to learn more.)

Monthly Coffee Break

February’s Coffee break is scheduled for Thursday, February 25th, being planned by @sukafia and @chaion07; a post with the zoom link and details will be published later this week.

Google Season of Docs

Updates from @tacitonic

Open Floor

Today is the last day to submit questions for the Full Site Editing call for questions.

Summary for Docs Mentorship Team Meeting on February 13th, 2021

The mentorship team is tasked with the responsibility of onboarding new members of the documentation team. You can learn more about the team’s responsibilities in the initial proposal.

On February 13th, 2021 the team met on Zoom to plan and set goals for the year.

Attendance

@sukafia, @chaion07 and @tacitonic

Team Goals for Q1 2021

  1. Automated slackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. bot to welcome new members with links to relevant resources.
  2. Add the mentorship team to the handbook
  3. Call word for mentorship (a word people can use in the slack channel that automatically pings members of the team)

Other plans/resolutions

  1. Welcoming new members during each docs team meeting 
  2. Monthly new contributors office hours (We hope to start this after the first quarter)

Your contributions/suggestions are welcome!