docs(v2): move the quotes to remark admonitions (#2313)

* docs(v2): move the quotes to remark admonitions

* Delete package-lock.json

Co-authored-by: Yangshun Tay <tay.yang.shun@gmail.com>
This commit is contained in:
Zhenchao Cai 2020-02-23 04:11:37 -06:00 committed by GitHub
parent d06ab640ff
commit b25eb5dd36
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
10 changed files with 91 additions and 19 deletions

View file

@ -62,7 +62,11 @@ Compiles your site for production.
### `docusaurus swizzle`
> ⚠️ We would like to discourage swizzling of components until we've minimally 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.
:::caution
We would like to discourage swizzling of components until we've minimally 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.
:::
Swizzle any Docusaurus Theme components with your own component with `docusaurus swizzle`.

View file

@ -142,4 +142,8 @@ const Hello = () => {
};
```
> 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`.
:::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`.
:::

View file

@ -3,7 +3,11 @@ id: design-principles
title: Design Principles
---
> :warning: _This section is a work in progress._
:::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.

View file

@ -3,7 +3,11 @@ id: lifecycle-apis
title: Lifecycle APIs
---
> :warning: _This section is a work in progress._
:::caution
_This section is a work in progress._
:::
Lifecycle APIs are shared by Themes and Plugins.

View file

@ -519,9 +519,17 @@ For any questions, you can ask in the [`#docusaurus-1-to-2-migration` Discord ch
## Versioned Site
> :warning: _This section is a work in progress._
:::caution
> ⚠️ Although we've implemented docs versioning since 2.0.0-alpha.37, we'd like to test it out for v2 users first before we recommend v1 users to migrate to v2. There are some changes in how v2 versioning works compared to v1. In the future, we might create a script to migrate your versioned docs easier. However, if you are adventurous enough to manually migrate, feel free to do so. Be warned though, the manual migration requires lot of work.
_This section is a work in progress._
:::
:::warning
Although we've implemented docs versioning since 2.0.0-alpha.37, we'd like to test it out for v2 users first before we recommend v1 users to migrate to v2. There are some changes in how v2 versioning works compared to v1. In the future, we might create a script to migrate your versioned docs easier. However, if you are adventurous enough to manually migrate, feel free to do so. Be warned though, the manual migration requires lot of work.
:::
## Changes from v1

View file

@ -126,4 +126,8 @@ The class names which will be processed by webpack into a globally unique class
### CSS-in-JS
> :warning: _This section is a work in progress._ [Welcoming PRs](https://github.com/facebook/docusaurus/issues/1640).\_
:::caution
_This section is a work in progress._ [Welcoming PRs](https://github.com/facebook/docusaurus/issues/1640).\_
:::

View file

@ -3,7 +3,11 @@ id: theme-classic
title: '@docusaurus/theme-classic'
---
> :warning: _This section is a work in progress._
:::caution
_This section is a work in progress._
:::
## Common

View file

@ -137,7 +137,11 @@ Provides the [Blog](blog.md) feature and is the default blog plugin for Docusaur
npm install --save @docusaurus/plugin-content-blog
```
> 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.
:::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.
:::
```js
// docusaurus.config.js
@ -174,7 +178,7 @@ module.exports = {
* Truncate marker, can be a regex or string.
*/
truncateMarker: /<!--\s*(truncate)\s*-->/,
/**
/**
* Blog feed
* If feedOptions is undefined, no rss feed will be generated
*/
@ -201,7 +205,11 @@ Provides the [Docs](markdown-features.mdx) functionality and is the default docs
npm install --save @docusaurus/plugin-content-docs
```
> 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.
:::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.
:::
```js
// docusaurus.config.js
@ -264,7 +272,11 @@ The default pages plugin for Docusaurus. The classic template ships with this pl
npm install --save @docusaurus/plugin-content-pages
```
> 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.
:::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.
:::
```js
// docusaurus.config.js
@ -301,7 +313,11 @@ The default [Google Analytics](https://developers.google.com/analytics/devguides
npm install --save @docusaurus/plugin-google-analytics
```
> If you have installed `@docusaurus/preset-classic`, you don't need to install it as a dependency.
:::tip
If you have installed `@docusaurus/preset-classic`, you don't need to install it as a dependency.
:::
**Configuration**
@ -329,7 +345,11 @@ The default [Global Site Tag (gtag.js)](https://developers.google.com/analytics/
npm install --save @docusaurus/plugin-google-gtag
```
> If you have installed `@docusaurus/preset-classic`, you don't need to install it as a dependency.
:::tip
If you have installed `@docusaurus/preset-classic`, you don't need to install it as a dependency.
:::
**Configuration**
@ -357,7 +377,11 @@ This plugin creates sitemap for your site so that search engine crawlers can cra
npm install --save @docusaurus/plugin-sitemap
```
> 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.
:::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.
:::
```js
// docusaurus.config.js

View file

@ -74,7 +74,11 @@ The content plugin remains the same and the only thing you need to change is the
## Swizzling theme components
> ⚠️ We would like to discourage swizzling of components until we've minimally 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.
:::caution
We would like to discourage swizzling of components until we've minimally 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.
:::
Docusaurus Themes' components are designed to be replaceable. To make it easier for you, we created a command for you to replace theme components called `swizzle`.
@ -104,7 +108,11 @@ The classic theme for Docusaurus. You can refer to [classic theme configuration]
npm install --save @docusaurus/theme-classic
```
> If you have installed `@docusaurus/preset-classic`, you don't need to install it as a dependency.
:::tip
If you have installed `@docusaurus/preset-classic`, you don't need to install it as a dependency.
:::
### `@docusaurus/theme-search-algolia`
@ -114,7 +122,11 @@ This theme provides a `@theme/SearchBar` component that integrates with Algolia
npm install --save @docusaurus/theme-search-algolia
```
> If you have installed `@docusaurus/preset-classic`, you don't need to install it as a dependency.
:::tip
If you have installed `@docusaurus/preset-classic`, you don't need to install it as a dependency.
:::
### `@docusaurus/theme-live-codeblock`

View file

@ -6,7 +6,11 @@ You can use the version script to cut a new documentation version based on the l
## :warning: Disclaimer
> Consider it really well before starting to version your documentation.
:::important
Consider it really well before starting to version your documentation.
:::
Most of the times, you don't need versioning and it will just increase your build time and introduces complexity to your codebase. Versioning is **best suited for website with high-traffic and rapid changes in documentation between version**. If your documentation rarely changes, don't version.