Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

We migrated a while ago all our python docs from sphinx and the free readthedocs to mkdocs. Two main reasons:

- we like markdown more and starting (actually we converted to markdown with pandoc) with a bunch of markdown files was a breeze. We also did not lost advanced documentation features because there are plenty of fantastic mkdocs plugins.

- readthedocs was unreliable for us but we also did not wanted to pay for our open source software documentation generation + hosting.

At the end we have an auto generated mkdocs with GitHub+Travis and all searchable with the fantastic mkdocs static page search functionality (maybe the biggest feature of mkdocs)

End result: https://docs.pybossa.com (hosted on GitHub)

Source: https://github.com/scifabric/docs.pybossa.com



Can someone please compare this to https://github.com/facebook/Docusaurus and Jekyll? TIA


I really dislike .rst (and .md in Sphinx is less than great) so I'd love to switch from Sphinx. Do you know if there's mkdocs has an equivalent to Sphinx's autodoc?


I'm curious why you didn't use the sphinx markdown option and/or use travis and github pages to generate the sphinx docs instead.


You would loose online search capabilities with this approach or we had to implement it ourself which would be a waste of time because we wanted to write docs not the system behind the docs. We also faced problems with the styling on Sphinx over time (the ready to use styling templates on mkdocs only needed very little modifications from our side).


> we also did not wanted to pay for our open source software documentation generation + hosting.

Actually, rtd is free for OSS projects


Yes I know. It was not reliable enough for us and sometimes it failed generating the docs. Paying for it (don't know if this would improve the situation) was out of question for us.


I frequently see failures on RTD doc builds due to memory exhaustion.


This is quite nice, high quality documentation, the template is eye-catchy, very nicely structured, well done!


thx :)


Github hosts your docs for free, with a custom domain name?


Yep, just search for DNS CNAME handling on GitHub docs. We put also Cloudflare DNS in front of it to get TLS/SSL but I've heard this is not necessary anymore nowadays.


It's not, GitHub automatically registers Let's Encrypt certs for custom domains :)


Cool, thanks. Looking at your yaml, it looks like the title of each doc has to be configured separately? Is that required?


No this is optional. You can also just throw a bunch of .md files in a directory structure and run mkdocs over it to generate a tree for navigation.


Github Pages doesn't cost money.


you're right it doesn't cost money however GitHub pages only just started handling SSL certificates for custom domains recently (https://blog.github.com/2018-05-01-github-pages-custom-domai...). before that you had to use a provider like cloudflare to handle the termination.


Custom domain is usually where sites look for revenue ops, though VC/MS money should last for a while.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: