Closed gene-eu-zz closed 8 years ago
What aspects of the GitHub wiki style are the most problematic?
three big ones:
I mean, people are not comparing us against ugly, default readthedocs or sphinx documentation. In life of modern developer, there is plenty of very high-quality designed and well-written docs. And if we could achieve at least some more accessibility by finding better design engine - we should do it.
good examples:
For docs hosting we might consider using GitHub pages: they support markdown, pretty fast, there are many beautiful templates out there. We can have any hierarchy and most of document generators generate html anyway. We still get all the git features for manipulating them.
+1 to github pages. for the current moment let's use some existing tools instead of creating 'yet-another-tool'.
Guys (and gals), sorry for creating this misunderstanding. I raised this as means to discuss what features we seek in documentation generation platform, not it's hosting. We can of course host them anywhere we want :)
Right now, I'm considering this one - http://daux.io/ as possibly the best option, if we find ways to skin it properly.
i like that 'Supports GitHub Flavored Markdown' in daux suport features list
Started porting the docs to daux.io, anyway.
By receiving a few bits of feedback sounding almost equally (github's wiki is not well suited to read our style of documentation), before proceeding with even betters docs and tutorials, which are on their way, I'd like to hear your opinions, which documentation hosting platforms / documentation generation systems could work for us.
We could of course write our own tiny website-like thing, suited for our documentation needs, but I doubt this effort is worth it right now.