- Fast dev workflow. The dependencies are kept relatively minimal, which is very appreciated.
- Very little magic. Doesn't opt you into a particular e.g. css paradigm. I personally appreciate the sweet spot where things "Just Work", but thanks to simplicity and obviousness, rather than explicitly architecting (though I'm sure the team actually put lots of thoughts into the design).
- Generates clean, idempotent static output, that you can manually introspect. A small source change leads to a small artifact change. A nice consequence derived from its simplicity.
- Generates static sites that work without JS, naturally. You can also progressively enhance it through regular JS.
- i18n! Super grateful we didn't need to handle that ourselves.
Haven't tried versioning, but we'd love to look into that as well.
I'm excited to have been involved with this project! Docusaurus already powers the documentation of Relay, React Native, Jest, Prettier, Reason-React and many more
Huge congrats to the hard work of the core team: @JoelMarcey @ericnakagawa @hectorramos and our former intern Frank Li.
Hopefully your next open source launch will be made a bit easier with this tool, and allow you to focus on writing great documentation!
Thanks @EricVicenti! And congrats to you as well, especially since you were the one who brought this idea to us back in the summer. So happy you did. :)
From first look, it seems that docusaurus comes with saner and simpler defaults for a site. Gatsbyjs has to have plugins installed just to get markdown working and then grok graphql syntax to fetch data from markdown.
Gatsby is a great tool for documentation as well. In fact, some of our open source projects use Gatsby (e.g., reactjs.org). We feel that Docusaurus serves a bit of a different audience. Docusaurus is focused on the fastest way to document a project. We wanted to provide a really quick way to get a site running with certain core functionality that folks might find useful. We can see Gatsby and Docusaurus possibly collaborating on some features. In fact, we could see integrating/adopting parts of Gatsby into Docusaurus under the hood. That is something that is worth exploring moving forward.
Hi @eitland! We wanted to start off relatively simply for the launch. Support for markdown and static assets, including images, css, raw HTML, etc.
However, we are definitely looking at supporting other formats moving forward. We just want to make sure we do not complicate Docusaurus too much by doing so. Trying to find a good balance.
- Fast dev workflow. The dependencies are kept relatively minimal, which is very appreciated. - Very little magic. Doesn't opt you into a particular e.g. css paradigm. I personally appreciate the sweet spot where things "Just Work", but thanks to simplicity and obviousness, rather than explicitly architecting (though I'm sure the team actually put lots of thoughts into the design). - Generates clean, idempotent static output, that you can manually introspect. A small source change leads to a small artifact change. A nice consequence derived from its simplicity. - Generates static sites that work without JS, naturally. You can also progressively enhance it through regular JS. - i18n! Super grateful we didn't need to handle that ourselves.
Haven't tried versioning, but we'd love to look into that as well.
Thank you Docusaurus team =)