Our docs are currently powered by versionpress/docs-site, a small Node.js app that serves a bunch of Markdown files – currently the contents of /docs/content folder in this repo. The idea was that we'd be able to switch versions of the documentation and language versions but the reality is that these features are not used and static site generation would be much simpler.

Specifically, MkDocs + mkdocs-material is a nice combo that we already use for our ".com" docs and would also provide all we really need for ".net" docs:

• Markdown source files
• Search
• Navigation: menu & prev/next
• Design options

If someone wanted to take this, it would be great. What should happen as part of the PR:

• Update the Markdown files and their structure for MkDocs
• Move the release notes to GitHub releases and/or CHANGELOG.md We'll keep them in the docs for now
• Ideally keep the design. I quite like the distinct, although relatively old-school looks of our docs.
• Update README / deployment instructions
  • The site is now deployed to GitHub Pages.

Related: versionpress/docs-site#92

🏁

Summary:

• Nice PR by @lisaross implementing all the necessary changes: Switch to MkDocs for documentation #1334
• Site deployed to GitHub Pages
• versionpress/docs-site Node.js app archived

New docs:

Original docs:

Blog post.