Before installing MkDocs, you need to make sure you have Python and
– the Python package manager – up and running. You can verify if you're already
good to go with the following commands:
python --version # Python 2.7.13 pip --version # pip 9.0.1
Installing and verifying MkDocs is as simple as:
pip install mkdocs && mkdocs --version # mkdocs, version 0.17.1
Material requires MkDocs >= 0.17.1.
Material can be installed with
pip install mkdocs-material
choco install mkdocs-material
cloning from GitHub¶
Material can also be used without a system-wide installation by cloning the repository into a subfolder of your project's root directory:
git clone https://github.com/squidfunk/mkdocs-material.git
Installation on macOS
When you're running the pre-installed version of Python on macOS,
tries to install packages in a folder for which your user might not have
the adequate permissions. There are two possible solutions for this:
Installing in user space (recommended): Provide the
--userflag to the install command and
pipwill install the package in a user-site location. This is the recommended way.
Switching to a homebrewed Python: Upgrade your Python installation to a self-contained solution by installing Python with Homebrew. This should eliminate a lot of problems you may be having with
Error: unrecognized theme 'material'
If you run into this error, the most common reason is that you installed
MkDocs through some package manager (e.g. Homebrew or
apt-get) and the
Material theme through
pip, so both packages end up in different
locations. MkDocs only checks its install location for themes.
Alternative: Using Docker¶
If you're familiar with Docker, the official Docker image for Material comes with all dependencies pre-installed and ready-to-use with the latest version published on PyPI, packaged in a very small image. Pull it with:
docker pull squidfunk/mkdocs-material
mkdocs executable is provided as an entrypoint,
serve is the default
command. Start the development server in your project root with:
docker run --rm -it -p 8000:8000 -v `pwd`:/docs squidfunk/mkdocs-material
In order to enable the theme just add one of the following lines to your
mkdocs.yml. If you installed Material using pip:
theme: name: 'material'
If you cloned Material from GitHub:
theme: name: null custom_dir: 'mkdocs-material/material'
MkDocs includes a development server, so you can review your changes as you go. The development server can be started with the following command:
Now you can point your browser to http://localhost:8000 and the Material theme should be visible. From here on, you can start writing your documentation, or read on and customize the theme.
A default hue is defined for every primary and accent color on Google's Material Design color palette, which makes it very easy to change the overall look of the theme. Just set the primary and accent colors using the following variables:
theme: palette: primary: 'indigo' accent: 'indigo'
Color names are case-insensitive, but must match the names of the Material
Design color palette. Valid values are:
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 automatically included. If you want to keep things lean, clone the repository and recompile the theme with your custom colors set. See the guide on customization for more information.
Click on a tile to change the primary color of the theme:
Click on a tile to change the accent color of the theme:
By default the Roboto font family is included with the theme, specifically
the regular sans-serif type for text and the
monospaced type for code. Both
fonts are loaded from Google Fonts and can be changed to other fonts,
like for example the Ubuntu font family:
theme: font: text: 'Ubuntu' code: 'Ubuntu Mono'
The text font will be loaded in weights 400 and 700, the
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
theme: font: false
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:
theme: logo: 'images/logo.svg'
Additionally, the default icon can be changed by setting an arbitrary ligature (or Unicode code point) from the Material Design icon font, e.g.
theme: logo: icon: 'cloud'
Material for MkDocs supports internationalization (i18n) and provides
translations for all template variables and labels in English
zh and Chinese (Traditional)
zh-Hant. Specify the language
theme: language: 'en'
If the language is not specified, Material falls back to English. To create a translation for another language, copy the localization file of an existing language, name the new file using the 2-letter language code and adjust all translations:
cp partials/language/en.html partials/language/jp.html
Feel free to contribute your localization to Material for MkDocs by opening a Pull Request.
Site search is implemented using lunr.js, which includes stemmers for the
English language by default, while stemmers for other languages are included
with lunr-languages, both of which are integrated with this theme. Support
for other languages and even multilingual search can be activated in your
extra: search: language: 'en, de, ru'
All defined languages are used only for stemming. This will automatically load the stemmers for the specified languages and set them up with site search.
At the time of writing, the following languages are supported: English
sv and Turkish
Only specify the languages you really need
The separator for tokenization can be customized which makes it possible
to index parts of words that are separated by
extra: search: tokenizer: '[\s\-\.]+'
The default favicon can be changed by setting the
favicon variable to an
.ico or image file:
theme: favicon: 'assets/mages/favicon.ico'
Material supports another layer on top of the main navigation for larger screens in the form of tabs. This is especially useful for larger documentation projects with only few top-level sections. Tabs can be enabled by setting the respective feature flag to true:
theme: feature: tabs: true
Adding a source repository¶
To include a link to the repository of your project within your documentation,
set the following variables via your project's
repo_name: 'squidfunk/mkdocs-material' repo_url: 'https://github.com/squidfunk/mkdocs-material'
The name of the repository will be rendered next to the search bar on big
screens and as part of the main navigation drawer on smaller screen sizes.
repo_url points to a GitHub, BitBucket or GitLab repository,
the respective service logo will be shown next to the name of the repository.
Additionally, for GitHub, the number of stars and forks is shown.
If the repository is hosted in a private environment, the service logo can be
set explicitly by setting
Why is there an edit button at the top of every article?
repo_url is set to a GitHub or BitBucket repository, and the
repo_name is set to GitHub or BitBucket (implied by default), an
edit button will appear at the top of every article. This is the automatic
behavior that MkDocs implements. See the MkDocs documentation on more
guidance regarding the
edit_uri attribute, which defines whether the edit
button is shown or not.
Adding social links¶
Social accounts can be linked in the footer of the documentation using the
automatically included FontAwesome webfont. The
type must denote the
name of the social service, e.g.
link must contain the URL you want to link to:
extra: social: - type: 'github' link: 'https://github.com/squidfunk' - type: 'twitter' link: 'https://twitter.com/squidfunk' - type: 'linkedin' link: 'https://linkedin.com/in/squidfunk'
The links are generated in order and the
type of the links must match the
name of the FontAwesome glyph. The
fa is automatically added, so
will result in
More advanced customization¶
If you want to change the general appearance of the Material theme, see this article for more information on advanced customization.
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
google_analytics: - 'UA-XXXXXXXX-X' - 'auto'
Material for MkDocs is integrated with Disqus, so if you want to add a
comments section to your documentation set the shortname of your Disqus project
extra: disqus: 'mkdocs-material'
site_url value must be set in
mkdocs.yml for the Disqus integration to
MkDocs supports several Markdown extensions. 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:
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:
Below is a full example configuration for a
# Project information site_name: 'Material for MkDocs' site_description: 'A Material Design theme for MkDocs' site_author: 'Martin Donath' site_url: 'https://squidfunk.github.io/mkdocs-material/' # Repository repo_name: 'squidfunk/mkdocs-material' repo_url: 'https://github.com/squidfunk/mkdocs-material' # Copyright copyright: 'Copyright © 2016 - 2017 Martin Donath' # Configuration theme: name: 'material' language: 'en' palette: primary: 'indigo' accent: 'indigo' font: text: 'Roboto' code: 'Roboto Mono' # Customization extra: social: - type: 'github' link: 'https://github.com/squidfunk' - type: 'twitter' link: 'https://twitter.com/squidfunk' - type: 'linkedin' link: 'https://linkedin.com/in/squidfunk' # Google Analytics google_analytics: - 'UA-XXXXXXXX-X' - 'auto' # Extensions markdown_extensions: - admonition - codehilite: guess_lang: false - toc: permalink: true