macos-defaults/build/docusaurus
2020-09-20 11:18:39 +02:00
..
__mocks__ 👷 Add a Docusaurus build action 2020-09-20 11:18:39 +02:00
__snapshots__ 👷 Add a Docusaurus build action 2020-09-20 11:18:39 +02:00
templates 👷 Add a Docusaurus build action 2020-09-20 11:18:39 +02:00
build.js 👷 Add a Docusaurus build action 2020-09-20 11:18:39 +02:00
netlify.toml 👷 Add a Docusaurus build action 2020-09-20 11:18:39 +02:00
package.json 👷 Add a Docusaurus build action 2020-09-20 11:18:39 +02:00
readme.md 👷 Add a Docusaurus build action 2020-09-20 11:18:39 +02:00
write-tree.js 👷 Add a Docusaurus build action 2020-09-20 11:18:39 +02:00
write-tree.test.js 👷 Add a Docusaurus build action 2020-09-20 11:18:39 +02:00
yarn.lock 👷 Add a Docusaurus build action 2020-09-20 11:18:39 +02:00

Docusaurus Build

Docusaurus build status

My opinion

Docusaurus was quite though to setup. It goes too far for my need. It's certainly more suited for real project documentation.

😄 Good

  • Default theme is nice
  • It's possible to use React components
  • Default theme got a footer

😕 Bad

  • The new project boilerplate is too complicated. Would have prefer something simpler but extensible as I need it
  • Search is only available using Algolia

😫 Ugly

  • Didn't find a way not to have that /docs/ base href

How does it work?

Here is the built website architecture:

All the other pages are markdown files that are carefully put under their folder (e.g. docs/screenshot/disable-shadow.md). Assets are stored under the docs/assets folder.

There is a second build phase where Docusaurus generates the static website.

Try locally

🏗 Install

yarn install

🚀 Usage

This will build the defaults.yml file and run a Docusaurus server on http://localhost:3000/docs/. Sources of the website are available in the dist folder.

yarn build

🚧 Run unit tests

yarn test