I think the best place to assign people to specific tasks (and follow progress) will be exactly where the project source code resides. We can use GitHub Issues and create discussions on a section level. We can then assign labels to help identify which issues are related to what.
How Issues will work
Each section will have its own Issue, this way we can discuss about that specific piece of the docs alone. Section issues should not be closed until that section is 100% written and revised.
Bugs and enchancements would get their own Issue. Found a bug? New Issue. Think some feature should be added? Another Issue.
How to use labels
As of now, those are the labels that will be used in the to identify the issues categories:
Writing: Label used on issues focused only on writing pieces of the documentation.
Section: Defined when the Issue is related to a whole section of the documentation.
Discussion: Wanna discuss something that isn't fully defined yet? Use this label.
Enhancement: Ask for some feature in the project (which isn't related to the text itself, but the website).
Bug: Report a bug in the project (which isn't related to the text itself, but the website).
Labels can also be combined. If I want to discuss about some specific section, I can add discussion and section labels to that Issue. This way I believe it will be easier to focus on specific points of the documentation.
GitHub Issues are also good because you can assign people to them. So I can explicitly say that Joe and Martha are working on that section and everyone will be able to see that and know who actually is working on what.
I believe it may be a little confusing in the beginning (especially to those who never used things such as GitHub or Git), but you can always check the already open Issues to learn by example.
Docs Issues can be found here: https://github.com/peercoin/docs/issues
This thread will keep being used because we a place to discuss the documentation as a whole, roadmap, status review and other generic topics that fit better in the forum.
@Sentinelrv what do you think?
We should use Github Issues to manage who is doing what in the docs.