So how does this work? the github.com/SublimeText/sublimetext.github.com hosts the built html files, but if we're using a lightweight markup language to do the writing, where do the .rst/.md files go?
Since I'm pretty sure I won't be converting my .rst to .md myself, I suggest the following:
- we use .rst + Sphinx for the current content and main guide
- we use .md for the knowledgebase
- we create a front page like sublimetext.info that forwards to each of the subsections, and other interesting locations
I like this idea because:
It's fair to assume that people willing to put in the time to write core documentation will take the time to look at other existing topics and get up to speed with Sphinx quickly enough.
I picture the knowledgebase as a collection of disparate tips, tutorials and troubleshooting topics with little or no interlinking: one file, one topic, and that's it. Sphinx doesn't seem to be useful there, except for the full-text index in JS.
It would allow me to push the existing content as soon as I learn where to. Later on, we might think about going Sphinxless, but right now I honestly don't se the urge to.
BTW, I'm also in favor of having two or three gatekeepers for the docs repo and let contributors edit content via pull requests.