WordPress / WordPress/Documentation-Issue-Tracker

[HelpHub] Overhauling articles in the WordPress overview category - READ FIRST

Open
#2,181 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

6.9 tracking issue user documentation (HelpHub) WP Overview
Dominant language
Shell
Stars
109
Forks
73
PR merge metrics
No merged PRs in 30d

Description

To update each article and update them to WP release 6.9, follow the instructions below:

  • Review the reference issues and PRs that have been added to the article. Some articles may only have one issue.
  • Make any valid updates from previous releases. If those updates are no longer relevant, close the the issue (NOTE: we can only close issues in the Documentation Issue Tracker, feel free to leave a comment in the Gutenberg repository so a PR can be closed.)
  • Make sure to follow the style guide for title, headers and tone.
  • Do NOT hotlink images, take the screenshots and upload them to the documentation site in WordPress
  • Update the Change log and add updater's WP.org username and any other contributors that have given feedback/solution even if it wasn't used (eg. updated by @estelaris @zzap)
  • When you are done updating a block article, mark them in the list below
  • If you cannot edit articles in WordPress.org/documentation, ping @estelaris in #docs Slack for access.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the reference issues and pull requests attached to each WordPress overview article, then read the linked WordPress documentation style guide. Update relevant articles for WordPress 6.9, replace hotlinked images with uploaded screenshots, and update the change log and contributor credits. Mark completed articles in the issue and request WordPress.org documentation access if needed.

Written by the indexing model from the issue text.

Assessment

Tech stack
wordpress
Domain
content, documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.