* Update api-site-config.md
Added a piece of text from the set-up guide to enable Google Fonts.
* Update api-site-config.md
* Update api-site-config.md
* Update api-site-config.md
Added a clarification to the cleanUrl property to set it false if the users intend to use docusaurus only offline.
* Update api-site-config.md
Added the copyright information.
* Update api-site-config.md
* Update getting-started-installation.md
Added a note that Docker files were not needed, and they may be deleted.
* Update getting-started-installation.md
I'm really bad at adding copyright notices.
* Update getting-started-installation.md
Fixed a styling issue.
* Update getting-started-installation.md
* docs: add past versions to the tutorial
I changed "we" to "you" like the other sections of the tutorial.
I removed yarn from the code because `yarn version` didn't run on my Windows 10 system (see issue [1743](https://github.com/facebook/docusaurus/issues/1743)).
I added headings for the current version, next version, and past versions.
* Update tutorial-version.md
* docs: add the repository to the localhost:3000 link
Fix two links on **[Create Pages](https://docusaurus.io/docs/en/next/tutorial-create-pages)**.
* docs: use the same start command on both pages
The start command in **[Scaffold the Site](https://docusaurus.io/docs/en/next/tutorial-create-new-site)** is "Run `npm start` or `yarn start.`" It will help new users to see the same start command again. A slightly different command will make new users think that something slightly different is happening.
* docs: change the ID of the new documentation page
The page ID "doc4" is already used by one of the downloaded pages, docs/exampledoc4.md, shown below:
```
---
id: doc4
title: Other Document
---
this is another document
```
* docs: removed docusaurus-tutorial/ from the links
I think the tutorial should tell Windows users to use Git Bash. Later in the tutorial is a command that worked in Git Bash, `publish-gh-pages`, but didn't work for me at the Windows command prompt.
* docs: add an HTTPS example for publish-gh-pages
I moved step 1 to step 2 so the terminal steps would be together. I added Git Bash, because `publish-gh-pages` worked for me in Git Bash but didn't work at the Windows command prompt.
I added HTTPS to step 4 because, on my system, HTTPS worked for me but SSH didn't work. I changed <GIT_USER> to USERNAME and deleted the $ prompt, to be consistent with other examples in the tutorial.
* Update tutorial-publish-site.md
The description of `npm` fits better in the opening paragraph than in a numbered step. The note about version 8 fits better in the Check section than the Install section.
The `cd` step seems like the first step of "Install the Docusaurus init command," instead of the last step of "Create a GitHub repository and local clone."
* Add a cd step before clone in "Setting Up"
Add a `cd` step before clone in **[Setting Up](https://docusaurus.io/docs/en/next/tutorial-setup)**, add examples of `cd` in steps 5 and 7, and edit other steps.
* Update tutorial-setup.md
I wanted to enable superscript and subscripting to a v1 site. It wasn't quite clear how to do it. @yangshun helped me figure it out. So I thought I would document it.
* feat(core): use 0.0.0.0 for livereload address
* test(core): update server tests
* feat(cli): add host by command line flag
* test: revert test changes
* fix(core): update server to use custom host if supplied
* refactor: nits
* doc: change tutorial git to suggest HTTPS
Since we're instructing the user to create a new repository, it might be a safe bet to assume that they don't have their SSH keys set up. HTTPS might be a better option in this context.
* docs: keep ssh add https
@Hongarc said, "How about keep `SSH` and add `HTTPS`." This is one way to do that.
* Update tutorial-setup.md
In this tutorial we assume that the user may or may not have used Node.js. It would follow then, based on how long it takes the "Linking dependencies" step to complete—243.61s for me—that we give them a hint that it might take a minute.
* Make it clear where the `docs` folder is
It was not clear, to the beginner user—who this tutorial is for—where the `docs` folder was . The only reason I know this is because I'm a beginner user and I tried for too many minutes to find the `docs` folder inside the `website` folder. I had this assumption because the previous example is offered under the assumption that you're in the `website` folder.
Feel free to change the wording, I just want to make it clear where you should be looking, if you're new.
* Update tutorial-create-pages.md
Dylan Myers