That’s a nice idea. Organizing docs by kind would be really helpful to new contributors, as each kind can have a certain structure, voice, audience, etc., and a template document can be used when creating new doc pages. It would also help in knowing what is missing, so instead of creating an issue to request “Document type class selection” it can be phrased “Explain type class selection”. Some kinds of documentation require deeper experience and understanding than others; I imagine the “Explanation” and “Reference” kinds would require cooperation with certain people whereas the “Tutorials” and “How-to guides” kinds seem like a relative newcomer to PureScript could contribute.
Currently, the purescript/documentation project’s “language” directory is mostly the “Reference” kind. The “guides” directory in the purescript/documentation project seems to be a mix of other kinds of docs, on the other hand, so that could use some organizing. As an example of another “Explanations” kind of docs, I’ve got a start for an explanation of bundling and I think a nice separate project would be an explanation of building/compiling.
We should just create a directory for each of these kinds of docs, include a template doc in each directory, and slowly move docs from the pre-existing directories into the new directories.
I’m mostly concerned with the purescript/documentation project. What other places need docs organization of efforts? Do we need a central listing of core & contrib libraries and their documentation status? If so, where would that go? I suppose we could make a new project, like “purescript/library-docs”, but that might fracture/confuse the docs-concerned community, so it might be better to just use a 1-2 doc pages in the purescript/documentation project.