Milana Cap 8:00 am on June 13, 2022  

Onboarding to Documentation team

Here is some quick info you need in order to start contributing to Documentation team.

Accounts:

Places:

  • Blog – for meeting agendas and summaries (and anything related to Docs team).
  • Slack channel #docs – where meetings are happening (and all communication regarding the team itself).
  • GitHub repository – where issues for all documentation are reported, discussed and worked on.
  • Handbook – how to contribute to the Documentation team (it’s a bit out of date).
  • Style guide – for how to write WordPress documentation.

Meetings (alternating every week) on Tuesdays at 2PM UTC:

  • Regular meeting with agenda published on our blog.
  • Issues triage where we discuss issues from the GitHubGitHub GitHub is a website that offers online implementation of git repositories that 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/ repository.

Live onboarding sessions

We recorded onboarding sessions for everyone interested in getting started with the Documentation team. We know that our “Getting started” documentation is out of date and getting involved can be very confusing and frustrating so we hope to ease the process with these sessions.

Overview

Recording: https://wordpress.tv/2022/06/21/milana-cap-overview-onboarding-for-wordpress-documentation-team/

End user documentation

Developer documentation

Developer documentation – 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 handbook

Developer documentation – Common APIs handbook

Developer documentation – Code reference handbook

Developer documentation – 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 handbook

Developer documentation – Themes handbook

Contributor documentation – Documentation team handbook

If you have any questions or you’d like to have an “in more detail” session, feel free to leave the comment below.

Estela Rueda 4:16 pm on January 16, 2023
Tags:   

Development and design work continues on Helphub

Docs team, please refrain from updating/uploading articles on Helphub still. Work will continue until Friday 20 January.

I will update the team if we need more time.

For 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 on docs 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/. channel.

#helphub

Javier Casares 3:42 pm on January 15, 2023
Tags: ,   

X-post: Advanced Administration Handbook: Status 2023-01-15

X-post from +make.wordpress.org/hosting: Advanced Administration Handbook: Status 2023-01-15

Jenni McKinnon 2:16 am on January 13, 2023
Tags: , ,   

Summary for Docs Team meeting, January 10, 2023

Attendance

@ninianepress @milana_cap @leonnugraha @femkreations @atachibana @thisisyeasin @estelaris @wigno @vanpariyar @kartiks16 @samanthaxmunoz @ninthcoder @daisyo @webtechpooja @onlykawshar

Housekeeping

Find the complete Transcript of the meeting on Slack.

Moving HelpHub to the New Site

@estelaris is working with 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 to replace the /support site with the /documentation site. The new URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org is expected to be ready after January 17, 2023. In the meantime, contributors should refrain from adding, editing, or publishing content on the /support site as they will be lost.

Read this post for more information.

Project Checks

@leonnugraha – Reviewed and published #234 and #314

@milana_cap – Almost completed the Team roles page(s)

@ninianepress – Finishing an update that was supposed to be done by the end of 2022

@wigno – Completed #506, and it’s now ready for review. Will plan to work on #508 and #502 this week

Topics for the 2023 WordPress Community Summit

We should think, as a team, of possible topics for the Community Summit. What are the Documentation team needs that can, in full or partially, be solved in an environment where all other teams are present? 

@estelaris proposed the following topic: How will we collaborate with polyglots to translate the documentation and help them create the new sitemap? We need to push for translations. Otherwise, a lot of our work will stagnate as an English version only

@ninianepress wants to submit a topic that @milana_cap mentioned during last year’s WCEU – about a waterfall solution across teams for everyone to be able to collaborate on projects across all teams. @milana_cap added an example that the Training/Learning team has been discussing for a long time with the Docs team on how to make a tool that would help us all communicate better about release changes.

@atachibana pointed out several workflow issues for the HelpHub that can be improved. Through the discussions, we agreed that we could discuss these issues internally within the Docs team.

Open Floor

@wigno volunteered to review and publish documentation content. @leonnugraha will help him to get going.

@milana_cap has an idea for three little tools that should help with some workflows and will build something to test out:

  • Meeting agenda generator
  • Meeting summary generator
  • New contributor orientation tool/onboarding tool

@estelaris will ask the meta team about the users’ access when the /documentation site is live.

Props to @leonnugraha for writing this meeting summary.

#docs, #meetings, #summary

Jenni McKinnon 6:00 am on January 10, 2023
Tags:   

Documentation Team Discussion on the 2023 Community Summit Call for Submissions

Summary: The documentation team will discuss topics we want to submit for collaboration at the 2023 WordPress Community Summit. Following the submission guidelines, the team can add their ideas in the comments section below for collaboration at the upcoming meeting.

On August 22-23 in National Harbor, DC, USA, the 2023 WordPress Community Summit will be held. There, the WordPress community will discuss and collaborate on specific challenges and opportunities for clarifying the vision for WordPress and its future.

A call for submissions was posted for topics to discuss during the summit. The lead organizing team is requiring all contributor teams to suggest points of interest.

The documentation team will be discussing topics for submission at our next meeting, which will be held on Tuesday, January 10, 2023 at 2 PM UTC.

Please leave your suggestions in the comments section below. But before you do, there are areas that need to be carefully considered.

As @milana_cap mentioned at the last meeting, it’s essential for us to collaborate on possible topics that keep the following in mind:

“What are the Documentation team needs that can, in full or partially, be solved in an environment where all other teams are present?”

Your suggestion in the comments also needs to follow the submission guidelines:

  1. Topic description
  2. Why would this topic benefit from in-person discussion or work at the summit?
  3. Who needs to participate in the discussion above where their absence would render any collaboration incomplete?

For the last point, you could include specific contributor teams, roles, individuals, or similar.

All comments will be reviewed and considered at our upcoming meeting.

#meetings

Estela Rueda 6:42 pm on January 7, 2023
Tags:   

There is work in progress in HelpHub (Documentation)

This post is to ask everyone who has access to HelpHub, to please refrain from adding, editing or publishing old or new articles as of the writing of this post.

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 the replacement of the /support/ site for a /documentation/ site and whatever is not there as of today, will be lost.

Please hold off any updates until after 17 January 2023. If you have any questions, reach out to @estelaris on #docs 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/. or leave a comment below.

Jenni McKinnon 10:09 pm on January 4, 2023
Tags: ,   

Agenda for Docs Team Bi-Weekly January 10, 2023

The next meeting is scheduled with the following details:

When: Tuesday, 10 January, 2023, 02:00 PM UTC

Where: #docs channel on Slack

Agenda:

  1. Attendance
  2. Note-taker and facilitator selection for next meeting
  3. Facilitator selection for next triage meeting
  4. Projects checks
  5. Collaborate on topics to submit for the 2023 WordPress Community Summit
  6. Open floor

If there’s anything you’d like to discuss on the open floor, please leave the comment below.

#agenda, #meetings

Milana Cap 3:40 pm on December 22, 2022
Tags:   

Summary for Docs Team meeting, December 13, 2022

Attendance

@ninianepress @milana_cap @leonnugraha @femkreations @atachibana @thisisyeasin @emmaht @juanmaguitar @estelaris @bph @themiked @psykro

Housekeeping

Find the complete Transcript of the meeting on Slack.

Documentation team holiday schedule

It has been decided that the Documentation team will have a 3 weeks long time off for the holidays. This means that no meetings will happen during this time, as well as the response in 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/. channel can be slower.

The time of is starting on Monday, December 19th 2022; and ends on Sunday, January 8th, 2023. The first meeting in 2023 will be on Tuesday, January 10th, at 2PM UTC. The format will be regular biweekly meeting.

Projects checks

@themiked – all the security related stuff is rewritten and consolidated now (#622, #623)

@femkreations – Reviewed, updated and closed 8 tasks for 6.1 Project and 9 tasks for 6.0 Project

@leonnugraha – Closed and published one high-prio 5.9 issue.

@atachibana – Tackling opened issues from the bottom (the oldest). Closed two issues and working #13.

@estelaris – working with 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. on the redesign for HelpHub and DevHub. We are testing the breadcrumbs and waiting on a resolution from coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. on next steps to do the reclassification of the articles, title changing and lots of 301s. May not have a holiday break.

@milana_cap – started working on Estela’s issue, did some reviewing of dev blog posts, a bit of onboarding docs (really hope to get that done before the next meeting).

Open floor

@estelaris – we need to add props for meeting facilitators and note takers so that everyone gets acknowledge.

@femkreations – saw this posting in the Make blog. Anything we can come up with for the Docs team?

Topics for the WordPress Community Summit 2023

We should think, as a team, of possible topics for Community Summit. What are the Documentation team needs that can, in full or partially, be solved in an environment where all other teams are present? This should be the first agenda item at the next meeting. Format:

  • Topic description
  • Why would this topic particularly benefit from in-person discussion/work at the Community Summit?
  • Who needs to participate in the discussion described above?(In other words, without these people in the room, the discussion may be incomplete. This may include specific Contributor Teams, roles, individuals, etc.)

Have a wonderful holidays and a good rest, team. See you in 2023.

#summary

Jenni McKinnon 1:05 pm on December 13, 2022
Tags: ,   

Agenda for Docs Team Bi-Weekly December 13, 2022

The next meeting is scheduled with the following details:

When: Tuesday, 13 December, 2022, 02:00 PM UTC

Where: #docs channel on Slack

Agenda:

  1. Attendance
  2. Projects checks
  3. Documentation team holiday schedule
  4. Note-taker and facilitator selection for next meeting
  5. Open floor

If there’s anything you’d like to discuss on the open floor, please leave the comment below.

#agenda, #meetings

Julia Golomb 3:41 pm on December 8, 2022
Tags: ,   

X-post: Suggest Topics for the 2023 WordPress Community Summit

X-comment from +make.wordpress.org/community: Comment on Suggest Topics for the 2023 WordPress Community Summit

JuanMa Garrido 7:39 am on November 30, 2022  

Summary for Docs Team Meeting November 29, 2022

Attendance

@estelaris @milana_cap @leonnugraha @femkreations @ninianepress @juanmaguitar @emmaht @samanthaxmunoz @malcolm

Housekeeping

Find the complete Transcript of the meeting on Slack.

Projects checks

@milana_cap has been mostly working on onboarding and roles docs, also handing out badges for docs contributors.

@leonnugraha reviewed and published #295 and #494 

@femkreations reviewed and closed 16 tasks for 6.1 Project and 1 task for 6.0 Project

@estelaris shares that HelpHub redesign is on the works but the reclassification part, meaning the new site map is on hold. The changelog as newly proposed is under review because it requires a new 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. and meta will work on that further.

It seems that all design changes will happen in the next 4-6 months and after that meta will look into structural changes.

DevHub redesign

@estelaris  wrote a post that has received very good feedback. The design worked out a second iteration, which she updated on the post. Call for feedback will finish this Friday.

There was a discussion about the resources that should be displayed in the new design. 

Structure of the Homepage

The conclusion of the conversations was that the resources shared from the landing page of developer.wordpress.org should be distributed in the following way:

< help yourself >

Documentation (left)

APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. Reference  (right)

< help yourself more + get other’s help >

More Resources

< read what’s new >

Developer Blog

  • 3 latest posts w/ their categories
  • Links to most popular categories in the blog

<  get involved >

Get Involved

#meeting-notes