Skip to content

Commit

Permalink
Revert ordered list change
Browse files Browse the repository at this point in the history
  • Loading branch information
@eric-hc
eric-hc committed Nov 11, 2019
1 parent 0f04c59 commit e9520ac
Show file tree
Hide file tree
Showing 12 changed files with 50 additions and 50 deletions.
4 changes: 2 additions & 2 deletions docs/getting-started-installation.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -14,15 +14,15 @@ We have created a helpful script that will get all of the infrastructure set up

> You have to be on Node >= 8.x and Yarn >= 1.5.
2. Create a project, if none exists, and change your directory to this project's root.
1. Create a project, if none exists, and change your directory to this project's root.

You will be creating the docs in this directory. The root directory may
contain other files. The Docusaurus installation script will create two new
directories: `docs` and `website`.

> Commonly, either an existing or newly created GitHub project will be the location for your Docusaurus site, but that is not mandatory to use Docusaurus.
3. Run the Docusaurus installation script: `npx docusaurus-init`.
1. Run the Docusaurus installation script: `npx docusaurus-init`.

> If you don't have Node 8.2+ or if you prefer to install Docusaurus globally, run `yarn global add docusaurus-init` or `npm install --global docusaurus-init`. After that, run `docusaurus-init`.
Expand Down
16 changes: 8 additions & 8 deletions docs/getting-started-publishing.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -221,10 +221,10 @@ Save this file as `config.yml` and place it in a `.circleci` directory inside yo
### Using Travis CI

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/)
2. Using your GitHub account, [add the Travis CI app](https://github.com/marketplace/travis-ci) to the repository you want to activate.
3. 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.
4. 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).
5. Create a `.travis.yml` on the root of your repository with below text.
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 below text.

```yaml
# .travis.yml
Expand Down Expand Up @@ -254,14 +254,14 @@ With [ZEIT Now](#using-zeit-now), you can deploy your site and connect it to [Gi
Steps to configure your Docusaurus-powered site on Netlify.

1. Select **New site from Git**
2. Connect to your preferred Git provider.
3. Select the branch to deploy. Default is `master`
4. Configure your build steps:
1. Connect to your preferred Git provider.
1. Select the branch to deploy. Default is `master`
1. Configure your build steps:

* For your build command enter: `cd website; npm install; npm run build;`
* For publish directory: `website/build/<projectName>` (use the `projectName` from your `siteConfig`)

5. Click **Deploy site**
1. Click **Deploy site**

You can also configure Netlify to rebuild on every commit to your repository, or only `master` branch commits.

Expand Down
2 changes: 1 addition & 1 deletion docs/getting-started-site-creation.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,7 @@ To create a fully functional site, you only need to do a few steps:
My new content here..
```

2. Add zero or more docs to the [`sidebars.json`](guides-navigation.md#adding-docs-to-a-sidebar) file so that your documentation is rendered in a sidebar if you choose them to be.
1. Add zero or more docs to the [`sidebars.json`](guides-navigation.md#adding-docs-to-a-sidebar) file so that your documentation is rendered in a sidebar if you choose them to be.

> If you do not add your documentation to the `sidebars.json` file, the docs will be rendered, but they can only be linked to from other documentation and visited with the known URL.

Expand Down
6 changes: 3 additions & 3 deletions docs/guides-blog.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -111,9 +111,9 @@ You can run your Docusaurus site without a landing page and instead have your bl
To do this:

1. Create a file `index.html` in `website/static/`.
2. Place the contents of the template below into `website/static/index.html`
3. Customize the `<title>` of `website/static/index.html`
4. Delete the dynamic landing page `website/pages/en/index.js`
1. Place the contents of the template below into `website/static/index.html`
1. Customize the `<title>` of `website/static/index.html`
1. Delete the dynamic landing page `website/pages/en/index.js`

> Now, when Docusaurus generates or builds your site, it will copy the file from `static/index.html` and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads, it will redirect the visitor to `/blog`.
Expand Down
16 changes: 8 additions & 8 deletions website-1.x/versioned_docs/version-1.10.x/getting-started-publishing.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -215,10 +215,10 @@ Save this file as `config.yml` and place it in a `.circleci` directory inside yo
### Using Travis CI

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/)
2. Using your GitHub account, [add the Travis CI app](https://github.com/marketplace/travis-ci) to the repository you want to activate.
3. 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.
4. 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).
5. Create a `.travis.yml` on the root of your repository with below text.
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 below text.

```yaml
# .travis.yml
Expand Down Expand Up @@ -248,14 +248,14 @@ With [ZEIT Now](#using-zeit-now), you can deploy your site and connect it to [Gi
Steps to configure your Docusaurus-powered site on Netlify.

1. Select **New site from Git**
2. Connect to your preferred Git provider.
3. Select the branch to deploy. Default is `master`
4. Configure your build steps:
1. Connect to your preferred Git provider.
1. Select the branch to deploy. Default is `master`
1. Configure your build steps:

* For your build command enter: `cd website; npm install; npm run build;`
* For publish directory: `website/build/<projectName>` (use the `projectName` from your `siteConfig`)

5. Click **Deploy site**
1. Click **Deploy site**

You can also configure Netlify to rebuild on every commit to your repository, or only `master` branch commits.

Expand Down
6 changes: 3 additions & 3 deletions website-1.x/versioned_docs/version-1.11.x/guides-blog.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -112,9 +112,9 @@ You can run your Docusaurus site without a landing page and instead have your bl
To do this:

1. Create a file `index.html` in `website/static/`.
2. Place the contents of the template below into `website/static/index.html`
3. Customize the `<title>` of `website/static/index.html`
4. Delete the dynamic landing page `website/pages/en/index.js`
1. Place the contents of the template below into `website/static/index.html`
1. Customize the `<title>` of `website/static/index.html`
1. Delete the dynamic landing page `website/pages/en/index.js`

> Now, when Docusaurus generates or builds your site, it will copy the file from `static/index.html` and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to `/blog`.
Expand Down
16 changes: 8 additions & 8 deletions website-1.x/versioned_docs/version-1.12.0/getting-started-publishing.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -216,10 +216,10 @@ Save this file as `config.yml` and place it in a `.circleci` directory inside yo
### Using Travis CI

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/)
2. Using your GitHub account, [add the Travis CI app](https://github.com/marketplace/travis-ci) to the repository you want to activate.
3. 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.
4. 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).
5. Create a `.travis.yml` on the root of your repository with below text.
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 below text.

```yaml
# .travis.yml
Expand Down Expand Up @@ -249,14 +249,14 @@ With [ZEIT Now](#using-zeit-now), you can deploy your site and connect it to [Gi
Steps to configure your Docusaurus-powered site on Netlify.

1. Select **New site from Git**
2. Connect to your preferred Git provider.
3. Select the branch to deploy. Default is `master`
4. Configure your build steps:
1. Connect to your preferred Git provider.
1. Select the branch to deploy. Default is `master`
1. Configure your build steps:

* For your build command enter: `cd website; npm install; npm run build;`
* For publish directory: `website/build/<projectName>` (use the `projectName` from your `siteConfig`)

5. Click **Deploy site**
1. Click **Deploy site**

You can also configure Netlify to rebuild on every commit to your repository, or only `master` branch commits.

Expand Down
6 changes: 3 additions & 3 deletions website-1.x/versioned_docs/version-1.12.0/guides-blog.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -112,9 +112,9 @@ You can run your Docusaurus site without a landing page and instead have your bl
To do this:

1. Create a file `index.html` in `website/static/`.
2. Place the contents of the template below into `website/static/index.html`
3. Customize the `<title>` of `website/static/index.html`
4. Delete the dynamic landing page `website/pages/en/index.js`
1. Place the contents of the template below into `website/static/index.html`
1. Customize the `<title>` of `website/static/index.html`
1. Delete the dynamic landing page `website/pages/en/index.js`

> Now, when Docusaurus generates or builds your site, it will copy the file from `static/index.html` and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads, it will redirect the visitor to `/blog`.
Expand Down
16 changes: 8 additions & 8 deletions website-1.x/versioned_docs/version-1.9.x/getting-started-publishing.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -215,10 +215,10 @@ Save this file as `config.yml` and place it in a `.circleci` directory inside yo
### Using Travis CI

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/)
2. Using your GitHub account, [add the Travis CI app](https://github.com/marketplace/travis-ci) to the repository you want to activate.
3. 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.
4. 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).
5. Create a `.travis.yml` on the root of your repository with below text.
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 below text.

```yaml
# .travis.yml
Expand Down Expand Up @@ -248,14 +248,14 @@ With [ZEIT Now](#using-zeit-now), you can deploy your site and connect it to [Gi
Steps to configure your Docusaurus-powered site on Netlify.

1. Select **New site from Git**
2. Connect to your preferred Git provider.
3. Select the branch to deploy. Default is `master`
4. Configure your build steps:
1. Connect to your preferred Git provider.
1. Select the branch to deploy. Default is `master`
1. Configure your build steps:

* For your build command enter: `cd website; npm install; npm run build;`
* For publish directory: `website/build/<projectName>` (use the `projectName` from your `siteConfig`)

5. Click **Deploy site**
1. Click **Deploy site**

You can also configure Netlify to rebuild on every commit to your repository, or only `master` branch commits.

Expand Down
2 changes: 1 addition & 1 deletion website-1.x/versioned_docs/version-1.9.x/getting-started-site-creation.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ To create a fully functional site, you only need to do a few steps:
My new content here..
```

2. Add zero or more docs to the [`sidebars.json`](guides-navigation.md#adding-docs-to-a-sidebar) file so that your documentation is rendered in a sidebar, if you choose them to be.
1. Add zero or more docs to the [`sidebars.json`](guides-navigation.md#adding-docs-to-a-sidebar) file so that your documentation is rendered in a sidebar, if you choose them to be.

> If you do not add your documentation to the `sidebars.json` file, the docs will be rendered, but they can only be linked to from other documentation and visited with the known URL.

Expand Down
6 changes: 3 additions & 3 deletions website-1.x/versioned_docs/version-1.9.x/guides-blog.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -112,9 +112,9 @@ You can run your Docusaurus site without a landing page and instead have your bl
To do this:

1. Create a file `index.html` in `website/static/`.
2. Place the contents of the template below into `website/static/index.html`
3. Customize the `<title>` of `website/static/index.html`
4. Delete the dynamic landing page `website/pages/en/index.js`
1. Place the contents of the template below into `website/static/index.html`
1. Customize the `<title>` of `website/static/index.html`
1. Delete the dynamic landing page `website/pages/en/index.js`

> Now, when Docusaurus generates or builds your site, it will copy the file from `static/index.html` and place it in the site's main directory. The static file is served when a visitor arrives on your page. When the page loads it will redirect the visitor to `/blog`.
Expand Down
4 changes: 2 additions & 2 deletions website/docs/using-themes.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -31,8 +31,8 @@ import Navbar from '@theme/Navbar';
The alias `@theme` can refer to a few directories, in the following priority:

1. A user's `website/src/theme` directory, which is a special directory that has the higher precedence.
2. A Docusaurus theme packages's `theme` directory.
3. Fallback components provided by Docusaurus core (usually not needed).
1. A Docusaurus theme packages's `theme` directory.
1. Fallback components provided by Docusaurus core (usually not needed).

Given the following structure

Expand Down

0 comments on commit e9520ac

Please sign in to comment.