WordPress / WordPress/secure-custom-fields
Audit the current documentation for missing gaps and opportunities
Open
Nobody has claimed this yet.
documentation
- Dominant language
- PHP
- Stars
- 131
- Forks
- 64
- Avg merge
- 10m
- Merged PRs (30d)
- 1
Description
The first step is to audit the current documentation, hosted in this same repository and available at https://developer.wordpress.org/secure-custom-fields/, with a focus on:
- Overall information architecture and learning pathways
- Missing API references
- Missing Field types
- Broken links
- Opportunities for tutorials
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the current documentation in the repository at https://developer.wordpress.org/secure-custom-fields/. Audit its information architecture and learning pathways, API and field-type coverage, links, and tutorial opportunities. Done means producing a clear inventory of missing gaps, broken links, and improvement opportunities.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100