ci: rename branch

.github/workflows/docs.yml

@@ -0,0 +1,36 @@
+name: Deploy Docs
+
+on:
+  push:
+    branches:
+      - main
+
+jobs:
+  build-deploy:
+    name: Build and deploy docs
+
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout 🛎️
+        uses: actions/checkout@v2
+
+      - name: Set up Python 3 ⚙️ 🐍
+        uses: actions/setup-python@v2
+
+      - name: Cache dependencies 💾
+        uses: actions/cache@v2
+        with:
+          path: ~/.cache/pip
+          key: ${{ runner.os }}-pip-${{ hashFiles('docs/requirements.txt') }}
+          restore-keys: |
+            ${{ runner.os }}-pip-
+            ${{ runner.os }}-
+
+      - name: Install dependencies 🔧
+        working-directory: docs
+        run: make install
+
+      - name: Build and deploy to GitHub Pages 🏗️ 🚀
+        working-directory: docs
+        run: make deploy

.github/workflows/main.yml

@@ -1,22 +0,0 @@
-name: Deploy docs
-
-on:
-  push:
-    branches:
-      - master
-    paths: 
-      - 'docs/**'
-        
-jobs:
-  build:
-    name: Build
-    runs-on: ubuntu-latest
-    
-    steps:
-      - name: Checkout master
-        uses: actions/checkout@v1
-
-      - name: Deploy to GH Pages
-        uses: mhausenblas/mkdocs-deploy-gh-pages@master
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.gitignore

@@ -1,3 +1,3 @@
-site/
-
 venv
+
+site/

.vscode/settings.json

@@ -1,3 +1,3 @@
 {
-    "python.pythonPath": "venv/bin/python"
-}
+  "python.pythonPath": "venv/bin/python"
+}

.vscode/tasks.json

@@ -1,51 +0,0 @@
-{
-    // See https://go.microsoft.com/fwlink/?LinkId=733558
-    // for the documentation about the tasks.json format
-    "version": "2.0.0",
-    "tasks": [
-        {
-            "label": "build",
-            "type": "process",
-            "command": "${config:python.pythonPath}",
-            "args": ["-m", "mkdocs", "build"],
-            "problemMatcher": [],
-            "group": {
-                "kind": "build",
-                "isDefault": true
-            }
-        },
-        {
-            "label": "serve",
-            "type": "process",
-            "command": "${config:python.pythonPath}",
-            "args": ["-m", "mkdocs", "serve"],
-            "problemMatcher": [],
-        },
-        {
-            "label": "deploy",
-            "type": "process",
-            "command": "${config:python.pythonPath}",
-            "args": ["-m", "mkdocs", "gh-deploy"],
-            "problemMatcher": [],
-        },
-        // Reference globally-installed MkDocs.
-        {
-            "label": "build-global",
-            "type": "shell",
-            "command": "mkdocs build",
-            "problemMatcher": [],
-        },
-        {
-            "label": "serve-global",
-            "type": "shell",
-            "command": "mkdocs serve",
-            "problemMatcher": [],
-        },
-        {
-            "label": "deploy-global",
-            "type": "shell",
-            "command": "mkdocs gh-deploy",
-            "problemMatcher": [],
-        }
-    ]
-}

LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2020 michaelcurrin
+Copyright (c) 2020 - 2021 MichaelCurrin
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

README.md

@@ -1,35 +1,67 @@
 # MkDocs Quickstart
-> A template, live demo and tutorial for how to setup a MkDocs docs site on GitHub Pages
+> Starter template for a MkDocs docs site on GH Pages - including CI
 
-![CI status](https://github.com/MichaelCurrin/mkdocs-quickstart/workflows/Deploy%20docs/badge.svg)
-[![Made with MkDocs](https://img.shields.io/badge/Made_with-MkDocs-blue)](https://www.mkdocs.org/)
-[![GitHub tag](https://img.shields.io/github/tag/MichaelCurrin/mkdocs-quickstart.svg)](https://GitHub.com/MichaelCurrin/mkdocs-quickstart/tags/)
-[![MIT license](https://img.shields.io/badge/License-MIT-blue.svg)](#license)
+[![CI status](https://github.com/MichaelCurrin/mkdocs-quickstart/workflows/Deploy%20Docs/badge.svg)](https://github.com/MichaelCurrin/mkdocs-quickstart/actions)
+[![GitHub tag](https://img.shields.io/github/tag/MichaelCurrin/mkdocs-quickstart?include_prereleases=&sort=semver)](https://github.com/MichaelCurrin/mkdocs-quickstart/releases/)
+[![License](https://img.shields.io/badge/License-MIT-blue)](#license)
 
+[![Made with Python](https://img.shields.io/badge/Python->%3D3.6-blue?logo=python&logoColor=white)](https://python.org)
+[![Made with MkDocs](https://img.shields.io/badge/mkdocs-1-blue)](https://www.mkdocs.org/)
+[![CI - GH Actions](https://img.shields.io/badge/CI-GH_Actions-blue?logo=github-actions&logoColor=white)](https://github.com/features/actions)
+
+A template, live demo and tutorial for how to set up a MkDocs docs site on GH Pages. Using GitHub Actions to automated deploys.
+
+MkDocs is a Python package when turns your docs directory and YAML config into a static website. No Python coding needed. Just Markdown and some light configuration including a theme choice and menu.
 
 <!-- TODO When creating a new project copied from this template, you can delete this README.md and start over -->
 
+
+## Purpose
+
+This project provides low-code content-focused way to set up and host a markdown-based documentation site, with a professional look and themes. Built with MkDocs - a Python package which is a static site generator specializing in documentation.
+
+A GitHub Actions workflow is provided with this template so you can easily deploy to GitHub Pages too.
+
+
 ## Preview
 
-[![Sample screenshot](/sample.png)](https://michaelcurrin.github.io/mkdocs-quickstart/)
+<div align="center">
+
+[![Sample screenshot](/sample.png)](https://michaelcurrin.github.io/mkdocs-quickstart/ "Sample screenshot")
+
+</div>
+
+This template project is configured to use the _Read the Docs_ theme, as shown above. 
+
+Thus looks like the the [Read The Docs][] site, but without having to have to overhead of using Sphinx.
+
+[Read The Docs]: https://docs.readthedocs.io
+
+This Read the Docs theme for MkDocs comes with MkDocs already, so you don't need to add to your dependencies. But you can switch to the MkDocs default or install and configure another theme.
+
+You can switch to the default theme or install some others, based on the instructions in this template project.
+
 
 ## How to use this project
 
 <div align="center">
-  
-[![GH Pages](https://img.shields.io/badge/Github_Pages-MkDocs_Quickstart-green?style=for-the-badge)](https://michaelcurrin.github.io/mkdocs-quickstart/)
-[![Use this template](https://img.shields.io/badge/Use_this_template-2ea44f?style=for-the-badge)](https://github.com/MichaelCurrin/mkdocs-quickstart/generate)
+
+[![GH Pages](https://img.shields.io/badge/View_site-MkDocs_Quickstart-blue?style=for-the-badge)](https://michaelcurrin.github.io/mkdocs-quickstart/)
+
+[![Use this template](https://img.shields.io/badge/Generate-Use_this_template-2ea44f?style=for-the-badge)](https://github.com/MichaelCurrin/mkdocs-quickstart/generate)
 
 </div>
 
 
 ## Features
 
-- A markdown-based docs site which is easy to edit - see the content [docs](/docs/) directory.
-- Easy to configure - see the short [mkdocs.yml](/mkdocs.yml) file.
-- Use the configured theme or switch to another - no need to write HTML and CSS.
-- Uses a deploy pipeline on GH Actions to deploy a GH Pages site.
-
+- A **markdown-based** docs site which is easy to edit - see the content in the [docs](/docs/docs/) directory.
+- Easy to **configure** - see the short [mkdocs.yml](/docs/mkdocs.yml) file.
+- Use the configured theme or switch to another - no need to write HTML and CSS yourself.
+- Each theme comes with a navbar and you write YAML - Jekyll themes on GH Pages need you to write your own HTML often and each theme handles navbar its own way (sometimes not at all).
+- Uses a deploy pipeline on GH Actions to deploy a GH Pages site - the action actually runs GH Pages deploy command.
+- The static site output is **SEO-friendly**.
+- Built on Python but you don't need to write any Python code.
 
 ### View live demo site
 
@@ -46,14 +78,24 @@ This repo also doubles as a template to create a new project from. Click the but
 
 Change the content and theme to suit your needs, based on the tutorial site or the MkDocs site.
 
+To isolate the MkDocs flow from the rest of your code, you can put the configs and the `docs` folder of content inside the `docs` directory. That means you end up having `docs/docs`, which is okay. Just make sure you select the `/docs` directory when setting up GH Pages.
 
-## Why use MkDocs? 
 
-If you're new to MkDocs, look at the tutorial added on this project's site, otherwise go to the MkDocs documentation.
+## About MkDocs
+
+### Resources
+
+- Homepage: [mkdocs.org](http://www.mkdocs.org/)
+- Repo: [![mkdocs - mkdocs](https://img.shields.io/static/v1?label=mkdocs&message=mkdocs&color=blue&logo=github)](https://github.com/mkdocs/mkdocs) [![stars - mkdocs](https://img.shields.io/github/stars/mkdocs/mkdocs?style=social)](https://github.com/mkdocs/mkdocs)
+- PyPI package: [mkdocs](https://pypi.org/project/mkdocs/)
+
+### Why MkDocs?
+
+If you're new to MkDocs, look at the tutorial added on this project's site, otherwise go to the MkDocs homepage for documentation.
 
 This project provides a way to write your docs in markdown and build a professional-looking docs site on top of it, without having to write HTML or CSS code and using a selection of themes. While MkDocs CLI has functionality to deploy from a local command-line, this project makes deploying effortless by using GitHub Actions to build and deploy the site to a `gh-pages` branch and GitHub Pages to serve the site.
 
-Compared with Jekyll and Docsify, I found the MkDocs code is much lighter to setup and changing themes is much easier than Jekyll. Also you get the benefits SEO which Docsify doesn't have. And it includes a search bar using JS.
+Compared with Jekyll and Docsify, I found the MkDocs code is much lighter to set up and changing themes is much easier than Jekyll. Also you get the benefits SEO which Docsify doesn't have. And it includes a search bar using JS.
 
 
 ## Contributing
@@ -63,12 +105,12 @@ Submit an issue.
 Or submit a code change:
 
 1. Fork this project.
-2. Set up the project locally - follow the instructions on the live tutorial or in the [TLDR](/docs/tutorial/tldr.md) page of the local docs.
-3. Make any changes you want. Be sure to keep a copy of the original license in the repo. 
+2. Set up the project locally - follow the instructions on the live tutorial or in the [TL;DR](/docs/docs/tutorial/tldr.md) page of the local docs.
+3. Make any changes you want. Be sure to keep a copy of the original license in the repo.
     - e.g. `cp LICENSE LICENSE-source`
 4. Create a Pull Request.
 
 
 ## License
 
-Released under [MIT](/LICENSE).
+Released under [MIT](/LICENSE) by [@MichaelCurrin](https://github.com/MichaelCurrin).

docs/Makefile

@@ -0,0 +1,29 @@
+.PHONY: docs
+
+default: install
+
+all: install build
+
+
+h help:
+	@grep '^[a-z]' Makefile
+
+
+install:
+	pip install pip --upgrade
+	pip install -r requirements.txt
+
+upgrade:
+	pip install pip --upgrade
+	pip install -r requirements.txt --upgrade
+
+
+s serve:
+	mkdocs serve --strict
+
+
+b build:
+	mkdocs build --strict
+
+d deploy:
+	mkdocs gh-deploy --strict --force

docs/docs/about-mkdocs.md

@@ -7,7 +7,7 @@ The description on the MkDocs site is:
 
 > Project documentation with Markdown.
 
-MkDocs is a Python tool generates a static site based on content written in *markdown*.
+MkDocs is a Python tool that generates a static site based on content written in Markdown.
 
 If you are new to markdown, see the [Getting Started](https://www.markdownguide.org/getting-started/) page on the Markdown Guide website.
 
@@ -17,12 +17,13 @@ If you are new to markdown, see the [Getting Started](https://www.markdownguide.
 - [mkdocs.org](https://www.mkdocs.org) homepage
 - [mkdocs/mkdocs ![Repo stars](https://img.shields.io/github/stars/mkdocs/mkdocs?style=social)](https://github.com/mkdocs/mkdocs)
 - [MkDocs Wiki](https://github.com/mkdocs/mkdocs/wiki) - covering themes, plugins, recipes and more.
+- [Release notes](https://www.mkdocs.org/about/release-notes/) for MkDocs.
 
 
 ## Reasons to use MkDocs
 
 - Create an elegant, modern docs site for your project.
-- Create a static site and serve from Github Pages easily.
+- Create a static site and serve from GitHub Pages easily.
 - Low-code solution
     - No need to write HTML or learn templating syntax needed
     - Use your existing markdown files as content.
@@ -37,4 +38,4 @@ If you are new to markdown, see the [Getting Started](https://www.markdownguide.
 
 ## Do I need to know Python?
 
-MkDocs is built in Python (like Sphynx), but you don't have to write Python code. If you setup a [Deploy](deloy) flow right, you don't even have to set it up locally, though then you can't preview.
+MkDocs is built in Python (like Sphinx), but you don't have to write Python code. If you set up a [Deploy](deploy) flow right, you don't even have to set it up locally, though then you can't preview.

docs/docs/index.md

@@ -1,10 +1,9 @@
 # MkDocs Quickstart
-> A template, live demo and tutorial for how to setup a MkDocs docs site on Github Pages
+>  Started template for a MkDocs docs site on GH Pages - including CI 
 
 [![Repo stars](https://img.shields.io/github/stars/MichaelCurrin/mkdocs-quickstart?style=social)](https://github.com/MichaelCurrin/mkdocs-quickstart)
 
-
-Use the MkDocs (make docs) tool to create build a docs site around markdown docs.
+Use the MkDocs (_make docs_) tool to create build a docs site around markdown docs.
 
 Follow the tutorial to add an existing project or create a project from scratch. The result will look like this project.
 
@@ -17,9 +16,9 @@ Follow the tutorial to add an existing project or create a project from scratch.
     - Run it locally.
     - Deploy it.
 - **Add a copy of this project to your repos**
-    - [![Use this template](https://img.shields.io/badge/Use_this_template-2ea44f)](https://github.com/MichaelCurrin/mkdocs-quickstart/generate)
+    - [![Use this template](https://img.shields.io/badge/Use_this_template-2ea44f?logo=github)](https://github.com/MichaelCurrin/mkdocs-quickstart/generate)
 - **View the live demo**
-    - This site is hosted on Github Pages. See if you like it. Other themes are available - see the tutorial.
+    - This site is hosted on GitHub Pages. See if you like it. Other themes are available - see the tutorial.
 
 
 The aim here is not be complete or explain all concepts. It is to provide a reference for common steps and choices needed when setting up a docs site, but still at a beginner-friendly level.

docs/docs/tutorial/advanced.md

@@ -1,7 +1,7 @@
 # Advanced
 > Beyond the basic configuration and content
 
-Once you've got the [Setup Project](setup_project.md) section, you can customize further using this guide. Or skip this and go to [Usage](usage.md).
+Once you've got the [Set up Project](setup-project.md) section, you can customize further using this guide. Or skip this and go to [Usage](usage.md).
 
 
 ## Navbar nesting
@@ -10,24 +10,14 @@ You can add an additional level to your navbar like this:
 
 ```yaml
 nav:
-    - Home: index.md
-    - About: about.md
-    - Foo:
-        - Overview: foo/index.md
-        - Bar: foo/bar.md
+  - Home: index.md
+  - About: about.md
+  - Foo:
+      - Overview: foo/index.md
+      - Bar: foo/bar.md
 ```
 
-However, adding a path when nesting as below is **invalid** and will give an error:
-
-```yaml
-nav:
-    - Home: index.md
-    - About: about.md
-    - Foo: foo/index.md
-        - Bar: foo/bar.md
-```
-
-See [issue #1139](https://github.com/mkdocs/mkdocs/issues/1139).
+The value can either be a string (as in the first case) or a map (as in the last case). This seems to be a YAML limitation but see also [issue #1139](https://github.com/mkdocs/mkdocs/issues/1139).
 
 
 ## Add config options
@@ -37,7 +27,7 @@ See [Configuration](https://www.mkdocs.org/user-guide/configuration/) page on Mk
 
 ## Separate docs directory approach
 
-You can also structure your project to have the setup above nested inside a `docs` directory. This is useful you have a few other directories and you want to keep the project root clean.
+You can also structure your project to have the set up above nested inside a `docs` directory. This is useful you have a few other directories and you want to keep the project root clean.
 
 
 - `docs/`

docs/docs/tutorial/deploy.md

@@ -0,0 +1,59 @@
+# Deploy
+> Build and deploy to a remote public site
+
+
+See [Deploying Your Docs](https://www.mkdocs.org/user-guide/deploying-your-docs/) on the Mkdocs site for more details.
+
+
+## GitHub Pages
+> How to deploy your docs site to GitHub Pages.
+
+Follow one of the approaches below:
+
+- [Run deploy command](#run-deploy-command) - Run a MkDocs CLI command locally to deploy.
+- [Deploy with GitHub Actions](#deploy-with-github-actions) - Use the project's CI workflow in the cloud to build and deploy to GH Pages on commits pushed to master.
+
+Then go to your repo's _Settings_ and _Pages_ then enable _GitHub Pages_ on the `gh-pages` branch's root.
+
+_Note this is for a Project Page on a subpath, you will have to make adjustments to the command below if you want an Organization or User Page on the root path._
+
+### Run deploy command
+> Run a MkDocs CLI command locally to deploy
+
+MkDocs needs to know where to publish commits on GitHub - so make sure you are working with a repo that you cloned, or that you initialize the local repo and add a `remote` repo.
+
+Run this command locally:
+
+```sh
+$ make d
+```
+
+That will use `Makefile` to run the following:
+
+```sh
+$ mkdocs gh-deploy --strict --force
+```
+
+That will do the following:
+
+1. Clean and build to `site` directory.
+2. Force push to `gh-pages` branch, overwriting any changes which were pushed from another build.
+
+Then go to your repo on GitHub, look at the *Environment* tab.
+
+When it is done building, click _View deployment_ to see your site.
+
+e.g. [michaelcurrin.github.io/mkdocs-quickstart/](https://michaelcurrin.github.io/mkdocs-quickstart/)
+
+See deploy options in the help:
+
+```sh
+$ mkdocs gh-deploy --help
+```
+
+### Deploy with GitHub Actions
+>  Set up continuous deployment config to enable deploys on a change to files on GitHub
+
+When you make changes to your docs config or the docs directory, especially editing on GitHub directly, it's often useful to have the docs site build and deploy automatically in a remote environment. This is provided for free by GitHub.
+
+See the [docs.yml](https://github.com/MichaelCurrin/mkdocs-quickstart/blob/master/.github/workflows/docs.yml) workflow provided with this project. You don't have to change anything there. The token will be generated for you by GitHub Actions.

docs/docs/tutorial/installation.md

@@ -0,0 +1,74 @@
+# Installation
+> How to install MkDocs locally.
+
+
+## Requirements
+
+- [Python 3](https://www.python.org/)
+- [Make](https://www.gnu.org/software/make/) - standard on macOS and Linux but can be installed on Windows too.
+
+
+## Install system dependencies
+
+<script src="https://gist.github.com/MichaelCurrin/57caae30bd7b0991098e9804a9494c23.js"></script>
+
+
+## Set up a new repo
+
+Follow the Tutorial page to set up a project from scratch.
+
+Or click this create your own copy of the repo.
+
+[![Use this template](https://img.shields.io/badge/Use_this_template-2ea44f?style=for-the-badge&logo=github)](https://github.com/MichaelCurrin/mkdocs-quickstart/generate)
+
+Then clone your repo.
+
+e.g.
+
+```sh
+$ git clone git@github.com:MichaelCurrin/mkdocs-quickstart.git
+$ cd mkdocs-quickstart
+```
+
+
+## Install project dependencies
+> Install MkDocs locally
+
+For more info, see the [Installation](https://www.mkdocs.org/#installation) page on the MkDocs site.
+
+### Install in a virtual environment
+
+Create a virtual environment at the project root - this is used to isolate project packages from the global packages.
+
+```sh
+$ python3 -m venv venv
+```
+
+Activate the environment.
+
+```sh
+$ source venv/bin/activate
+```
+
+Install `mkdocs` - this is covered in the project requirements file.
+
+```sh
+$ cd docs
+$ make install
+```
+
+Note - `mkdocs` 1.2 causes a break on force pushes, so this is excluded in the requirements. See issue [#2447](https://github.com/mkdocs/mkdocs/issues/2447).
+
+### Install globally
+
+If you prefer to install MkDocs once and reuse it across projects, then you can install it globally instead.
+
+MkDocs is available using package managers like `apt-get`, `homebrew` and `yum`.
+
+Or you can install like this:
+
+```sh
+$ python3 -m pip install mkdocs
+```
+
+If you get prompted for `sudo` use, then cancel and run again with `-U` flag for user-level install.

docs/docs/tutorial/setup-project.md

@@ -0,0 +1,150 @@
+# Set up project
+> How to create a MkDocs site from scratch
+
+This is a summary of the tutorial on [mkdocs.org](https://www.mkdocs.org/).
+
+
+## How to use this guide
+
+Use one of the approaches below:
+
+- Create a quickstart project with the `new` command covered in [Create a starter site](#create-a-starter-site).
+- Follow the extended guide to create a [Set up up docs site](#setup-a-docs-site) by hand.
+
+### Basic structure
+
+This is the simplest MkDocs site you can make:
+
+- `docs/`
+    - `index.md` - Homepage in the `docs` directory (by default).
+- `mkdocs.yml`
+    - Config at the root - control appearance and navigation of your site.
+    - See this project's [docs/mkdocs.yml](https://github.com/MichaelCurrin/mkdocs-quickstart/blob/master/docs/mkdocs.yml) file on GitHub.
+
+Notes on fields for the config:
+
+- `site_name` - title of your site.
+- `site_description` - used as a description for SEO and you could use it somewhere in your template.
+- `site_url` - now a _required_ field when running a deploy. Include the subpath on the domain. If your site is not ready to be hosted, set this field to an empty string.
+- `repo_url` - for _Edit on GitHub_ button. See [docs](https://www.mkdocs.org/user-guide/configuration/#repo_url).
+- `edit_uri` - defaults to `edit/master/docs/`, which includes `docs` directory of markdown files inside your repo root. But, if the site's root is in an outer `docs` directory, then you need to _also_ add that, so paths do not break. e.g. `edit/master/docs/docs`. See [docs](https://www.mkdocs.org/user-guide/configuration/#edit_uri)
+
+### Requirements file
+
+A requirements file is optional but it can make it easier to manage dependencies. If you choose not use the file, make sure `pip install mkdocs` and `pip install THEME` lines are your instructions.
+
+If you want to add, then include `requirements.txt` at the root. If your project is already a Python project, you might prefer to add `mkdocs` in `requirements-dev.txt` or at `docs/requirements.txt` to keep it isolated.This file should have `mkdocs` in it and also any themes if needed.
+
+### Create a starter site
+
+Run this command to create a starter site. This make the steps below go quicker.
+
+```sh
+cd my-project
+mkdocs new PATH
+```
+
+The result will be same as the [Basic structure](#basic-structure) defined above and will include minimal text content generated by the MkDocs CLI. This text is defined in the project's [new.py](https://github.com/mkdocs/mkdocs/blob/master/mkdocs/commands/new.py) module.
+
+### Set up a docs site
+
+_Tip: Optionally use the `new` command covered above to set up the config and index page first and then continue_.
+
+1. Create doc pages.
+    1. Create a `docs` directory.
+    2. Create `index.md` as your homepage.
+    3. Create other markdown pages (optional).
+        - Use placeholder content if you want to move on and then come back to expand them.
+        - If you have any existing markdown docs, these will work too.
+2. Set up config.
+    1. Create `mkdocs.yml` at the project root.
+    2. Set up a navbar there.
+    3. Choose a theme.
+3. Create a favicon (optional).
+    - It will be picked up at this path: `docs/img/favicon.ico`.
+4. Add to your `.gitignore`.
+    - Add build directory. This will prevent it from being versioned on `master` branch.
+    - Add virtual environment, if using one.
+
+You project should now look this this:
+
+- `docs/`
+    - `index.md`
+    - More pages...
+- `mkdocs.yml`
+- `.gitignore`
+- `venv`
+- `requirements.txt` - optional
+
+
+## Sample content
+
+### Ignore file
+
+`.gitignore`
+```
+site/
+
+venv
+```
+
+### Navbar
+
+`mkdocs.yml`
+```yaml
+nav:
+    - Home: index.md
+    - About: about.md
+```
+
+### Themes
+
+#### Builtin
+
+Use a builtin theme that comes with MkDocs.
+
+The default.
+
+```yaml
+theme: mkdocs
+```
+
+Using ReadTheDocs theme and alternative config syntax.
+
+```yaml
+theme:
+  name: readthedocs
+```
+
+Find more [supported themes](https://github.com/mkdocs/mkdocs/wiki/MkDocs-Themes). If it doesn't immediately, you'll have to use `pip` to install it and add to a `requirements.txt` file.
+
+#### ReadTheDocs Dropdown theme
+
+See below using [mkdocs-rtd-dropdown](https://github.com/cjsheets/mkdocs-rtd-dropdown).
+
+`requirements.txt`:
+```
+mkdocs-rtd-dropdown
+```
+
+`mkdocs.yml`:
+
+```yaml
+theme:
+  name: 'rtd-dropdown'
+```
+
+### Material for MkdDocs theme
+
+See the [MkDocs for Material](https://squidfunk.github.io/mkdocs-material/) homepage. See the Set up page for config options.
+
+`requirements.txt`:
+```
+mkdocs-material-extensions>=1.0
+```
+
+`mkdocs.yml`:
+```yaml
+theme:
+  name: 'material'
+```

docs/docs/tutorial/tldr.md

@@ -6,23 +6,23 @@
 
 1. [Install](installation.md)
     - `pip install mkdocs`
-2. [Setup project](setup_project.md)
-    - `mkdocs new .` or [![Use this template](https://img.shields.io/badge/Use_this_template-green.svg)](https://github.com/MichaelCurrin/mkdocs-quickstart/generate)
+2. [Set up project](setup-project.md)
+    - `mkdocs new .` or [![Use this template](https://img.shields.io/badge/Use_this_template-2ea44f&logo=github)](https://github.com/MichaelCurrin/mkdocs-quickstart/generate)
 3. [Run](usage.md)
     - `mkdocs serve`
-4. View on [http://localhost:8000](http://localhost:8000)
+4. View on [localhost:8000](http://localhost:8000)
 
 
 ## Deploy to remote site
 
 ### Run deploy command locally
 
-1. [Deploy](deploy.md) to Github Pages
+1. [Deploy](deploy.md) to GitHub Pages
     - `mkdocs gh-deploy`
-2. View published site on Github Pages at `https://USERNAME.github.io/REPO-NAME/`
+2. View published site on GitHub Pages at `https://USERNAME.github.io/REPO-NAME/`
 
 ### Run continuous integration
 
-For CI/CD deploy, use Github Actions with an action such as [Deploy MkDocs](https://github.com/marketplace/actions/deploy-mkdocs). Or use Netlify.
+For CI/CD deploy, use GitHub Actions with an action such as [Deploy MkDocs](https://github.com/marketplace/actions/deploy-mkdocs). Or use Netlify.
 
 This is not covered in this tutorial.

docs/docs/tutorial/usage.md

@@ -0,0 +1,47 @@
+# Usage
+> Build and preview a site locally
+
+Make sure to run all commands from the `docs` directory, as that is where `Makefile` is.
+
+```sh
+$ cd docs
+```
+
+
+## CLI help
+
+```sh
+$ make help
+```
+```
+default: install
+all: install build
+h help:
+install:
+upgrade:
+s serve:
+b build:
+d deploy:
+```
+
+
+## Serve docs
+
+This will build the docs in memory (not to disk) and serve an auto-reloading server.
+
+```sh
+$ make serve
+```
+
+Then open in your browser:
+
+- [localhost:8000](http://localhost:8000)
+
+
+## Build docs
+
+Build docs site to `site` directory. This is useful for a CI flow.
+
+```sh
+$ make build
+```

docs/mkdocs.yml

@@ -0,0 +1,23 @@
+### Site metadata ###
+
+site_name: MkDocs Quickstart
+site_description: Starter template for a MkDocs docs site on GH Pages - including CI
+site_url: https://michaelcurrin.github.io/mkdocs-quickstart/
+
+repo_url: https://github.com/MichaelCurrin/mkdocs-quickstart
+edit_uri: edit/master/docs/docs
+
+### Build settings ###
+
+theme: readthedocs
+
+nav:
+  - Home: index.md
+  - About MkDocs: about-mkdocs.md
+  - Tutorial:
+      - TL;DR: tutorial/tldr.md
+      - Installation: tutorial/installation.md
+      - Set up project: tutorial/setup-project.md
+      - Advanced: tutorial/advanced.md
+      - Usage: tutorial/usage.md
+      - Deploy: tutorial/deploy.md

docs/requirements.txt

@@ -0,0 +1 @@
+mkdocs~=1.1,!=1.2

docs/tutorial/deploy.md

@@ -1,58 +0,0 @@
-# Deploy
-> Build and deploy to a remote public site
-
-
-See [Deploying Your Docs](https://www.mkdocs.org/user-guide/deploying-your-docs/) on the Mkdocs site for more details.
-
-
-## Github Pages
-> How to deploy your docs site to Github Pages.
-
-Follow one of the approaches below:
-
-- [Run deploy command](#run-deploy-command) - Run a MkDocs CLI command locally to deploy.
-- [Deploy with Githhub Actions](#deploy-with-github-actions) - Setup continous deployment config to enable deploys on a change to files on Github.
-
-
-_Note this is for a Project Page and not Organization or User Pages._
-
-### Run deploy command
-> Run a MkDocs CLI command locally to deploy
-
-MkDocs needs to know where to publish commits on Github - so make sure you are working with a repo that you cloned, or that you initialize the local repo and add a `remote` repo.
-
-Run this command locally:
-
-```sh
-mkdocs gh-deploy
-```
-
-That will do the following:
-
-1. Clean and build to `site` directory.
-2. Push to `gh-pages` branch. Note: You must not edit this branch directly.
-3. Enable Github Pages if it was not yet enabled
-
-Then go to your repo on Github, see the *environment* tab and click _View deployment_.
-
-e.g.
-
-- [michaelcurrin.github.io/mkdocs-quickstart/](https://michaelcurrin.github.io/mkdocs-quickstart/)
-
-
-See deploy options:
-
-```sh
-mkdocs gh-deploy --help
-```
-
-### Deploy with Github Actions
->  Setup continous deployment config to enable deploys on a change to files on Github
-
-When you make changes to your docs config or the docs directory, especially editing on Github directly, it's often useful to have the docs site build and deploy automatically in a remote environment. This is provided for free by Github.
-
-This action is setup to do that for MkDocs:
-
-- [deploy-mkdocs](https://github.com/marketplace/actions/deploy-mkdocs) action in marketplace.
-
-See this implemented in the [workflow](https://github.com/MichaelCurrin/mkdocs-quickstart/blob/master/.github/workflows/main.yml) file of this MkDocs Quickstart project.

docs/tutorial/installation.md

@@ -1,66 +0,0 @@
-# Installation
-> How to install MkDocs locally.
-
-
-## Requirements
-
-- [Python 3](https://www.python.org/)
-
-
-## Install system dependencies
-
-<script src="https://gist.github.com/MichaelCurrin/57caae30bd7b0991098e9804a9494c23.js"></script>
-
-
-## Setup repo
-
-Choose or setup a MkDocs project.
-
-- Follow the tutorial page to setup a project.
-- Or click _Use this template_ on this repo to create your own copy of the repo, then clone it.
-
-
-## Install project dependencies
-> Install MkDocs locally
-
-For more info, see the [Installation](https://www.mkdocs.org/#installation) page on the MkDocs site.
-
-### Use a virtual environment
-
-Create a virtual environment at the project root.
-
-```sh
-python3 -m venv venv
-```
-
-Activate it.
-
-```sh
-source venv/bin/activate
-```
-
-Install dependencies using one of these approaches:
-
-<!-- Using `sh` for code block breaks for bullet points at least for read the docs theme -->
-
-- Install directly.
-    ```bash
-    pip install mkdocs
-    ```
-- Create a `requirements.txt` file, add `mkdocs` to it then install from the file.
-    ```bash
-    echo 'mkdocs' > requirements.txt
-    pip install -r requirements.txt
-    ```
-
-### Install globally
-
-If you prefer to install MkDocs once and reuse it across projects, then you can install it globally.
-
-MkDocs is available using package managers like `apt-get`, `homebrew` and `yum`.
-
-You can install like this too:
-
-```sh
-python3 -m pip install mkdocs
-```

docs/tutorial/setup-project.md

@@ -1,88 +0,0 @@
-# Setup project
-> How to create a MkDocs site from scratch
-
-This is a summary of the tutorial on [mkdocs.org](https://www.mkdocs.org/).
-
-
-## How to use this guide
-
-Use one of the approaches below:
-
-- Create a quickstart project with the `new` command covered in [Create a starter site](#create-a-starter-site).
-- Follow the extended guide to create a [Setup up docs site](#setup-a-docs-site) by hand.
-
-
-### Basic structure
-
-This is the simplest MkDocs site you can make:
-
-- `docs/`
-    - `index.md` - Homepage in the `docs` directory (by default).
-- `mkdocs.yml` - Config at the root.
-
-
-### Requirements file
-
-A requirements file is optional but it can make it easier to manage dependencies. If you choose not use the file, make sure `pip install mkdocs` and `pip install THEME` lines are your instructions.
-
-If you want to add, then include `requirements.txt` at the root. If your project is already a Python project, you might prefer to add `mkdocs` in `dev-requirements.txt` or at `docs/requirements.txt` to keep it isolated.This file should have `mkdocs` in it and also any themes if needed. 
-
-
-### Create a starter site
-
-Run this command to create a starter site. This make the steps below go quicker.
-
-```sh
-cd my-project
-mkdocs new PATH
-```
-
-The result will be same as the [Basic structure](#basic-structure) defined above and will include minimal text content generated by the MkDocs CLI. This text is defined in the project's [new.py](https://github.com/mkdocs/mkdocs/blob/master/mkdocs/commands/new.py) module.
-
-
-### Setup a docs site
-
-_Tip: Optionally use the `new` command covered above to setup the config and index page first and then continue_.
-
-1. Create doc pages.
-    1. Create a `docs` directory.
-    2. Create `index.md` as your homepage.
-    3. Create other markdown pages (optional).
-        - Use placeholder content if you want to move on and then come back to expand them.
-        - If you have any existing markdown docs, these will work too.
-2. Setup config.
-    1. Create `mkdocs.yml` at project root.
-    2. Setup navbar there. e.g.
-        ```yaml
-        nav:
-            - Home: index.md
-            - About: about.md
-        ```
-    3. Choose a theme. 
-        - An example of choosing a theme which is builtin:
-            ```yaml
-            theme: readthedocs
-            ```
-        - Find more [supported themes](https://github.com/mkdocs/mkdocs/wiki/MkDocs-Themes). If it doesn't immediately, you'll have to use `pip` to install it and add to a `requirements.txt` file.
-            
-3. Create a favicon (optional).
-    - It will be picked up at this path: `docs/img/favicon.ico`.
-4. Add to your `.gitignore`.
-    - Add build directory. This will prevent it from being versioned on `master` branch.
-    - Add virtual environment, if using one.
-    - For example:
-    ```
-    site/
-
-    venv
-    ```
-
-You project should now look this this:
-
-- `docs/`
-    - `index.md`
-    - Other pages...
-- `mkdocs.yml`
-- `.gitignore`
-- `venv`
-- `requirements.txt` - optional

docs/tutorial/usage.md

@@ -1,33 +0,0 @@
-# Usage
-> Build and preview a site locally
-
-_Note: If using VS Code, you can use the command palette instead to run the configured tasks - these are setup in `.vscode/tasks.json`._
-
-
-## Serve docs
-
-This will build the docs in memory (not to disk) and serve an auto-reloading server.
-
-```sh
-mkdocs serve
-```
-
-Open URL:
-
-- [localhost:8000](http://localhost:8000)
-
-
-## Build docs
-
-Build docs site to `site` directory. Useful for production build or simulating that locally.
-
-
-```sh
-mkdocs build
-```
-
-Add this flag to remove stale files when building.
-
-```sh
-mkdocs build --clean
-```

mkdocs.yml

@@ -1,19 +0,0 @@
-site_name: MkDocs Quickstart
-# For SEO.
-site_description: 'A concise recipe for setting up a MkDocs docs site on GitHub Pages'
-
-nav:
-    - Home: index.md
-    - About MkDocs: about-mkdocs.md
-    - Tutorial:
-        - TL;DR: tutorial/tldr.md
-        - Installation: tutorial/installation.md
-        - Setup project: tutorial/setup-project.md
-        - Advanced: tutorial/advanced.md
-        - Usage: tutorial/usage.md
-        - Deploy: tutorial/deploy.md
-        
-theme: readthedocs
-
-# URL for the Edit in GitHub button.
-repo_url: https://github.com/MichaelCurrin/mkdocs-quickstart/

requirements.txt

@@ -1 +0,0 @@
-mkdocs