diff --git a/CHANGELOG-2.x.md b/CHANGELOG-2.x.md index 5c7802f90e..57e2930331 100644 --- a/CHANGELOG-2.x.md +++ b/CHANGELOG-2.x.md @@ -1,5 +1,90 @@ # Docusaurus 2 Changelog +## 2.0.0-alpha.72 (2021-03-16) + +### :boom: Breaking Change + +Starting with this release for a proper work of i18n functionality, you need to either use Node v14+ or in case of using earlier version of Node.js install [`full-icu` package](https://www.npmjs.com/package/full-icu) and set `NODE_ICU_DATA` environment variable in your npm scripts, for example: + +```json +"scripts": { + "start": "cross-env NODE_ICU_DATA=node_modules/full-icu docusaurus start" +} +``` + +#### :rocket: New Feature + +- `docusaurus-init` + - [#4302](https://github.com/facebook/docusaurus/pull/4302) feat(v2): Improve the initial templates ([@ShinteiMai](https://github.com/ShinteiMai)) +- `docusaurus-theme-classic` + - [#4390](https://github.com/facebook/docusaurus/pull/4390) feat(v2): Add korean default translations ([@koko8829](https://github.com/koko8829)) + +#### :bug: Bug Fix + +- `docusaurus-theme-classic` + - [#4429](https://github.com/facebook/docusaurus/pull/4429) chore(v2): upgrade Infima to v0.2.0-alpha.21 ([@lex111](https://github.com/lex111)) + - [#4428](https://github.com/facebook/docusaurus/pull/4428) fix(v2): allow using pre tag in Markdown directly ([@lex111](https://github.com/lex111)) + - [#4381](https://github.com/facebook/docusaurus/pull/4381) fix(v2): specify proper TS path in classic theme ([@lex111](https://github.com/lex111)) + - [#4383](https://github.com/facebook/docusaurus/pull/4383) fix(v2): set theme color mode for SSR ([@lex111](https://github.com/lex111)) +- `docusaurus-plugin-pwa` + - [#4424](https://github.com/facebook/docusaurus/pull/4424) fix(v2): add missing peer dep on @babel/core ([@SimenB](https://github.com/SimenB)) + - [#4377](https://github.com/facebook/docusaurus/pull/4377) fix(v2): PWA issues + improve docs ([@slorber](https://github.com/slorber)) +- `docusaurus` + - [#4407](https://github.com/facebook/docusaurus/pull/4407) fix(v2): broken link checker should not report false positives when using encoded chars ([@Harvtronix](https://github.com/Harvtronix)) +- Other + - [#4410](https://github.com/facebook/docusaurus/pull/4410) fix(v1): Fix v1 site deployment with Crowdin again... ([@slorber](https://github.com/slorber)) + - [#4396](https://github.com/facebook/docusaurus/pull/4396) fix(v1): Temp fix v1 site deployment: fail-safe on Crowdin upload translations error ([@slorber](https://github.com/slorber)) + - [#4395](https://github.com/facebook/docusaurus/pull/4395) fix(v1): fix v1 site deploy issues ([@slorber](https://github.com/slorber)) + +#### :nail_care: Polish + +- `docusaurus-plugin-content-blog`, `docusaurus-plugin-content-docs`, `docusaurus-plugin-content-pages`, `docusaurus-plugin-sitemap`, `docusaurus-theme-classic`, `docusaurus-types`, `docusaurus-utils-validation`, `docusaurus` + - [#4418](https://github.com/facebook/docusaurus/pull/4418) refactor(v2): correct plugin types ([@armano2](https://github.com/armano2)) +- `docusaurus-plugin-content-blog`, `docusaurus-plugin-content-docs`, `docusaurus-theme-common`, `docusaurus-utils`, `docusaurus` + - [#4405](https://github.com/facebook/docusaurus/pull/4405) refactor(v2): i18n cleanups / refactors ([@longlho](https://github.com/longlho)) +- `docusaurus-module-type-aliases` + - [#4387](https://github.com/facebook/docusaurus/pull/4387) refactor(v2): add ExecutionEnvironment, BrowserOnly, isInternalUrl to type aliases ([@armano2](https://github.com/armano2)) +- `docusaurus-plugin-content-blog`, `docusaurus-plugin-content-docs`, `docusaurus-utils` + - [#4402](https://github.com/facebook/docusaurus/pull/4402) refactor(v2): merge linkify function used in blog and docs and align properties ([@armano2](https://github.com/armano2)) +- `docusaurus-plugin-client-redirects`, `docusaurus-plugin-content-docs`, `docusaurus-theme-common`, `docusaurus-utils-validation`, `docusaurus` + - [#4382](https://github.com/facebook/docusaurus/pull/4382) refactor(v2): correct some of type errors reported by eslint ([@armano2](https://github.com/armano2)) +- `docusaurus-theme-bootstrap`, `docusaurus-theme-classic`, `docusaurus-theme-common` + - [#4385](https://github.com/facebook/docusaurus/pull/4385) refactor(v2): add missing theme-classic types ([@armano2](https://github.com/armano2)) + +#### :memo: Documentation + +- [#4416](https://github.com/facebook/docusaurus/pull/4416) docs(v2): add Realtime Web Applications Workshop to showcase ([@lowenhere](https://github.com/lowenhere)) +- [#4408](https://github.com/facebook/docusaurus/pull/4408) docs(v2): add gladysassistant.com to showcase ([@Pierre-Gilles](https://github.com/Pierre-Gilles)) +- [#4386](https://github.com/facebook/docusaurus/pull/4386) docs(v2): Showcase the pnpm docs ([@zkochan](https://github.com/zkochan)) +- [#4367](https://github.com/facebook/docusaurus/pull/4367) docs(v2): releasing i18n blog post ([@slorber](https://github.com/slorber)) + +#### :house: Internal + +- `docusaurus-1.x` + - [#4401](https://github.com/facebook/docusaurus/pull/4401) chore(v1): fix CircleCI v1 site deploy ([@slorber](https://github.com/slorber)) +- Other + - [#4399](https://github.com/facebook/docusaurus/pull/4399) chore(v2): upgrade example projects ([@slorber](https://github.com/slorber)) + - [#4398](https://github.com/facebook/docusaurus/pull/4398) chore(v1): trigger v1 site deploy through CI ([@slorber](https://github.com/slorber)) +- `docusaurus-utils` + - [#4384](https://github.com/facebook/docusaurus/pull/4384) chore(v2): avoid bad publish of intl-locales-supported ([@lex111](https://github.com/lex111)) + +#### Committers: 14 + +- Alexey Pyltsyn ([@lex111](https://github.com/lex111)) +- Armano ([@armano2](https://github.com/armano2)) +- Harvtronix ([@Harvtronix](https://github.com/Harvtronix)) +- Joon-Ha Lee ([@koko8829](https://github.com/koko8829)) +- Leandro Oriente ([@leandrooriente](https://github.com/leandrooriente)) +- Long Ho ([@longlho](https://github.com/longlho)) +- Lowen ([@lowenhere](https://github.com/lowenhere)) +- Pierre-Gilles Leymarie ([@Pierre-Gilles](https://github.com/Pierre-Gilles)) +- Quan ([@quanengineering](https://github.com/quanengineering)) +- Simen Bekkhus ([@SimenB](https://github.com/SimenB)) +- Steven Hansel ([@ShinteiMai](https://github.com/ShinteiMai)) +- Sébastien Lorber ([@slorber](https://github.com/slorber)) +- Zoltan Kochan ([@zkochan](https://github.com/zkochan)) +- [@Rhodanthe1116](https://github.com/Rhodanthe1116) + ## 2.0.0-alpha.71 (2021-03-09) #### :rocket: New Feature diff --git a/lerna.json b/lerna.json index f40a46686e..01c2a67319 100644 --- a/lerna.json +++ b/lerna.json @@ -1,5 +1,5 @@ { - "version": "2.0.0-alpha.71", + "version": "2.0.0-alpha.72", "npmClient": "yarn", "useWorkspaces": true, "changelog": { diff --git a/packages/docusaurus-1.x/package.json b/packages/docusaurus-1.x/package.json index 783fa4c8f7..981b433a6d 100644 --- a/packages/docusaurus-1.x/package.json +++ b/packages/docusaurus-1.x/package.json @@ -1,7 +1,7 @@ { "name": "docusaurus", "description": "Easy to Maintain Open Source Documentation Websites", - "version": "2.0.0-alpha.71", + "version": "2.0.0-alpha.72", "private_comment": "MADE PRIVATE ON PURPOSE! READ V1 PUBLISH GUIDE", "private": true, "license": "MIT", diff --git a/packages/docusaurus-cssnano-preset/package.json b/packages/docusaurus-cssnano-preset/package.json index 36207cb728..f378732120 100644 --- a/packages/docusaurus-cssnano-preset/package.json +++ b/packages/docusaurus-cssnano-preset/package.json @@ -1,6 +1,6 @@ { "name": "@docusaurus/cssnano-preset", - "version": "2.0.0-alpha.71", + "version": "2.0.0-alpha.72", "description": "Advanced cssnano preset for maximum optimization.", "main": "index.js", "license": "MIT", diff --git a/packages/docusaurus-init-1.x/package.json b/packages/docusaurus-init-1.x/package.json index a1412c5192..49d933af5f 100644 --- a/packages/docusaurus-init-1.x/package.json +++ b/packages/docusaurus-init-1.x/package.json @@ -1,7 +1,7 @@ { "name": "docusaurus-init", "description": "Initialization script for Docusaurus", - "version": "2.0.0-alpha.71", + "version": "2.0.0-alpha.72", "private_comment": "MADE PRIVATE ON PURPOSE! READ V1 PUBLISH GUIDE", "private": true, "license": "MIT", diff --git a/packages/docusaurus-init/package.json b/packages/docusaurus-init/package.json index efea0c687a..1071595250 100644 --- a/packages/docusaurus-init/package.json +++ b/packages/docusaurus-init/package.json @@ -1,6 +1,6 @@ { "name": "@docusaurus/init", - "version": "2.0.0-alpha.71", + "version": "2.0.0-alpha.72", "description": "Create Docusaurus apps easily.", "repository": { "type": "git", diff --git a/packages/docusaurus-init/templates/bootstrap/package.json b/packages/docusaurus-init/templates/bootstrap/package.json index 5f6b47ec40..d8e04ee07f 100644 --- a/packages/docusaurus-init/templates/bootstrap/package.json +++ b/packages/docusaurus-init/templates/bootstrap/package.json @@ -1,6 +1,6 @@ { "name": "docusaurus-2-bootstrap-template", - "version": "2.0.0-alpha.71", + "version": "2.0.0-alpha.72", "private": true, "scripts": { "docusaurus": "docusaurus", @@ -14,8 +14,8 @@ "write-heading-ids": "docusaurus write-heading-ids" }, "dependencies": { - "@docusaurus/core": "2.0.0-alpha.71", - "@docusaurus/preset-bootstrap": "2.0.0-alpha.71", + "@docusaurus/core": "2.0.0-alpha.72", + "@docusaurus/preset-bootstrap": "2.0.0-alpha.72", "@mdx-js/react": "^1.5.8", "classnames": "^2.2.6", "react": "^17.0.1", diff --git a/packages/docusaurus-init/templates/classic/package.json b/packages/docusaurus-init/templates/classic/package.json index 32bed133c3..f24250a855 100644 --- a/packages/docusaurus-init/templates/classic/package.json +++ b/packages/docusaurus-init/templates/classic/package.json @@ -1,6 +1,6 @@ { "name": "docusaurus-2-classic-template", - "version": "2.0.0-alpha.71", + "version": "2.0.0-alpha.72", "private": true, "scripts": { "docusaurus": "docusaurus", @@ -14,8 +14,8 @@ "write-heading-ids": "docusaurus write-heading-ids" }, "dependencies": { - "@docusaurus/core": "2.0.0-alpha.71", - "@docusaurus/preset-classic": "2.0.0-alpha.71", + "@docusaurus/core": "2.0.0-alpha.72", + "@docusaurus/preset-classic": "2.0.0-alpha.72", "@mdx-js/react": "^1.6.21", "clsx": "^1.1.1", "react": "^17.0.1", diff --git a/packages/docusaurus-init/templates/facebook/package.json b/packages/docusaurus-init/templates/facebook/package.json index 081ffdf34d..f33dc79d21 100644 --- a/packages/docusaurus-init/templates/facebook/package.json +++ b/packages/docusaurus-init/templates/facebook/package.json @@ -1,6 +1,6 @@ { "name": "docusaurus-2-facebook-template", - "version": "2.0.0-alpha.71", + "version": "2.0.0-alpha.72", "private": true, "scripts": { "docusaurus": "docusaurus", @@ -18,8 +18,8 @@ "prettier:diff": "prettier --config .prettierrc --list-different \"**/*.{js,jsx,ts,tsx,md,mdx}\"" }, "dependencies": { - "@docusaurus/core": "2.0.0-alpha.71", - "@docusaurus/preset-classic": "2.0.0-alpha.71", + "@docusaurus/core": "2.0.0-alpha.72", + "@docusaurus/preset-classic": "2.0.0-alpha.72", "@mdx-js/react": "^1.6.21", "clsx": "^1.1.1", "react": "^17.0.1", diff --git a/packages/docusaurus-mdx-loader/package.json b/packages/docusaurus-mdx-loader/package.json index 2c2936b846..a47bfec783 100644 --- a/packages/docusaurus-mdx-loader/package.json +++ b/packages/docusaurus-mdx-loader/package.json @@ -1,6 +1,6 @@ { "name": "@docusaurus/mdx-loader", - "version": "2.0.0-alpha.71", + "version": "2.0.0-alpha.72", "description": "Docusaurus Loader for MDX", "main": "src/index.js", "publishConfig": { @@ -18,8 +18,8 @@ "dependencies": { "@babel/parser": "^7.12.16", "@babel/traverse": "^7.12.13", - "@docusaurus/core": "2.0.0-alpha.71", - "@docusaurus/utils": "2.0.0-alpha.71", + "@docusaurus/core": "2.0.0-alpha.72", + "@docusaurus/utils": "2.0.0-alpha.72", "@mdx-js/mdx": "^1.6.21", "@mdx-js/react": "^1.6.21", "escape-html": "^1.0.3", @@ -36,7 +36,7 @@ "webpack": "^4.44.1" }, "devDependencies": { - "@docusaurus/types": "2.0.0-alpha.71", + "@docusaurus/types": "2.0.0-alpha.72", "remark": "^12.0.0", "remark-mdx": "^1.6.21", "to-vfile": "^6.0.0", diff --git a/packages/docusaurus-migrate/package.json b/packages/docusaurus-migrate/package.json index a852e214ff..faf2835294 100644 --- a/packages/docusaurus-migrate/package.json +++ b/packages/docusaurus-migrate/package.json @@ -1,6 +1,6 @@ { "name": "@docusaurus/migrate", - "version": "2.0.0-alpha.71", + "version": "2.0.0-alpha.72", "description": "A CLI tool to migrate from older versions of Docusuarus.", "main": "lib/index.js", "license": "MIT", diff --git a/packages/docusaurus-module-type-aliases/package.json b/packages/docusaurus-module-type-aliases/package.json index fbfb3eb234..f2747f6322 100644 --- a/packages/docusaurus-module-type-aliases/package.json +++ b/packages/docusaurus-module-type-aliases/package.json @@ -1,6 +1,6 @@ { "name": "@docusaurus/module-type-aliases", - "version": "2.0.0-alpha.71", + "version": "2.0.0-alpha.72", "description": "Docusaurus module type aliases.", "types": "./src/index.d.ts", "publishConfig": { diff --git a/packages/docusaurus-plugin-client-redirects/package.json b/packages/docusaurus-plugin-client-redirects/package.json index f6173c9832..7f7e5549e5 100644 --- a/packages/docusaurus-plugin-client-redirects/package.json +++ b/packages/docusaurus-plugin-client-redirects/package.json @@ -1,6 +1,6 @@ { "name": "@docusaurus/plugin-client-redirects", - "version": "2.0.0-alpha.71", + "version": "2.0.0-alpha.72", "description": "Client redirects plugin for Docusaurus.", "main": "lib/index.js", "scripts": { @@ -17,10 +17,10 @@ }, "license": "MIT", "dependencies": { - "@docusaurus/core": "2.0.0-alpha.71", - "@docusaurus/types": "2.0.0-alpha.71", - "@docusaurus/utils": "2.0.0-alpha.71", - "@docusaurus/utils-validation": "2.0.0-alpha.71", + "@docusaurus/core": "2.0.0-alpha.72", + "@docusaurus/types": "2.0.0-alpha.72", + "@docusaurus/utils": "2.0.0-alpha.72", + "@docusaurus/utils-validation": "2.0.0-alpha.72", "chalk": "^3.0.0", "eta": "^1.11.0", "fs-extra": "^9.1.0", diff --git a/packages/docusaurus-plugin-content-blog/package.json b/packages/docusaurus-plugin-content-blog/package.json index 43c7a248f8..d7ab91e1da 100644 --- a/packages/docusaurus-plugin-content-blog/package.json +++ b/packages/docusaurus-plugin-content-blog/package.json @@ -1,6 +1,6 @@ { "name": "@docusaurus/plugin-content-blog", - "version": "2.0.0-alpha.71", + "version": "2.0.0-alpha.72", "description": "Blog plugin for Docusaurus.", "main": "lib/index.js", "types": "index.d.ts", @@ -18,11 +18,11 @@ }, "license": "MIT", "dependencies": { - "@docusaurus/core": "2.0.0-alpha.71", - "@docusaurus/mdx-loader": "2.0.0-alpha.71", - "@docusaurus/types": "2.0.0-alpha.71", - "@docusaurus/utils": "2.0.0-alpha.71", - "@docusaurus/utils-validation": "2.0.0-alpha.71", + "@docusaurus/core": "2.0.0-alpha.72", + "@docusaurus/mdx-loader": "2.0.0-alpha.72", + "@docusaurus/types": "2.0.0-alpha.72", + "@docusaurus/utils": "2.0.0-alpha.72", + "@docusaurus/utils-validation": "2.0.0-alpha.72", "chalk": "^4.1.0", "feed": "^4.2.2", "fs-extra": "^9.1.0", diff --git a/packages/docusaurus-plugin-content-docs/package.json b/packages/docusaurus-plugin-content-docs/package.json index 9b1b7c5efd..e08440c82f 100644 --- a/packages/docusaurus-plugin-content-docs/package.json +++ b/packages/docusaurus-plugin-content-docs/package.json @@ -1,6 +1,6 @@ { "name": "@docusaurus/plugin-content-docs", - "version": "2.0.0-alpha.71", + "version": "2.0.0-alpha.72", "description": "Docs plugin for Docusaurus.", "main": "lib/index.js", "types": "src/plugin-content-docs.d.ts", @@ -18,17 +18,17 @@ }, "license": "MIT", "devDependencies": { - "@docusaurus/module-type-aliases": "2.0.0-alpha.71", + "@docusaurus/module-type-aliases": "2.0.0-alpha.72", "@types/picomatch": "^2.2.1", "commander": "^5.1.0", "picomatch": "^2.1.1" }, "dependencies": { - "@docusaurus/core": "2.0.0-alpha.71", - "@docusaurus/mdx-loader": "2.0.0-alpha.71", - "@docusaurus/types": "2.0.0-alpha.71", - "@docusaurus/utils": "2.0.0-alpha.71", - "@docusaurus/utils-validation": "2.0.0-alpha.71", + "@docusaurus/core": "2.0.0-alpha.72", + "@docusaurus/mdx-loader": "2.0.0-alpha.72", + "@docusaurus/types": "2.0.0-alpha.72", + "@docusaurus/utils": "2.0.0-alpha.72", + "@docusaurus/utils-validation": "2.0.0-alpha.72", "chalk": "^4.1.0", "execa": "^5.0.0", "fs-extra": "^9.1.0", diff --git a/packages/docusaurus-plugin-content-pages/package.json b/packages/docusaurus-plugin-content-pages/package.json index 6727de982a..18f8bdf58c 100644 --- a/packages/docusaurus-plugin-content-pages/package.json +++ b/packages/docusaurus-plugin-content-pages/package.json @@ -1,6 +1,6 @@ { "name": "@docusaurus/plugin-content-pages", - "version": "2.0.0-alpha.71", + "version": "2.0.0-alpha.72", "description": "Pages plugin for Docusaurus.", "main": "lib/index.js", "types": "src/plugin-content-pages.d.ts", @@ -18,11 +18,11 @@ }, "license": "MIT", "dependencies": { - "@docusaurus/core": "2.0.0-alpha.71", - "@docusaurus/mdx-loader": "2.0.0-alpha.71", - "@docusaurus/types": "2.0.0-alpha.71", - "@docusaurus/utils": "2.0.0-alpha.71", - "@docusaurus/utils-validation": "2.0.0-alpha.71", + "@docusaurus/core": "2.0.0-alpha.72", + "@docusaurus/mdx-loader": "2.0.0-alpha.72", + "@docusaurus/types": "2.0.0-alpha.72", + "@docusaurus/utils": "2.0.0-alpha.72", + "@docusaurus/utils-validation": "2.0.0-alpha.72", "globby": "^11.0.2", "joi": "^17.4.0", "loader-utils": "^1.2.3", diff --git a/packages/docusaurus-plugin-debug/package.json b/packages/docusaurus-plugin-debug/package.json index 52322ff3a8..3d1ff6d59f 100644 --- a/packages/docusaurus-plugin-debug/package.json +++ b/packages/docusaurus-plugin-debug/package.json @@ -1,6 +1,6 @@ { "name": "@docusaurus/plugin-debug", - "version": "2.0.0-alpha.71", + "version": "2.0.0-alpha.72", "description": "Debug plugin for Docusaurus.", "main": "lib/index.js", "scripts": { @@ -17,9 +17,9 @@ }, "license": "MIT", "dependencies": { - "@docusaurus/core": "2.0.0-alpha.71", - "@docusaurus/types": "2.0.0-alpha.71", - "@docusaurus/utils": "2.0.0-alpha.71", + "@docusaurus/core": "2.0.0-alpha.72", + "@docusaurus/types": "2.0.0-alpha.72", + "@docusaurus/utils": "2.0.0-alpha.72", "react-json-view": "^1.21.1" }, "peerDependencies": { diff --git a/packages/docusaurus-plugin-google-analytics/package.json b/packages/docusaurus-plugin-google-analytics/package.json index d23e9f103d..1116e46140 100644 --- a/packages/docusaurus-plugin-google-analytics/package.json +++ b/packages/docusaurus-plugin-google-analytics/package.json @@ -1,6 +1,6 @@ { "name": "@docusaurus/plugin-google-analytics", - "version": "2.0.0-alpha.71", + "version": "2.0.0-alpha.72", "description": "Global analytics (analytics.js) plugin for Docusaurus.", "main": "src/index.js", "publishConfig": { @@ -13,7 +13,7 @@ }, "license": "MIT", "dependencies": { - "@docusaurus/core": "2.0.0-alpha.71" + "@docusaurus/core": "2.0.0-alpha.72" }, "peerDependencies": { "react": "^16.8.4 || ^17.0.0", diff --git a/packages/docusaurus-plugin-google-gtag/package.json b/packages/docusaurus-plugin-google-gtag/package.json index 263f494585..360ed6a029 100644 --- a/packages/docusaurus-plugin-google-gtag/package.json +++ b/packages/docusaurus-plugin-google-gtag/package.json @@ -1,6 +1,6 @@ { "name": "@docusaurus/plugin-google-gtag", - "version": "2.0.0-alpha.71", + "version": "2.0.0-alpha.72", "description": "Global Site Tag (gtag.js) plugin for Docusaurus.", "main": "src/index.js", "publishConfig": { @@ -13,7 +13,7 @@ }, "license": "MIT", "dependencies": { - "@docusaurus/core": "2.0.0-alpha.71" + "@docusaurus/core": "2.0.0-alpha.72" }, "peerDependencies": { "react": "^16.8.4 || ^17.0.0", diff --git a/packages/docusaurus-plugin-ideal-image/package.json b/packages/docusaurus-plugin-ideal-image/package.json index 9efff025a2..74aafbf1ca 100644 --- a/packages/docusaurus-plugin-ideal-image/package.json +++ b/packages/docusaurus-plugin-ideal-image/package.json @@ -1,6 +1,6 @@ { "name": "@docusaurus/plugin-ideal-image", - "version": "2.0.0-alpha.71", + "version": "2.0.0-alpha.72", "description": "Docusaurus Plugin to generate an almost ideal image (responsive, lazy-loading, and low quality placeholder).", "main": "lib/index.js", "scripts": { @@ -20,9 +20,9 @@ "fs-extra": "^9.1.0" }, "dependencies": { - "@docusaurus/core": "2.0.0-alpha.71", - "@docusaurus/lqip-loader": "2.0.0-alpha.71", - "@docusaurus/types": "2.0.0-alpha.71", + "@docusaurus/core": "2.0.0-alpha.72", + "@docusaurus/lqip-loader": "2.0.0-alpha.72", + "@docusaurus/types": "2.0.0-alpha.72", "@endiliey/react-ideal-image": "^0.0.11", "@endiliey/responsive-loader": "^1.3.2", "react-waypoint": "^9.0.2", diff --git a/packages/docusaurus-plugin-pwa/package.json b/packages/docusaurus-plugin-pwa/package.json index a3be8e724a..acc9400fab 100644 --- a/packages/docusaurus-plugin-pwa/package.json +++ b/packages/docusaurus-plugin-pwa/package.json @@ -1,6 +1,6 @@ { "name": "@docusaurus/plugin-pwa", - "version": "2.0.0-alpha.71", + "version": "2.0.0-alpha.72", "description": "Docusaurus Plugin to add PWA support.", "main": "src/index.js", "publishConfig": { @@ -16,7 +16,7 @@ "@babel/plugin-proposal-nullish-coalescing-operator": "^7.12.13", "@babel/plugin-proposal-optional-chaining": "^7.12.16", "@babel/preset-env": "^7.12.16", - "@docusaurus/core": "2.0.0-alpha.71", + "@docusaurus/core": "2.0.0-alpha.72", "babel-loader": "^8.2.2", "clsx": "^1.1.1", "core-js": "^2.6.5", diff --git a/packages/docusaurus-plugin-sitemap/package.json b/packages/docusaurus-plugin-sitemap/package.json index 5d962f9383..0a228c5fb2 100644 --- a/packages/docusaurus-plugin-sitemap/package.json +++ b/packages/docusaurus-plugin-sitemap/package.json @@ -1,6 +1,6 @@ { "name": "@docusaurus/plugin-sitemap", - "version": "2.0.0-alpha.71", + "version": "2.0.0-alpha.72", "description": "Simple sitemap generation plugin for Docusaurus.", "main": "lib/index.js", "scripts": { @@ -17,9 +17,9 @@ }, "license": "MIT", "dependencies": { - "@docusaurus/core": "2.0.0-alpha.71", - "@docusaurus/types": "2.0.0-alpha.71", - "@docusaurus/utils": "2.0.0-alpha.71", + "@docusaurus/core": "2.0.0-alpha.72", + "@docusaurus/types": "2.0.0-alpha.72", + "@docusaurus/utils": "2.0.0-alpha.72", "fs-extra": "^9.1.0", "joi": "^17.4.0", "sitemap": "^6.3.6" diff --git a/packages/docusaurus-preset-bootstrap/package.json b/packages/docusaurus-preset-bootstrap/package.json index 59c1afe42a..d1a1febea1 100644 --- a/packages/docusaurus-preset-bootstrap/package.json +++ b/packages/docusaurus-preset-bootstrap/package.json @@ -1,6 +1,6 @@ { "name": "@docusaurus/preset-bootstrap", - "version": "2.0.0-alpha.71", + "version": "2.0.0-alpha.72", "description": "Bootstrap preset for Docusaurus.", "main": "src/index.js", "license": "MIT", @@ -13,11 +13,11 @@ "directory": "packages/docusaurus-preset-bootstrap" }, "dependencies": { - "@docusaurus/core": "2.0.0-alpha.71", - "@docusaurus/plugin-content-blog": "2.0.0-alpha.71", - "@docusaurus/plugin-content-docs": "2.0.0-alpha.71", - "@docusaurus/plugin-content-pages": "2.0.0-alpha.71", - "@docusaurus/theme-bootstrap": "2.0.0-alpha.71" + "@docusaurus/core": "2.0.0-alpha.72", + "@docusaurus/plugin-content-blog": "2.0.0-alpha.72", + "@docusaurus/plugin-content-docs": "2.0.0-alpha.72", + "@docusaurus/plugin-content-pages": "2.0.0-alpha.72", + "@docusaurus/theme-bootstrap": "2.0.0-alpha.72" }, "peerDependencies": { "react": "^16.8.4 || ^17.0.0", diff --git a/packages/docusaurus-preset-classic/package.json b/packages/docusaurus-preset-classic/package.json index 102c114c70..75f2fd1def 100644 --- a/packages/docusaurus-preset-classic/package.json +++ b/packages/docusaurus-preset-classic/package.json @@ -1,6 +1,6 @@ { "name": "@docusaurus/preset-classic", - "version": "2.0.0-alpha.71", + "version": "2.0.0-alpha.72", "description": "Classic preset for Docusaurus.", "main": "src/index.js", "publishConfig": { @@ -13,16 +13,16 @@ }, "license": "MIT", "dependencies": { - "@docusaurus/core": "2.0.0-alpha.71", - "@docusaurus/plugin-content-blog": "2.0.0-alpha.71", - "@docusaurus/plugin-content-docs": "2.0.0-alpha.71", - "@docusaurus/plugin-content-pages": "2.0.0-alpha.71", - "@docusaurus/plugin-debug": "2.0.0-alpha.71", - "@docusaurus/plugin-google-analytics": "2.0.0-alpha.71", - "@docusaurus/plugin-google-gtag": "2.0.0-alpha.71", - "@docusaurus/plugin-sitemap": "2.0.0-alpha.71", - "@docusaurus/theme-classic": "2.0.0-alpha.71", - "@docusaurus/theme-search-algolia": "2.0.0-alpha.71" + "@docusaurus/core": "2.0.0-alpha.72", + "@docusaurus/plugin-content-blog": "2.0.0-alpha.72", + "@docusaurus/plugin-content-docs": "2.0.0-alpha.72", + "@docusaurus/plugin-content-pages": "2.0.0-alpha.72", + "@docusaurus/plugin-debug": "2.0.0-alpha.72", + "@docusaurus/plugin-google-analytics": "2.0.0-alpha.72", + "@docusaurus/plugin-google-gtag": "2.0.0-alpha.72", + "@docusaurus/plugin-sitemap": "2.0.0-alpha.72", + "@docusaurus/theme-classic": "2.0.0-alpha.72", + "@docusaurus/theme-search-algolia": "2.0.0-alpha.72" }, "peerDependencies": { "react": "^16.8.4 || ^17.0.0", diff --git a/packages/docusaurus-remark-plugin-npm2yarn/package.json b/packages/docusaurus-remark-plugin-npm2yarn/package.json index 00333ebf2b..e902d3972c 100644 --- a/packages/docusaurus-remark-plugin-npm2yarn/package.json +++ b/packages/docusaurus-remark-plugin-npm2yarn/package.json @@ -1,6 +1,6 @@ { "name": "@docusaurus/remark-plugin-npm2yarn", - "version": "2.0.0-alpha.71", + "version": "2.0.0-alpha.72", "description": "Remark plugin for converting npm commands to Yarn commands as tabs.", "main": "src/index.js", "publishConfig": { diff --git a/packages/docusaurus-theme-bootstrap/package.json b/packages/docusaurus-theme-bootstrap/package.json index 309ab9d93a..d058a85bab 100644 --- a/packages/docusaurus-theme-bootstrap/package.json +++ b/packages/docusaurus-theme-bootstrap/package.json @@ -1,6 +1,6 @@ { "name": "@docusaurus/theme-bootstrap", - "version": "2.0.0-alpha.71", + "version": "2.0.0-alpha.72", "description": "Bootstrap theme for Docusaurus.", "main": "src/index.js", "types": "src/types.d.ts", @@ -14,12 +14,12 @@ "directory": "packages/docusaurus-theme-bootstrap" }, "dependencies": { - "@docusaurus/core": "2.0.0-alpha.71", - "@docusaurus/plugin-content-blog": "2.0.0-alpha.71", - "@docusaurus/plugin-content-docs": "2.0.0-alpha.71", - "@docusaurus/plugin-content-pages": "2.0.0-alpha.71", - "@docusaurus/theme-common": "2.0.0-alpha.71", - "@docusaurus/types": "2.0.0-alpha.71", + "@docusaurus/core": "2.0.0-alpha.72", + "@docusaurus/plugin-content-blog": "2.0.0-alpha.72", + "@docusaurus/plugin-content-docs": "2.0.0-alpha.72", + "@docusaurus/plugin-content-pages": "2.0.0-alpha.72", + "@docusaurus/theme-common": "2.0.0-alpha.72", + "@docusaurus/types": "2.0.0-alpha.72", "@mdx-js/react": "^1.6.21", "bootstrap": "^4.4.1", "classnames": "^2.2.6", @@ -28,7 +28,7 @@ "reactstrap": "^8.4.1" }, "devDependencies": { - "@docusaurus/module-type-aliases": "2.0.0-alpha.71" + "@docusaurus/module-type-aliases": "2.0.0-alpha.72" }, "scripts": { "build": "tsc --noEmit && yarn babel && yarn prettier", diff --git a/packages/docusaurus-theme-classic/package.json b/packages/docusaurus-theme-classic/package.json index b9044920f6..e701095b3a 100644 --- a/packages/docusaurus-theme-classic/package.json +++ b/packages/docusaurus-theme-classic/package.json @@ -1,6 +1,6 @@ { "name": "@docusaurus/theme-classic", - "version": "2.0.0-alpha.71", + "version": "2.0.0-alpha.72", "description": "Classic theme for Docusaurus", "main": "lib/index.js", "types": "src/types.d.ts", @@ -23,14 +23,14 @@ "update-code-translations": "node update-code-translations.js" }, "dependencies": { - "@docusaurus/core": "2.0.0-alpha.71", - "@docusaurus/plugin-content-blog": "2.0.0-alpha.71", - "@docusaurus/plugin-content-docs": "2.0.0-alpha.71", - "@docusaurus/plugin-content-pages": "2.0.0-alpha.71", - "@docusaurus/theme-common": "2.0.0-alpha.71", - "@docusaurus/types": "2.0.0-alpha.71", - "@docusaurus/utils": "2.0.0-alpha.71", - "@docusaurus/utils-validation": "2.0.0-alpha.71", + "@docusaurus/core": "2.0.0-alpha.72", + "@docusaurus/plugin-content-blog": "2.0.0-alpha.72", + "@docusaurus/plugin-content-docs": "2.0.0-alpha.72", + "@docusaurus/plugin-content-pages": "2.0.0-alpha.72", + "@docusaurus/theme-common": "2.0.0-alpha.72", + "@docusaurus/types": "2.0.0-alpha.72", + "@docusaurus/utils": "2.0.0-alpha.72", + "@docusaurus/utils-validation": "2.0.0-alpha.72", "@mdx-js/mdx": "^1.6.21", "@mdx-js/react": "^1.6.21", "@types/react-toggle": "^4.0.2", @@ -52,7 +52,7 @@ "rtlcss": "^2.6.2" }, "devDependencies": { - "@docusaurus/module-type-aliases": "2.0.0-alpha.71" + "@docusaurus/module-type-aliases": "2.0.0-alpha.72" }, "peerDependencies": { "react": "^16.8.4 || ^17.0.0", diff --git a/packages/docusaurus-theme-common/package.json b/packages/docusaurus-theme-common/package.json index d81d052bed..4f367d1ea3 100644 --- a/packages/docusaurus-theme-common/package.json +++ b/packages/docusaurus-theme-common/package.json @@ -1,6 +1,6 @@ { "name": "@docusaurus/theme-common", - "version": "2.0.0-alpha.71", + "version": "2.0.0-alpha.72", "description": "Common code for Docusaurus themes.", "main": "./lib/index.js", "types": "./lib/index.d.ts", @@ -18,14 +18,14 @@ }, "license": "MIT", "dependencies": { - "@docusaurus/core": "2.0.0-alpha.71", - "@docusaurus/plugin-content-blog": "2.0.0-alpha.71", - "@docusaurus/plugin-content-docs": "2.0.0-alpha.71", - "@docusaurus/plugin-content-pages": "2.0.0-alpha.71", - "@docusaurus/types": "2.0.0-alpha.71" + "@docusaurus/core": "2.0.0-alpha.72", + "@docusaurus/plugin-content-blog": "2.0.0-alpha.72", + "@docusaurus/plugin-content-docs": "2.0.0-alpha.72", + "@docusaurus/plugin-content-pages": "2.0.0-alpha.72", + "@docusaurus/types": "2.0.0-alpha.72" }, "devDependencies": { - "@docusaurus/module-type-aliases": "2.0.0-alpha.71" + "@docusaurus/module-type-aliases": "2.0.0-alpha.72" }, "peerDependencies": { "react": "^16.8.4 || ^17.0.0", diff --git a/packages/docusaurus-theme-live-codeblock/package.json b/packages/docusaurus-theme-live-codeblock/package.json index dad1d80ea1..58156b72b3 100644 --- a/packages/docusaurus-theme-live-codeblock/package.json +++ b/packages/docusaurus-theme-live-codeblock/package.json @@ -1,6 +1,6 @@ { "name": "@docusaurus/theme-live-codeblock", - "version": "2.0.0-alpha.71", + "version": "2.0.0-alpha.72", "description": "Docusaurus live code block component.", "main": "src/index.js", "publishConfig": { @@ -13,7 +13,7 @@ }, "license": "MIT", "dependencies": { - "@docusaurus/core": "2.0.0-alpha.71", + "@docusaurus/core": "2.0.0-alpha.72", "@philpl/buble": "^0.19.7", "clsx": "^1.1.1", "joi": "^17.4.0", diff --git a/packages/docusaurus-theme-search-algolia/package.json b/packages/docusaurus-theme-search-algolia/package.json index 82225d0204..d30bad456a 100644 --- a/packages/docusaurus-theme-search-algolia/package.json +++ b/packages/docusaurus-theme-search-algolia/package.json @@ -1,6 +1,6 @@ { "name": "@docusaurus/theme-search-algolia", - "version": "2.0.0-alpha.71", + "version": "2.0.0-alpha.72", "description": "Algolia search component for Docusaurus.", "main": "src/index.js", "publishConfig": { @@ -14,9 +14,9 @@ "license": "MIT", "dependencies": { "@docsearch/react": "^3.0.0-alpha.33", - "@docusaurus/core": "2.0.0-alpha.71", - "@docusaurus/theme-common": "2.0.0-alpha.71", - "@docusaurus/utils": "2.0.0-alpha.71", + "@docusaurus/core": "2.0.0-alpha.72", + "@docusaurus/theme-common": "2.0.0-alpha.72", + "@docusaurus/utils": "2.0.0-alpha.72", "algoliasearch": "^4.8.4", "algoliasearch-helper": "^3.3.4", "clsx": "^1.1.1", diff --git a/packages/docusaurus-types/package.json b/packages/docusaurus-types/package.json index dc89794747..f7c080c18c 100644 --- a/packages/docusaurus-types/package.json +++ b/packages/docusaurus-types/package.json @@ -1,6 +1,6 @@ { "name": "@docusaurus/types", - "version": "2.0.0-alpha.71", + "version": "2.0.0-alpha.72", "description": "Common types for Docusaurus packages.", "main": "./src/index.js", "types": "./src/index.d.ts", @@ -16,8 +16,8 @@ "dependencies": { "@types/webpack": "^4.41.0", "commander": "^5.1.0", + "joi": "^17.4.0", "querystring": "0.2.0", - "webpack-merge": "^4.2.2", - "joi": "^17.4.0" + "webpack-merge": "^4.2.2" } } diff --git a/packages/docusaurus-utils-validation/package.json b/packages/docusaurus-utils-validation/package.json index 1db3c4086e..2425a98060 100644 --- a/packages/docusaurus-utils-validation/package.json +++ b/packages/docusaurus-utils-validation/package.json @@ -1,6 +1,6 @@ { "name": "@docusaurus/utils-validation", - "version": "2.0.0-alpha.71", + "version": "2.0.0-alpha.72", "description": "Node validation utility functions for Docusaurus packages.", "main": "./lib/index.js", "types": "./lib/index.d.ts", @@ -18,7 +18,7 @@ }, "license": "MIT", "dependencies": { - "@docusaurus/utils": "2.0.0-alpha.71", + "@docusaurus/utils": "2.0.0-alpha.72", "chalk": "^4.1.0", "joi": "^17.4.0" }, diff --git a/packages/docusaurus-utils/package.json b/packages/docusaurus-utils/package.json index aff834b9e5..203da806e8 100644 --- a/packages/docusaurus-utils/package.json +++ b/packages/docusaurus-utils/package.json @@ -1,6 +1,6 @@ { "name": "@docusaurus/utils", - "version": "2.0.0-alpha.71", + "version": "2.0.0-alpha.72", "description": "Node utility functions for Docusaurus packages.", "main": "./lib/index.js", "types": "./lib/index.d.ts", @@ -18,7 +18,7 @@ }, "license": "MIT", "dependencies": { - "@docusaurus/types": "2.0.0-alpha.71", + "@docusaurus/types": "2.0.0-alpha.72", "@types/github-slugger": "^1.3.0", "chalk": "^4.1.0", "escape-string-regexp": "^4.0.0", diff --git a/packages/docusaurus/package.json b/packages/docusaurus/package.json index df75799681..9b66fa88a9 100644 --- a/packages/docusaurus/package.json +++ b/packages/docusaurus/package.json @@ -1,7 +1,7 @@ { "name": "@docusaurus/core", "description": "Easy to Maintain Open Source Documentation Websites", - "version": "2.0.0-alpha.71", + "version": "2.0.0-alpha.72", "license": "MIT", "publishConfig": { "access": "public" @@ -31,7 +31,7 @@ "url": "https://github.com/facebook/docusaurus/issues" }, "devDependencies": { - "@docusaurus/module-type-aliases": "2.0.0-alpha.71", + "@docusaurus/module-type-aliases": "2.0.0-alpha.72", "@types/detect-port": "^1.3.0", "@types/nprogress": "^0.2.0", "tmp-promise": "^3.0.2" @@ -49,11 +49,11 @@ "@babel/runtime": "^7.12.5", "@babel/runtime-corejs3": "^7.12.13", "@babel/traverse": "^7.12.13", - "@docusaurus/cssnano-preset": "2.0.0-alpha.71", + "@docusaurus/cssnano-preset": "2.0.0-alpha.72", "@docusaurus/react-loadable": "5.5.0", - "@docusaurus/types": "2.0.0-alpha.71", - "@docusaurus/utils": "2.0.0-alpha.71", - "@docusaurus/utils-validation": "2.0.0-alpha.71", + "@docusaurus/types": "2.0.0-alpha.72", + "@docusaurus/utils": "2.0.0-alpha.72", + "@docusaurus/utils-validation": "2.0.0-alpha.72", "@endiliey/static-site-generator-webpack-plugin": "^4.0.0", "@svgr/webpack": "^5.5.0", "autoprefixer": "^10.2.5", diff --git a/packages/lqip-loader/package.json b/packages/lqip-loader/package.json index a851bf512c..73d85c078f 100644 --- a/packages/lqip-loader/package.json +++ b/packages/lqip-loader/package.json @@ -1,6 +1,6 @@ { "name": "@docusaurus/lqip-loader", - "version": "2.0.0-alpha.71", + "version": "2.0.0-alpha.72", "description": "Low Quality Image Placeholders (LQIP) loader for webpack.", "main": "src/index.js", "publishConfig": { diff --git a/packages/stylelint-copyright/package.json b/packages/stylelint-copyright/package.json index c9ecec8e80..83136bc5fd 100644 --- a/packages/stylelint-copyright/package.json +++ b/packages/stylelint-copyright/package.json @@ -1,6 +1,6 @@ { "name": "stylelint-copyright", - "version": "2.0.0-alpha.71", + "version": "2.0.0-alpha.72", "description": "Stylelint plugin to check CSS files for a copyright header.", "main": "index.js", "license": "MIT", diff --git a/website-1.x/package.json b/website-1.x/package.json index 047c6658af..199840af26 100644 --- a/website-1.x/package.json +++ b/website-1.x/package.json @@ -1,6 +1,6 @@ { "name": "docusaurus-1-website", - "version": "2.0.0-alpha.71", + "version": "2.0.0-alpha.72", "private": true, "scripts": { "start": "docusaurus-start", @@ -15,6 +15,6 @@ "netlify:build": "yarn crowdin-download && yarn build" }, "dependencies": { - "docusaurus": "2.0.0-alpha.71" + "docusaurus": "2.0.0-alpha.72" } } diff --git a/website/package.json b/website/package.json index 2779640521..1f0092ced8 100644 --- a/website/package.json +++ b/website/package.json @@ -1,6 +1,6 @@ { "name": "docusaurus-2-website", - "version": "2.0.0-alpha.71", + "version": "2.0.0-alpha.72", "private": true, "scripts": { "docusaurus": "docusaurus", @@ -31,13 +31,13 @@ }, "dependencies": { "@crowdin/cli": "^3.5.2", - "@docusaurus/core": "2.0.0-alpha.71", - "@docusaurus/plugin-client-redirects": "2.0.0-alpha.71", - "@docusaurus/plugin-ideal-image": "2.0.0-alpha.71", - "@docusaurus/plugin-pwa": "2.0.0-alpha.71", - "@docusaurus/preset-classic": "2.0.0-alpha.71", - "@docusaurus/remark-plugin-npm2yarn": "2.0.0-alpha.71", - "@docusaurus/theme-live-codeblock": "2.0.0-alpha.71", + "@docusaurus/core": "2.0.0-alpha.72", + "@docusaurus/plugin-client-redirects": "2.0.0-alpha.72", + "@docusaurus/plugin-ideal-image": "2.0.0-alpha.72", + "@docusaurus/plugin-pwa": "2.0.0-alpha.72", + "@docusaurus/preset-classic": "2.0.0-alpha.72", + "@docusaurus/remark-plugin-npm2yarn": "2.0.0-alpha.72", + "@docusaurus/theme-live-codeblock": "2.0.0-alpha.72", "clsx": "^1.1.1", "color": "^3.1.3", "npm-to-yarn": "^1.0.0-2", diff --git a/website/versioned_docs/version-2.0.0-alpha.72/api/docusaurus.config.js.md b/website/versioned_docs/version-2.0.0-alpha.72/api/docusaurus.config.js.md new file mode 100644 index 0000000000..fcdc89450b --- /dev/null +++ b/website/versioned_docs/version-2.0.0-alpha.72/api/docusaurus.config.js.md @@ -0,0 +1,477 @@ +--- +id: docusaurus.config.js +title: docusaurus.config.js +description: API reference for Docusaurus configuration file. +slug: /docusaurus.config.js +--- + +## Overview + +`docusaurus.config.js` contains configurations for your site and is placed in the root directory of your site. + +## Required fields + +### `title` + +- Type: `string` + +Title for your website. + +```js title="docusaurus.config.js" +module.exports = { + title: 'Docusaurus', +}; +``` + +### `favicon` + +- Type: `string` + +URL for site favicon. Example: + +```js title="docusaurus.config.js" +module.exports = { + favicon: 'https://v2.docusaurus.io/favicon.ico', +}; +``` + +You can also use the favicon URL relative to the `static` directory of your site. For example, your site has the following directory structure: + +```bash +. +├── README.md +├ # ... other files in root directory +└─ static + └── img + └── favicon.ico +``` + +So you can refer it like below: + +```js title="docusaurus.config.js" +module.exports = { + favicon: 'img/favicon.ico', +}; +``` + +### `url` + +- Type: `string` + +URL for your website. This can also be considered the top-level hostname. For example, `https://facebook.github.io` is the URL of https://facebook.github.io/metro/, and `https://docusaurus.io` is the URL for https://docusaurus.io. This field is related to the [baseUrl](#baseurl) field. + +```js title="docusaurus.config.js" +module.exports = { + url: 'https://docusaurus.io', +}; +``` + +### `baseUrl` + +- Type: `string` + +Base URL for your site. This can also be considered the path after the host. For example, `/metro/` is the baseUrl of https://facebook.github.io/metro/. For URLs that have no path, the baseUrl should be set to `/`. This field is related to the [url](#url) field. + +```js title="docusaurus.config.js" +module.exports = { + baseUrl: '/', +}; +``` + +## Optional fields + +### `i18n` + +- Type: `Object` + +The i18n configuration object to [localize your site](../i18n/i18n-introduction.md). + +Example: + +```js title="docusaurus.config.js" +module.exports = { + i18n: { + defaultLocale: 'en', + locales: ['en', 'fr'], + localeConfigs: { + en: { + label: 'English', + direction: 'ltr', + }, + fr: { + label: 'Français', + direction: 'ltr', + }, + }, + }, +}; +``` + +- `label`: the label to use for this locale +- `direction`: `ltr` (default) or `rtl` (for [right-to-left languages](https://developer.mozilla.org/en-US/docs/Glossary/rtl) like Araric, Hebrew, etc.) + +### `noIndex` + +- Type: `boolean` + +This option adds `` in pages, to tell search engines to avoid indexing your site (more information [here](https://moz.com/learn/seo/robots-meta-directives)). + +Example: + +```js title="docusaurus.config.js" +module.exports = { + noIndex: true, // Defaults to `false` +}; +``` + +### `onBrokenLinks` + +- Type: `'ignore' | 'log' | 'warn' | 'error' | 'throw'` + +The behavior of Docusaurus, when it detects any broken link. + +By default, it throws an error, to ensure you never ship any broken link, but you can lower this security if needed. + +:::note + +The broken links detection is only available for a production build (`docusaurus build`). + +::: + +### `onBrokenMarkdownLinks` + +- Type: `'ignore' | 'log' | 'warn' | 'error' | 'throw'` + +The behavior of Docusaurus, when it detects any broken markdown link. + +By default, it prints a warning, to let you know about your broken markdown link, but you can change this security if needed. + +### `onDuplicateRoutes` + +- Type: `'ignore' | 'log' | 'warn' | 'error' | 'throw'` + +The behavior of Docusaurus when it detects any [duplicate routes](/guides/creating-pages.md#duplicate-routes). + +By default, it displays a warning after you run `yarn start` or `yarn build`. + +### `tagline` + +- Type: `string` + +The tagline for your website. + +```js title="docusaurus.config.js" +module.exports = { + tagline: + 'Docusaurus makes it easy to maintain Open Source documentation websites.', +}; +``` + +### `organizationName` + +- Type: `string` + +The GitHub user or organization that owns the repository. Used by the deployment command. + +```js title="docusaurus.config.js" +module.exports = { + // Docusaurus' organization is facebook + organizationName: 'facebook', +}; +``` + +### `projectName` + +- Type: `string` + +The name of the GitHub repository. Used by the deployment command. + +```js title="docusaurus.config.js" +module.exports = { + projectName: 'docusaurus', +}; +``` + +### `githubHost` + +- Type: `string` + +The hostname of your server. Useful if you are using GitHub Enterprise. + +```js title="docusaurus.config.js" +module.exports = { + githubHost: 'github.com', +}; +``` + +### `themeConfig` + +- Type: `Object` + +The [theme configuration](./themes/theme-configuration.md) object, to customize your site UI like navbar, footer. + +Example: + +```js title="docusaurus.config.js" +module.exports = { + themeConfig: { + hideableSidebar: false, + colorMode: { + defaultMode: 'light', + disableSwitch: false, + respectPrefersColorScheme: true, + switchConfig: { + darkIcon: '🌙', + lightIcon: '\u2600', + // React inline style object + // see https://reactjs.org/docs/dom-elements.html#style + darkIconStyle: { + marginLeft: '2px', + }, + lightIconStyle: { + marginLeft: '1px', + }, + }, + }, + navbar: { + title: 'Site Title', + logo: { + alt: 'Site Logo', + src: 'img/logo.svg', + }, + items: [ + { + to: 'docs/docusaurus.config.js', + activeBasePath: 'docs', + label: 'docusaurus.config.js', + position: 'left', + }, + // ... other links + ], + }, + footer: { + style: 'dark', + links: [ + { + title: 'Docs', + items: [ + { + label: 'Docs', + to: 'docs/doc1', + }, + ], + }, + // ... other links + ], + logo: { + alt: 'Facebook Open Source Logo', + src: 'https://docusaurus.io/img/oss_logo.png', + }, + copyright: `Copyright © ${new Date().getFullYear()} Facebook, Inc.`, // You can also put own HTML here + }, + }, +}; +``` + +### `plugins` + + + +- Type: `any[]` + +```js title="docusaurus.config.js" +module.exports = { + plugins: [], +}; +``` + +### `themes` + + + +- Type: `any[]` + +```js title="docusaurus.config.js" +module.exports = { + themes: [], +}; +``` + +### `presets` + + + +- Type: `any[]` + +```js title="docusaurus.config.js" +module.exports = { + presets: [], +}; +``` + +### `customFields` + +Docusaurus guards `docusaurus.config.js` from unknown fields. To add a custom field, define it on `customFields`. + +- Type: `Object` + +```js title="docusaurus.config.js" +module.exports = { + customFields: { + admin: 'endi', + superman: 'lol', + }, +}; +``` + +Attempting to add unknown field in the config will lead to error in build time: + +```bash +Error: The field(s) 'foo', 'bar' are not recognized in docusaurus.config.js +``` + +### `scripts` + +An array of scripts to load. The values can be either strings or plain objects of attribute-value maps. The ` + <% }); %> + <%~ it.postBodyTags %> + + +}; +``` + +### `stylesheets` + +An array of CSS sources to load. The values can be either strings or plain objects of attribute-value maps. The `` tags will be inserted in the HTML ``. + +- Type: `(string | Object)[]` + +Example: + +```js title="docusaurus.config.js" +module.exports = { + stylesheets: [ + // String format. + 'https://docusaurus.io/style.css', + // Object format. + { + href: 'http://mydomain.com/style.css', + type: 'text/css', + }, + ], +}; +``` + +### `titleDelimiter` + +- Type: `string` + +A string that will be used as title delimiter in the generated `` tag. + +Example: + +```js title="docusaurus.config.js" +module.exports = { + titleDelimiter: '🦖', // Defaults to `|` +}; +``` + +### `baseUrlIssueBanner` + +- Type: `boolean` + +When enabled, will show a banner in case your site can't load its CSS or JavaScript files, which is a very common issue, often related to a wrong `baseUrl` in site config. + +Example: + +```js title="docusaurus.config.js" +module.exports = { + baseUrlIssueBanner: true, // Defaults to `true` +}; +``` + +![baseUrlIssueBanner](/img/baseUrlIssueBanner.png) + +:::caution + +This banner need to inline CSS / JS. + +If you have a strict [Content Security Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP), you should rather disable it. + +::: diff --git a/website/versioned_docs/version-2.0.0-alpha.72/api/plugins/overview.md b/website/versioned_docs/version-2.0.0-alpha.72/api/plugins/overview.md new file mode 100644 index 0000000000..b9ddd805b5 --- /dev/null +++ b/website/versioned_docs/version-2.0.0-alpha.72/api/plugins/overview.md @@ -0,0 +1,28 @@ +--- +id: plugins-overview +title: 'Docusaurus plugins' +sidebar_label: Plugins overview +slug: '/api/plugins' +--- + +We provide official Docusaurus plugins. + +## Content plugins + +These plugins are responsible to load your site's content, and create pages for your theme to render. + +- [@docusaurus/plugin-content-docs](./plugin-content-docs.md) +- [@docusaurus/plugin-content-blog](./plugin-content-blog.md) +- [@docusaurus/plugin-content-pages](./plugin-content-pages.md) + +## Behavior plugins + +These plugins will add a useful behavior to your Docusaurus site. + +- [@docusaurus/plugin-debug](./plugin-debug.md) +- [@docusaurus/plugin-sitemap](./plugin-sitemap.md) +- [@docusaurus/plugin-pwa](./plugin-pwa.md) +- [@docusaurus/plugin-client-redirects](./plugin-client-redirects.md) +- [@docusaurus/plugin-ideal-image](./plugin-ideal-image.md) +- [@docusaurus/plugin-google-analytics](./plugin-google-analytics.md) +- [@docusaurus/plugin-google-gtag](./plugin-google-gtag.md) diff --git a/website/versioned_docs/version-2.0.0-alpha.72/api/plugins/plugin-client-redirects.md b/website/versioned_docs/version-2.0.0-alpha.72/api/plugins/plugin-client-redirects.md new file mode 100644 index 0000000000..513ef09ba8 --- /dev/null +++ b/website/versioned_docs/version-2.0.0-alpha.72/api/plugins/plugin-client-redirects.md @@ -0,0 +1,129 @@ +--- +id: plugin-client-redirects +title: '📦 plugin-client-redirects' +slug: '/api/plugins/@docusaurus/plugin-client-redirects' +--- + +Docusaurus Plugin to generate **client-side redirects**. + +This plugin will write additional HTML pages to your static site, that redirects the user to your existing Docusaurus pages with JavaScript. + +:::note + +This plugin only create redirects for the production build. + +::: + +:::caution + +It is better to use server-side redirects whenever possible. + +Before using this plugin, you should look if your hosting provider doesn't offer this feature. + +::: + +## Installation + +```bash npm2yarn +npm install --save @docusaurus/plugin-client-redirects +``` + +## Configuration + +Main usecase: you have `/myDocusaurusPage`, and you want to redirect to this page from `/myDocusaurusPage.html`: + +```js title="docusaurus.config.js" +module.exports = { + plugins: [ + [ + '@docusaurus/plugin-client-redirects', + { + fromExtensions: ['html'], + }, + ], + ], +}; +``` + +Second usecase: you have `/myDocusaurusPage.html`, and you want to redirect to this page from `/myDocusaurusPage`. + +```js title="docusaurus.config.js" +module.exports = { + plugins: [ + [ + '@docusaurus/plugin-client-redirects', + { + toExtensions: ['html'], + }, + ], + ], +}; +``` + +For custom redirect logic, provide your own `createRedirects` function. + +Let's imagine you change the url of an existing page, you might want to make sure the old url still works: + +```js title="docusaurus.config.js" +module.exports = { + plugins: [ + [ + '@docusaurus/plugin-client-redirects', + { + redirects: [ + { + to: '/docs/newDocPath', // string + from: ['/docs/oldDocPathFrom2019', '/docs/legacyDocPathFrom2016'], // string | string[] + }, + ], + }, + ], + ], +}; +``` + +It's possible to use a function to create the redirects for each existing path: + +```js title="docusaurus.config.js" +module.exports = { + plugins: [ + [ + '@docusaurus/plugin-client-redirects', + { + createRedirects: function (existingPath) { + if (existingPath === '/docs/newDocPath') { + return ['/docs/oldDocPathFrom2019', '/docs/legacyDocPathFrom2016']; // string | string[] + } + }, + }, + ], + ], +}; +``` + +Finally, it's possible to use all options at the same time: + +```js title="docusaurus.config.js" +module.exports = { + plugins: [ + [ + '@docusaurus/plugin-client-redirects', + { + fromExtensions: ['html', 'htm'], + toExtensions: ['exe', 'zip'], + redirects: [ + { + to: '/docs/newDocPath', + from: '/docs/oldDocPath', + }, + ], + createRedirects: function (existingPath) { + if (existingPath === '/docs/newDocPath2') { + return ['/docs/oldDocPath2']; + } + }, + }, + ], + ], +}; +``` diff --git a/website/versioned_docs/version-2.0.0-alpha.72/api/plugins/plugin-content-blog.md b/website/versioned_docs/version-2.0.0-alpha.72/api/plugins/plugin-content-blog.md new file mode 100644 index 0000000000..a320a91f3b --- /dev/null +++ b/website/versioned_docs/version-2.0.0-alpha.72/api/plugins/plugin-content-blog.md @@ -0,0 +1,140 @@ +--- +id: plugin-content-blog +title: '📦 plugin-content-blog' +slug: '/api/plugins/@docusaurus/plugin-content-blog' +--- + +Provides the [Blog](blog.md) feature and is the default blog plugin for Docusaurus. + +## Installation + +```bash npm2yarn +npm install --save @docusaurus/plugin-content-blog +``` + +:::tip + +If you have installed `@docusaurus/preset-classic`, you don't need to install it as a dependency. You can also configure it through the [classic preset options](presets.md#docusauruspreset-classic) instead of doing it like below. + +::: + +## Configuration + +```js title="docusaurus.config.js" +module.exports = { + plugins: [ + [ + '@docusaurus/plugin-content-blog', + { + /** + * Path to data on filesystem relative to site dir. + */ + path: 'blog', + /** + * Base url to edit your site. + * Docusaurus will compute the final editUrl with "editUrl + relativeDocPath" + */ + editUrl: 'https://github.com/facebook/docusaurus/edit/master/website/', + /** + * For advanced cases, compute the edit url for each markdown file yourself. + */ + editUrl: ({locale, blogDirPath, blogPath, permalink}) => { + return `https://github.com/facebook/docusaurus/edit/master/website/${blogDirPath}/${blogPath}`; + }, + /** + * Useful if you commit localized files to git. + * When markdown files are localized, the edit url will target the localized file, + * instead of the original unlocalized file. + * Note: this option is ignored when editUrl is a function + */ + editLocalizedFiles: false, + /** + * Blog page title for better SEO + */ + blogTitle: 'Blog title', + /** + * Blog page meta description for better SEO + */ + blogDescription: 'Blog', + /** + * Number of blog post elements to show in the blog sidebar + * 'ALL' to show all blog posts + * 0 to disable + */ + blogSidebarCount: 5, + /** + * Title of the blog sidebar + */ + blogSidebarTitle: 'All our posts', + /** + * URL route for the blog section of your site. + * *DO NOT* include a trailing slash. + */ + routeBasePath: 'blog', + include: ['*.md', '*.mdx'], + postsPerPage: 10, + /** + * Theme components used by the blog pages. + */ + blogListComponent: '@theme/BlogListPage', + blogPostComponent: '@theme/BlogPostPage', + blogTagsListComponent: '@theme/BlogTagsListPage', + blogTagsPostsComponent: '@theme/BlogTagsPostsPage', + /** + * Remark and Rehype plugins passed to MDX. + */ + remarkPlugins: [ + /* require('remark-math') */ + ], + rehypePlugins: [], + /** + * Custom Remark and Rehype plugins passed to MDX before + * the default Docusaurus Remark and Rehype plugins. + */ + beforeDefaultRemarkPlugins: [], + beforeDefaultRehypePlugins: [], + /** + * Truncate marker, can be a regex or string. + */ + truncateMarker: /<!--\s*(truncate)\s*-->/, + /** + * Show estimated reading time for the blog post. + */ + showReadingTime: true, + /** + * Blog feed. + * If feedOptions is undefined, no rss feed will be generated. + */ + feedOptions: { + type: '', // required. 'rss' | 'feed' | 'all' + title: '', // default to siteConfig.title + description: '', // default to `${siteConfig.title} Blog` + copyright: '', + language: undefined, // possible values: http://www.w3.org/TR/REC-html40/struct/dirlang.html#langcodes + }, + }, + ], + ], +}; +``` + +## i18n + +Read the [i18n introduction](../../i18n/i18n-introduction.md) first. + +### Translation files location + +- **Base path**: `website/i18n/<locale>/docusaurus-plugin-content-blog` +- **Multi-instance path**: `website/i18n/<locale>/docusaurus-plugin-content-blog-<pluginId>` +- **JSON files**: N/A +- **Markdown files**: `website/i18n/<locale>/docusaurus-plugin-content-blog` + +### Example file-system structure + +```bash +website/i18n/<locale>/docusaurus-plugin-content-blog +│ +│ # translations for website/blog +├── first-blog-post.md +└── second-blog-post.md +``` diff --git a/website/versioned_docs/version-2.0.0-alpha.72/api/plugins/plugin-content-docs.md b/website/versioned_docs/version-2.0.0-alpha.72/api/plugins/plugin-content-docs.md new file mode 100644 index 0000000000..e3f4f2b9ff --- /dev/null +++ b/website/versioned_docs/version-2.0.0-alpha.72/api/plugins/plugin-content-docs.md @@ -0,0 +1,215 @@ +--- +id: plugin-content-docs +title: '📦 plugin-content-docs' +slug: '/api/plugins/@docusaurus/plugin-content-docs' +--- + +Provides the [Docs](../../guides/docs/docs-introduction.md) functionality and is the default docs plugin for Docusaurus. + +## Installation + +```bash npm2yarn +npm install --save @docusaurus/plugin-content-docs +``` + +:::tip + +If you have installed `@docusaurus/preset-classic`, you don't need to install it as a dependency. You can also configure it through the [classic preset options](presets.md#docusauruspreset-classic) instead of doing it like below. + +::: + +## Configuration + +```js title="docusaurus.config.js" +module.exports = { + plugins: [ + [ + '@docusaurus/plugin-content-docs', + { + /** + * Path to data on filesystem relative to site dir. + */ + path: 'docs', + /** + * Base url to edit your site. + * Docusaurus will compute the final editUrl with "editUrl + relativeDocPath" + */ + editUrl: 'https://github.com/facebook/docusaurus/edit/master/website/', + /** + * For advanced cases, compute the edit url for each markdown file yourself. + */ + editUrl: function ({ + locale, + version, + versionDocsDirPath, + docPath, + permalink, + }) { + return `https://github.com/facebook/docusaurus/edit/master/website/${versionDocsDirPath}/${docPath}`; + }, + /** + * Useful if you commit localized files to git. + * When markdown files are localized, the edit url will target the localized file, + * instead of the original unlocalized file. + * Note: this option is ignored when editUrl is a function + */ + editLocalizedFiles: false, + /** + * Useful if you don't want users to submit doc pull-requests to older versions. + * When docs are versioned, the edit url will link to the doc + * in current version, instead of the versioned doc. + * Note: this option is ignored when editUrl is a function + */ + editCurrentVersion: false, + /** + * URL route for the docs section of your site. + * *DO NOT* include a trailing slash. + * INFO: It is possible to set just `/` for shipping docs without base path. + */ + routeBasePath: 'docs', + include: ['**/*.md', '**/*.mdx'], // Extensions to include. + /** + * Path to sidebar configuration for showing a list of markdown pages. + * Warning: will change + */ + sidebarPath: '', + /** + * Theme components used by the docs pages + */ + docLayoutComponent: '@theme/DocPage', + docItemComponent: '@theme/DocItem', + /** + * Remark and Rehype plugins passed to MDX + */ + remarkPlugins: [ + /* require('remark-math') */ + ], + rehypePlugins: [], + /** + * Custom Remark and Rehype plugins passed to MDX before + * the default Docusaurus Remark and Rehype plugins. + */ + beforeDefaultRemarkPlugins: [], + beforeDefaultRehypePlugins: [], + /** + * Whether to display the author who last updated the doc. + */ + showLastUpdateAuthor: false, + /** + * Whether to display the last date the doc was updated. + */ + showLastUpdateTime: false, + /** + * By default, versioning is enabled on versioned sites. + * This is a way to explicitly disable the versioning feature. + */ + disableVersioning: false, + /** + * Skip the next release docs when versioning is enabled. + * This will not generate HTML files in the production build for documents + * in `/docs/next` directory, only versioned docs. + */ + excludeNextVersionDocs: false, + /** + * The last version is the one we navigate to in priority on versioned sites + * It is the one displayed by default in docs navbar items + * By default, the last version is the first one to appear in versions.json + * By default, the last version is at the "root" (docs have path=/docs/myDoc) + * Note: it is possible to configure the path and label of the last version + * Tip: using lastVersion: 'current' make sense in many cases + */ + lastVersion: undefined, + /** + * The docusaurus versioning defaults don't make sense for all projects + * This gives the ability customize the label and path of each version + * You may not like that default version + */ + versions: { + /* + Example configuration: + current: { + label: 'Android SDK v2.0.0 (WIP)', + path: 'android-2.0.0', + }, + '1.0.0': { + label: 'Android SDK v1.0.0', + path: 'android-1.0.0', + }, + */ + }, + /** + * Sometimes you only want to include a subset of all available versions. + * Tip: limit to 2 or 3 versions to improve startup and build time in dev and deploy previews + */ + onlyIncludeVersions: undefined, // ex: ["current", "1.0.0", "2.0.0"] + }, + ], + ], +}; +``` + +## Markdown Frontmatter + +Markdown documents can use the following markdown frontmatter metadata fields, enclosed by a line `---` on either side: + +- `id`: A unique document id. If this field is not present, the document's `id` will default to its file name (without the extension) +- `title`: The title of your document. If this field is not present, the document's `title` will default to its `id` +- `hide_title`: Whether to hide the title at the top of the doc. By default it is `false` +- `hide_table_of_contents`: Whether to hide the table of contents to the right. By default it is `false` +- `sidebar_label`: The text shown in the document sidebar and in the next/previous button for this document. If this field is not present, the document's `sidebar_label` will default to its `title` +- `custom_edit_url`: The URL for editing this document. If this field is not present, the document's edit URL will fall back to `editUrl` from options fields passed to `docusaurus-plugin-content-docs` +- `keywords`: Keywords meta tag for the document page, for search engines +- `description`: The description of your document, which will become the `<meta name="description" content="..."/>` and `<meta property="og:description" content="..."/>` in `<head>`, used by search engines. If this field is not present, it will default to the first line of the contents +- `image`: Cover or thumbnail image that will be used when displaying the link to your post +- `slug`: Allows to customize the document url + +Example: + +```yml +--- +id: doc-markdown +title: Markdown Features +hide_title: false +hide_table_of_contents: false +sidebar_label: Markdown :) +custom_edit_url: https://github.com/facebook/docusaurus/edit/master/docs/api-doc-markdown.md +description: How do I find you when I cannot solve this problem +keywords: + - docs + - docusaurus +image: https://i.imgur.com/mErPwqL.png +slug: /myDoc +--- +My Document Markdown content +``` + +## i18n + +Read the [i18n introduction](../../i18n/i18n-introduction.md) first. + +### Translation files location + +- **Base path**: `website/i18n/<locale>/docusaurus-plugin-content-docs` +- **Multi-instance path**: `website/i18n/<locale>/docusaurus-plugin-content-docs-<pluginId>` +- **JSON files**: extracted with [`docusaurus write-translations`](../../cli.md#docusaurus-write-translations) +- **Markdown files**: `website/i18n/<locale>/docusaurus-plugin-content-docs/<version>` + +### Example file-system structure + +```bash +website/i18n/<locale>/docusaurus-plugin-content-docs +│ +│ # translations for website/docs +├── current +│   ├── api +│   │   └── config.md +│   └── getting-started.md +├── current.json +│ +│ # translations for website/versioned_docs/version-1.0.0 +├── version-1.0.0 +│   ├── api +│   │   └── config.md +│   └── getting-started.md +└── version-1.0.0.json +``` diff --git a/website/versioned_docs/version-2.0.0-alpha.72/api/plugins/plugin-content-pages.md b/website/versioned_docs/version-2.0.0-alpha.72/api/plugins/plugin-content-pages.md new file mode 100644 index 0000000000..b63ba654d1 --- /dev/null +++ b/website/versioned_docs/version-2.0.0-alpha.72/api/plugins/plugin-content-pages.md @@ -0,0 +1,89 @@ +--- +id: plugin-content-pages +title: '📦 plugin-content-pages' +slug: '/api/plugins/@docusaurus/plugin-content-pages' +--- + +The default pages plugin for Docusaurus. The classic template ships with this plugin with default configurations. This plugin provides [creating pages](guides/creating-pages.md) functionality. + +## Installation + +```bash npm2yarn +npm install --save @docusaurus/plugin-content-pages +``` + +:::tip + +If you have installed `@docusaurus/preset-classic`, you don't need to install it as a dependency. You can also configure it through the [classic preset options](presets.md#docusauruspreset-classic) instead of doing it like below. + +::: + +## Configuration + +```js title="docusaurus.config.js" +module.exports = { + plugins: [ + [ + '@docusaurus/plugin-content-pages', + { + /** + * Path to data on filesystem + * relative to site dir + * components in this directory will be automatically converted to pages + */ + path: 'src/pages', + /** + * URL route for the page section of your site + * do not include trailing slash + */ + routeBasePath: '', + include: ['**/*.{js,jsx,ts,tsx,md,mdx}'], + /** + * No Route will be created for matching files + */ + exclude: [ + '**/_*.{js,jsx,ts,tsx,md,mdx}', + '**/*.test.{js,ts}', + '**/__tests__/**', + ], + /** + * Theme component used by markdown pages. + */ + mdxPageComponent: '@theme/MDXPage', + /** + * Remark and Rehype plugins passed to MDX + */ + remarkPlugins: [], + rehypePlugins: [], + /** + * Custom Remark and Rehype plugins passed to MDX before + * the default Docusaurus Remark and Rehype plugins. + */ + beforeDefaultRemarkPlugins: [], + beforeDefaultRehypePlugins: [], + }, + ], + ], +}; +``` + +## i18n + +Read the [i18n introduction](../../i18n/i18n-introduction.md) first. + +### Translation files location + +- **Base path**: `website/i18n/<locale>/docusaurus-plugin-content-pages` +- **Multi-instance path**: `website/i18n/<locale>/docusaurus-plugin-content-pages-<pluginId>` +- **JSON files**: extracted with [`docusaurus write-translations`](../../cli.md#docusaurus-write-translations) +- **Markdown files**: `website/i18n/<locale>/docusaurus-plugin-content-pages` + +### Example file-system structure + +```bash +website/i18n/<locale>/docusaurus-plugin-content-pages +│ +│ # translations for website/src/pages +├── first-markdown-page.md +└── second-markdown-page.md +``` diff --git a/website/versioned_docs/version-2.0.0-alpha.72/api/plugins/plugin-debug.md b/website/versioned_docs/version-2.0.0-alpha.72/api/plugins/plugin-debug.md new file mode 100644 index 0000000000..ff1e194577 --- /dev/null +++ b/website/versioned_docs/version-2.0.0-alpha.72/api/plugins/plugin-debug.md @@ -0,0 +1,39 @@ +--- +id: plugin-debug +title: '📦 plugin-debug' +slug: '/api/plugins/@docusaurus/plugin-debug' +--- + +The debug plugin will display useful debug information at [http://localhost:3000/\_\_docusaurus/debug](http://localhost:3000/__docusaurus/debug). + +It is mostly useful for plugin authors, that will be able to inspect more easily the content of the `.docusaurus` folder (like the creates routes), but also be able to inspect data structures that are never written to disk, like the plugin data loaded through the `contentLoaded` lifecycle. + +:::note + +If you report a bug, we will probably ask you to have this plugin turned on in the production, so that we can inspect your deployment config more easily. + +If you don't have any sensitive information, you can keep it on in production [like we do](http://v2.docusaurus.io/__docusaurus/debug). + +::: + +## Installation + +```bash npm2yarn +npm install --save @docusaurus/plugin-debug +``` + +:::tip + +If you have installed `@docusaurus/preset-classic`, you don't need to install it as a dependency. You can also configure it through the [classic preset options](presets.md#docusauruspreset-classic) instead of doing it like below. + +By default, it's enabled in dev, and disabled in prod, to avoid exposing potentially sensitive information. + +::: + +## Configuration + +```js title="docusaurus.config.js" +module.exports = { + plugins: ['@docusaurus/plugin-debug'], +}; +``` diff --git a/website/versioned_docs/version-2.0.0-alpha.72/api/plugins/plugin-google-analytics.md b/website/versioned_docs/version-2.0.0-alpha.72/api/plugins/plugin-google-analytics.md new file mode 100644 index 0000000000..3f026ffa96 --- /dev/null +++ b/website/versioned_docs/version-2.0.0-alpha.72/api/plugins/plugin-google-analytics.md @@ -0,0 +1,34 @@ +--- +id: plugin-google-analytics +title: '📦 plugin-google-analytics' +slug: '/api/plugins/@docusaurus/plugin-google-analytics' +--- + +The default [Google Analytics](https://developers.google.com/analytics/devguides/collection/analyticsjs/) plugin. It is a JavaScript library for measuring how users interact with your website. + +## Installation + +```bash npm2yarn +npm install --save @docusaurus/plugin-google-analytics +``` + +:::tip + +If you have installed `@docusaurus/preset-classic`, you don't need to install it as a dependency. + +::: + +## Configuration + +```js title="docusaurus.config.js" +module.exports = { + plugins: ['@docusaurus/plugin-google-analytics'], + themeConfig: { + googleAnalytics: { + trackingID: 'UA-141789564-1', + // Optional fields. + anonymizeIP: true, // Should IPs be anonymized? + }, + }, +}; +``` diff --git a/website/versioned_docs/version-2.0.0-alpha.72/api/plugins/plugin-google-gtag.md b/website/versioned_docs/version-2.0.0-alpha.72/api/plugins/plugin-google-gtag.md new file mode 100644 index 0000000000..f9af53c3e6 --- /dev/null +++ b/website/versioned_docs/version-2.0.0-alpha.72/api/plugins/plugin-google-gtag.md @@ -0,0 +1,34 @@ +--- +id: plugin-google-gtag +title: '📦 plugin-google-gtag' +slug: '/api/plugins/@docusaurus/plugin-google-gtag' +--- + +The default [Global Site Tag (gtag.js)](https://developers.google.com/analytics/devguides/collection/gtagjs/) plugin. It is a JavaScript tagging framework and API that allows you to send event data to Google Analytics, Google Ads, and Google Marketing Platform. This section describes how to configure a Docusaurus site to enable global site tag for Google Analytics. + +## Installation + +```bash npm2yarn +npm install --save @docusaurus/plugin-google-gtag +``` + +:::tip + +If you have installed `@docusaurus/preset-classic`, you don't need to install it as a dependency. + +::: + +## Configuration + +```js title="docusaurus.config.js" +module.exports = { + plugins: ['@docusaurus/plugin-google-gtag'], + themeConfig: { + gtag: { + trackingID: 'UA-141789564-1', + // Optional fields. + anonymizeIP: true, // Should IPs be anonymized? + }, + }, +}; +``` diff --git a/website/versioned_docs/version-2.0.0-alpha.72/api/plugins/plugin-ideal-image.md b/website/versioned_docs/version-2.0.0-alpha.72/api/plugins/plugin-ideal-image.md new file mode 100644 index 0000000000..93e69e5f35 --- /dev/null +++ b/website/versioned_docs/version-2.0.0-alpha.72/api/plugins/plugin-ideal-image.md @@ -0,0 +1,52 @@ +--- +id: plugin-ideal-image +title: '📦 plugin-ideal-image' +slug: '/api/plugins/@docusaurus/plugin-ideal-image' +--- + +Docusaurus Plugin to generate an almost ideal image (responsive, lazy-loading, and low quality placeholder) **in the production builds**. + +## Installation + +```bash npm2yarn +npm install --save @docusaurus/plugin-ideal-image +``` + +## Configuration + +Modify your `docusaurus.config.js` + +```diff +module.exports = { + ... ++ plugins: ['@docusaurus/plugin-ideal-image'], + ... +} +``` + +## Usage + +This plugin supports the PNG, GIF and JPG formats only. + +```jsx +import Image from '@theme/IdealImage'; +import thumbnail from './path/to/img.png'; + +// your React code +<Image img={thumbnail} /> + +// or +<Image img={require('./path/to/img.png')} /> +``` + +## Options + +| Option | Type | Default | Description | +| --- | --- | --- | --- | +| `name` | `string` | `ideal-img/[name].[hash:hex:7].[width].[ext]` | Filename template for output files. | +| `sizes` | `array` | _original size_ | Specify all widths you want to use. If a specified size exceeds the original image's width, the latter will be used (i.e. images won't be scaled up). | +| `size` | `integer` | _original size_ | Specify one width you want to use; if the specified size exceeds the original image's width, the latter will be used (i.e. images won't be scaled up) | +| `min` | `integer` | | As an alternative to manually specifying `sizes`, you can specify `min`, `max` and `steps`, and the sizes will be generated for you. | +| `max` | `integer` | | See `min` above | +| `steps` | `integer` | `4` | Configure the number of images generated between `min` and `max` (inclusive) | +| `quality` | `integer` | `85` | JPEG compression quality | diff --git a/website/versioned_docs/version-2.0.0-alpha.72/api/plugins/plugin-pwa.md b/website/versioned_docs/version-2.0.0-alpha.72/api/plugins/plugin-pwa.md new file mode 100644 index 0000000000..94bcd63d4c --- /dev/null +++ b/website/versioned_docs/version-2.0.0-alpha.72/api/plugins/plugin-pwa.md @@ -0,0 +1,313 @@ +--- +id: plugin-pwa +title: '📦 plugin-pwa' +slug: '/api/plugins/@docusaurus/plugin-pwa' +--- + +Docusaurus Plugin to add PWA support using [Workbox](https://developers.google.com/web/tools/workbox). This plugin generates a [Service Worker](https://developers.google.com/web/fundamentals/primers/service-workers) in production build only, and allows you to create fully PWA-compliant documentation site with offline and installation support. + +## Installation + +```bash npm2yarn +npm install --save @docusaurus/plugin-pwa +``` + +## Configuration + +Create a [PWA manifest](https://web.dev/add-manifest/) at `./static/manifest.json`. + +Modify `docusaurus.config.js` with a minimal PWA config, like: + +```js title="docusaurus.config.js" +module.exports = { + plugins: [ + [ + '@docusaurus/plugin-pwa', + { + debug: true, + offlineModeActivationStrategies: [ + 'appInstalled', + 'standalone', + 'queryString', + ], + pwaHead: [ + { + tagName: 'link', + rel: 'icon', + href: '/img/docusaurus.png', + }, + { + tagName: 'link', + rel: 'manifest', + href: '/manifest.json', // your PWA manifest + }, + { + tagName: 'meta', + name: 'theme-color', + content: 'rgb(37, 194, 160)', + }, + ], + }, + ], + ], +}; +``` + +## Progressive Web App + +Having a service worker installed is not enough to make your application a PWA. You'll need to at least include a [Web App Manifest](https://developer.mozilla.org/en-US/docs/Web/Manifest) and have the correct tags in `<head>` ([Options > pwaHead](#pwahead)). + +After deployment, you can use [Lighthouse](https://developers.google.com/web/tools/lighthouse) to run an audit on your site. + +For a more exhaustive list of what it takes for your site to be a PWA, refer to the [PWA Checklist](https://developers.google.com/web/progressive-web-apps/checklist) + +## App installation support + +If your browser supports it, you should be able to install a Docusaurus site as an app. + +![pwa_install.gif](/img/pwa_install.gif) + +:::note + +App installation requires the https protocol and a valid manifest. + +::: + +## Offline mode (precaching) + +We enable users to browse a Docusaurus site offline, by using service-worker precaching. + +> ### [What is Precaching?](https://developers.google.com/web/tools/workbox/modules/workbox-precaching) +> +> One feature of service workers is the ability to save a set of files to the cache when the service worker is installing. This is often referred to as "precaching", since you are caching content ahead of the service worker being used. +> +> The main reason for doing this is that it gives developers control over the cache, meaning they can determine when and how long a file is cached as well as serve it to the browser without going to the network, meaning it can be used to create web apps that work offline. +> +> Workbox takes a lot of the heavy lifting out of precaching by simplifying the API and ensuring assets are downloaded efficiently. + +By default, offline mode is enabled when the site is installed as an app. See the `offlineModeActivationStrategies` option for details. + +After the site has been precached, the service worker will serve cached responses for later visits. When a new build is deployed along with a new service worker, the new one will begin installing and eventually move to a waiting state. During this waiting state, a reload popup will show and ask the user to reload the page for new content. Until the user either clears the application cache or clicks the `reload` button on the popup, the service worker will continue serving the old content. + +:::caution + +Offline mode / precaching requires downloading all the static assets of the site ahead of time, and can consume unnecessary bandwidth. It may not be a good idea to activate it for all kind of sites. + +::: + +## Options + +### `debug` + +- Type: `boolean` +- Default: `false` + +Turn debug mode on: + +- Workbox logs +- Additional Docusaurus logs +- Unoptimized SW file output +- Source maps + +### `offlineModeActivationStrategies` + +- Type: `Array<'appInstalled' | 'mobile' | 'saveData'| 'queryString' | 'always'>` +- Default: `['appInstalled','queryString','standalone']` + +Strategies used to turn the offline mode on: + +- `appInstalled`: activates for users having installed the site as an app (not 100% reliable) +- `standalone`: activates for users running the app as standalone (often the case once a PWA is installed) +- `queryString`: activates if queryString contains `offlineMode=true` (convenient for PWA debugging) +- `mobile`: activates for mobile users (width <= 940px) +- `saveData`: activates for users with `navigator.connection.saveData === true` +- `always`: activates for all users + +:::caution + +Use this carefully: some users may not like to be forced to use the offline mode. + +::: + +:::danger + +It is not possible to detect if an as a PWA in a very reliable way. + +The `appinstalled` event has been [removed from the specification](https://github.com/w3c/manifest/pull/836), and the [`navigator.getInstalledRelatedApps()`](https://web.dev/get-installed-related-apps/) API is only supported in recent Chrome versions and require `related_applications` declared in the manifest. + +The [`standalone` strategy](https://petelepage.com/blog/2019/07/is-my-pwa-installed/) is a nice fallback to activate the offline mode (at least when running the installed app). + +::: + +### `injectManifestConfig` + +[Workbox options](https://developers.google.com/web/tools/workbox/reference-docs/latest/module-workbox-build#.injectManifest) to pass to `workbox.injectManifest()`. This gives you control over which assets will be precached, and be available offline. + +- Type: `InjectManifestOptions` +- Default: `{}` + +```js title="docusaurus.config.js" +module.exports = { + plugins: [ + [ + '@docusaurus/plugin-pwa', + { + injectManifestConfig: { + manifestTransforms: [ + //... + ], + modifyURLPrefix: { + //... + }, + // We already add regular static assets (html, images...) to be available offline + // You can add more files according to your needs + globPatterns: ['**/*.{pdf,docx,xlsx}'], + // ... + }, + }, + ], + ], +}; +``` + +### `reloadPopup` + +- Type: `string | false` +- Default: `'@theme/PwaReloadPopup'` + +Module path to reload popup component. This popup is rendered when a new service worker is waiting to be installed, and we suggest a reload to the user. + +Passing `false` will disable the popup, but this is not recommended: users won't have a way to get up-to-date content. + +A custom component can be used, as long as it accepts `onReload` as a prop. The `onReload` callback should be called when the `reload` button is clicked. This will tell the service worker to install the waiting service worker and reload the page. + +```ts +interface PwaReloadPopupProps { + onReload: () => void; +} +``` + +The default theme includes an implementation for the reload popup and uses [Infima Alerts](https://infima.dev/docs/components/alert). + +![pwa_reload.gif](/img/pwa_reload.gif) + +### `pwaHead` + +- Type: `Array<{ tagName: string } & Record<string,string>>` +- Default: `[]` + +Array of objects containing `tagName` and key-value pairs for attributes to inject into the `<head>` tag. Technically you can inject any head tag through this, but it's ideally used for tags to make your site PWA compliant. Here's a list of tag to make your app fully compliant: + +```js +module.exports = { + plugins: [ + [ + '@docusaurus/plugin-pwa', + { + pwaHead: [ + { + tagName: 'link', + rel: 'icon', + href: '/img/docusaurus.png', + }, + { + tagName: 'link', + rel: 'manifest', + href: '/manifest.json', + }, + { + tagName: 'meta', + name: 'theme-color', + content: 'rgb(37, 194, 160)', + }, + { + tagName: 'meta', + name: 'apple-mobile-web-app-capable', + content: 'yes', + }, + { + tagName: 'meta', + name: 'apple-mobile-web-app-status-bar-style', + content: '#000', + }, + { + tagName: 'link', + rel: 'apple-touch-icon', + href: '/img/docusaurus.png', + }, + { + tagName: 'link', + rel: 'mask-icon', + href: '/img/docusaurus.svg', + color: 'rgb(37, 194, 160)', + }, + { + tagName: 'meta', + name: 'msapplication-TileImage', + content: '/img/docusaurus.png', + }, + { + tagName: 'meta', + name: 'msapplication-TileColor', + content: '#000', + }, + ], + }, + ], + ], +}; +``` + +### `swCustom` + +- Type: `string | undefined` +- Default: `undefined` + +Useful for additional Workbox rules. You can do whatever a service worker can do here, and use the full power of workbox libraries. The code is transpiled, so you can use modern ES6+ syntax here. + +For example, to cache files from external routes: + +```js +import {registerRoute} from 'workbox-routing'; +import {StaleWhileRevalidate} from 'workbox-strategies'; + +// default fn export receiving some useful params +export default function swCustom(params) { + const { + debug, // :boolean + offlineMode, // :boolean + } = params; + + // Cache responses from external resources + registerRoute((context) => { + return [ + /graph\.facebook\.com\/.*\/picture/, + /netlify\.com\/img/, + /avatars1\.githubusercontent/, + ].some((regex) => context.url.href.match(regex)); + }, new StaleWhileRevalidate()); +} +``` + +The module should have a `default` function export, and receives some params. + +### `swRegister` + +- Type: `string | false` +- Default: `'docusaurus-plugin-pwa/src/registerSW.js'` + +Adds an entry before the Docusaurus app so that registration can happen before the app runs. The default `registerSW.js` file is enough for simple registration. + +Passing `false` will disable registration entirely. + +## Manifest example + +The Docusaurus site manifest can serve as an inspiration: + +```mdx-code-block +import CodeBlock from '@theme/CodeBlock'; + +<CodeBlock className="language-json"> + {JSON.stringify(require("@site/static/manifest.json"),null,2)} +</CodeBlock> +``` diff --git a/website/versioned_docs/version-2.0.0-alpha.72/api/plugins/plugin-sitemap.md b/website/versioned_docs/version-2.0.0-alpha.72/api/plugins/plugin-sitemap.md new file mode 100644 index 0000000000..70abf94940 --- /dev/null +++ b/website/versioned_docs/version-2.0.0-alpha.72/api/plugins/plugin-sitemap.md @@ -0,0 +1,36 @@ +--- +id: plugin-sitemap +title: '📦 plugin-sitemap' +slug: '/api/plugins/@docusaurus/plugin-sitemap' +--- + +This plugin creates sitemap for your site so that search engine crawlers can crawl your site more accurately. + +## Installation + +```bash npm2yarn +npm install --save @docusaurus/plugin-sitemap +``` + +:::tip + +If you have installed `@docusaurus/preset-classic`, you don't need to install it as a dependency. You can also configure it through the [classic preset options](presets.md#docusauruspreset-classic) instead of doing it like below. + +::: + +## Configuration + +```js title="docusaurus.config.js" +module.exports = { + plugins: [ + [ + '@docusaurus/plugin-sitemap', + { + changefreq: 'weekly', + priority: 0.5, + trailingSlash: false, + }, + ], + ], +}; +``` diff --git a/website/versioned_docs/version-2.0.0-alpha.72/api/themes/overview.md b/website/versioned_docs/version-2.0.0-alpha.72/api/themes/overview.md new file mode 100644 index 0000000000..d5b4518e7d --- /dev/null +++ b/website/versioned_docs/version-2.0.0-alpha.72/api/themes/overview.md @@ -0,0 +1,32 @@ +--- +id: themes-overview +title: 'Docusaurus themes' +sidebar_label: Themes overview +slug: '/api/themes' +--- + +We provide official Docusaurus themes. + +## Main themes + +The main themes implement the user interface for the [docs](../plugins/plugin-content-docs.md), [blog](../plugins/plugin-content-blog.md) and [pages](../plugins/plugin-content-pages.md) plugins. + +- [@docusaurus/theme-classic](./theme-classic.md) +- [@docusaurus/theme-bootstrap](./theme-bootstrap.md) 🚧 + +:::caution + +The goal is to have all themes share the exact same features, user-experience and configuration. + +Only the UI design and underlying styling framework should change, and you should be able to change theme easily. + +We are not there yet: only the classic theme is production ready. + +::: + +## Enhancement themes + +These themes will enhance the existing main themes with additional user-interface related features. + +- [@docusaurus/theme-live-codeblock](./theme-live-codeblock.md) +- [@docusaurus/theme-search-algolia](./theme-search-algolia.md) diff --git a/website/versioned_docs/version-2.0.0-alpha.72/api/themes/theme-bootstrap.md b/website/versioned_docs/version-2.0.0-alpha.72/api/themes/theme-bootstrap.md new file mode 100644 index 0000000000..2c2dc05a62 --- /dev/null +++ b/website/versioned_docs/version-2.0.0-alpha.72/api/themes/theme-bootstrap.md @@ -0,0 +1,25 @@ +--- +id: theme-bootstrap +title: '📦 theme-bootstrap' +slug: '/api/themes/@docusaurus/theme-bootstrap' +--- + +:::danger + +The bootstrap theme is a work in progress, and is not production ready. + +::: + +🚧 The bootstrap theme for Docusaurus. + +You can refer to the [theme configuration page](theme-configuration.md) for more details on the configuration. + +```bash npm2yarn +npm install --save @docusaurus/theme-bootstrap +``` + +:::tip + +If you have installed `@docusaurus/preset-bootstrap`, you don't need to install it as a dependency. + +::: diff --git a/website/versioned_docs/version-2.0.0-alpha.72/api/themes/theme-classic.md b/website/versioned_docs/version-2.0.0-alpha.72/api/themes/theme-classic.md new file mode 100644 index 0000000000..3b5a3a764c --- /dev/null +++ b/website/versioned_docs/version-2.0.0-alpha.72/api/themes/theme-classic.md @@ -0,0 +1,19 @@ +--- +id: theme-classic +title: '📦 theme-classic' +slug: '/api/themes/@docusaurus/theme-classic' +--- + +The classic theme for Docusaurus. + +You can refer to the [theme configuration page](theme-configuration.md) for more details on the configuration. + +```bash npm2yarn +npm install --save @docusaurus/theme-classic +``` + +:::tip + +If you have installed `@docusaurus/preset-classic`, you don't need to install it as a dependency. + +::: diff --git a/website/versioned_docs/version-2.0.0-alpha.72/api/themes/theme-configuration.md b/website/versioned_docs/version-2.0.0-alpha.72/api/themes/theme-configuration.md new file mode 100644 index 0000000000..c6f88dfca2 --- /dev/null +++ b/website/versioned_docs/version-2.0.0-alpha.72/api/themes/theme-configuration.md @@ -0,0 +1,575 @@ +--- +id: theme-configuration +title: 'Theme configuration' +slug: '/api/themes/configuration' +--- + +This configuration applies to all [main themes](./overview.md). + +## Common + +### Color mode - dark mode + +The classic theme provides by default light and dark mode support, with a navbar switch for the user. + +It is possible to customize the color mode support with the following configuration: + +```js {6-35} title="docusaurus.config.js" +module.exports = { + // ... + themeConfig: { + // ... + colorMode: { + // "light" | "dark" + defaultMode: 'light', + + // Hides the switch in the navbar + // Useful if you want to support a single color mode + disableSwitch: false, + + // Should we use the prefers-color-scheme media-query, + // using user system preferences, instead of the hardcoded defaultMode + respectPrefersColorScheme: false, + + // Dark/light switch icon options + switchConfig: { + // Icon for the switch while in dark mode + darkIcon: '🌙', + + // CSS to apply to dark icon, + // React inline style object + // see https://reactjs.org/docs/dom-elements.html#style + darkIconStyle: { + marginLeft: '2px', + }, + + // Unicode icons such as '\u2600' will work + // Unicode with 5 chars require brackets: '\u{1F602}' + lightIcon: '\u{1F602}', + + lightIconStyle: { + marginLeft: '1px', + }, + }, + }, + // ... + }, + // ... +}; +``` + +:::caution + +With `respectPrefersColorScheme: true`, the `defaultMode` is overridden by user system preferences. + +If you only want to support one color mode, you likely want to ignore user system preferences. + +::: + +### Meta image + +You can configure a default image that will be used for your meta tag, in particular `og:image` and `twitter:image`. + +```js {4-6} title="docusaurus.config.js" +module.exports = { + // ... + themeConfig: { + // Relative to your site's "static" directory. + // Cannot be SVGs. Can be external URLs too. + image: 'img/docusaurus.png', + // ... + }, +}; +``` + +### Metadatas + +You can configure additional html metadatas (and override existing ones). + +```js {4} title="docusaurus.config.js" +module.exports = { + // ... + themeConfig: { + metadatas: [{name: 'twitter:card', content: 'summary'}], + // ... + }, +}; +``` + +### Announcement bar + +Sometimes you want to announce something in your website. Just for such a case, you can add an announcement bar. This is a non-fixed and optionally dismissable panel above the navbar. + +```js {4-11} title="docusaurus.config.js" +module.exports = { + // ... + themeConfig: { + announcementBar: { + id: 'support_us', // Any value that will identify this message. + content: + 'We are looking to revamp our docs, please fill <a target="_blank" rel="noopener noreferrer" href="#">this survey</a>', + backgroundColor: '#fafbfc', // Defaults to `#fff`. + textColor: '#091E42', // Defaults to `#000`. + isCloseable: false, // Defaults to `true`. + }, + // ... + }, +}; +``` + +## i18n + +Read the [i18n introduction](../../i18n/i18n-introduction.md) first. + +### Translation files location + +- **Base path**: `website/i18n/<locale>/docusaurus-theme-<themeName>` +- **Multi-instance path**: N/A +- **JSON files**: extracted with [`docusaurus write-translations`](../../cli.md#docusaurus-write-translations) +- **Markdown files**: `N/A + +### Example file-system structure + +```bash +website/i18n/<locale>/docusaurus-theme-classic +│ +│ # translations for the theme +├── navbar.json +└── footer.json +``` + +## Hooks + +### `useThemeContext` + +React hook to access theme context. This context contains functions for setting light and dark mode and boolean property, indicating which mode is currently in use. + +Usage example: + +```jsx +import React from 'react'; +// highlight-next-line +import useThemeContext from '@theme/hooks/useThemeContext'; + +const Example = () => { + // highlight-next-line + const {isDarkTheme, setLightTheme, setDarkTheme} = useThemeContext(); + + return <h1>Dark mode is now {isDarkTheme ? 'on' : 'off'}</h1>; +}; +``` + +:::note + +The component calling `useThemeContext` must be a child of the `Layout` component. + +```jsx +function ExamplePage() { + return ( + <Layout> + <Example /> + </Layout> + ); +} +``` + +::: + +## Navbar + +### Navbar title & logo + +You can add a logo and title to the navbar via `themeConfig.navbar`. Logo can be placed in [static folder](static-assets.md). Logo URL is set to base URL of your site by default. Although you can specify your own URL for the logo, if it is an external link, it will open in a new tab. In addition, you can override a value for the target attribute of logo link, it can come in handy if you are hosting docs website in a subdirectory of your main website, and in which case you probably do not need a link in the logo to the main website will open in a new tab. + +To improve dark mode support, you can also set a different logo for this mode. + +```js {5-11} title="docusaurus.config.js" +module.exports = { + // ... + themeConfig: { + navbar: { + title: 'Site Title', + logo: { + alt: 'Site Logo', + src: 'img/logo.svg', + srcDark: 'img/logo_dark.svg', // Default to `logo.src`. + href: 'https://v2.docusaurus.io/', // Default to `siteConfig.baseUrl`. + target: '_self', // By default, this value is calculated based on the `href` attribute (the external link will open in a new tab, all others in the current one). + }, + }, + // ... + }, +}; +``` + +### Navbar items + +You can add items to the navbar via `themeConfig.navbar.items`. + +By default, Navbar items are regular links (internal or external). + +```js title="docusaurus.config.js" +module.exports = { + // ... + themeConfig: { + navbar: { + // highlight-start + items: [ + { + // Client-side routing, used for navigating within the website. + // The baseUrl will be automatically prepended to this value. + to: 'docs/introduction', + // A full-page navigation, used for navigating outside of the website. + // You should only use either `to` or `href`. + href: 'https://www.facebook.com', + // Prepends the baseUrl to href values. + prependBaseUrlToHref: true, + // The string to be shown. + label: 'Introduction', + // Left or right side of the navbar. + position: 'left', // or 'right' + // To apply the active class styling on all + // routes starting with this path. + // This usually isn't necessary + activeBasePath: 'docs', + // Alternative to activeBasePath if required. + activeBaseRegex: 'docs/(next|v8)', + // Custom CSS class (for styling any item). + className: '', + }, + // ... other items + ], + // highlight-end + }, + // ... + }, +}; +``` + +React Router should automatically apply active link styling to links, but you can use `activeBasePath` in edge cases. For cases in which a link should be active on several different paths (such as when you have multiple doc folders under the same sidebar), you can use `activeBaseRegex`. `activeBaseRegex` is a more flexible alternative to `activeBasePath` and takes precedence over it -- Docusaurus parses it into a regular expression that is tested against the current URL. + +Outbound (external) links automatically get `target="_blank" rel="noopener noreferrer"` attributes. + +### Navbar dropdown + +Navbar items can also be dropdown items by specifying the `items`, an inner array of navbar items. + +```js {9-19} title="docusaurus.config.js" +module.exports = { + // ... + themeConfig: { + navbar: { + items: [ + { + label: 'Community', + position: 'left', // or 'right' + items: [ + { + label: 'Facebook', + href: '...', + }, + { + label: 'GitHub', + href: '...', + }, + // ... more items + ], + }, + ], + }, + // ... + }, +}; +``` + +### Navbar doc link + +If you want to link to a specific doc, this special navbar item type will render the link to the doc of the provided `docId`. It will get the class `navbar__link--active` as long as you browse a doc of the same sidebar. + +```js title="docusaurus.config.js" +module.exports = { + themeConfig: { + navbar: { + items: [ + // highlight-start + { + type: 'doc', + docId: 'introduction', + + //// Optional + position: 'left', + label: 'Docs', + activeSidebarClassName: 'navbar__link--active', + docsPluginId: 'default', + }, + // highlight-end + ], + }, + }, +}; +``` + +### Navbar docs version dropdown + +If you use docs with versioning, this special navbar item type that will render a dropdown with all your site's available versions. + +The user will be able to switch from one version to another, while staying on the same doc (as long as the doc id is constant across versions). + +```js {5-8} title="docusaurus.config.js" +module.exports = { + themeConfig: { + navbar: { + items: [ + { + type: 'docsVersionDropdown', + + //// Optional + position: 'left', + // Add additional dropdown items at the beginning/end of the dropdown. + dropdownItemsBefore: [], + dropdownItemsAfter: [{to: '/versions', label: 'All versions'}], + // Do not add the link active class when browsing docs. + dropdownActiveClassDisabled: true, + docsPluginId: 'default', + }, + ], + }, + }, +}; +``` + +### Navbar docs version + +If you use docs with versioning, this special navbar item type will link to the active/browsed version of your doc (depends on the current url), and fallback to the latest version. + +```js title="docusaurus.config.js" +module.exports = { + themeConfig: { + navbar: { + items: [ + // highlight-start + { + type: 'docsVersion', + + //// Optional + position: 'left', + to: '/path', // by default, link to active/latest version + label: 'label', // by default, show active/latest version label + docsPluginId: 'default', + }, + // highlight-end + ], + }, + }, +}; +``` + +### Navbar locale dropdown + +If you use the [i18n feature](../../i18n/i18n-introduction.md), this special navbar item type will render a dropdown with all your site's available locales. + +The user will be able to switch from one locale to another, while staying on the same page. + +```js {5-8} title="docusaurus.config.js" +module.exports = { + themeConfig: { + navbar: { + items: [ + { + type: 'localeDropdown', + + //// Optional + position: 'left', + // Add additional dropdown items at the beginning/end of the dropdown. + dropdownItemsBefore: [], + dropdownItemsAfter: [ + { + to: 'https://my-site.com/help-us-translate', + label: 'Help us translate', + }, + ], + }, + ], + }, + }, +}; +``` + +### Navbar search + +If you use the [search](../../search.md), the search bar will be the rightmost element in the navbar. + +However, with this special navbar item type, you can change the default location. + +```js {5-8} title="docusaurus.config.js" +module.exports = { + themeConfig: { + navbar: { + items: [ + { + type: 'search', + position: 'right', + }, + ], + }, + }, +}; +``` + +### Auto-hide sticky navbar + +You can enable this cool UI feature that automatically hides the navbar when a user starts scrolling down the page, and show it again when the user scrolls up. + +```js {5} title="docusaurus.config.js" +module.exports = { + // ... + themeConfig: { + navbar: { + hideOnScroll: true, + }, + // ... + }, +}; +``` + +### Navbar style + +You can set the static Navbar style without disabling the theme switching ability. The selected style will always apply no matter which theme user have selected. + +Currently, there are two possible style options: `dark` and `primary` (based on the `--ifm-color-primary` color). You can see the styles preview in the [Infima documentation](https://infima.dev/docs/components/navbar/). + +```js {5} title="docusaurus.config.js" +module.exports = { + // ... + themeConfig: { + navbar: { + style: 'primary', + }, + // ... + }, +}; +``` + +<!-- + +## Footer + +TODO. + +--> + +## CodeBlock + +Docusaurus uses [Prism React Renderer](https://github.com/FormidableLabs/prism-react-renderer) to highlight code blocks. + +### Theme + +By default, we use [Palenight](https://github.com/FormidableLabs/prism-react-renderer/blob/master/src/themes/palenight.js) as syntax highlighting theme. You can specify a custom theme from the [list of available themes](https://github.com/FormidableLabs/prism-react-renderer/tree/master/src/themes). If you want to use a different syntax highlighting theme when the site is in dark mode, you may also do so. + +```js {5-6} title="docusaurus.config.js" +module.exports = { + // ... + themeConfig: { + prism: { + theme: require('prism-react-renderer/themes/github'), + darkTheme: require('prism-react-renderer/themes/dracula'), + }, + // ... + }, +}; +``` + +:::note + +If you use the line highlighting Markdown syntax, you might need to specify a different highlight background color for the dark mode syntax highlighting theme. Refer to the [docs for guidance](../../guides/markdown-features/markdown-features-code-blocks.mdx#line-highlighting). + +::: + +### Default language + +You can set a default language for code blocks if no language is added after the opening triple backticks (i.e. ```). Note that a valid [language name](https://prismjs.com/#supported-languages) must be passed, e.g.: + +```js {5} title="docusaurus.config.js" +module.exports = { + // ... + themeConfig: { + prism: { + defaultLanguage: 'javascript', + }, + // ... + }, +}; +``` + +## Footer + +You can add logo and a copyright to the footer via `themeConfig.footer`. Logo can be placed in [static folder](static-assets.md). Logo URL works in the same way of the navbar logo. + +```js {5-15} title="docusaurus.config.js" + // ... + footer: { + logo: { + alt: 'Facebook Open Source Logo', + src: 'img/oss_logo.png', + href: 'https://opensource.facebook.com', + }, + copyright: `Copyright © ${new Date().getFullYear()} My Project, Inc. Built with Docusaurus.`, + } +``` + +## Footer Links + +You can add links to the navbar via `themeConfig.footer.links`: + +```js {5-15} title="docusaurus.config.js" +module.exports = { + // ... + footer: { + links: [ + { + // Label of the section of these links + title: 'Docs', + items: [ + { + // Label of the link + label: 'Style Guide', + // Client-side routing, used for navigating within the website. + // The baseUrl will be automatically prepended to this value. + to: 'docs/', + }, + { + label: 'Second Doc', + to: 'docs/doc2/', + }, + ], + }, + { + title: 'Community', + items: [ + { + label: 'Stack Overflow', + // A full-page navigation, used for navigating outside of the website. + href: 'https://stackoverflow.com/questions/tagged/docusaurus', + }, + { + label: 'Discord', + href: 'https://discordapp.com/invite/docusaurus', + }, + { + label: 'Twitter', + href: 'https://twitter.com/docusaurus', + }, + { + //Renders the html pass-through instead of a simple link + html: ` + <a href="https://www.netlify.com" target="_blank" rel="noreferrer noopener" aria-label="Deploys by Netlify"> + <img src="https://www.netlify.com/img/global/badges/netlify-color-accent.svg" alt="Deploys by Netlify" /> + </a> + `, + }, + ], + }, + ], + }, +}; +``` diff --git a/website/versioned_docs/version-2.0.0-alpha.72/api/themes/theme-live-codeblock.md b/website/versioned_docs/version-2.0.0-alpha.72/api/themes/theme-live-codeblock.md new file mode 100644 index 0000000000..8a676646f4 --- /dev/null +++ b/website/versioned_docs/version-2.0.0-alpha.72/api/themes/theme-live-codeblock.md @@ -0,0 +1,28 @@ +--- +id: theme-live-codeblock +title: '📦 theme-live-codeblock' +slug: '/api/themes/@docusaurus/theme-live-codeblock' +--- + +This theme provides a `@theme/CodeBlock` component that is powered by react-live. You can read more on [interactive code editor](../../guides/markdown-features/markdown-features-code-blocks.mdx#interactive-code-editor) documentation. + +```bash npm2yarn +npm install --save @docusaurus/theme-live-codeblock +``` + +### Configuration + +```jsx title="docusaurus.config.js" +module.exports = { + plugins: ['@docusaurus/theme-live-codeblock'], + themeConfig: { + liveCodeBlock: { + /** + * The position of the live playground, above or under the editor + * Possible values: "top" | "bottom" + */ + playgroundPosition: 'bottom', + }, + }, +}; +``` diff --git a/website/versioned_docs/version-2.0.0-alpha.72/api/themes/theme-search-algolia.md b/website/versioned_docs/version-2.0.0-alpha.72/api/themes/theme-search-algolia.md new file mode 100644 index 0000000000..753d8ca66e --- /dev/null +++ b/website/versioned_docs/version-2.0.0-alpha.72/api/themes/theme-search-algolia.md @@ -0,0 +1,19 @@ +--- +id: theme-search-algolia +title: '📦 theme-search-algolia' +slug: '/api/themes/@docusaurus/theme-search-algolia' +--- + +This theme provides a `@theme/SearchBar` component that integrates with Algolia DocSearch easily. Combined with `@docusaurus/theme-classic`, it provides a very easy search integration. You can read more on [search](../../search.md) documentation. + +```bash npm2yarn +npm install --save @docusaurus/theme-search-algolia +``` + +This theme also adds search page available at `/search` (as swizzleable `SearchPage` component) path with OpenSearch support. + +:::tip + +If you have installed `@docusaurus/preset-classic`, you don't need to install it as a dependency. + +::: diff --git a/website/versioned_docs/version-2.0.0-alpha.72/assets/docusaurus-asset-example-banner.png b/website/versioned_docs/version-2.0.0-alpha.72/assets/docusaurus-asset-example-banner.png new file mode 100644 index 0000000000..ebe95f5ec8 Binary files /dev/null and b/website/versioned_docs/version-2.0.0-alpha.72/assets/docusaurus-asset-example-banner.png differ diff --git a/website/versioned_docs/version-2.0.0-alpha.72/assets/docusaurus-asset-example-pdf.pdf b/website/versioned_docs/version-2.0.0-alpha.72/assets/docusaurus-asset-example-pdf.pdf new file mode 100644 index 0000000000..188262276a Binary files /dev/null and b/website/versioned_docs/version-2.0.0-alpha.72/assets/docusaurus-asset-example-pdf.pdf differ diff --git a/website/versioned_docs/version-2.0.0-alpha.72/assets/docusaurus-asset-example.xyz b/website/versioned_docs/version-2.0.0-alpha.72/assets/docusaurus-asset-example.xyz new file mode 100644 index 0000000000..188262276a Binary files /dev/null and b/website/versioned_docs/version-2.0.0-alpha.72/assets/docusaurus-asset-example.xyz differ diff --git a/website/versioned_docs/version-2.0.0-alpha.72/blog.md b/website/versioned_docs/version-2.0.0-alpha.72/blog.md new file mode 100644 index 0000000000..635a35c31b --- /dev/null +++ b/website/versioned_docs/version-2.0.0-alpha.72/blog.md @@ -0,0 +1,222 @@ +--- +id: blog +title: Blog +--- + +## Initial setup + +To setup your site's blog, start by creating a `blog` directory. + +Then, add an item link to your blog within `docusaurus.config.js`: + +```js title="docusaurus.config.js" +module.exports = { + themeConfig: { + // ... + navbar: { + items: [ + // ... + // highlight-next-line + {to: 'blog', label: 'Blog', position: 'left'}, // or position: 'right' + ], + }, + }, +}; +``` + +## Adding posts + +To publish in the blog, create a file within the blog directory with a formatted name of `YYYY-MM-DD-my-blog-post-title.md`. The post date is extracted from the file name. + +For example, at `my-website/blog/2019-09-05-hello-docusaurus-v2.md`: + +```yml +--- +title: Welcome Docusaurus v2 +author: Joel Marcey +author_title: Co-creator of Docusaurus 1 +author_url: https://github.com/JoelMarcey +author_image_url: https://graph.facebook.com/611217057/picture/?height=200&width=200 +tags: [hello, docusaurus-v2] +description: This is my first post on Docusaurus 2. +image: https://i.imgur.com/mErPwqL.png +hide_table_of_contents: false +--- +Welcome to this blog. This blog is created with [**Docusaurus 2 alpha**](https://v2.docusaurus.io/). + +<!--truncate--> + +This is my first post on Docusaurus 2. + +A whole bunch of exploration to follow. +``` + +## Header options + +The only required field is `title`; however, we provide options to add author information to your blog post as well along with other options. + +- `author` - The author name to be displayed. +- `author_url` - The URL that the author's name will be linked to. This could be a GitHub, Twitter, Facebook profile URL, etc. +- `author_image_url` - The URL to the author's thumbnail image. +- `author_title` - A description of the author. +- `title` - The blog post title. +- `tags` - A list of strings to tag to your post. +- `draft` - A boolean flag to indicate that the blog post is work-in-progress and therefore should not be published yet. However, draft blog posts will be displayed during development. +- `description`: The description of your post, which will become the `<meta name="description" content="..."/>` and `<meta property="og:description" content="..."/>` in `<head>`, used by search engines. If this field is not present, it will default to the first line of the contents. +- `image`: Cover or thumbnail image that will be used when displaying the link to your post. +- `hide_table_of_contents`: Whether to hide the table of contents to the right. By default it is `false`. + +## Summary truncation + +Use the `<!--truncate-->` marker in your blog post to represent what will be shown as the summary when viewing all published blog posts. Anything above `<!--truncate-->` will be part of the summary. For example: + +```yml +--- +title: Truncation Example +--- +All these will be part of the blog post summary. + +Even this. + +<!--truncate--> + +But anything from here on down will not be. + +Not this. + +Or this. +``` + +## Feed + +You can generate RSS/Atom feed by passing feedOptions. By default, RSS and Atom feeds are generated. To disable feed generation, set `feedOptions.type` to `null`. + +```ts +feedOptions?: { + type?: 'rss' | 'atom' | 'all' | null; + title?: string; + description?: string; + copyright: string; + language?: string; // possible values: http://www.w3.org/TR/REC-html40/struct/dirlang.html#langcodes +}; +``` + +Example usage: + +```js {8-11} title="docusaurus.config.js" +module.exports = { + // ... + presets: [ + [ + '@docusaurus/preset-classic', + { + blog: { + feedOptions: { + type: 'all', + copyright: `Copyright © ${new Date().getFullYear()} Facebook, Inc.`, + }, + }, + }, + ], + ], +}; +``` + +Accessing the feed: + +The feed for RSS can be found at: + +```text +https://{your-domain}/blog/rss.xml +``` + +and for Atom: + +```text +https://{your-domain}/blog/atom.xml +``` + +## Advanced topics + +### Blog-only mode + +You can run your Docusaurus 2 site without a landing page and instead have your blog's post list page as the index page. Set the `routeBasePath` to be `'/'` to indicate it's the root path. + +```js {9} title="docusaurus.config.js" +module.exports = { + // ... + presets: [ + [ + '@docusaurus/preset-classic', + { + docs: false, + blog: { + path: './blog', + routeBasePath: '/', // Set this value to '/'. + }, + }, + ], + ], +}; +``` + +:::caution + +Don't forget to delete the existing homepage at `./src/pages/index.js` or else there will be two files mapping to the same route! + +::: + +You can also add meta description to the blog list page for better SEO: + +```js {8} title="docusaurus.config.js" +module.exports = { + // ... + presets: [ + [ + '@docusaurus/preset-classic', + { + blog: { + blogTitle: 'Docusaurus blog!', + blogDescription: 'A docusaurus powered blog!', + }, + }, + ], + ], +}; +``` + +### Multiple blogs + +By default, the classic theme assumes only one blog per website and hence includes only one instance of the blog plugin. If you would like to have multiple blogs on a single website, it's possible too! You can add another blog by specifying another blog plugin in the `plugins` option for `docusaurus.config.js`. + +Set the `routeBasePath` to the URL route that you want your second blog to be accessed on. Note that the `routeBasePath` here has to be different from the first blog or else there could be a collision of paths! Also, set `path` to the path to the directory containing your second blog's entries. + +As documented for [multi-instance plugins](./using-plugins.md#multi-instance-plugins-and-plugin-ids), you need to assign a unique id to the plugins. + +```js title="docusaurus.config.js" +module.exports = { + // ... + plugins: [ + [ + '@docusaurus/plugin-content-blog', + { + /** + * Required for any multi-instance plugin + */ + id: 'second-blog', + /** + * URL route for the blog section of your site. + * *DO NOT* include a trailing slash. + */ + routeBasePath: 'my-second-blog', + /** + * Path to data on filesystem relative to site dir. + */ + path: './my-second-blog', + }, + ], + ], +}; +``` + +As an example, we host a second blog [here](/second-blog). diff --git a/website/versioned_docs/version-2.0.0-alpha.72/cli.md b/website/versioned_docs/version-2.0.0-alpha.72/cli.md new file mode 100644 index 0000000000..4d0e125083 --- /dev/null +++ b/website/versioned_docs/version-2.0.0-alpha.72/cli.md @@ -0,0 +1,187 @@ +--- +id: cli +title: CLI +--- + +Docusaurus provides a set of scripts to help you generate, serve, and deploy your website. + +Once your website is bootstrapped, the website source will contain the Docusaurus scripts that you can invoke with your package manager: + +```json title="package.json" +{ + // ... + "scripts": { + "docusaurus": "docusaurus", + "start": "docusaurus start", + "build": "docusaurus build", + "swizzle": "docusaurus swizzle", + "deploy": "docusaurus deploy", + "clear": "docusaurus clear", + "serve": "docusaurus serve", + "write-translations": "docusaurus write-translations", + "write-heading-ids": "docusaurus write-heading-ids" + } +} +``` + +## Index + +import TOCInline from "@theme/TOCInline" + +<TOCInline toc={toc[1].children}/> + +## Docusaurus CLI commands + +Below is a list of Docusaurus CLI commands and their usages: + +### `docusaurus start [siteDir]` + +Builds and serves a preview of your site locally with [Webpack Dev Server](https://webpack.js.org/configuration/dev-server). + +#### Options + +| Name | Default | Description | +| --- | --- | --- | +| `--port` | `3000` | Specifies the port of the dev server. | +| `--host` | `localhost` | Specify a host to use. For example, if you want your server to be accessible externally, you can use `--host 0.0.0.0`. | +| `--hot-only` | `false` | Enables Hot Module Replacement without page refresh as fallback in case of build failures. More information [here](https://webpack.js.org/configuration/dev-server/#devserverhotonly). | +| `--no-open` | `false` | Do not open automatically the page in the browser. | +| `--config` | `undefined` | Path to docusaurus config file, default to `[siteDir]/docusaurus.config.js` | +| `--poll [optionalIntervalMs]` | `false` | Use polling of files rather than watching for live reload as a fallback in environments where watching doesn't work. More information [here](https://webpack.js.org/configuration/watch/#watchoptionspoll). | + +:::important + +Please note that some functionality (for example, anchor links) will not work in development. The functionality will work as expected in production. + +::: + +#### Enabling HTTPS` + +There are multiple ways to obtain a certificate. We will use [mkcert](https://github.com/FiloSottile/mkcert) as an example. + +1. Run `mkcert localhost` to generate `localhost.pem` + `localhost-key.pem` + +2. Run `mkcert -install` to install the cert in your trust store, and restart your browser + +3. Start the app with Docusaurus HTTPS env variables: + +```shell +HTTPS=true SSL_CRT_FILE=localhost.pem SSL_KEY_FILE=localhost-key.pem yarn start +``` + +4. Open `https://localhost:3000/` + +### `docusaurus build [siteDir]` + +Compiles your site for production. + +#### Options + +| Name | Default | Description | +| --- | --- | --- | +| `--bundle-analyzer` | `false` | Analyze your bundle with the [webpack bundle analyzer](https://github.com/webpack-contrib/webpack-bundle-analyzer). | +| `--out-dir` | `build` | The full path for the new output directory, relative to the current workspace. | +| `--config` | `undefined` | Path to docusaurus config file, default to `[siteDir]/docusaurus.config.js` | +| `--no-minify` | `false` | Build website without minimizing JS/CSS bundles. | + +:::info + +For advanced minification of CSS bundle, we use the [advanced cssnano preset](https://github.com/cssnano/cssnano/tree/master/packages/cssnano-preset-advanced) (along with additional several PostCSS plugins) and [level 2 optimization of clean-css](https://github.com/jakubpawlowicz/clean-css#level-2-optimizations). If as a result of this advanced CSS minification you find broken CSS, build your website with the environment variable `USE_SIMPLE_CSS_MINIFIER=true` to minify CSS with the [default cssnano preset](https://github.com/cssnano/cssnano/tree/master/packages/cssnano-preset-default). **Please [fill out an issue](https://github.com/facebook/docusaurus/issues/new?labels=bug%2C+needs+triage&template=bug.md) if you experience CSS minification bugs.** + +::: + +### `docusaurus swizzle [siteDir]` + +:::caution + +We highly discourage swizzling of components until we've reached a Beta stage. The components APIs have been changing rapidly and are likely to keep changing until we reach Beta. Stick with the default appearance for now if possible to save yourself some potential pain in future. + +::: + +Change any Docusaurus theme components to your liking with `npm run swizzle`. + +```bash npm2yarn +npm run swizzle [themeName] [componentName] [siteDir] + +# Example (leaving out the siteDir to indicate this directory) +npm run swizzle @docusaurus/theme-classic DocSidebar +``` + +Running the command will copy the relevant theme files to your site folder. You may then make any changes to it and Docusaurus will use it instead of the one provided from the theme. + +`npm run swizzle` without `themeName` lists all the themes available for swizzling similarly `npm run swizzle <themeName>` without `componentName` lists all the components available for swizzling. + +#### Options + +| Name | Description | +| ------------------ | -------------------------------------- | +| `themeName` | The name of the theme you are using. | +| `swizzleComponent` | The name of the component to swizzle. | +| `--danger` | Allow swizzling of unstable components | +| `--typescript` | Swizzle TypeScript components | + +An example to use `--danger` flag let's consider the below code: + +```bash npm2yarn +npm run swizzle @docusaurus/theme-classic Logo -- --danger +``` + +:::caution + +Unstable Components: components that have a higher risk of breaking changes due to internal refactorings. + +::: + +To unswizzle a component, simply delete the files of the swizzled component. + +<!-- +TODO a separate section for swizzle tutorial. +To learn more about swizzling, check [here](#). +--> + +### `docusaurus deploy [siteDir]` + +Deploys your site with [GitHub Pages](https://pages.github.com/). Check out the docs on [deployment](deployment.mdx#deploying-to-github-pages) for more details. + +#### Options + +| Name | Default | Description | +| --- | --- | --- | +| `--out-dir` | `build` | The full path for the new output directory, relative to the current workspace. | +| `--skip-build` | `false` | Deploy website without building it. This may be useful when using custom deploy script. | +| `--config` | `undefined` | Path to docusaurus config file, default to `[siteDir]/docusaurus.config.js` | + +### `docusaurus serve [siteDir]` + +Serve your built website locally. + +| Name | Default | Description | +| --- | --- | --- | +| `--port` | `3000` | Use specified port | +| `--dir` | `build` | The full path for the output directory, relative to the current workspace | +| `--build` | `false` | Build website before serving | +| `--config` | `undefined` | Path to docusaurus config file, default to `[siteDir]/docusaurus.config.js` | +| `--host` | `localhost` | Specify a host to use. For example, if you want your server to be accessible externally, you can use `--host 0.0.0.0`. | + +### `docusaurus clear [siteDir]` + +Clear a Docusaurus site's generated assets, caches, build artifacts. + +We recommend running this command before reporting bugs, after upgrading versions, or anytime you have issues with your Docusaurus site. + +### `docusaurus write-translations [siteDir]` + +Write the JSON translation files that you will have to translate. + +By default, the files are written in `website/i18n/<defaultLocale>/...`. + +| Name | Default | Description | +| --- | --- | --- | +| `--locale` | `<defaultLocale>` | Define which locale folder you want to write translations the JSON files in | +| `--override` | `false` | Override existing translation messages | +| `--config` | `undefined` | Path to docusaurus config file, default to `[siteDir]/docusaurus.config.js` | +| `--messagePrefix` | `''` | Allows to add a prefix to each translation message, to help you highlight untranslated strings | + +### `docusaurus write-heading-ids [siteDir]` + +Add [explicit heading ids](./guides/markdown-features/markdown-features-headings.mdx#explicit-ids) to the Markdown documents of your site. diff --git a/website/versioned_docs/version-2.0.0-alpha.72/configuration.md b/website/versioned_docs/version-2.0.0-alpha.72/configuration.md new file mode 100644 index 0000000000..d59769af18 --- /dev/null +++ b/website/versioned_docs/version-2.0.0-alpha.72/configuration.md @@ -0,0 +1,161 @@ +--- +id: configuration +title: Configuration +--- + +import TOCInline from '@theme/TOCInline'; + +Docusaurus has a unique take on configurations. We encourage you to congregate information of your site into one place. We guard the fields of this file, and facilitate making this data object accessible across your site. + +Keeping a well-maintained `docusaurus.config.js` helps you, your collaborators, and your open source contributors be able to focus on documentation while still being able to customize the site. + +## What goes into a `docusaurus.config.js`? + +You should not have to write your `docusaurus.config.js` from scratch even if you are developing your site. All templates come with a `docusaurus.config.js` that includes defaults for the common options. + +However, it can be helpful if you have a high-level understanding of how the configurations are designed and implemented. + +The high-level overview of Docusaurus configuration can be categorized into: + +<TOCInline toc={toc[0].children} /> + +For exact reference to each of the configurable fields, you may refer to [**`docusaurus.config.js` API reference**](api/docusaurus.config.js.md). + +### Site metadata + +Site metadata contains the essential global metadata such as `title`, `url`, `baseUrl` and `favicon`. + +They are used in a number of places such as your site's title and headings, browser tab icon, social sharing (Facebook, Twitter) information or even to generate the correct path to serve your static files. + +### Deployment configurations + +Deployment configurations such as `projectName` and `organizationName` are used when you deploy your site with the `deploy` command. + +It is recommended to check the [deployment docs](deployment.mdx) for more information. + +### Theme, plugin, and preset configurations + +List the [theme](using-themes.md), [plugins](using-plugins.md), and [presets](presets.md) for your site in the `themes`, `plugins`, and `presets` fields, respectively. These are typically npm packages: + +```js title="docusaurus.config.js" +module.exports = { + // ... + plugins: [ + '@docusaurus/plugin-content-blog', + '@docusaurus/plugin-content-pages', + ], + themes: ['@docusaurus/theme-classic'], +}; +``` + +They can also be loaded from local directories: + +```js title="docusaurus.config.js" +const path = require('path'); + +module.exports = { + // ... + themes: [path.resolve(__dirname, '/path/to/docusaurus-local-theme')], +}; +``` + +To specify options for a plugin or theme, replace the name of the plugin or theme in the config file with an array containing the name and an options object: + +```js title="docusaurus.config.js" +module.exports = { + // ... + plugins: [ + [ + '@docusaurus/plugin-content-blog', + { + path: 'blog', + routeBasePath: 'blog', + include: ['*.md', '*.mdx'], + // ... + }, + ], + '@docusaurus/plugin-content-pages', + ], +}; +``` + +To specify options for a plugin or theme that is bundled in a preset, pass the options through the `presets` field. In this example, `docs` refers to `@docusaurus/plugin-content-docs` and `theme` refers to `@docusaurus/theme-classic`. + +```js title="docusaurus.config.js" +module.exports = { + // ... + presets: [ + [ + '@docusaurus/preset-classic', + { + docs: { + sidebarPath: require.resolve('./sidebars.js'), + }, + theme: { + customCss: [require.resolve('./src/css/custom.css')], + }, + }, + ], + ], +}; +``` + +For further help configuring themes, plugins, and presets, see [Using Themes](using-themes.md), [Using Plugins](using-plugins.md), and [Using Presets](presets.md). + +### Custom configurations + +Docusaurus guards `docusaurus.config.js` from unknown fields. To add custom fields, define them in `customFields`. + +Example: + +```js title="docusaurus.config.js" +module.exports = { + // ... + // highlight-start + customFields: { + image: '', + keywords: [], + }, + // highlight-end + // ... +}; +``` + +## Accessing configuration from components + +Your configuration object will be made available to all the components of your site. And you may access them via React context as `siteConfig`. + +Basic example: + +```jsx +import React from 'react'; +// highlight-next-line +import useDocusaurusContext from '@docusaurus/useDocusaurusContext'; + +const Hello = () => { + // highlight-start + const {siteConfig} = useDocusaurusContext(); + // highlight-end + const {title, tagline} = siteConfig; + + return <div>{`${title} · ${tagline}`}</div>; +}; +``` + +:::tip + +If you just want to use those fields on the client side, you could create your own JS files and import them as ES6 modules, there is no need to put them in `docusaurus.config.js`. + +::: + +## Customizing Babel Configuration + +For new Docusaurus projects, we automatically generated a `babel.config.js` in project root. + +```js title="babel.config.js" +module.exports = { + presets: [require.resolve('@docusaurus/core/lib/babel/preset')], +}; +``` + +Most of the times, this configuration will work just fine. If you want to customize it, you can directly edit this file to customize babel configuration. For your changes to take effect, you need to restart Docusaurus devserver. diff --git a/website/versioned_docs/version-2.0.0-alpha.72/contributing.md b/website/versioned_docs/version-2.0.0-alpha.72/contributing.md new file mode 100644 index 0000000000..130a7f42a9 --- /dev/null +++ b/website/versioned_docs/version-2.0.0-alpha.72/contributing.md @@ -0,0 +1,190 @@ +--- +id: contributing +title: Contributing +--- + +[Docusaurus 2](https://v2.docusaurus.io/) is currently under alpha development. We have [early adopters who already started using it](/showcase). We are now welcoming contributors to collaborate on the next Docusaurus. + +The [Open Source Guides](https://opensource.guide/) website has a collection of resources for individuals, communities, and companies who want to learn how to run and contribute to an open source project. Contributors and people new to open source alike will find the following guides especially useful: + +- [How to Contribute to Open Source](https://opensource.guide/how-to-contribute/) +- [Building Welcoming Communities](https://opensource.guide/building-community/) + +## [Code of Conduct](https://code.fb.com/codeofconduct) + +Facebook has adopted a Code of Conduct that we expect project participants to adhere to. Please read [the full text](https://code.fb.com/codeofconduct) so that you can understand what actions will and will not be tolerated. + +## Get involved + +There are many ways to contribute to Docusaurus, and many of them do not involve writing any code. Here's a few ideas to get started: + +- Start using Docusaurus 2! Go through the [Getting Started](installation.md) guides. Does everything work as expected? If not, we're always looking for improvements. Let us know by [opening an issue](#reporting-new-issues). +- Look through the [v2.0 issues](https://github.com/facebook/docusaurus/labels/v2). If you find an issue you would like to fix, [open a pull request](#your-first-pull-request). Issues tagged as [_Good first issue_](https://github.com/facebook/docusaurus/labels/Good%20first%20issue) are a good place to get started. +- Help us making the docs better. File an issue if you find anything that is confusing or can be improved. We also have [an umbrella issue for v2 docs](https://github.com/facebook/docusaurus/issues/1640) where we are planning and working on all v2 docs. You may adopt a doc piece there to work on. +- Take a look at the [features requested](https://github.com/facebook/docusaurus/labels/enhancement) by others in the community and consider opening a pull request if you see something you want to work on. + +Contributions are very welcome. If you think you need help planning your contribution, please ping us on Twitter at [@docusaurus](https://twitter.com/docusaurus) and let us know you are looking for a bit of help. + +### Join our Discord channel + +To participate in Docusaurus 2 dev, join the [#docusaurus-2-dev](https://discord.gg/Je6Ash6) channel. + +## Our development process + +Docusaurus uses [GitHub](https://github.com/facebook/docusaurus) as its source of truth. The core team will be working directly there. All changes will be public from the beginning. + +When a change made on GitHub is approved, it will be checked by our continuous integration system, CircleCI. + +### Reporting new issues + +When [opening a new issue](https://github.com/facebook/docusaurus/issues/new/choose), always make sure to fill out the issue template. **This step is very important!** Not doing so may result in your issue not managed in a timely fashion. Don't take this personally if this happens, and feel free to open a new issue once you've gathered all the information required by the template. + +- **One issue, one bug:** Please report a single bug per issue. +- **Provide reproduction steps:** List all the steps necessary to reproduce the issue. The person reading your bug report should be able to follow these steps to reproduce your issue with minimal effort. + +### Reporting bugs + +We use [GitHub Issues](https://github.com/facebook/docusaurus/issues) for our public bugs. If you would like to report a problem, take a look around and see if someone already opened an issue about it. If you a are certain this is a new, unreported bug, you can submit a [bug report](#reporting-new-issues). + +If you have questions about using Docusaurus, contact the Docusaurus Twitter account at [@docusaurus](https://twitter.com/docusaurus), and we will do our best to answer your questions. + +You can also file issues as [feature requests or enhancements](https://github.com/facebook/docusaurus/labels/feature). If you see anything you'd like to be implemented, create an issue with [feature template](https://raw.githubusercontent.com/facebook/docusaurus/master/.github/ISSUE_TEMPLATE/feature.md/) + +### Reporting security bugs + +Facebook has a [bounty program](https://www.facebook.com/whitehat/) for the safe disclosure of security bugs. With that in mind, please do not file public issues; go through the process outlined on that page. + +## Working on Docusaurus code + +### Installation + +1. Ensure you have [Yarn](https://yarnpkg.com/) installed +2. After cloning the repository, run `yarn install` in the root of the repository +3. To start a local development server serving the Docusaurus docs, go into the `website` directory and run `yarn start` + +### Semantic commit messages + +See how a minor change to your commit message style can make you a better programmer. + +Format: `<type>(<scope>): <subject>` + +`<scope>` is optional + +**Example** + +``` +feat: allow overriding of webpack config +^--^ ^------------^ +| | +| +-> Summary in present tense. +| ++-------> Type: chore, docs, feat, fix, refactor, style, or test. +``` + +The various types of commits: + +- `feat`: (new feature for the user, not a new feature for build script) +- `fix`: (bug fix for the user, not a fix to a build script) +- `docs`: (changes to the documentation) +- `style`: (formatting, missing semi colons, etc; no production code change) +- `refactor`: (refactoring production code, eg. renaming a variable) +- `test`: (adding missing tests, refactoring tests; no production code change) +- `chore`: (updating grunt tasks etc; no production code change) + +Use lower case not title case! + +### Code conventions + +#### Style guide + +[Prettier](https://prettier.io/) will catch most styling issues that may exist in your code. You can check the status of your code styling by simply running `npm run prettier`. + +However, there are still some styles that Prettier cannot pick up. + +#### General + +- **Most important: Look around.** Match the style you see used in the rest of the project. This includes formatting, naming files, naming things in code, naming things in documentation. +- "Attractive" + +#### Documentation + +- Do not wrap lines at 80 characters - configure your editor to soft-wrap when editing documentation. + +## Pull requests + +### Your first pull request + +So you have decided to contribute code back to upstream by opening a pull request. You've invested a good chunk of time, and we appreciate it. We will do our best to work with you and get the PR looked at. + +Working on your first Pull Request? You can learn how from this free video series: + +[**How to Contribute to an Open Source Project on GitHub**](https://egghead.io/courses/how-to-contribute-to-an-open-source-project-on-github) + +We have a list of [beginner friendly issues](https://github.com/facebook/docusaurus/labels/good%20first%20issue) to help you get your feet wet in the Docusaurus codebase and familiar with our contribution process. This is a great place to get started. + +### Proposing a change + +If you would like to request a new feature or enhancement but are not yet thinking about opening a pull request, you can also file an issue with [feature template](https://github.com/facebook/docusaurus/issues/new?template=feature.md/). + +If you intend to change the public API (e.g., something in `docusaurus.config.js`), or make any non-trivial changes to the implementation, we recommend filing an issue with [proposal template](https://github.com/facebook/docusaurus/issues/new?template=proposal.md) and including `[Proposal]` in the title. This lets us reach an agreement on your proposal before you put significant effort into it. These types of issues should be rare. + +If you're only fixing a bug, it's fine to submit a pull request right away but we still recommend to file an issue detailing what you're fixing. This is helpful in case we don't accept that specific fix but want to keep track of the issue. + +### Sending a pull request + +Small pull requests are much easier to review and more likely to get merged. Make sure the PR does only one thing, otherwise please split it. It is recommended to follow this [commit message style](#semantic-commit-messages). + +Please make sure the following is done when submitting a pull request: + +1. Fork [the repository](https://github.com/facebook/docusaurus) and create your branch from `master`. +1. Add the copyright notice to the top of any code new files you've added. +1. Describe your [test plan](#test-plan) in your pull request description. Make sure to [test your changes](https://github.com/facebook/docusaurus/blob/master/admin/testing-changes-on-Docusaurus-itself.md/)! +1. Make sure your code lints (`yarn prettier && yarn lint`). +1. Make sure your Jest tests pass (`yarn test`). +1. If you haven't already, [sign the CLA](https://code.facebook.com/cla). + +All pull requests should be opened against the `master` branch. + +#### Test plan + +A good test plan has the exact commands you ran and their output, provides screenshots or videos if the pull request changes UI. + +- If you've changed APIs, update the documentation. + +#### Breaking changes + +When adding a new breaking change, follow this template in your pull request: + +```md +### New breaking change here + +- **Who does this affect**: +- **How to migrate**: +- **Why make this breaking change**: +- **Severity (number of people affected x effort)**: +``` + +#### Copyright header for source code + +Copy and paste this to the top of your new file(s): + +```js +/** + * Copyright (c) Facebook, Inc. and its affiliates. + * + * This source code is licensed under the MIT license found in the + * LICENSE file in the root directory of this source tree. + */ +``` + +#### Contributor License Agreement (CLA) + +In order to accept your pull request, we need you to submit a CLA. You only need to do this once, so if you've done this for another Facebook open source project, you're good to go. If you are submitting a pull request for the first time, the Facebook GitHub Bot will reply with a link to the CLA form. You may also [complete your CLA here](https://code.facebook.com/cla). + +### What happens next? + +The core Docusaurus team will be monitoring for pull requests. Do help us by keeping pull requests consistent by following the guidelines above. + +## License + +By contributing to Docusaurus, you agree that your contributions will be licensed under its MIT license. diff --git a/website/versioned_docs/version-2.0.0-alpha.72/deployment.mdx b/website/versioned_docs/version-2.0.0-alpha.72/deployment.mdx new file mode 100644 index 0000000000..1061a21ac6 --- /dev/null +++ b/website/versioned_docs/version-2.0.0-alpha.72/deployment.mdx @@ -0,0 +1,399 @@ +--- +id: deployment +title: Deployment +--- + +To build the static files of your website for production, run: + +```bash npm2yarn +npm run build +``` + +Once it finishes, the static files will be generated within the `build/` directory. + +You can deploy your site to static site hosting services such as [Vercel](https://vercel.com/), [GitHub Pages](https://pages.github.com/), [Netlify](https://www.netlify.com/), [Render](https://render.com/docs/static-sites), and [Surge](https://surge.sh/help/getting-started-with-surge). Docusaurus sites are statically rendered so they work without JavaScript too! + +## Testing Build Local + +It is important to test build before deploying to a production. Docusaurus includes a [`docusaurus serve`](cli.md#docusaurus-serve) command to test build locally. + +```bash npm2yarn +npm run serve +``` + +## Self Hosting + +:::warning + +It is not the most performant solution + +::: + +Docusaurus can be self hosted using [`docusaurus serve`](cli.md#docusaurus-serve). Change port using `--port` and `--host` to change host. + +```bash npm2yarn +npm run serve -- --build --port 80 --host 0.0.0.0 +``` + +## Deploying to GitHub Pages + +Docusaurus provides an easy way to publish to [GitHub Pages](https://pages.github.com/). Which is hosting that comes for free with every GitHub repository. + +### `docusaurus.config.js` settings + +First, modify your `docusaurus.config.js` and add the required params: + +| Name | Description | +| --- | --- | +| `organizationName` | The GitHub user or organization that owns the repository. If you are the owner, it is your GitHub username. In the case of Docusaurus, it is "_facebook_" which is the GitHub organization that owns Docusaurus. | +| `projectName` | The name of the GitHub repository. For example, the repository name for Docusaurus is "docusaurus", so the project name is "docusaurus". | +| `url` | URL for your GitHub Page's user/organization page. This is commonly https://_username_.github.io. | +| `baseUrl` | Base URL for your project. For projects hosted on GitHub pages, it follows the format "/_projectName_/". For https://github.com/facebook/docusaurus, `baseUrl` is `/docusaurus/`. | + +:::info + +In case you want to use your custom domain for GitHub Pages, create a `CNAME` file in the `static` directory. Anything within the `static` directory will be copied to the root of the `build` directory for deployment. + +You may refer to GitHub Pages' documentation [User, Organization, and Project Pages](https://help.github.com/en/articles/user-organization-and-project-pages) for more details. + +::: + +Example: + +```jsx {3-6} title="docusaurus.config.js" +module.exports = { + // ... + url: 'https://endiliey.github.io', // Your website URL + baseUrl: '/', + projectName: 'endiliey.github.io', + organizationName: 'endiliey', + // ... +}; +``` + +:::warning + +By default, GitHub Pages runs published files through [Jekyll](https://jekyllrb.com/). Since Jekyll will discard any files that begin with `_`, it is recommended that you disable Jekyll by adding an empty file named `.nojekyll` file to your `static` directory. + +::: + +### Environment settings + +Specify the Git user as an environment variable. + +| Name | Description | +| --- | --- | +| `GIT_USER` | The username for a GitHub account that has commit access to this repo. For your own repositories, this will usually be your GitHub username. The specified `GIT_USER` must have push access to the repository specified in the combination of `organizationName` and `projectName`. | + +Optional parameters, also set as environment variables: + +| Name | Description | +| --- | --- | +| `USE_SSH` | Set to `true` to use SSH instead of the default HTTPS for the connection to the GitHub repo. | +| `DEPLOYMENT_BRANCH` | The branch that the website will be deployed to, defaults to `gh-pages` for normal repos and `master` for repository names ending in `github.io`. | +| `CURRENT_BRANCH` | The branch that contains the latest docs changes that will be deployed. Usually, the branch will be `master`, but it could be any branch (default or otherwise) except for `gh-pages`. If nothing is set for this variable, then the current branch will be used. | +| `GIT_PASS` | Password (or token) of the `git` user (specified by `GIT_USER`). For example, to facilitate non-interactive deployment (e.g. continuous deployment) | + +GitHub enterprise installations should work in the same manner as github.com; you only need to set the organization's GitHub Enterprise host as an environment veriable: + +| Name | Description | +| ------------- | ----------------------------------------------- | +| `GITHUB_HOST` | The domain name of your GitHub enterprise site. | + +### Deploy + +Finally, to deploy your site to GitHub Pages, run: + +````mdx-code-block +<Tabs + defaultValue="bash" + values={[ + { label: 'Bash', value: 'bash' }, + { label: 'Windows', value: 'windows' }, + { label: 'PowerShell', value: 'powershell' } +]}> +<TabItem value="bash"> + +```bash +GIT_USER=<GITHUB_USERNAME> yarn deploy +``` + +</TabItem> +<TabItem value="windows"> + +```batch +cmd /C "set "GIT_USER=<GITHUB_USERNAME>" && yarn deploy" +``` + +</TabItem> +<TabItem value="powershell"> + +```powershell +cmd /C 'set "GIT_USER=<GITHUB_USERNAME>" && yarn deploy' +``` + +</TabItem> +</Tabs> +```` + +### Triggering deployment with GitHub Actions + +[GitHub Actions](https://help.github.com/en/actions) allow you to automate, customize, and execute your software development workflows right in your repository. + +This workflow assumes your documentation resided in `documentation` branch of your repository and your [publishing source](https://help.github.com/en/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site) is configured for `gh-pages` branch. + +1. Generate a new [SSH key](https://help.github.com/en/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent). +1. By default, your public key should have been created in `~/.ssh/id_rsa.pub` or use the name you've provided in the previous step to add your key to [GitHub deploy keys](https://developer.github.com/v3/guides/managing-deploy-keys/). +1. Copy key to clipboard with `xclip -sel clip < ~/.ssh/id_rsa.pub` and paste it as a [deploy key](https://developer.github.com/v3/guides/managing-deploy-keys/#deploy-keys) in your repository. Copy file content if the command line doesn't work for you. Check the box for `Allow write access` before saving your deployment key. +1. You'll need your private key as a [GitHub secret](https://help.github.com/en/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets) to allow Docusaurus to run the deployment for you. +1. Copy your private key with `xclip -sel clip < ~/.ssh/id_rsa` and paste a GitHub secret with name `GH_PAGES_DEPLOY`. Copy file content if the command line doesn't work for you. Save your secret. +1. Create you [documentation workflow file](https://help.github.com/en/actions/configuring-and-managing-workflows/configuring-a-workflow#creating-a-workflow-file) in `.github/workflows/`. In this example it's `documentation.yml`. + +```yaml title="documentation.yml" +name: documentation + +on: + pull_request: + branches: [documentation] + push: + branches: [documentation] + +jobs: + checks: + if: github.event_name != 'push' + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v1 + - uses: actions/setup-node@v1 + with: + node-version: '12.x' + - name: Test Build + run: | + if [ -e yarn.lock ]; then + yarn install --frozen-lockfile + elif [ -e package-lock.json ]; then + npm ci + else + npm i + fi + npm run build + gh-release: + if: github.event_name != 'pull_request' + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v1 + - uses: actions/setup-node@v1 + with: + node-version: '12.x' + - uses: webfactory/ssh-agent@v0.5.0 + with: + ssh-private-key: ${{ secrets.GH_PAGES_DEPLOY }} + - name: Release to GitHub Pages + env: + USE_SSH: true + GIT_USER: git + run: | + git config --global user.email "actions@github.com" + git config --global user.name "gh-actions" + if [ -e yarn.lock ]; then + yarn install --frozen-lockfile + elif [ -e package-lock.json ]; then + npm ci + else + npm i + fi + npm run deploy +``` + +1. Now when a new pull request arrives towards your repository in branch `documentation` it will automatically ensure that Docusaurus build is successful. +1. When pull request is merged to `documentation` branch or someone pushes to `documentation` branch directly it will be built and deployed to `gh-pages` branch. +1. After this step, your updated documentation will be available on the GitHub pages. + +### Triggering deployment with Travis CI + +Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and deploying changes to your website. All you need to do to automate the deployment of your website is to invoke the `yarn deploy` script whenever your website is updated. The following section covers how to do just that using [Travis CI](https://travis-ci.com/), a popular continuous integration service provider. + +1. Go to https://github.com/settings/tokens and generate a new [personal access token](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/). When creating the token, grant it the `repo` scope so that it has the permissions it needs. +1. Using your GitHub account, [add the Travis CI app](https://github.com/marketplace/travis-ci) to the repository you want to activate. +1. Open your Travis CI dashboard. The URL looks like https://travis-ci.com/USERNAME/REPO, and navigate to the `More options` > `Setting` > `Environment Variables` section of your repository. +1. Create a new environment variable named `GH_TOKEN` with your newly generated token as its value, then `GH_EMAIL` (your email address) and `GH_NAME` (your GitHub username). +1. Create a `.travis.yml` on the root of your repository with the following: + +```yaml title=".travis.yml" +language: node_js +node_js: + - '10' +branches: + only: + - master +cache: + yarn: true +script: + - git config --global user.name "${GH_NAME}" + - git config --global user.email "${GH_EMAIL}" + - echo "machine github.com login ${GH_NAME} password ${GH_TOKEN}" > ~/.netrc + - yarn && GIT_USER="${GH_NAME}" yarn deploy +``` + +Now, whenever a new commit lands in `master`, Travis CI will run your suite of tests and if everything passes, your website will be deployed via the `yarn deploy` script. + +### Using Azure Pipelines + +1. Sign Up at [Azure Pipelines](https://azure.microsoft.com/en-us/services/devops/pipelines/) if you haven't already. +1. Create an organization and within the organization create a project and connect your repository from GitHub. +1. Go to https://github.com/settings/tokens and generate a new [personal access token](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/) with the `repo` scope. +1. In the project page (which looks like https://dev.azure.com/ORG_NAME/REPO_NAME/_build) create a new pipeline with the following text. Also, click on edit and add a new environment variable named `GH_TOKEN` with your newly generated token as its value, then `GH_EMAIL` (your email address) and `GH_NAME` (your GitHub username). Make sure to mark them as secret. Alternatively, you can also add a file named `azure-pipelines.yml` at yout repository root. + +```yaml title="azure-pipelines.yml" +trigger: + - master + +pool: + vmImage: 'ubuntu-latest' + +steps: + - checkout: self + persistCredentials: true + + - task: NodeTool@0 + inputs: + versionSpec: '10.x' + displayName: 'Install Node.js' + + - script: | + git config --global user.name "${GH_NAME}" + git config --global user.email "${GH_EMAIL}" + git checkout -b master + echo "machine github.com login ${GH_NAME} password ${GH_TOKEN}" > ~/.netrc + yarn && GIT_USER="${GH_NAME}" yarn deploy + env: + GH_NAME: $(GH_NAME) + GH_EMAIL: $(GH_EMAIL) + GH_TOKEN: $(GH_TOKEN) + displayName: 'yarn install and build' +``` + +### Using Drone + +1. Create a new ssh key that will be the [deploy key](https://docs.github.com/en/free-pro-team@latest/developers/overview/managing-deploy-keys#deploy-keys) for your project. +1. Name your private and public keys to be specific and so that it does not overwrite your other [ssh keys](https://docs.github.com/en/free-pro-team@latest/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent). +1. Go to https://github.com/USERNAME/REPO/settings/keys and add a new deploy key by pasting in our public key you just generated. +1. Open your Drone.io dashboard and login. The URL looks like https://cloud.drone.io/USERNAME/REPO. +1. Click on the repository, click on activate repository, and add a secret called `git_deploy_private_key` with your private key value that you just generated. +1. Create a `.drone.yml` on the root of your repository with below text. + +```yaml +# .drone.yml +kind: pipeline +type: docker +trigger: + event: + - tag +- name: Website + image: node + commands: + - mkdir -p $HOME/.ssh + - ssh-keyscan -t rsa github.com >> $HOME/.ssh/known_hosts + - echo "$GITHUB_PRIVATE_KEY > $HOME/.ssh/id_rsa" + - chmod 0600 $HOME/.ssh/id_rsa + - cd website + - npm i + - npm run publish-gh-pages + environment: + USE_SSH: true + GIT_USER: $DRONE_COMMIT_AUTHOR + GITHUB_PRIVATE_KEY: git_deploy_private_key +``` + +Now, whenever you push a new tag to github, this trigger will start the drone ci job to publish your website. + +## Deploying to Netlify + +To deploy your Docusaurus 2 sites to [Netlify](https://www.netlify.com/), first make sure the following options are properly configured: + +```js {2-3} title="docusaurus.config.js" +module.exports = { + url: 'https://docusaurus-2.netlify.com', // Url to your site with no trailing slash + baseUrl: '/', // Base directory of your site relative to your repo + // ... +}; +``` + +Then, [create your site with Netlify](https://app.netlify.com/start). + +While you set up the site, specify the build commands and directories as follows: + +- build command: `npm run build` +- build directory: `build` + +If you did not configure these build options, you may still go to "Site settings" -> "Build and deploy" after your site is created. + +Once properly configured with the above options, your site should deploy and automatically redeploy upon merging to your deploy branch, which defaults to `master`. + +:::important + +Make sure to disable Netlify setting `Pretty URLs` to prevent lowercased URLs, unnecessary redirects and 404 errors. + +::: + +## Deploying to Vercel + +Deploying your Docusaurus project to [Vercel](https://vercel.com/) will provide you with [various benefits](https://vercel.com/) in the areas of performance and ease of use. + +To deploy your Docusaurus project with a [Vercel for Git Integration](https://vercel.com/docs/git-integrations), make sure it has been pushed to a Git repository. + +Import the project into Vercel using the [Import Flow](https://vercel.com/import/git). During the import, you will find all relevant options preconfigured for you; however, you can choose to change any of these options, a list of which can be found [here](https://vercel.com/docs/build-step#build-&-development-settings). + +After your project has been imported, all subsequent pushes to branches will generate [Preview Deployments](https://vercel.com/docs/platform/deployments#preview), and all changes made to the [Production Branch](https://vercel.com/docs/git-integrations#production-branch) (commonly "main") will result in a [Production Deployment](https://vercel.com/docs/platform/deployments#production). + +## Deploying to Render + +[Render](https://render.com) offers [free static site hosting](https://render.com/docs/static-sites) with fully managed SSL, custom domains, a global CDN and continuous auto-deploy from your Git repo. Get started in just a few minutes by following [Render's guide to deploying Docusaurus](https://render.com/docs/deploy-docusaurus). + +## Deploying to Surge + +Surge is a [static web hosting platform](https://surge.sh/help/getting-started-with-surge), it is used to deploy your Docusaurus project from the command line in a minute. Deploying your project to Surge is easy and it is also free (including a custom domain and SSL). + +Deploy your app in a matter of seconds using surge with the following steps: + +1. First, install Surge using npm by running the following command: + +```bash +npm install --g surge +``` + +2. To build the static files of your site for production in the root directory of your project, run: + +```bash +npm run build +``` + +3. Then, run this command inside the root directory of your project: + +```bash +surge build/ +``` + +First-time users of Surge would be prompted to create an account from the command line(happens only once). + +Confirm that the site you want to publish is in the `build` directory, a randomly generated subdomain `*.surge.sh subdomain` is always given (which can be edited). + +### Using your domain + +If you have a domain name you can deploy your site using surge to your domain using the command: + +```bash +surge build/ yourdomain.com +``` + +Your site is now deployed for free at `subdomain.surge.sh` or `yourdomain.com` depending on the method you chose. + +### Setting up CNAME file + +Store your domain in a CNAME file for future deployments with the following command: + +```bash +echo subdomain.surge.sh > CNAME +``` + +You can deploy any other changes in the future with the command `surge`. diff --git a/website/versioned_docs/version-2.0.0-alpha.72/design-principles.md b/website/versioned_docs/version-2.0.0-alpha.72/design-principles.md new file mode 100644 index 0000000000..8e85dbfde8 --- /dev/null +++ b/website/versioned_docs/version-2.0.0-alpha.72/design-principles.md @@ -0,0 +1,34 @@ +--- +id: design-principles +title: Design Principles +--- + +:::caution + +This section is a work in progress. + +::: + +- **Little to learn** - Docusaurus should be easy to learn and use as the API is quite small. Most things will still be achievable by users, even if it takes them more code and more time to write. Not having abstractions is better than having the wrong abstractions, and we don't want users to have to hack around the wrong abstractions. Mandatory talk - [Minimal API Surface Area](https://www.youtube.com/watch?v=4anAwXYqLG8). +- **Intuitive** - Users will not feel overwhelmed when looking at the project directory of a Docusaurus project or adding new features. It should look intuitive and easy to build on top of, using approaches they are familiar with. +- **Layered architecture** - The separations of concerns between each layer of our stack (content/theming/styling) should be clear - well-abstracted and modular. +- **Sensible defaults** - Common and popular performance optimizations and configurations will be done for users but they are given the option to override them. +- **No vendor-lock in** - Users are not required to use the default plugins or CSS, although they are highly encouraged to. Certain core lower-level infra level pieces like React Loadable, React Router cannot be swapped because we do default performance optimization on them. But not higher level ones, such as choice of Markdown engines, CSS frameworks, CSS methodology will be entirely up to users. + +## How Docusaurus works + +<!-- moved in from how Docusaurus works @yangshun --> + +We believe that as developers, knowing how a library works is helpful in allowing us to become better at using it. Hence we're dedicating effort into explaining the architecture and various components of Docusaurus with the hope that users reading it will gain a deeper understanding of the tool and be even more proficient in using it. + +<!-- + +Explain the principles that guide the development of Docusaurus. + +References +--- +- https://www.gatsbyjs.org/docs/behind-the-scenes/ +- https://reactjs.org/docs/design-principles.html +- https://v1.vuepress.vuejs.org/miscellaneous/design-concepts.html + +--> diff --git a/website/versioned_docs/version-2.0.0-alpha.72/docusaurus-core.md b/website/versioned_docs/version-2.0.0-alpha.72/docusaurus-core.md new file mode 100644 index 0000000000..b9ea6e3c1f --- /dev/null +++ b/website/versioned_docs/version-2.0.0-alpha.72/docusaurus-core.md @@ -0,0 +1,540 @@ +--- +id: docusaurus-core +title: Docusaurus Client API +sidebar_label: Client API +--- + +Docusaurus provides some APIs on the clients that can be helpful to you when building your site. + +## Components + +### `<Head/>` + +This reusable React component will manage all of your changes to the document head. It takes plain HTML tags and outputs plain HTML tags and is beginner-friendly. It is a wrapper around [React Helmet](https://github.com/nfl/react-helmet). + +Usage Example: + +```jsx {2,5,10} +import React from 'react'; +import Head from '@docusaurus/Head'; + +const MySEO = () => ( + <Head> + <meta property="og:description" content="My custom description" /> + <meta charSet="utf-8" /> + <title>My Title + + +); +``` + +Nested or latter components will override duplicate usages: + +```jsx {2,5,8,11} + + + My Title + + + + + Nested Title + + + + +``` + +Outputs: + +```html + + Nested Title + + +``` + +### `` + +This component enables linking to internal pages as well as a powerful performance feature called preloading. Preloading is used to prefetch resources so that the resources are fetched by the time the user navigates with this component. We use an `IntersectionObserver` to fetch a low-priority request when the `` is in the viewport and then use an `onMouseOver` event to trigger a high-priority request when it is likely that a user will navigate to the requested resource. + +The component is a wrapper around react-router’s `` component that adds useful enhancements specific to Docusaurus. All props are passed through to react-router’s `` component. + +```jsx {2,7} +import React from 'react'; +import Link from '@docusaurus/Link'; + +const Page = () => ( +
+

+ Check out my blog! +

+

+ {/* Note that external links still use `a` tags, but automatically opens in new tab. */} + Follow me on Twitter! +

+
+); +``` + +#### `to`: string + +The target location to navigate to. Example: `/docs/introduction`. + +```jsx + +``` + +### `` + +Rendering a `` will navigate to a new location. The new location will override the current location in the history stack, like server-side redirects (HTTP 3xx) do. You can refer to [React Router's Redirect documentation](https://reacttraining.com/react-router/web/api/Redirect) for more info on available props. + +Example usage: + +```jsx {2,5} +import React from 'react'; +import {Redirect} from '@docusaurus/router'; + +const Home = () => { + return ; +}; +``` + +:::note + +`@docusaurus/router` implements [React Router](https://reacttraining.com/react-router/web/guides/quick-start) and supports its features. + +::: + +### `` + +The `` component accepts a `children` prop, a render function which will not be executed during the pre-rendering phase of the build process. This is useful for hiding code that is only meant to run in the browsers (e.g. where the `window`/`document` objects are being accessed). To improve SEO, you can also provide fallback content using the `fallback` prop, which will be prerendered until in the build process and replaced with the client-side only contents when viewed in the browser. + +```jsx {1,5-10} +import BrowserOnly from '@docusaurus/BrowserOnly'; + +const MyComponent = () => { + return ( + The fallback content to display on prerendering}> + {() => { + // Something that should be excluded during build process prerendering. + }} + + ); +}; +``` + +### `` + +A simple interpolation component for text containing dynamic placeholders. + +The placeholders will be replaced with the provided dynamic values and JSX elements of your choice (strings, links, styled elements...). + +#### Props + +- `children`: text containing interpolation placeholders like `{placeholderName}` +- `values`: object containing interpolation placeholder values + +```jsx +import React from 'react'; +import Link from '@docusaurus/Link'; +import Interpolate from '@docusaurus/Interpolate'; + +export default function VisitMyWebsiteMessage() { + return ( + // highlight-start + + website + + ), + }}> + {'Hello, {firstName}! How are you? Take a look at my {website}'} + + // highlight-end + ); +} +``` + +### `` + +When [localizing your site](./i18n/i18n-introduction.md), the `` component will allow providing **translation support to React components**, such as your homepage. The `` component supports [interpolation](#interpolate). + +The translation strings will be extracted from your code with the [`docusaurus write-translations`](./cli.md#docusaurus-write-translations) CLI and create a `code.json` translation file in `website/i18n/`. + +:::note + +The `` props **must be hardcoded strings**. + +Apart the `values` prop used for interpolation, it is **not possible to use variables**, or the static extraction wouldn't work. + +::: + +#### Props + +- `children`: untranslated string in the default site locale (can contain [interpolation placeholders](#interpolate)) +- `id`: optional value to use as key in JSON translation files +- `description`: optional text to help the translator +- `values`: optional object containing interpolation placeholder values + +#### Example + +```jsx title="src/index.js" +import React from 'react'; +import Layout from '@theme/Layout'; + +// highlight-start +import Translate from '@docusaurus/Translate'; +// highlight-end + +export default function Home() { + return ( + +

+ {/* highlight-start */} + + Welcome to my website + + {/* highlight-end */} +

+
+ {/* highlight-start */} + + {'Welcome, {firstName}! How are you?'} + + {/* highlight-end */} +
+ + ); +} +``` + +## Hooks + +### `useDocusaurusContext` + +React hook to access Docusaurus Context. Context contains `siteConfig` object from [docusaurus.config.js](api/docusaurus.config.js.md), and some additional site metadata. + +```ts +type DocusaurusPluginVersionInformation = + | {readonly type: 'package'; readonly version?: string} + | {readonly type: 'project'} + | {readonly type: 'local'} + | {readonly type: 'synthetic'}; + +interface DocusaurusSiteMetadata { + readonly docusaurusVersion: string; + readonly siteVersion?: string; + readonly pluginVersions: Record; +} + +interface DocusaurusContext { + siteConfig: DocusaurusConfig; + siteMetadata: DocusaurusSiteMetadata; +} +``` + +Usage example: + +```jsx {5,8-10} +import React from 'react'; +import useDocusaurusContext from '@docusaurus/useDocusaurusContext'; + +const MyComponent = () => { + const {siteConfig, siteMetadata} = useDocusaurusContext(); + return ( +
+

{siteConfig.title}

+
{siteMetadata.siteVersion}
+
{siteMetadata.docusaurusVersion}
+
+ ); +}; +``` + +### `useBaseUrl` + +React hook to prepend your site `baseUrl` to a string. + +:::caution + +**Don't use it for regular links!** + +The `/baseUrl/` prefix is automatically added to all **absolute paths** by default: + +- Markdown: `[link](/my/path)` will link to `/baseUrl/my/path` +- React: `link` will link to `/baseUrl/my/path` + +::: + +#### Options + +```ts +type BaseUrlOptions = { + forcePrependBaseUrl: boolean; + absolute: boolean; +}; +``` + +#### Example usage: + +```jsx +import React from 'react'; +import useBaseUrl from '@docusaurus/useBaseUrl'; + +const SomeImage = () => { + // highlight-start + const imgSrc = useBaseUrl('/img/myImage.png'); + // highlight-end + return ; +}; +``` + +:::tip + +In most cases, you don't need `useBaseUrl`. + +Prefer a `require()` call for [assets](./guides/markdown-features/markdown-features-assets.mdx): + +```jsx + +``` + +::: + +### `useBaseUrlUtils` + +Sometimes `useBaseUrl` is not good enough. This hook return additional utils related to your site's base url. + +- `withBaseUrl`: useful if you need to add base urls to multiple urls at once. + +```jsx +import React from 'react'; +import {useBaseUrlUtils} from '@docusaurus/useBaseUrl'; + +const Component = () => { + const urls = ['/a', '/b']; + // highlight-start + const {withBaseUrl} = useBaseUrlUtils(); + const urlsWithBaseUrl = urls.map(withBaseUrl); + // highlight-end + return
{/* ... */}
; +}; +``` + +### `useGlobalData` + +React hook to access Docusaurus global data created by all the plugins. + +Global data is namespaced by plugin name, and plugin id. + +:::info + +Plugin id is only useful when a plugin is used multiple times on the same site. Each plugin instance is able to create its own global data. + +::: + +```ts +type GlobalData = Record< + PluginName, + Record< + PluginId, // "default" by default + any // plugin-specific data + > +>; +``` + +Usage example: + +```jsx {2,5-7} +import React from 'react'; +import useGlobalData from '@docusaurus/useGlobalData'; + +const MyComponent = () => { + const globalData = useGlobalData(); + const myPluginData = globalData['my-plugin']['default']; + return
{myPluginData.someAttribute}
; +}; +``` + +:::tip + +Inspect your site's global data at `./docusaurus/globalData.json` + +::: + +### `usePluginData` + +Access global data created by a specific plugin instance. + +This is the most convenient hook to access plugin global data, and should be used most of the time. + +`pluginId` is optional if you don't use multi-instance plugins. + +```ts +usePluginData(pluginName: string, pluginId?: string) +``` + +Usage example: + +```jsx {2,5-6} +import React from 'react'; +import {usePluginData} from '@docusaurus/useGlobalData'; + +const MyComponent = () => { + const myPluginData = usePluginData('my-plugin'); + return
{myPluginData.someAttribute}
; +}; +``` + +### `useAllPluginInstancesData` + +Access global data created by a specific plugin. Given a plugin name, it returns the data of all the plugins instances of that name, by plugin id. + +```ts +useAllPluginInstancesData(pluginName: string) +``` + +Usage example: + +```jsx {2,5-7} +import React from 'react'; +import {useAllPluginInstancesData} from '@docusaurus/useGlobalData'; + +const MyComponent = () => { + const allPluginInstancesData = useAllPluginInstancesData('my-plugin'); + const myPluginData = allPluginInstancesData['default']; + return
{myPluginData.someAttribute}
; +}; +``` + +## Functions + +### `interpolate` + +The imperative counterpart of the [``](#interpolate) component. + +#### Signature + +```ts +// Simple string interpolation +function interpolate(text: string, values: Record): string; + +// JSX interpolation +function interpolate( + text: string, + values: Record, +): ReactNode; +``` + +#### Example + +```jsx +// highlight-start +import {interpolate} from '@docusaurus/Interpolate'; +// highlight-end + +const message = interpolate('Welcome {firstName}', {firstName: 'Sébastien'}); +``` + +### `translate` + +The imperative counterpart of the [``](#translate) component. Also supporting [placeholders interpolation](#interpolate). + +:::tip + +Use the imperative API for the **rare cases** where a **component cannot be used**, such as: + +- the page `title` metadata +- the `placeholder` props of form inputs +- the `aria-label` props for accessibility + +::: + +#### Signature + +```ts +function translate( + translation: {message: string; id?: string; description?: string}, + values: Record, +): string; +``` + +#### Example + +```jsx title="src/index.js" +import React from 'react'; +import Layout from '@theme/Layout'; + +// highlight-start +import {translate} from '@docusaurus/Translate'; +// highlight-end + +export default function Home() { + return ( + + + + ); +} +``` + +## Modules + +### `ExecutionEnvironment` + +A module which exposes a few boolean variables to check the current rendering environment. Useful if you want to only run certain code on client/server or need to write server-side rendering compatible code. + +```jsx {2,5} +import React from 'react'; +import ExecutionEnvironment from '@docusaurus/ExecutionEnvironment'; + +const MyPage = () => { + const location = ExecutionEnvironment.canUseDOM ? window.location.href : null; + return
{location}
; +}; +``` + +| Field | Description | +| --- | --- | +| `ExecutionEnvironment.canUseDOM` | `true` if on client, `false` if prerendering. | +| `ExecutionEnvironment.canUseEventListeners` | `true` if on client and has `window.addEventListener`. | +| `ExecutionEnvironment.canUseIntersectionObserver` | `true` if on client and has `IntersectionObserver`. | +| `ExecutionEnvironment.canUseViewport` | `true` if on client and has `window.screen`. | + +### `constants` + +A module exposing useful constants to client-side theme code. + +```jsx +import {DEFAULT_PLUGIN_ID} from '@docusaurus/constants'; +``` + +| Named export | Value | +| ------------------- | --------- | +| `DEFAULT_PLUGIN_ID` | `default` | diff --git a/website/versioned_docs/version-2.0.0-alpha.72/guides/creating-pages.md b/website/versioned_docs/version-2.0.0-alpha.72/guides/creating-pages.md new file mode 100644 index 0000000000..d90215dfc5 --- /dev/null +++ b/website/versioned_docs/version-2.0.0-alpha.72/guides/creating-pages.md @@ -0,0 +1,122 @@ +--- +id: creating-pages +title: Creating Pages +slug: /creating-pages +--- + +In this section, we will learn about creating ad-hoc pages in Docusaurus using React. This is most useful for creating one-off standalone pages like a showcase page, playground page or support page. + +The functionality of pages is powered by `@docusaurus/plugin-content-pages`. + +You can use React components, or Markdown. + +## Add a React page + +Create a file `/src/pages/helloReact.js`: + +```jsx title="/src/pages/helloReact.js" +import React from 'react'; +import Layout from '@theme/Layout'; + +function Hello() { + return ( + +
+

+ Edit pages/hello.js and save to reload. +

+
+ + ); +} + +export default Hello; +``` + +Once you save the file, the development server will automatically reload the changes. Now open `http://localhost:3000/helloReact`, you will see the new page you just created. + +Each page doesn't come with any styling. You will need to import the `Layout` component from `@theme/Layout` and wrap your contents within that component if you want the navbar and/or footer to appear. + +:::tip + +You can also create TypeScript pages with the `.tsx` extension (`helloReact.tsx`). + +::: + +## Add a Markdown page + +Create a file `/src/pages/helloMarkdown.md`: + +```mdx title="/src/pages/helloMarkdown.md" +--- +title: my hello page title +description: my hello page description +hide_table_of_contents: true +--- + +# Hello + +How are you? +``` + +In the same way, a page will be created at `http://localhost:3000/helloMarkdown`. + +Markdown pages are less flexible than React pages, because it always uses the theme layout. + +Here's an [example Markdown page](/examples/markdownPageExample). + +:::tip + +You can use the full power of React in Markdown pages too, refer to the [MDX](https://mdxjs.com/) documentation. + +::: + +## Routing + +If you are familiar with other static site generators like Jekyll and Next, this routing approach will feel familiar to you. Any JavaScript file you create under `/src/pages/` directory will be automatically converted to a website page, following the `/src/pages/` directory hierarchy. For example: + +- `/src/pages/index.js` → `` +- `/src/pages/foo.js` → `/foo` +- `/src/pages/foo/test.js` → `/foo/test` +- `/src/pages/foo/index.js` → `/foo/` + +In this component-based development era, it is encouraged to co-locate your styling, markup and behavior together into components. Each page is a component, and if you need to customize your page design with your own styles, we recommend co-locating your styles with the page component in its own directory. For example, to create a "Support" page, you could do one of the following: + +- Add a `/src/pages/support.js` file +- Create a `/src/pages/support/` directory and a `/src/pages/support/index.js` file. + +The latter is preferred as it has the benefits of letting you put files related to the page within that directory. For example, a CSS module file (`styles.module.css`) with styles meant to only be used on the "Support" page. **Note:** this is merely a recommended directory structure and you will still need to manually import the CSS module file within your component module (`support/index.js`). By default, any Markdown or Javascript file starting with `_` will be ignored, and no routes will be created for that file (see the `exclude` option). + +```sh +my-website +├── src +│ └── pages +│ ├── styles.module.css +│ ├── index.js +| ├──_ignored.js +│ └── support +│ ├── index.js +│ └── styles.module.css +. +``` + +:::caution + +All JavaScript/TypeScript files within the `src/pages/` directory will have corresponding website paths generated for them. If you want to create reusable components into that directory, use the `exclude` option (by default, files prefixed with `_`, test files(`.test.js`) and files in `__tests__` directory are not turned into pages). + +::: + +## Using React + +React is used as the UI library to create pages. Every page component should export a React component, and you can leverage on the expressiveness of React to build rich and interactive content. + +## Duplicate Routes + +You may accidentally create multiple pages that are meant to be accessed on the same route. When this happens, Docusaurus will warn you about duplicate routes when you run `yarn start` or `yarn build`, but the site will still be built successfully. The page that was created last will be accessible, but it will override other conflicting pages. To resolve this issue, you should modify or remove any conflicting routes. diff --git a/website/versioned_docs/version-2.0.0-alpha.72/guides/docs/docs-create-doc.mdx b/website/versioned_docs/version-2.0.0-alpha.72/guides/docs/docs-create-doc.mdx new file mode 100644 index 0000000000..49841e7158 --- /dev/null +++ b/website/versioned_docs/version-2.0.0-alpha.72/guides/docs/docs-create-doc.mdx @@ -0,0 +1,79 @@ +--- +id: create-doc +title: Create a doc +description: Create a Markdown Document +slug: /create-doc +--- + +Create a markdown file, `greeting.md`, and place it under the `docs` directory. + +```bash +website # root directory of your site +├── docs +│   └── greeting.md +├── src +│   └── pages +├── docusaurus.config.js +├── ... +``` + +At the top of the file, specify `id` and `title` in the front matter, so that Docusaurus will pick them up correctly when generating your site. + +```yml +--- +id: greeting +title: Hello +--- + +## Hello from Docusaurus + +Are you ready to create the documentation site for your open source project? + +### Headers + +will show up on the table of contents on the upper right + +So that your users will know what this page is all about without scrolling down or even without reading too much. + +### Only h2 and h3 will be in the toc + +The headers are well-spaced so that the hierarchy is clear. + +- lists will help you +- present the key points +- that you want your users to remember + - and you may nest them + - multiple times + +### Custom id headers {#custom-id} + +With `{#custom-id}` syntax you can set your own header id. +``` + +This will render in the browser as follows: + +import BrowserWindow from '@site/src/components/BrowserWindow'; + + + +

Hello from Docusaurus

+ +Are you ready to create the documentation site for your open source project? + +

Headers

+ +will show up on the table of contents on the upper right + +So that your users will know what this page is all about without scrolling down or even without reading too much. + +

Only h2 and h3 will be in the toc

+ +The headers are well-spaced so that the hierarchy is clear. + +- lists will help you +- present the key points +- that you want your users to remember + - and you may nest them + - multiple times + + diff --git a/website/versioned_docs/version-2.0.0-alpha.72/guides/docs/docs-introduction.md b/website/versioned_docs/version-2.0.0-alpha.72/guides/docs/docs-introduction.md new file mode 100644 index 0000000000..b56c7a561c --- /dev/null +++ b/website/versioned_docs/version-2.0.0-alpha.72/guides/docs/docs-introduction.md @@ -0,0 +1,80 @@ +--- +id: introduction +title: Docs Introduction +sidebar_label: Introduction +slug: /docs-introduction +--- + +The docs feature provides users with a way to organize Markdown files in a hierarchical format. + +## Document ID + +Every document has a unique `id`. By default, a document `id` is the name of the document (without the extension) relative to the root docs directory. + +For example, `greeting.md` id is `greeting` and `guide/hello.md` id is `guide/hello`. + +```bash +website # Root directory of your site +└── docs +   ├── greeting.md + └── guide + └── hello.md +``` + +However, the **last part** of the `id` can be defined by user in the front matter. For example, if `guide/hello.md`'s content is defined as below, its final `id` is `guide/part1`. + +```yml +--- +id: part1 +--- +Lorem ipsum +``` + +If you want more control over the last part of the document URL, it is possible to add a `slug` (defaults to the `id`). + +```yml +--- +id: part1 +slug: part1.html +--- +Lorem ipsum +``` + +:::note + +It is possible to use: + +- absolute slugs: `slug: /mySlug`, `slug: /`... +- relative slugs: `slug: mySlug`, `slug: ./../mySlug`... + +::: + +## Home page docs + +If you want a document to be available at the root, and have a path like `https://v2.docusaurus.io/docs/`, you can use the slug frontmatter: + +```yml +--- +id: my-home-doc +slug: / +--- +Lorem ipsum +``` + +## Docs-only mode + +If you only want the documentation feature, you can run your Docusaurus 2 site without a landing page and display your documentation page as the index page instead. + +To enable docs-only mode, set the docs plugin `routeBasePath: '/'`, and use the frontmatter `slug: /` on the document that should be the index page ([more infos](#home-page-docs)). + +:::caution + +You should delete the existing homepage at `./src/pages/index.js`, or else there will be two files mapping to the same route! + +::: + +:::tip + +There's also a "blog-only mode" for those who only want to use the blog feature of Docusaurus 2. You can use the same method detailed above. Follow the setup instructions on [Blog-only mode](../../blog.md#blog-only-mode). + +::: diff --git a/website/versioned_docs/version-2.0.0-alpha.72/guides/docs/docs-markdown-features.mdx b/website/versioned_docs/version-2.0.0-alpha.72/guides/docs/docs-markdown-features.mdx new file mode 100644 index 0000000000..0035a655f2 --- /dev/null +++ b/website/versioned_docs/version-2.0.0-alpha.72/guides/docs/docs-markdown-features.mdx @@ -0,0 +1,28 @@ +--- +id: markdown-features +title: Docs Markdown Features +description: Docusaurus Markdown features that are specific to the docs plugin +slug: /docs-markdown-features +--- + +Docs can use any [Markdown feature](../markdown-features/markdown-features-intro.mdx), and have a few additional Docs-specific markdown features. + +## Markdown frontmatter + +Markdown docs have their own [Markdown frontmatter](../../api/plugins/plugin-content-docs.md#markdown-frontmatter) + +## Referencing other documents + +If you want to reference another document file, you could use the name of the document you want to reference. Docusaurus will convert the file path to be the final website path (and remove the `.md`). + +For example, if you are in `doc2.md` and you want to reference `doc1.md` and `folder/doc3.md`: + +```md +I am referencing a [document](doc1.md). Reference to another [document in a folder](folder/doc3.md). + +[Relative document](../doc2.md) referencing works as well. +``` + +One benefit of this approach is that the links to external files will still work if you are viewing the file on GitHub. + +Another benefit, for versioned docs, is that one versioned doc will link to another doc of the exact same version. diff --git a/website/versioned_docs/version-2.0.0-alpha.72/guides/docs/docs-multi-instance.mdx b/website/versioned_docs/version-2.0.0-alpha.72/guides/docs/docs-multi-instance.mdx new file mode 100644 index 0000000000..a498952474 --- /dev/null +++ b/website/versioned_docs/version-2.0.0-alpha.72/guides/docs/docs-multi-instance.mdx @@ -0,0 +1,212 @@ +--- +id: multi-instance +title: Docs Multi-instance +description: Use multiple docs plugin instances on a single Docusaurus site. +slug: /docs-multi-instance +--- + +The `@docusaurus/plugin-content-docs` plugin can support [multi-instance](../../using-plugins.md#multi-instance-plugins-and-plugin-ids). + +:::note + +This feature is only useful for [versioned documentations](./versioning.md). It is recommended to be familiar with docs versioning before reading this page. + +::: + +## Use-cases + +Sometimes you want a Docusaurus site to host 2 distinct sets of documentation (or more). + +These documentations may even have different versioning/release lifecycles. + +### Mobile SDKs documentation + +If you build a cross-platform mobile SDK, you may have 2 documentations: + +- Android SDK documentation (`v1.0`, `v1.1`) +- iOS SDK documentation (`v1.0`, `v2.0`) + +In such case, you can use a distinct docs plugin instance per mobile SDK documentation. + +:::caution + +If each documentation instance is very large, you should rather create 2 distinct Docusaurus sites. + +If someone edits the iOS documentation, is it really useful to rebuild everything, including the whole Android documentation that did not change? + +::: + +### Versioned and unversioned doc + +Sometimes, you want some documents to be versioned, while other documents are more "global", and it feels useless to version them. + +We use this pattern on the Docusaurus website itself: + +- The [/docs/\*](/docs) section is versioned +- The [/community/\*](/community/support) section is unversioned + +## Setup + +Let's consider we 2 documentations: + +- Product: some versioned doc about your product +- Community: some unversioned doc about the community around your product + +You have to use twice the same plugin in your site configuration. + +:::caution + +`@docusaurus/preset-classic` already includes a docs plugin instance for you! + +::: + +When using the preset: + +```js title="docusaurus.config.js" +module.exports = { + presets: [ + [ + '@docusaurus/preset-classic', + { + docs: { + // highlight-start + // id: 'product', // omitted => default instance + // highlight-end + path: 'product', + routeBasePath: 'product', + sidebarPath: require.resolve('./sidebarsProduct.js'), + // ... other options + }, + }, + ], + ], + plugins: [ + [ + '@docusaurus/plugin-content-docs', + { + // highlight-start + id: 'community', + // highlight-end + path: 'community', + routeBasePath: 'community', + sidebarPath: require.resolve('./sidebarsCommunity.js'), + // ... other options + }, + ], + ], +}; +``` + +When not using the preset: + +```js title="docusaurus.config.js" +module.exports = { + plugins: [ + [ + '@docusaurus/plugin-content-docs', + { + // highlight-start + // id: 'product', // omitted => default instance + // highlight-end + path: 'product', + routeBasePath: 'product', + sidebarPath: require.resolve('./sidebarsProduct.js'), + // ... other options + }, + ], + [ + '@docusaurus/plugin-content-docs', + { + // highlight-start + id: 'community', + // highlight-end + path: 'community', + routeBasePath: 'community', + sidebarPath: require.resolve('./sidebarsCommunity.js'), + // ... other options + }, + ], + ], +}; +``` + +Don't forget to assign a unique `id` attribute to plugin instances. + +:::note + +We consider that the `product` instance is the most important one, and make it the "default" instance by not assigning any id. + +::: + +## Versioned paths + +Each instance will store versioned docs in a distinct folder. + +The default plugin instance will use these paths: + +- `website/versions.json` +- `website/versioned_docs` +- `website/versioned_sidebars` + +The other plugin instances (with an `id` attribute) will use these paths: + +- `website/_versions.json` +- `website/_versioned_docs` +- `website/_versioned_sidebars` + +:::tip + +You can omit the `id` attribute (defaults to `default`) for one of the docs plugin instances. + +The instance paths will be simpler, and retro-compatible with a single-instance setup. + +::: + +## Tagging new versions + +Each plugin instance will have its own cli command to tag a new version. They will be displayed if you run: + +```bash npm2yarn +npm run docusaurus -- --help +``` + +To version the product/default docs plugin instance: + +```bash npm2yarn +npm run docusaurus docs:version 1.0.0 +``` + +To version the non-default/community docs plugin instance: + +```bash npm2yarn +npm run docusaurus docs:version:community 1.0.0 +``` + +## Docs navbar items + +Each docs-related [theme navbar items](../../api/themes/theme-configuration.md#navbar) take an optional `docsPluginId` attribute. + +For example, if you want to have one version dropdown for each mobile SDK (iOS and Android), you could do: + +```js title="docusaurus.config.js" +module.exports = { + themeConfig: { + navbar: { + items: [ + { + type: 'docsVersionDropdown', + // highlight-start + docsPluginId: 'ios', + // highlight-end + }, + { + type: 'docsVersionDropdown', + // highlight-start + docsPluginId: 'android', + // highlight-end + }, + ], + }, + }, +}; +``` diff --git a/website/versioned_docs/version-2.0.0-alpha.72/guides/docs/sidebar.md b/website/versioned_docs/version-2.0.0-alpha.72/guides/docs/sidebar.md new file mode 100644 index 0000000000..f7267581f5 --- /dev/null +++ b/website/versioned_docs/version-2.0.0-alpha.72/guides/docs/sidebar.md @@ -0,0 +1,323 @@ +--- +id: sidebar +title: Sidebar +slug: /sidebar +--- + +To generate a sidebar to your Docusaurus site: + +1. Define a file that exports a [sidebar object](#sidebar-object). +1. Pass this object into the `@docusaurus/plugin-docs` plugin directly or via `@docusaurus/preset-classic`. + +```js {8-9} title="docusaurus.config.js" +module.exports = { + // ... + presets: [ + [ + '@docusaurus/preset-classic', + { + docs: { + // Sidebars filepath relative to the site dir. + sidebarPath: require.resolve('./sidebars.js'), + }, + // ... + }, + ], + ], +}; +``` + +## Sidebar object + +A sidebar object contains [sidebar items](#understanding-sidebar-items) and it is defined like this: + +```typescript +type Sidebar = { + [sidebarId: string]: + | { + [sidebarCategory: string]: SidebarItem[]; + } + | SidebarItem[]; +}; +``` + +For example: + +```js title="sidebars.js" +module.exports = { + docs: [ + { + type: 'category', + label: 'Getting Started', + items: ['greeting'], + }, + { + type: 'category', + label: 'Docusaurus', + items: ['doc1'], + }, + ], +}; +``` + +In this example, notice the following: + +- The key `docs` is the id of the sidebar. The id can be any value, not necessarily `docs`. +- `Getting Started` is a category within the sidebar. +- `greeting` and `doc1` are both [sidebar item](#sidebar-item). + +Shorthand notation can also be used: + +```js title="sidebars.js" +module.exports = { + docs: { + 'Getting started': ['greeting'], + Docusaurus: ['doc1'], + }, +}; +``` + +:::note + +Shorthand notation relies on the iteration order of JavaScript object keys for the category name. When using this notation, keep in mind that EcmaScript does not guarantee `Object.keys({a,b}) === ['a','b']`, yet this is generally true. + +::: + +## Using multiple sidebars + +You can have multiple sidebars for different Markdown files by adding more top-level keys to the exported object. + +Example: + +```js title="sidebars.js" +module.exports = { + firstSidebar: { + 'Category A': ['doc1'], + }, + secondSidebar: { + 'Category A': ['doc2'], + 'Category B': ['doc3'], + }, +}; +``` + +By default, the doc page the user is reading will display the sidebar that it is part of. This can be customized with the [sidebar type](#understanding-sidebar-items). + +For example, with the above example, when displaying the `doc2` page, the sidebar will contain the items of `secondSidebar` only. Another example of multiple sidebars is the `API` and `Docs` sections on the Docusaurus website. + +For more information about sidebars and how they relate to doc pages, see [Navbar doc link](../../api/themes/theme-configuration.md#navbar-doc-link). + +## Understanding sidebar items + +As the name implies, `SidebarItem` is an item defined in a Sidebar. A SidebarItem as a `type` that defines what the item links to. + +`type` supports the following values + +- [Doc](#linking-to-a-doc-page) +- [Link](#creating-a-generic-link) +- [Ref](#creating-a-link-to-page-without-sidebar) +- [Category](#creating-a-hierarchy) + +### Linking to a doc page + +Set `type` to `doc` to link to a documentation page. This is the default type. + +```typescript +type SidebarItemDoc = + | string + | { + type: 'doc'; + id: string; + }; +``` + +Example: + +```js +{ + type: 'doc', + id: 'doc1', // string - document id +} +``` + +Using just the [Document ID](#document-id) is also valid, the following is equivalent to the above: + +```js +'doc1'; // string - document id + +``` + +Using this type will bind the linked doc to current sidebar. This means that if you access the `doc1` page, the sidebar displayed will be the sidebar that contains this doc page. + +In the example below, `doc1` is bound to `firstSidebar`. + +```js title="sidebars.js" +module.exports = { + firstSidebar: { + 'Category A': ['doc1'], + }, + secondSidebar: { + 'Category A': ['doc2'], + 'Category B': ['doc3'], + }, +}; +``` + +### Creating a generic link + +Set `type` to `link` to link to a non-documentation page. For example, to create an external link. + +```typescript +type SidebarItemLink = { + type: 'link'; + label: string; + href: string; +}; +``` + +Example: + +```js +{ + type: 'link', + label: 'Custom Label', // The label that should be displayed (string). + href: 'https://example.com' // The target URL (string). +} +``` + +### Creating a link to page without sidebar + +Set `type` to `ref` to link to a documentation page without binding it to a sidebar. This means the sidebar disappears when the user displays the linked page. + +```typescript +type SidebarItemRef = { + type: 'ref'; + id: string; +}; +``` + +Example: + +```js +{ + type: 'ref', + id: 'doc1', // Document id (string). +} +``` + +### Creating a hierarchy + +The Sidebar item type that creates a hierarchy in the sidebar. Set `type` to `category`. + +```typescript +type SidebarItemCategory = { + type: 'category'; + label: string; // Sidebar label text. + items: SidebarItem[]; // Array of sidebar items. + collapsed: boolean; // Set the category to be collapsed or open by default +}; +``` + +Example: + +```js title="sidebars.js" +module.exports = { + docs: [ + { + ... + }, + { + type: 'category', + label: 'Guides', + items: [ + 'guides/creating-pages', + { + Docs: ['docs-introduction', 'docs-sidebar', 'markdown-features', 'versioning'], + }, + ], + }, + ], +}; +``` + +**Note**: it's possible to use the shorthand syntax to create nested categories: + +```js title="sidebars.js" +module.exports = { + docs: { + Guides: [ + 'creating-pages', + { + Docs: [ + 'docs-introduction', + 'docs-sidebar', + 'markdown-features', + 'versioning', + ], + }, + ], + }, +}; +``` + +#### Collapsible categories + +For sites with a sizable amount of content, we support the option to expand/collapse a category to toggle the display of its contents. Categories are collapsible by default. If you want them to be always expanded, set `themeConfig.sidebarCollapsible` to `false`: + +```js {4} title="docusaurus.config.js" +module.exports = { + // ... + themeConfig: { + sidebarCollapsible: false, + // ... + }, +}; +``` + +#### Expanded categories by default + +For docs that have collapsible categories, you may want more fine-grain control over certain categories. If you want specific categories to be always expanded, you can set `collapsed` to `false`: + +```js title="sidebars.js" +module.exports = { + docs: { + Guides: [ + 'creating-pages', + { + type: 'category', + label: 'Docs', + collapsed: false, + items: ['markdown-features', 'sidebar', 'versioning'], + }, + ], + }, +}; +``` + +## Hideable sidebar + +Using the enabled `themeConfig.hideableSidebar` option, you can make the entire sidebar hidden, allowing you to better focus your users on the content. This is especially useful when content consumption on medium screens (e.g. on tablets). + +```js {4} title="docusaurus.config.js" +module.exports = { + // ... + themeConfig: { + hideableSidebar: true, + // ... + }, +}; +``` + +## Passing custom props + +To pass in custom props to a swizzled sidebar item, add the optional `customProps` object to any of the items: + +```js +{ + type: 'doc'; + id: 'doc1'; + customProps: { + /* props */ + } +} +``` diff --git a/website/versioned_docs/version-2.0.0-alpha.72/guides/docs/versioning.md b/website/versioned_docs/version-2.0.0-alpha.72/guides/docs/versioning.md new file mode 100644 index 0000000000..d61e383c57 --- /dev/null +++ b/website/versioned_docs/version-2.0.0-alpha.72/guides/docs/versioning.md @@ -0,0 +1,208 @@ +--- +id: versioning +title: Versioning +slug: /versioning +--- + +You can use the version script to create a new documentation version based on the latest content in the `docs` directory. That specific set of documentation will then be preserved and accessible even as the documentation in the `docs` directory changes moving forward. + +:::caution + +Think about it before starting to version your documentation - it can become difficult for contributors to help improve it! + +::: + +Most of the time, you don't need versioning as it will just increase your build time, and introduce complexity to your codebase. Versioning is **best suited for websites with high-traffic and rapid changes to documentation between versions**. If your documentation rarely changes, don't add versioning to your documentation. + +To better understand how versioning works and see if it suits your needs, you can read on below. + +## Directory structure + +```shell +website +├── sidebars.json # sidebar for master (next) version +├── docs # docs directory for master (next) version +│ ├── foo +│ │ └── bar.md # https://mysite.com/docs/next/foo/bar +│ └── hello.md # https://mysite.com/docs/next/hello +├── versions.json # file to indicate what versions are available +├── versioned_docs +│ ├── version-1.1.0 +│ │ ├── foo +│ │ │ └── bar.md # https://mysite.com/docs/foo/bar +│ │ └── hello.md +│ └── version-1.0.0 +│ ├── foo +│ │ └── bar.md # https://mysite.com/docs/1.0.0/foo/bar +│ └── hello.md +├── versioned_sidebars +│ ├── version-1.1.0-sidebars.json +│ └── version-1.0.0-sidebars.json +├── docusaurus.config.js +└── package.json +``` + +The table below explains how a versioned file maps to its version and the generated URL. + +| Path | Version | URL | +| --------------------------------------- | -------------- | ----------------- | +| `versioned_docs/version-1.0.0/hello.md` | 1.0.0 | /docs/1.0.0/hello | +| `versioned_docs/version-1.1.0/hello.md` | 1.1.0 (latest) | /docs/hello | +| `docs/hello.md` | next | /docs/next/hello | + +### Tagging a new version + +1. First, make sure your content in the `docs` directory is ready to be frozen as a version. A version always should be based from master. +1. Enter a new version number. + +```bash npm2yarn +npm run docusaurus docs:version 1.1.0 +``` + +When tagging a new version, the document versioning mechanism will: + +- Copy the full `docs/` folder contents into a new `versioned_docs/version-/` folder. +- Create a versioned sidebars file based from your current [sidebar](docs-introduction.md#sidebar) configuration (if it exists) - saved as `versioned_sidebars/version--sidebars.json`. +- Append the new version number to `versions.json`. + +## Docs + +### Creating new docs + +1. Place the new file into the corresponding version folder. +1. Include the reference for the new file into the corresponding sidebar file, according to version number. + +**Master docs** + +```shell +# The new file. +docs/new.md + +# Edit the corresponding sidebar file. +sidebar.js +``` + +**Older docs** + +```shell +# The new file. +versioned_docs/version-1.0.0/new.md + +# Edit the corresponding sidebar file. +versioned_sidebars/version-1.0.0-sidebars.json +``` + +### Linking docs + +- Remember to include the `.md` extension. +- Files will be linked to correct corresponding version. +- Relative paths work as well. + +```md +The [@hello](hello.md#paginate) document is great! + +See the [Tutorial](../getting-started/tutorial.md) for more info. +``` + +## Versions + +Each directory in `versioned_docs/` will represent a documentation version. + +### Updating an existing version + +You can update multiple docs versions at the same time because each directory in `versioned_docs/` represents specific routes when published. + +1. Edit any file. +1. Commit and push changes. +1. It will be published to the version. + +Example: When you change any file in `versioned_docs/version-2.6/`, it will only affect the docs for version `2.6`. + +### Deleting an existing version + +You can delete/remove versions as well. + +1. Remove the version from `versions.json`. + +Example: + +```diff {4} +[ + "2.0.0", + "1.9.0", +- "1.8.0" +] +``` + +2. Delete the versioned docs directory. Example: `versioned_docs/version-1.8.0`. +3. Delete the versioned sidebars file. Example: `versioned_sidebars/version-1.8.0-sidebars.json`. + +## Recommended practices + +### Figure out the behavior for the "current" version + +The "current" version is the version name for the `./docs` folder. + +There are different ways to manage versioning, but two very common patterns are: + +- You release v1, and start immediately working on v2 (including its docs) +- You release v1, and will maintain it for some time before thinking about v2. + +Docusaurus defaults work great for the first usecase. + +**For the 2nd usecase**: if you release v1 and don't plan to work on v2 anytime soon, instead of versioning v1 and having to maintain the docs in 2 folders (`./docs` + `./versioned_docs/version-1.0.0`), you may consider using the following configuration instead: + +```json +{ + "lastVersion": "current", + "versions": { + "current": { + "label": "1.0.0", + "path": "1.0.0" + } + } +} +``` + +The docs in `./docs` will be served at `/docs/1.0.0` instead of `/docs/next`, and `1.0.0` will become the default version we link to in the navbar dropdown, and you will only need to maintain a single `./docs` folder. + +See [docs plugin configuration](../../api/plugins/plugin-content-docs.md) for more details. + +### Version your documentation only when needed + +For example, you are building a documentation for your npm package `foo` and you are currently in version 1.0.0. You then release a patch version for a minor bug fix and it's now 1.0.1. + +Should you cut a new documentation version 1.0.1? **You probably shouldn't**. 1.0.1 and 1.0.0 docs shouldn't differ according to semver because there are no new features!. Cutting a new version for it will only just create unnecessary duplicated files. + +### Keep the number of versions small + +As a good rule of thumb, try to keep the number of your versions below 10. **It is very likely** that you will have a lot of obsolete versioned documentation that nobody even reads anymore. For example, [Jest](https://jestjs.io/versions) is currently in version `24.9`, and only maintains several latest documentation version with the lowest being `22.X`. Keep it small 😊 + +### Use absolute import within the docs + +Don't use relative paths import within the docs. Because when we cut a version the paths no longer work (the nesting level is different, among other reasons). You can utilize the `@site` alias provided by docusaurus, that points to the `website` directory. Example: + +```diff +- import Foo from '../src/components/Foo'; ++ import Foo from '@site/src/components/Foo'; +``` + +### Global or versioned colocated assets + +You should decide if assets like images and files are per version or shared between versions + +If your assets should be versioned, put them in the docs version, and use relative paths: + +```md +![img alt](./myImage.png) + +[download this file](./file.pdf) +``` + +If your assets are global, put them in `/static` and use absolute paths: + +```md +![img alt](/myImage.png) + +[download this file](/file.pdf) +``` diff --git a/website/versioned_docs/version-2.0.0-alpha.72/guides/markdown-features/markdown-features-admonitions.mdx b/website/versioned_docs/version-2.0.0-alpha.72/guides/markdown-features/markdown-features-admonitions.mdx new file mode 100644 index 0000000000..c692e1dda2 --- /dev/null +++ b/website/versioned_docs/version-2.0.0-alpha.72/guides/markdown-features/markdown-features-admonitions.mdx @@ -0,0 +1,86 @@ +--- +id: admonitions +title: Admonitions +description: Handling admonitions/callouts in Docusaurus Markdown +slug: /markdown-features/admonitions +--- + +In addition to the basic Markdown syntax, we use [remark-admonitions](https://github.com/elviswolcott/remark-admonitions) alongside MDX to add support for admonitions. Admonitions are wrapped by a set of 3 colons. + +Example: + + :::note + + The content and title *can* include markdown. + + ::: + + :::tip You can specify an optional title + + Heads up! Here's a pro-tip. + + ::: + + :::info + + Useful information. + + ::: + + :::caution + + Warning! You better pay attention! + + ::: + + :::danger + + Danger danger, mayday! + + ::: + +:::note + +The content and title _can_ include markdown. + +::: + +:::tip You can specify an optional title + +Heads up! Here's a pro-tip. + +::: + +:::info + +Useful information. + +::: + +:::caution + +Warning! You better pay attention! + +::: + +:::danger + +Danger danger, mayday! + +::: + +## Specifying title + +You may also specify an optional title + + :::note Your Title + + The content and title *can* include markdown. + + ::: + +:::note Your Title + +The content and title _can_ include Markdown. + +::: diff --git a/website/versioned_docs/version-2.0.0-alpha.72/guides/markdown-features/markdown-features-assets.mdx b/website/versioned_docs/version-2.0.0-alpha.72/guides/markdown-features/markdown-features-assets.mdx new file mode 100644 index 0000000000..c0b8f992eb --- /dev/null +++ b/website/versioned_docs/version-2.0.0-alpha.72/guides/markdown-features/markdown-features-assets.mdx @@ -0,0 +1,147 @@ +--- +id: assets +title: Assets +description: Handling assets in Docusaurus Markdown +slug: /markdown-features/assets +--- + +Sometimes you want to link to static assets directly from Markdown files, and it is convenient to co-locate the asset next to the markdown file using it. + +We have setup Webpack loaders to handle most common file types, so that when you import a file, you get its url, and the asset is automatically copied to the output folder. + +Let's imagine the following file structure: + +``` +# Your doc +/website/docs/myFeature.mdx + +# Some assets you want to use +/website/docs/assets/docusaurus-asset-example-banner.png +/website/docs/assets/docusaurus-asset-example-pdf.pdf +``` + +## Images + +You can use images in Markdown, or by requiring them and using a JSX image tag: + +```mdx +# My Markdown page + +Example banner + +or + +![Example banner](./assets/docusaurus-asset-example-banner.png) +``` + +The ES imports syntax also works: + +```mdx +# My Markdown page + +import myImageUrl from './assets/docusaurus-asset-example-banner.png'; + +My image alternative text +``` + +This results in displaying the image: + +![My image alternative text](../../assets/docusaurus-asset-example-banner.png) + +:::note + +If you are using [@docusaurus/plugin-ideal-image](../../using-plugins.md#docusaurusplugin-ideal-image), you need to use the dedicated image component, as documented. + +::: + +## Files + +In the same way, you can link to existing assets by requiring them and using the returned url in videos, links etc. + +```mdx +# My Markdown page + + + Download this PDF + + +or + +[Download this PDF using Markdown](./assets/docusaurus-asset-example-pdf.pdf) +``` + + + Download this PDF + + +[Download this PDF using Markdown](../../assets/docusaurus-asset-example-pdf.pdf) + +## Inline SVGs + +Docusaurus supports inlining SVGs out of the box. + +```jsx +import DocusaurusSvg from './docusaurus.svg'; + +; +``` + +import DocusaurusSvg from '@site/static/img/docusaurus.svg'; + + + +This can be useful, if you want to alter the part of the SVG image via CSS. For example, you can change one of the SVG colors based on the current theme. + +```jsx +import DocusaurusSvg from './docusaurus.svg'; + +; +``` + +```css +html[data-theme='light'] .themedDocusaurus [fill='#FFFF50'] { + fill: greenyellow; +} + +html[data-theme='dark'] .themedDocusaurus [fill='#FFFF50'] { + fill: seagreen; +} +``` + + + +## Themed Images + +Docusaurus supports themed images: the `ThemedImage` component (included in the classic/bootstrap themes) allows you to switch the image source based on the current theme. + +```jsx {5-8} +import ThemedImage from '@theme/ThemedImage'; + +; +``` + +```mdx-code-block +import useBaseUrl from '@docusaurus/useBaseUrl'; +import ThemedImage from '@theme/ThemedImage'; + + +``` diff --git a/website/versioned_docs/version-2.0.0-alpha.72/guides/markdown-features/markdown-features-code-blocks.mdx b/website/versioned_docs/version-2.0.0-alpha.72/guides/markdown-features/markdown-features-code-blocks.mdx new file mode 100644 index 0000000000..270f92d05a --- /dev/null +++ b/website/versioned_docs/version-2.0.0-alpha.72/guides/markdown-features/markdown-features-code-blocks.mdx @@ -0,0 +1,443 @@ +--- +id: code-blocks +title: Code blocks +description: Handling code blocks in Docusaurus Markdown +slug: /markdown-features/code-blocks +--- + +Code blocks within documentation are super-powered 💪. + +## Code title + +You can add a title to the code block by adding `title` key after the language (leave a space between them). + + ```jsx title="/src/components/HelloCodeTitle.js" + function HelloCodeTitle(props) { + return

Hello, {props.name}

; + } + ``` + +```jsx title="/src/components/HelloCodeTitle.js" +function HelloCodeTitle(props) { + return

Hello, {props.name}

; +} +``` + +## Syntax highlighting + +Code blocks are text blocks wrapped around by strings of 3 backticks. You may check out [this reference](https://github.com/mdx-js/specification) for specifications of MDX. + + ```jsx + console.log('Every repo must come with a mascot.'); + ``` + + + +Use the matching language meta string for your code block, and Docusaurus will pick up syntax highlighting automatically, powered by [Prism React Renderer](https://github.com/FormidableLabs/prism-react-renderer). + +```jsx +console.log('Every repo must come with a mascot.'); +``` + +By default, the Prism [syntax highlighting theme](https://github.com/FormidableLabs/prism-react-renderer#theming) we use is [Palenight](https://github.com/FormidableLabs/prism-react-renderer/blob/master/src/themes/palenight.js). You can change this to another theme by passing `theme` field in `prism` as `themeConfig` in your docusaurus.config.js. + +For example, if you prefer to use the `dracula` highlighting theme: + +```js {4} title="docusaurus.config.js" +module.exports = { + themeConfig: { + prism: { + theme: require('prism-react-renderer/themes/dracula'), + }, + }, +}; +``` + +By default, Docusaurus comes with this subset of [commonly used languages](https://github.com/FormidableLabs/prism-react-renderer/blob/master/src/vendor/prism/includeLangs.js). + +To add syntax highlighting for any of the other [Prism supported languages](https://prismjs.com/#supported-languages), define it in an array of additional languages. + +For example, if you want to add highlighting for the `powershell` language: + +```js {5} title="docusaurus.config.js" +module.exports = { + // ... + themeConfig: { + prism: { + additionalLanguages: ['powershell'], + }, + // ... + }, +}; +``` + +If you want to add highlighting for languages not yet supported by Prism, you can swizzle `prism-include-languages`: + +```bash npm2yarn +npm run swizzle @docusaurus/theme-classic prism-include-languages +``` + +It will produce `prism-include-languages.js` in your `src/theme` folder. You can add highlighting support for custom languages by editing `prism-include-languages.js`: + +```js {8} title="src/theme/prism-include-languages.js" +const prismIncludeLanguages = (Prism) => { + // ... + + additionalLanguages.forEach((lang) => { + require(`prismjs/components/prism-${lang}`); // eslint-disable-line + }); + + require('/path/to/your/prism-language-definition'); + + // ... +}; +``` + +You can refer to [Prism's official language definitions](https://github.com/PrismJS/prism/tree/master/components) when you are writing your own language definitions. + +## Line highlighting + +You can bring emphasis to certain lines of code by specifying line ranges after the language meta string (leave a space after the language). + + ```jsx {3} + function HighlightSomeText(highlight) { + if (highlight) { + return 'This text is highlighted!'; + } + + return 'Nothing highlighted'; + } + ``` + +```jsx {3} +function HighlightSomeText(highlight) { + if (highlight) { + return 'This text is highlighted!'; + } + + return 'Nothing highlighted'; +} +``` + +To accomplish this, Docusaurus adds the `docusaurus-highlight-code-line` class to the highlighted lines. You will need to define your own styling for this CSS, possibly in your `src/css/custom.css` with a custom background color which is dependent on your selected syntax highlighting theme. The color given below works for the default highlighting theme (Palenight), so if you are using another theme, you will have to tweak the color accordingly. + +```css title="/src/css/custom.css" +.docusaurus-highlight-code-line { + background-color: rgb(72, 77, 91); + display: block; + margin: 0 calc(-1 * var(--ifm-pre-padding)); + padding: 0 var(--ifm-pre-padding); +} + +/* If you have a different syntax highlighting theme for dark mode. */ +html[data-theme='dark'] .docusaurus-highlight-code-line { + background-color: ; /* Color which works with dark mode syntax highlighting theme */ +} +``` + +To highlight multiple lines, separate the line numbers by commas or use the range syntax to select a chunk of lines. This feature uses the `parse-number-range` library and you can find [more syntax](https://www.npmjs.com/package/parse-numeric-range) on their project details. + + ```jsx {1,4-6,11} + import React from 'react'; + + function MyComponent(props) { + if (props.isBar) { + return
Bar
; + } + + return
Foo
; + } + + export default MyComponent; + ``` + +```jsx {1,4-6,11} +import React from 'react'; + +function MyComponent(props) { + if (props.isBar) { + return
Bar
; + } + + return
Foo
; +} + +export default MyComponent; +``` + +You can also use comments with `highlight-next-line`, `highlight-start`, and `highlight-end` to select which lines are highlighted. + + ```jsx + function HighlightSomeText(highlight) { + if (highlight) { + // highlight-next-line + return 'This text is highlighted!'; + } + + return 'Nothing highlighted'; + } + + function HighlightMoreText(highlight) { + // highlight-start + if (highlight) { + return 'This range is highlighted!'; + } + // highlight-end + + return 'Nothing highlighted'; + } + ``` + +```jsx +function HighlightSomeText(highlight) { + if (highlight) { + // highlight-next-line + return 'This text is highlighted!'; + } + + return 'Nothing highlighted'; +} + +function HighlightMoreText(highlight) { + // highlight-start + if (highlight) { + return 'This range is highlighted!'; + } + // highlight-end + + return 'Nothing highlighted'; +} +``` + +Supported commenting syntax: + +| Language | Syntax | +| ---------- | ------------------------ | +| JavaScript | `/* ... */` and `// ...` | +| JSX | `{/* ... */}` | +| Python | `# ...` | +| HTML | `` | + +If there's a syntax that is not currently supported, we are open to adding them! Pull requests welcome. + +## Interactive code editor + +(Powered by [React Live](https://github.com/FormidableLabs/react-live)) + +You can create an interactive coding editor with the `@docusaurus/theme-live-codeblock` plugin. + +First, add the plugin to your package. + +```bash npm2yarn +npm install --save @docusaurus/theme-live-codeblock +``` + +You will also need to add the plugin to your `docusaurus.config.js`. + +```js {3} +module.exports = { + // ... + themes: ['@docusaurus/theme-live-codeblock'], + // ... +}; +``` + +To use the plugin, create a code block with `live` attached to the language meta string. + + ```jsx live + function Clock(props) { + const [date, setDate] = useState(new Date()); + useEffect(() => { + var timerID = setInterval(() => tick(), 1000); + + return function cleanup() { + clearInterval(timerID); + }; + }); + + function tick() { + setDate(new Date()); + } + + return ( +
+

It is {date.toLocaleTimeString()}.

+
+ ); + } + ``` + +The code block will be rendered as an interactive editor. Changes to the code will reflect on the result panel live. + +```jsx live +function Clock(props) { + const [date, setDate] = useState(new Date()); + useEffect(() => { + var timerID = setInterval(() => tick(), 1000); + + return function cleanup() { + clearInterval(timerID); + }; + }); + + function tick() { + setDate(new Date()); + } + + return ( +
+

It is {date.toLocaleTimeString()}.

+
+ ); +} +``` + +### Imports + +:::caution react-live and imports + +It is not possible to import components directly from the react-live code editor, you have to define available imports upfront. + +::: + +By default, all React imports are available. If you need more imports available, swizzle the react-live scope: + +```bash npm2yarn +npm run swizzle @docusaurus/theme-live-codeblock ReactLiveScope +``` + +```jsx {3-15,21} title="src/theme/ReactLiveScope/index.js" +import React from 'react'; + +const ButtonExample = (props) => ( +