⚠️ How to use the Final Review list 👇
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 333
- Forks
- 127
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 11
Description
The Final Review list is for lesson plans, workshops and courses that have been through copyediting, instructional review, and testing and are nearly ready for official publication.
The Training Team admins will review for:
- Adherence to the current template
- Adherence to the current style guide
- Quality and completeness of information
- Any technical formatting details needing to be changed in order for the content to be published
- Slide review or creation
- Anything else needing attention before publication
Cards move out of this list (and to the Ready for Publication list) when they have been approved by the team admins.
Checklist: https://docs.google.com/document/d/1GZuIUgEuwTWfAQe9gElFYBwNSD9smUMCvgKjOZFEnwM/edit?usp=sharing
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
Read the issue body and the linked Final Review checklist first. The payload does not name a file, test, or specific documentation change; work would be complete only when a concrete, current update to the review-list guidance is defined and published.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100