feat(getting-started): running workflow complete

Author: Eric Lin

docs/getting-started/img/commit.gif

@@ -7,3 +7,146 @@ sidebar_position: 3
 Once you have cloned your new docs repository, you will want to be able to know how to start previews, lint, build, and do all the necessary things in development.
 
 Ideally, you would be somewhat acquainted with `npm` or `yarn` project workflows, as Docusaurus is a React-based project.
+
+## 👨‍💻 Committing to your repo
+
+As part of running `npm prepare` when initializing this repo, [**`husky`**](https://typicode.github.io/husky/#/) is installed to manage pre-commit hooks.
+
+All commits are linted with `commitlint` with the conventional rules found in `package.json`.
+
+`lint-staged` is used to run checks on certain _staged_ Git files when committing. The commands that are run and on what files can be found in the `package.json` under the `lint-staged` key.
+
+:::tip
+
+It is recommended to use the command `git commit` only after staging files.
+
+You should generally avoid `git commit -m` or similar commands which pass in the command-line or args like `--allow-empty`.
+
+:::
+
+<details>
+  <summary>
+    See example of <b>git commit</b> flow
+  </summary>
+  <div>
+    <img src={require("./img/commit.gif").default} alt="gifExample" />
+  </div>
+</details>
+
+## 📦 `npm` commands and scripts
+
+Here is an exhaustive list of what each `npm` script does in the `package.json`.
+
+:::caution
+
+This is likely to change every so often and documentation may not be updated to reflect it always.
+
+Please open an issue or PR to address it!
+
+:::
+
+### 🐎 `npm run start`
+
+Run Docusaurus locally on port [http://localhost:3000](http://localhost:3000) to preview and supports automatic refresh when changes are made. This is usually used in development while making changes to Markdown or certain configuration files.
+
+:::note
+
+**Not all** changes made are supported by the automatic refresh and may require restarting the command.
+
+:::
+
+### 👷 `npm run build`
+
+Build Docusaurus for **production** into the `./build` directory of the root folder of this project.
+
+It is usually not necessary to do this in development and is usually only used by CI when building to be deployed.
+
+:::caution
+
+There is still an open issue regarding proper and stable CSS insertion ordering that may differ between `npm run start` and `npm run build` results.
+
+Please see [**here**](https://github.com/facebook/docusaurus/issues/3678) for more details.
+
+This is usually not an issue and can be mitigated with adding `!important` to CSS styles.
+
+:::
+
+### 📑 `npm run build:docs`
+
+If you have chosen to use `docusaurus-plugin-openapi-docs` plugin for integrating OpenAPI to your docs, then this command will clean existing generated Markdown API docs and re-generate them.
+
+This command is bundled into the `npm run build` command.
+
+You can safely remove this script from the `package.json` if you are not using the plugin.
+
+### 🖋️ `npm run swizzle`
+
+[**Swizzling**](https://docusaurus.io/docs/swizzling) allows more advanced customization of React Components in Docusaurus beyond simple CSS modifications.
+
+### ✈️ `npm run deploy`
+
+Built-in as part of Docusaurus for [deploying](https://docusaurus.io/docs/deployment#deploying-to-github-pages) project.
+
+:::note
+
+This command should not be necessary to use at all.
+
+:::
+
+### ⌦ `npm run clear`
+
+If you are running into some issues with error when running `npm run start`, it is recommended to use the clear command to remove all generated assets, caches or build artifacts.
+
+### 📺 `npm run serve`
+
+This is to be run after the `npm run build` command as it will serve the files generated by the build output from the `./build` directory for local viewing.
+
+:::note
+
+As `npm run build` is for production building or debugging production build issues, it should not be necessary to use `npm runs serve` except where those two scenarios require it.
+
+:::
+
+### 🌎 `npm run write-translations`
+
+Only needed where [translations](https://docusaurus.io/docs/cli#docusaurus-write-translations-sitedir) are to be added.
+
+### 🌎 `npm run write-heading-ids`
+
+Only needed where [translations](https://docusaurus.io/docs/cli#docusaurus-write-heading-ids-sitedir) are to be added.
+
+### ⌨️ `npm run typecheck`
+
+Typechecking with TypeScript and `tsconfig.json`.
+
+### ⌨️ `npm run typecheck-staged`
+
+Typechecking _staged-only_ files which is used by `lint-staged` when committing.
+
+### 🧼 `npm run lint`
+
+Combined command which includes spell check, JS/TS linting, and CSS linting.
+
+### 🧼 `npm run lint:js`
+
+Lint JS/TS with ESLint.
+
+### 🧼 `npm run lint:spelling`
+
+Checking spelling with CSpell.
+
+### 🧼 `npm run lint:style`
+
+Lint CSS files with specific styling.
+
+### 🧼 `npm run lint:fix`
+
+Pass the `--fix` CLI argument to `npm run lint:js` to attempt to fix issues.
+
+### 🖨️ `npm run format`
+
+Run Prettier to format code before commit for consistency in the repo.
+
+### 🥗 `npm run prepare`
+
+After `npm install` for the very first time, `husky` is installed for Git pre-commit hooks.