Planner could use a documentation website to teach users how to install, build or use it. It could be seperate from the main website to reduce clutter on the main website while allowing the docs to be in depth. I'd be willing to contribute to it myself.
Some options for hosting it include using a github wiki on the main repo, or alternatively, storing markdown files in a seperate docs repo and building the docs with ReadTheDocs. I recommend the latter but that's just me. We could also store the docs in the main repo as well while still being able to process them with ReadTheDocs. This has a bonus advantage of having everything in one location
Planner could use a documentation website to teach users how to install, build or use it. It could be seperate from the main website to reduce clutter on the main website while allowing the docs to be in depth. I'd be willing to contribute to it myself.
Some options for hosting it include using a github wiki on the main repo, or alternatively, storing markdown files in a seperate docs repo and building the docs with ReadTheDocs. I recommend the latter but that's just me. We could also store the docs in the main repo as well while still being able to process them with ReadTheDocs. This has a bonus advantage of having everything in one location