Tag Archives: summary

Birgit Pauli-Haack 9:22 am on August 10, 2022
Tags: 6.1, Dev Note, , , summary   

Kick-off WordPress 6.1 release docs

Thank you for participating in the kick-off meeting for the WordPress 6.1 release documentation team: @milana_cap, @femkreations, @mburridge, @bph (facilitator and notetaker). @webcommsat participated asynchronously and added input from the video. 

The meeting was recorded and is available on YouTube.

Updated August 11: refined the instructions to match the GitHub Tracking issue for 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 PRs.

TL;DR: Follow the progress

Links to relevant information.

Next Steps and process for 6.1

Triage Phase

DevNotes and Developer Documentation

  • Add ‘Needs Dev Note’ label to tickets in milestones, and 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/ 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 releases
  • Trac tickets ‘needs-dev-note’
  • 🙋‍♀️ Triage TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets – Milana
  • GitHub (Gutenberg) needs dev note
  • 🙋‍♀️ Triage Gutenberg plugin PRs – Birgit

End User Documentation

  • Add '[Type] User Documentation' or needs user-doc labels to Trac tickets and Gutenberg PRs and all will be tracked via the 6.1 Project for both (trac + 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/)
  • GitHub Gutenberg [Type] User Documentation
  • 🙋‍♀️ Add labels to PRs on Gutenberg – Femy
  • 🙋‍♀️ Trac Tickets to be labeled with needs-user-docs: Milana

Tracking

  • Add ‘needs dev note’ / ‘needs dev docs’ tickets to the project – Milana
  • Create issues for pages once the scope of user-facing features tracked with [Type] User Documentation is determined – Femy
  • Track Gutenberg needs dev note via the Tracking issue on GitHub and connect with developers regarding delivery – Birgit
  • Reach out to the Component Maintainers for the “But Wait there is more” tickets – Birgit. Abha, if extra hands needed

Delivery and Collecting the Dev Notes Tasks

After 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. 1, it will be pretty clear which patch and PR will make it into the WordPress 6.1 release. It would help tremendously if dev notes are drafted between Beta 1 and Beta 2 (for 6.1, this will be between September 20 and 27, 2022). This will help the reviewers have more time to give it a fuller review.

Stand-along Post

If a dev note requires a separate post, the process is slightly different between dev notes concerning the Gutenberg project and developers who provided a patch on trac.
The instructions for dev notes on Editor features are listed in the GitHub Tracking Issue for DevNotes

For developers who provided commits via trac also draft the dev note on Make Blog, and once drafted, the developer should add a message to the docs channel, with the public preview link to let the team know it’s ready for review.

For small dev notes for a combined post

If only a small dev note is required, it will be published with other notes in a combined post (Miscellaneous Block Editor, or Miscellaneous Theme, Miscellaneous Caching). The developer assigned will add the dev notes as a comment to the particular PR or the Trac ticket.
Trac tickets also are then labeled with has dev note.
For the GitHub PRs the developer should post a comment on the GitHub tracking issue
The release documentation team will review and collect those for the Miscellaneous blog posts.

Tasks for release documentation team:

  • provide author privileges to developers who write dev notes
  • collect the small notes from the PRs and organize them on Miscellaneous Dev Note posts
  • collect snippets from the Component Maintainers’ responses
  • compile the Field Guide
  • assist in triaging, prioritizing and recruit writers for End User Documentation

How to get involved? 

End User Documentation updates

With new features coming to WordPress, the majority of help is needed in triaging, scoping and executing changes to the end user documentation for the block editor. Femy Praseeth @femkreations, a documentation team project rep and one of the co-leads of the 6.1 release documentation team, is the contact point if you can help with one of the areas listed below.

  • Triaging: join in on labeling user-facing Gutenberg PRs for End-User Documentation
  • Issue Gardening: once all issues are reviewed, create issues in Documentation Issue Tracker repo for End-User Documentation, adding information from the PRs to the description
  • Writing: add and edit identified pages of  End User documentation 
  • Taking screenshots (Training video)

Abha will support Femy in triaging, prioritizing and recruiting writers for End User Documentation.

Write and review 6.1 Dev Notes

In the next few weeks, Abha will co-ordinate additional steps to help those writing dev notes, including information on adding excerpts, a summary paragraph at the top of the post, the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. style guide, and avoiding using ‘here’ for links which are difficult for 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), etc.

Developers of release features which will be relevant for other developers will write the dev notes or the relevant section to include into a collection of dev notes. If you are assigned a dev note, drafting it on the Make blog between Beta 1 and Beta 2 would be great. Please do not publish the dev note until it has been through its review stages. It will be published by the Release Documentation Team and the GitHub entry updated.

Each dev note requires two people to review, plus final review by the documentation release team. If you like to review other people’s writing, reviewing dev notes could be for you! 

Find out more

As the team is just starting to get all the pieces in place, they might not have all the answers yet.

Please don’t hesitate to comment below or send a message via the Make WordPress 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/. #docs channel and 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.” either @femkreations, @milana_cap or @bph.

Props for reviewing the post: @webcommsat, @milana_cap, @femkreations, @audrasjb

#6-1, #dev-note, #meetings, #summary

Estela Rueda 11:27 am on August 3, 2022
Tags: , props, summary   

Summary of Docs Team Biweekly Meeting August 2, 2022

Housekeeping

Project Checks

Documentation Issue Tracker Updates

  • @leonnugraha is almost finished with #315 and #270
  • @lucp is still working on #375
  • @milana_cap
    • created two 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/ workflows: 1. automated adding issue to the project based on applied labels; 2. automated comment on the issue, mentioning project reps based on applied labels
    • moved docs handbook project to new ones to make above automation possible: https://github.com/orgs/WordPress/projects/43/views/1
    • continue working on team roles docs: https://github.com/WordPress/Documentation-Issue-Tracker/issues/385
  • @colorful-tones is adding lots of feedback to the Patterns doc for the Theme Developer Handbook #342
  • @femkreations
    • 19 items  in the 5.9 issues have been closed (all of them have been updated now for 6.0 as well)
    • 2 new pages were created and updated for 6.0. 12 pages are a work in progress currently
    • the 5.9 issues project board and merging it into the 6.0 soon. New contributors please refer to the 6.0 issue board for 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 docs

Inventory of technical Parts from End-User docs

@estelaris is updating the Inventory of technical Parts from End-User docs, adding other articles to be reviewed and edited after the second site map revision.

Helphub redesign/reclassification project

@estelaris reported that the last revision of the site map has taken longer than expected and will write a post after the second revision is done. These items are still in the works:

  • Update the template with the developers block
  • Add a link to features and requirements (under the About menu item)
  • Finish updating the tickets for articles to rename, move to DevHub and delete
  • Update the categories/subcategories in HelpHub (per 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. instructions) but not changing categories to any article yet

Updates on the Five for the Future program and proposed improvements

The idea is to track better and more contributions, especially those that are not code. As of last week, there are new items already showing in contributors profiles.

For docs team, it mean that opening/closing/being assigned to an issue in the Issue tracker repo is going to be displayed on your profile. Still we will have to track some things manually, like facilitating meetings in the #props Slack channel. For contributions done in GitHub see issue #178.

Open Floor

@audrasjb asked if anyone is also curating DevHub user contributed notes and he will write a draft on his process to facilitate other contributions.

@lucp raised his hand as team repTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. for the advanced administration handbook and he will take over the Inventory of technical Parts from End-User docs.

#meetings, #summary

Justin Tadlock 8:44 pm on July 19, 2022
Tags: , summary   

Summary of Docs Team Biweekly Meeting July 19th, 2022

Housekeeping

Project Checks

  • @milana_cap re-wrote the homepage and requests feedback in the ticket
  • @milana_cap started working on team roles page.
  • Updated Team page with open positions (see rep positions below).
  • Completed and reviewed 5.9 Block Editor Doc Project tasks:
  • HelpHub design and reclassification project updates from @estelaris:
    • Waiting on a site map review for some articles to move to DevHub.
    • Update two items on the design: change dev docs link for a dev 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. similar to the support block and change items in the menu.
    • Update the images on the post.
    • Plan to release the post with the new design on Thursday, July 21.

DevHub Handbook: Advanced Administration

A 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. TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. ticket is now open for new handbook. Currently, there are developer and end-user docs, but many unsorted docs fall under an “advanced administration” term. Most of the content will be pulled from:

  • HelpHub – Pages that are too technical for end-user docs (see “Technical guides” column in HelpHub sitemap spreadsheet).
  • Codex – Pages that have not been migrated to DevHub/HelpHub because they did not fit into either.

Approving User-Contributed Notes

@lucp linked to a Slack conversation on pending comments on DevHub, some of them dating back for a year. There is ongoing discussion about how to best handle this and a Meta ticket that proposes emailing users when a comment is approved/deleted.

Rep Positions

There are three open rep positions. Those interested should contact @milana_cap.

  • Block Editor Developer Handbook
  • More Info Curator (Code reference)
  • Upcoming Advanced Administration Handbook

See onboarding video for more information. Also, see the complete list of roles.

Open Floor

@colorful-tones started a draft on patterns for the theme developer handbook.

@bph noted that comments on the upcoming developer blog editorial process close on July 20.

#meetings, #summary

LucP 7:08 pm on July 5, 2022
Tags: , , summary   

Summary of Docs Team Biweekly Meeting July 5th, 2022

Housekeeping

Projects checks

DevHub & Learn WordPress development

  • The #meta team is working on improvements to DevHub (the developers documentation). If you have any suggestions, please comment on this post
  • There is also an x-post from the Learn team. Again, if you are interesting in either collaborating or have ideas, please comment. The docs team is actively contributing with the Learn team.

Open Floor

  • @mburridge wanted clarification on whether to continue creating 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 issues in the Documentation-Issue-Tracker. (see issues #379 and #75).
  • While the Block Editor Handbook falls under the 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/ team, @milana_cap mentioned in one of the issues that we might as well gather all issues regarding the Block Editor Handbook in the Documentation-Issue-Tracker while the docs team is preparing to send over a larger issue to the Gutenberg team with all sorts of improvements.
  • Similar issues as #379 and #75 should be posted in #docs so the team can take a look at it. @milana_cap later clarified the point on slack

Props to @greenshady for helping with notes.

#summary

Estela Rueda 2:48 pm on June 28, 2022
Tags: , summary   

Summary of Docs Team Biweekly Meeting June 21, 2022

Housekeeping

Open Floor

Docs Onboarding Videos

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. Documentation Comments

@lucp and @milana_cap:

5.9 Issues for HelpHub

@femkreations:

  • Issues with WordPress version 5.9 for the HelpHub are being worked on.
  • Later, the issues will be merged into the 6.0 project.
  • A lot of images don’t have ALT text and this needs to be emphasized for adding screenshots to HelpHub articles.
  • @milana_cap noted that ALT text is mentioned in the docs team Handbook.
  • A list will be added for this to the GitHub Issue Template for resolving on WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. contributor days.
  • An extra phase in the content review process will be added to address this issue.

@milana_cap will add a link to the list on the Leading a Contribution Day Handbook page.

Props to @ninianepress for writing the notes.

#summary

Femy Praseeth 9:08 pm on June 8, 2022
Tags: , summary   

Summary of Docs Team Meeting June 7, 2022

Housekeeping

Project Updates

WCEU contributor dayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/.

@milana_cap:

  • We had a packed WCEU contributor Day for the Docs team. We worked on various issues mostly on the 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 end user ones.
  • @bph and @leogermani helped out in co-leading and onboarding.

New block editor end-user rep

  • We have a new block editor end-user docs rep – @femkreations 
  • @milana_cap will be moving to other projects such as improving the onboarding process, updating the related docs, recording videos, and doing live onboarding sessions.

Docs design updates:

@estelaris:

  • The design for the Docs is almost done.
  • @estelaris will also add design elements for warnings and notes that @femkreations asked for. 
  • Each section of 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/ will have a similar look with a different color palette. This will make it easy to know what we are looking at.
  • The look and feel of Devhub will be the same as Helphub.
  • The landing page for documentation will now include everything:
    • The last section in the landing page design (under Developers) will replace https://developer.wordpress.org/
  • At some point, DevHub will also go through a site map review, as she did for HelpHub.
  • We’ll also have some kind of automated linking to the Learn platform, like a widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. in the sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme..

URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org for the documentation:

@milana_cap and @estelaris:

  • There are two items on the menu under support: documentation and forums.
  • The URL for documentation is wordpress.org/support which makes no sense.
  • The URL for the documentation needs to be more obvious. e.g. docs.wordpress.org
  • Support is not a place where developers look for docs.
  • Support means interaction, docs are information.
  • Support needs to go to the support forums and not to documentation.
  • @estelaris to discuss this with Josepha and 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 and start the implementation soon.

Moving the Action and FilterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. reference pages from Codex to DevHub

  • @psykro raised the question about moving the Action Reference and Filter Reference pages from the Codex to DevHub.
  • He will open new GH tickets for each one, to allow for further discussion there.
  • It will be moved into the Common 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..
  • The order of firing will be updated and new 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. will be added.

Open floor

Coffee and chat

  • We are bringing back the zoom hangouts for coffee and chat.
  • It’s a 30 min hangout, once a month.
  • @estelaris will set up a doodle for the summer dates – June-August where folks can vote for the time/date.

Onboarding sessions

For anyone interested in starting to help with the docs

#meetings, #summary

Femy Praseeth 12:08 am on May 26, 2022
Tags: , summary   

Summary of Docs Team Meeting May 24, 2022

Housekeeping

Discussions

Here are the updates and discussions from the Docs meeting held on May 24th.

#meetings, #summary

JuanMa Garrido 10:57 am on May 11, 2022
Tags: summary   

Summary of Docs Team Meeting May 10, 2022

Housekeeping

Project Updates

  •  @milana_cap shares the status of docs regarding WordPress 6.0
    • last week we had RC1 out, all Dev Notes and Field Guide are published
    • we’re moving on to updating end user and dev docs – anyone wants to help just 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.” me
  • @juanmaguitar asked about a list of Projects related to Docs
    • The list is here but it’s probably a bit outdated
  •  @milana_cap shares that besides 6.0 she has created two new projects in the Docs repo:
  • @femkreations shares:
    • she completed triaging the google doc and created trackers for 6.0 end-user documentation,
    • she reviewed the google doc with help of @milana_cap on a video call and @bph (async) for clarifications.
    • she also reviewed the WP 6.0 release candidateRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. post and About Page (draft)  for the HelpHub updates required and updated the trackers.
  •  @milana_cap shares she’s working on getting more people making code examples for code reference

Open Floor

#meeting

#summary

Femy Praseeth 2:29 am on April 22, 2022
Tags: , summary   

Summary of Docs Team Meeting April 19, 2022

Housekeeping

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 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..

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

@milana_cap:

  • Closed a few more 5.9 block editor end-user issues.
  • All tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets are labeled for docs and GitHub project is ready.
  • We have a new channel #docs-firehose for getting 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/ updates so that we keep the #docs channel clean

@femkreations:

  • 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.

@estelaris:

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 WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Athens in person.

@milana_cap to lead the Docs table at the Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. for WCEU.

#meeting, #summary

Femy Praseeth 12:31 am on April 6, 2022
Tags: , summary   

Summary of Docs team meeting Apr 5, 2022

Housekeeping

Project updates

WordPress 6.0 End User Documentation 

@bph created a list of changes coming to WordPress 6.0 that would need End-User Documentation. She is waiting for the 13.0 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/ 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 release happening on Friday 4/8 and the walk-through before completing the list and setting priorities. Currently, some of the sections are not fully curated and some PRs might not be user-facing. She hopes to have the list completed by Monday, April 11th.

@milana_cap to start creating GitHub issues in the tracker repo from the list, once the list of changes is finalized. She also created 2 priority levels for the tasks: High and Medium.

@estelaris noted: Contributors who work on End-User Documentation need to follow the style guide such as using sentence case for headings and adding the word ‘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.’ to the title and URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org for all the block pages.

@bph to start wrangling PR authors for their Dev Notes for the release and the Field guide.

@bph/@milana_cap to go through all TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets to collect all DevNotes, dev and end-user docs. They will also update the Contributors-wanted post and share the post on the internet.

Other updates

@estelaris: Work on the HelpHub is progressing well. The 301 redirects issue will be fixed for wordpress.org and will be on the list of features for the next release. HelpHub sitemap has been approved by Josepha and the Docs team.

@estelaris is currently working on the HelpHub design. The Docs team reviewed the first draft in the meeting. Once the design is approved by the design team, it will be shared. And the next step will be to redirect articles (changing titles/URLs/merging articles, etc).

@milana_cap: recorded onboarding session. She will upload it to wordpress.tv after she edits out a section. She did some work on triaging Trac tickets for 6.0 docs. She also reviewed quite a few block editor end-user issues.

@femkreations: Added more new pages to the Block Editor End-User Docs for the missing block pages for the 5.9 release.

@themiked: Updated a plugin handbook page.

#meetings, #summary