# Getting started ## Installation ### Installing MkDocs Before installing [MkDocs][1], you need to make sure you have Python and `pip` – the Python package manager – up and running. You can verify if you're already good to go with the following commands: ``` sh python --version # Python 2.7.13 pip --version # pip 9.0.1 ``` Installing and verifying MkDocs is as simple as: ``` sh pip install mkdocs && mkdocs --version # mkdocs, version 0.16.0 ``` !!! warning "MkDocs for Material requirements" Material requires MkDocs >= 0.16. Furthermore, it is highly recommended to install [Pygments][2] and the [PyMdown Extensions][3] to get the most out of the Material theme: ```sh pip install pygments pip install pymdown-extensions ``` [1]: http://www.mkdocs.org [2]: http://pygments.org [3]: http://facelessuser.github.io/pymdown-extensions/ ### Installing Material #### by using pip Material can be installed with `pip`: ``` sh pip install mkdocs-material ``` !!! warning "Installation on Mac OS X" When you're running the pre-installed version of Python on OS X, `pip` tries to install packages in a folder for which your user might not have the adequate permissions. There are two possible solutions to this: 1. **Installing in user space** (recommended): Provide the `--user` flag to the install command and `pip` will install the package in a user-site location. This is the recommended way. 2. **Switching to a homebrewed Python**: Upgrade your Python installation to a self-contained solution by installing Python with Homebrew. This will also eliminate any problems you may be having with `pip`. #### by cloning from GitHub Material can also be used without system-wide installation by cloning the repository into a subfolder of your project's root directory: ``` sh git clone https://github.com/squidfunk/mkdocs-material.git ``` This is especially useful if you want to extend the theme and use partials. The theme will reside in the folder `mkdocs-material/material`. ## Usage In order to enable the Material theme just add one of the following lines to your `mkdocs.yml`. If you installed Material using pip: ``` yaml theme: 'material' ``` When you cloned Material from GitHub, use: ``` yaml theme_dir: 'mkdocs-material/material' ``` That's it. MkDocs includes a development server, so you can view your changes as you go - very handy. Spin it up with the following command: ``` sh mkdocs serve ``` Now you can point your browser to [localhost:8000](http://localhost:8000) and the Material theme should be visible. You can now start writing your documentation, or read on and customize the theme through some options. ## Options The Material theme adds some extra variables for configuration via your project's `mkdocs.yml`. See the following section for all available options. ### Changing the color palette Material defines a default hue for every primary and accent color on Google's material design [color palette][4]. This makes it very easy to change the overall look of the theme. Just set the primary and accent colors using the following variables in your `mkdocs.yml`: ``` yaml extra: palette: primary: 'indigo' accent: 'light blue' ``` Color names can be written upper- or lowercase but must match the names of the material design color palette. Valid values are: `red`, `pink`, `purple`, `deep purple`, `indigo`, `blue`, `light blue`, `cyan`, `teal`, `green`, `light green`, `lime`, `yellow`, `amber`, `orange`, `deep orange`, `brown`, `grey` and `blue grey`. The last three colors can only be used as a primary color. If the color is set via this configuration, an additional CSS file that defines the color palette is included. If you want to keep things lean, clone the repository and recompile the theme with your custom colors set. See [this article](customization.md) for more information. [4]: http://www.materialui.co/colors #### Primary colors Click on a tile to change the primary color of the theme: #### Accent colors Click on a tile to change the accent color of the theme: ### Changing the font family Material uses the [Roboto font family][5] by default, specifically the regular sans-serif type for text and the monospaced type for code. Both fonts are loaded from [Google Fonts][6] and can easily be changed to other fonts, like for example the [Ubuntu font family][7]: ``` yaml extra: font: text: 'Ubuntu' code: 'Ubuntu Mono' ``` The text font will be loaded in font-weights 400 and **700**, the monospaced font in regular weight. If you want to load fonts from other destinations or don't want to use the Google Fonts loading magic, just set `font` to `'none'`: ``` yaml extra: font: 'none' ``` [5]: https://fonts.google.com/specimen/Roboto [6]: https://fonts.google.com/ [7]: https://fonts.google.com/specimen/Ubuntu ### Adding a logo Material makes it easy to add your logo. Your logo should have rectangular shape with a minimum resolution of 128x128, leave some room towards the edges and be composed of high contrast areas on a transparent ground, as it will be placed on the colored header bar and drawer. Simply create the folder `docs/images`, add your logo and embed it with: ``` yaml extra: logo: 'images/logo.svg' ``` ### Adding social links If you want to link your social accounts, the Material theme provides an easy way for doing this in the footer of the documentation using the automatically included [Socicon][8] webfont. The syntax is simple - the `type` denotes the name of the social service, e.g. `github`, `twitter` or `linkedin` and the `link`, well, resembles the link: ``` yaml extra: social: - type: 'github' link: 'https://github.com/squidfunk' - type: 'twitter' link: 'https://twitter.com/squidfunk' - type: 'linkedin' link: 'https://de.linkedin.com/in/martin-donath-20a95039' ``` The links are generated in order. [8]: http://www.socicon.com/chart.php ### Google Analytics integration MkDocs makes it easy to integrate site tracking with Google Analytics. Besides basic tracking, clicks on all outgoing links can be tracked as well as how site search is used. Tracking can be activated in your project's `mkdocs.yml`: ``` yaml google_analytics: - 'UA-XXXXXXXX-X' - 'auto' ``` ### More advanced customization If you want to change the general appearance of the Material theme, see [this article](customization.md) for more information on advanced customization. ## Extensions MkDocs supports several [Markdown extensions][9]. The following extensions are not enabled by default (see the link for which are enabled by default) but highly recommended, so they should be switched on at all times: ``` yaml markdown_extensions: - admonition - codehilite(guess_lang=false) - toc(permalink=true) ``` For more information, see the following list of extensions supported by the Material theme including more information regarding installation and usage: * [Admonition](extensions/admonition.md) * [Codehilite](extensions/codehilite.md) * [Permalinks](extensions/permalinks.md) * [Footnotes](extensions/footnotes.md) * [PyMdown Extensions](extensions/pymdown.md) [9]: http://www.mkdocs.org/user-guide/writing-your-docs/#markdown-extensions ## Full example Below is a full example configuration for a `mkdocs.yml`: ``` yaml # Project information site_name: 'My Project' site_description: 'A short description of my project' site_author: 'John Doe' site_url: 'https://my-github-handle.github.io/my-project' # Repository repo_name: 'GitHub' repo_url: 'https://github.com/my-github-handle/my-project' # Copyright copyright: 'Copyright © 2016 John Doe' # Documentation and theme theme: 'material' # Options extra: logo: 'images/logo.svg' palette: primary: 'indigo' accent: 'indigo' font: text: 'Roboto' code: 'Roboto Mono' social: - type: 'github' link: 'https://github.com/squidfunk' - type: 'twitter' link: 'https://twitter.com/squidfunk' - type: 'linkedin' link: 'https://de.linkedin.com/in/martin-donath-20a95039' # Google Analytics google_analytics: - 'UA-XXXXXXXX-X' - 'auto' # Extensions markdown_extensions: - admonition - codehilite(guess_lang=false) - footnotes - meta - toc(permalink=true) ```