Open olafveerman opened 5 years ago
This is good info! There are definitely some things we can borrow from it!
Another data point: for Scoreboard, we used Docusaurus and integrated DocSearch by Algolia because it has an official integration. The process to apply was straightforward, I added my site (https://developmentseed.org/scoreboard) and my email and they gave me an api key by email to enter into Docusaurus
Relevant code: https://github.com/developmentseed/scoreboard/pull/326/commits/0df441465d7db2eb795e61ec4142d6129a33220d Scoreboard docseed: https://developmentseed.org/scoreboard
For AF Elections we needed a simple site for developer documentation. Even though we started with
doc-seed
, we ended up using Docusaurus. This post briefly captures its advantages and disadvantages.The live site is here: http://devseed.com/af-elections-docs/docs/results
:+1: Docusaurus
The first and second level navigation is manually configured. It's an extra step, but quicker and more intuitive than
doc-seed
's automatically generated menu. This also provides more flexibility in how one organizes the markdown files. -> https://github.com/developmentseed/af-elections-docs/blob/master/website/sidebars.jsonContextual nav (right side) is auto-generated from markdown headings
Nice code highlighting with
highlight.js
, which was critical for the API-like documentation that we neededIt's a
npm
package :rocket::+1: Doc Seed
doc-seed
's simple structure.Next time
The configurable navigation and code highlighting are great features of Docusaurus. If we bring that into
doc-seed
, I would use it for a similar documentation project next time.cc @danielfdsilva @ricardomestre