Adopt some existing documentation system

[borekb]

In the long run, we should not maintain our own project just to render the documentation. A year ago, I didn't find anything quite suitable but I'll open this issue to gather some links to interesting projects.

Previous discussion about server-side rendering vs. static site generation: #12

Good docs

For inspiration:

• Hexo docs
• VSCode docs

Tools

• Algolia – search, alternative to Google Custom Search

[borekb]

Some other ideas:

• GitBook. Examples: Rust docs (well, that is probably rustbook) or Basarat's TypeScript book.
• VSCode has nice docs, I couldn't find the tool they use to convert the source repo to the final site, maybe it's not public.
• ReadTheDocs, somehow I'm not a big fan of the output.
• DevDocs – is that available to clone? Has some useful features like offline reading & common format.

Other resources:

• Beautiful Docs – a list to nice documentations & tools to generate them

[borekb]

Webpack 2 has a very nice documentation:

• Edit via GitHub
• Inline Gitter in top right corner, sort of like Intercom

[borekb]

Next.js intro is nice: https://learnnextjs.com/basics/getting-started

[borekb]

• DocFX – generates MS docs, maybe even VSCode docs?
• docsify – client-side solution (fetches Markdown to browser, renders there)
• MkDocs – another quite popular solution, there's nothing stunning about it at first sight.

[borekb]

Bootstrap 4 docs don't seem bad.

[borekb]

We now use MkDocs + mkdocs-material for docs.versionpress.com (see PR https://github.com/versionpress/platform/pull/1715) and it is awesome. This will be the way to go for docs.versionpress.net as well.