Skip to main content

Docusaurus 2019 Recap

· 1分で読めます
Yangshun Tay
Meta社フロントエンドエンジニア

2019 was a great year for Docusaurus - we've made tremendous progress on Docusaurus 2. Current Docusaurus 1 users who aren't using the translations feature can feel free to check it out and migrate to it! Otherwise we will work with you to make that happen in 2020 :)

Towards Docusaurus 2

· 1分で読めます
Endilie Yacop Sucipto
Maintainer of Docusaurus

Docusaurus was officially announced over nine months ago as a way to easily build open source documentation websites. Since then, it has amassed over 8,600 GitHub Stars, and is used by many popular open source projects such as React Native, Babel, Jest, Reason and Prettier.

There is a saying that the very best software is constantly evolving, and the very worst is not. In case you are not aware, we have been planning and working on the next version of Docusaurus 🎉.

How I Converted Profilo to Docusaurus in Under 2 Hours

· 1分で読めます

“Joel and I were discussing having a website and how it would have been great to launch with it. So I challenged myself to add Docusaurus support. It took just over an hour and a half. I'm going to send you a PR with the addition so you can take a look and see if you like it. Your workflow for adding docs wouldn't be much different from editing those Markdown files.”

— Note sent to the Profilo team

This is the story of the rather short journey it took to create the Profilo website using Docusaurus.

Profilo, an Android library for collecting performance traces from production, was announced earlier this year. The project was published on GitHub with a less than a handful or Markdown files to describe its functionality and no website to showcase any branding and highlight the logo. The task at hand was to turn these existing docs and logo into a website.

はじめに

· 1分で読めます
Joel Marcey
Meta社デベロッパー・アドボケート

We are very happy to introduce Docusaurus to help you manage one or many open source websites.

We created Docusaurus for the following reasons:

  1. Webサイトのインフラを気にするのではなく、良いドキュメントを書くことに重点を置くこと。
  2. ブログのサポート、検索、バージョン管理など、必要とする機能を提供するため。
  3. アップデート、新機能、バグ修正を簡単に更新できるようにするため。
  4. そして最後に、すべてのオープンソースプロジェクトで一貫した外観を提供することです。