diff --git a/blog/2019/12/30/docusaurus-2019-recap.html b/blog/2019/12/30/docusaurus-2019-recap.html index dcfd5442a8..b15a0f4c25 100644 --- a/blog/2019/12/30/docusaurus-2019-recap.html +++ b/blog/2019/12/30/docusaurus-2019-recap.html @@ -84,7 +84,7 @@
In 2018, we proposed to rebuild Docusaurus from the ground up. It involved a major rearchitecture effort - we created a content-centric CSS framework from scratch, a plugins system, and moved from static HTML pages to be a single page-app with prerendered routes. It was a wild adventure and a tough feat, especially with no dedicated FTE working on the project. With the help of @endilie, our ex-intern-turned-contributor-turned-maintainer, we made really good progress on D2 and are currently on version 2.0.0-alpha.40. All features in Docusaurus 1 except for translations have been ported over.
-D2's killer features are Dark Mode and its superb performance. D2 has dark mode support out-of-the-box and its near effortless to create a dark mode-friendly documentation site. Endilie put in great effort into optimizing the performance of the site and a bunch of performance optimization tricks have been done under the hood by default - optimized images, prerendering every route to static HTML and client-side routing thereafter, prefetching assets needed by future navigations whenever the user hovers over a navigation link, etc.
+D2's killer features are Dark Mode and its superb performance. D2 has dark mode support out-of-the-box and it is near effortless to create a dark mode-friendly documentation site. Endilie put in great effort into optimizing the performance of the site and a bunch of performance optimization tricks have been done under the hood by default - optimized images, prerendering every route to static HTML and client-side routing thereafter, prefetching assets needed by future navigations whenever the user hovers over a navigation link, etc.
Last but not least, we implemented a plugins architecture and turned the repo into a Lerna monorepo. We believe this plugin architecture will be helpful towards building a community and also allowing users to build their own features for their unique use cases.
In 2018, we proposed to rebuild Docusaurus from the ground up. It involved a major rearchitecture effort - we created a content-centric CSS framework from scratch, a plugins system, and moved from static HTML pages to be a single page-app with prerendered routes. It was a wild adventure and a tough feat, especially with no dedicated FTE working on the project. With the help of @endilie, our ex-intern-turned-contributor-turned-maintainer, we made really good progress on D2 and are currently on version 2.0.0-alpha.40. All features in Docusaurus 1 except for translations have been ported over.
-D2's killer features are Dark Mode and its superb performance. D2 has dark mode support out-of-the-box and its near effortless to create a dark mode-friendly documentation site. Endilie put in great effort into optimizing the performance of the site and a bunch of performance optimization tricks have been done under the hood by default - optimized images, prerendering every route to static HTML and client-side routing thereafter, prefetching assets needed by future navigations whenever the user hovers over a navigation link, etc.
+D2's killer features are Dark Mode and its superb performance. D2 has dark mode support out-of-the-box and it is near effortless to create a dark mode-friendly documentation site. Endilie put in great effort into optimizing the performance of the site and a bunch of performance optimization tricks have been done under the hood by default - optimized images, prerendering every route to static HTML and client-side routing thereafter, prefetching assets needed by future navigations whenever the user hovers over a navigation link, etc.
Last but not least, we implemented a plugins architecture and turned the repo into a Lerna monorepo. We believe this plugin architecture will be helpful towards building a community and also allowing users to build their own features for their unique use cases.
Windows
-cmd /C "set "GIT_USER=<GIT_USER>" && set CURRENT_BRANCH=master && set USE_SSH=true && yarn run publish-gh-pages"
+cmd /C "set "GIT_USER=<GIT_USER>"&& set CURRENT_BRANCH=master && set USE_SSH=true && yarn run publish-gh-pages"
There are also two optional parameters that are set as environment variables:
@@ -349,7 +349,7 @@
Alter your siteConfig.js
to add a property 'githubHost'
which represents the GitHub Enterprise hostname. Alternatively, set an environment variable GITHUB_HOST
when executing the publish command.
-Last updated on 2/16/2020 by Ondřej Nepožitek