Establishing a Review Process is something which is hit on in the DeveloperHub blog. Indeed – we’d like to choose a specific method of reviewing, and that being in the DeveloperHub platform itself. Currently, the internal comments for collaboration are the mechanism for which this can be accomplished – collaborating between those with a reviewer/writer vs publisher role.
To expand upon this workflow, it would be nice to have a “pipeline”, essentially, where an article can be in a “Ready for Review” state prior to being moved to “Published”, for example – with the option for those as publishers to skip this and publish directly, as normal.
Currently, the only article states are “Draft” and “Published”, essentially – where an article can be “Published” but also in “Draft” if any modifications are made after the fact.
A mechanism is needed to signal to publishers and/or those responsible for reviewing articles otherwise that these articles are ready to go, and not still being worked on (aside from a comment tagging these individuals and stating as such).