24 Commits

Author SHA1 Message Date
michaelcurrin
49b3a80578 Update README.md 2020-09-10 17:35:30 +02:00
michaelcurrin
dbc5a5a15e Update mkdocs.yml 2020-09-10 17:33:50 +02:00
michaelcurrin
bcd5d97980 Update README.md 2020-09-10 17:31:20 +02:00
michaelcurrin
bf0b822e71 Update README.md 2020-09-10 17:24:39 +02:00
michaelcurrin
1743e1c99f Update README.md 2020-09-10 17:22:18 +02:00
michaelcurrin
a4858ef9ef Update README.md 2020-09-10 17:21:33 +02:00
michaelcurrin
24fcac8f5b Update index.md 2020-09-10 17:20:30 +02:00
michaelcurrin
aa732678ba Update README.md 2020-09-10 17:20:19 +02:00
michaelcurrin
66f0fa8cd7 Update README.md 2020-09-10 17:19:15 +02:00
michaelcurrin
eebbe99358 Update README.md 2020-09-10 17:18:51 +02:00
michaelcurrin
0f4f91bbc8 Update README.md 2020-09-10 17:15:44 +02:00
michaelcurrin
bbdbd30f69 Update index.md 2020-06-16 20:50:36 +02:00
michaelcurrin
09f8bc898f Update deploy.md 2020-06-16 20:49:42 +02:00
michaelcurrin
8aa74eb6b0 Update README.md 2020-06-16 19:47:33 +02:00
michaelcurrin
9571f1ad46 Update and rename about_mkdocs.md to about-mkdocs.md 2020-06-16 19:46:59 +02:00
michaelcurrin
91582e3392 Update mkdocs.yml 2020-06-16 19:46:35 +02:00
michaelcurrin
b4f9479472 Rename setup_project.md to setup-project.md 2020-06-16 19:45:22 +02:00
michaelcurrin
7b0ffe8c9d chore: Update main.yml 2020-06-16 19:44:23 +02:00
michaelcurrin
a8d346de5d Update setup_project.md 2020-06-16 19:38:50 +02:00
michaelcurrin
aa4bf1088c Update installation.md 2020-06-16 19:34:14 +02:00
michaelcurrin
84b65458a2 chore: Add workflow 2020-06-16 19:28:11 +02:00
michaelcurrin
f4f6a6861d Create main.yml 2020-06-16 19:25:14 +02:00
michaelcurrin
735ab35a26 Update setup_project.md 2020-06-16 19:21:26 +02:00
michaelcurrin
65d7c7343b Update README.md 2020-06-16 18:23:36 +02:00
8 changed files with 110 additions and 47 deletions

22
.github/workflows/main.yml vendored Normal file
View File

@@ -0,0 +1,22 @@
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 }}

View File

@@ -1,52 +1,72 @@
# MkDocs Quickstart
> A concise recipe for setting up a MkDocs docs site on Github Pages
> A template, live demo and tutorial for how to setup a MkDocs docs site on GitHub Pages
[![Made with MkDocs](https://img.shields.io/badge/Made_with-MkDocs-blue.svg)](https://www.mkdocs.org/)
![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)](https://github.com/MichaelCurrin/mkdocs-quickstart/blob/master/LICENSE)
[![MIT license](https://img.shields.io/badge/License-MIT-blue.svg)](#license)
<!-- TODO When creating a new project copied from this, you can delete this README.md and start over -->
[![GH pages](https://img.shields.io/badge/Github_Pages-MkDocs_Quickstart-green.svg?style=for-the-badge)](https://michaelcurrin.github.io/mkdocs-quickstart/)
[![Use this template](https://img.shields.io/badge/Use_this_template-green.svg?style=for-the-badge)](https://github.com/MichaelCurrin/mkdocs-quickstart/generate)
<!-- TODO When creating a new project copied from this template, you can delete this README.md and start over -->
## Preview
![sample](/sample.png)
[![Sample screenshot](/sample.png)](https://michaelcurrin.github.io/mkdocs-quickstart/)
## 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)
</div>
## Live site
## Features
This project has a site deployed to Github Pages.
- 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.
_Note: The deploy is currently manually triggered by a local command, however there are Issues open to setup CI/CI remote deploys with Netlify or Github Actions._
### View live demo site
This project has a site deployed to GitHub Pages.
Purposes of the site:
- A live demo.
- Content for a beginner-friendly tutorial on how to setup, run, deploy and customize a MkDocs project like this one.
## Use this template
### Use this template
This repo also doubles as a template to create a new project from. Click the button at the top.
Change the content and theme to suit your needs, based on the tutorial site or the MkDocs site.
## 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.
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.
## Contributing
Fork this project.
Submit an issue.
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.
Or submit a code change:
Make any changes you want. Be sure to keep a copy of the original license in the repo. e.g. `cp LICENSE LICENSE-source`.
Create a Pull Request.
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.
- e.g. `cp LICENSE LICENSE-source`
4. Create a Pull Request.
## License

View File

@@ -1,7 +1,6 @@
# About MkDocs
## What is MkDocs?
The description on the MkDocs site is:

View File

@@ -1,5 +1,5 @@
# MkDocs Quickstart
> A concise recipe for setting up a MkDocs docs site on Github Pages
> A template, live demo and tutorial for how to setup a MkDocs docs site on Github Pages
[![Repo stars](https://img.shields.io/github/stars/MichaelCurrin/mkdocs-quickstart?style=social)](https://github.com/MichaelCurrin/mkdocs-quickstart)
@@ -17,7 +17,7 @@ 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-green.svg)](https://github.com/MichaelCurrin/mkdocs-quickstart/generate)
- [![Use this template](https://img.shields.io/badge/Use_this_template-2ea44f)](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.

View File

@@ -8,10 +8,16 @@ See [Deploying Your Docs](https://www.mkdocs.org/user-guide/deploying-your-docs/
## Github Pages
> How to deploy your docs site to Github Pages.
_Note this is for a Project Page and not Organization and User 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.
@@ -40,11 +46,13 @@ See deploy options:
mkdocs gh-deploy --help
```
### Remote build
> How to trigger a rebuild of your docs site on changes
### 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 without you running a command. A remote build also means you not need to setup Python or MkDocs on your local machine just to get the docs site to work.
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.
So setup a Github Action such as this to your project.
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.

View File

@@ -21,7 +21,7 @@ Choose or setup a MkDocs project.
## Install project dependencies
> Install MkDocs
> Install MkDocs locally
For more info, see the [Installation](https://www.mkdocs.org/#installation) page on the MkDocs site.
@@ -39,22 +39,25 @@ Activate it.
source venv/bin/activate
```
Install dependencies.
Install dependencies using one of these approaches:
- Directly.
```sh
<!-- Using `sh` for code block breaks for bullet points at least for read the docs theme -->
- Install directly.
```bash
pip install mkdocs
```
- Or use a `requirements.txt` file with `mkdocs` in it.
```sh
- 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, you can install it globally.
If you prefer to install MkDocs once and reuse it across projects, then you can install it globally.
MkDocs is available with package managers like `apt-get`, `homebrew` and `yum`.
MkDocs is available using package managers like `apt-get`, `homebrew` and `yum`.
You can install like this too:

View File

@@ -21,6 +21,13 @@ This is the simplest MkDocs site you can make:
- `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.
@@ -56,19 +63,19 @@ _Tip: Optionally use the `new` command covered above to setup the config and ind
```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 it to a `requirements.txt` file.
- 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.
- e.g.
```
site/
- For example:
```
site/
venv
```
venv
```
You project should now look this this:
@@ -78,3 +85,4 @@ You project should now look this this:
- `mkdocs.yml`
- `.gitignore`
- `venv`
- `requirements.txt` - optional

View File

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