Minimal Mistakes has been developed as a Jekyll theme gem for easier use. It is also 100% compatible with GitHub Pages — just with slightly different installation process.
Installing the Theme
If you’re running Jekyll v3.5+ and self-hosting you can quickly install the theme as a Ruby gem.
ProTip: Be sure to remove
/test if you forked Minimal Mistakes. These folders contain documentation and test pages for the theme and you probably don’t want them littering up your repo.
Note: The theme uses the jekyll-include-cache plugin which will need to be installed in your
Gemfile and added to the
plugins array of
_config.yml. Otherwise you’ll throw
Unknown tag 'include_cached' errors at build.
Ruby Gem Method
Add this line to your Jekyll site’s
Add these lines to your Jekyll site’s
theme: minimal-mistakes-jekyll plugins: - jekyll-include-cache
Then run Bundler to install the theme gem and dependencies:
GitHub Pages Method
GitHub Pages has added full support for any GitHub-hosted theme.
gem "jekyll" with:
gem "github-pages", group: :jekyll_plugins
bundle update and verify that all gems install properly.
remote_theme: "mmistakes/minimal-mistakes" to your
_config.yml file. Remove any other
plugins like so:
plugins: - jekyll-include-cache
You may also optionally specify a branch, tag, or commit to use by appending an @ and the Git ref (e.g.,
mmistakes/minimal-mistakes@bbf3cbc5fd64a3e1885f3f99eb90ba92af84063d). If you don’t specify a Git ref, the master branch will be used.
Note: Your Jekyll site should be viewable immediately at http://USERNAME.github.io. If it’s not, you can force a rebuild by Customizing Your Site (see below for more details).
If you’re hosting several Jekyll based sites under the same GitHub username you will have to use Project Pages instead of User Pages. Essentially you rename the repo to something other than USERNAME.github.io and create a
gh-pages branch off of
master. For more details on how to set things up check GitHub’s documentation.
You can also install the theme by copying all of the theme files1 into your project.
To do so fork the Minimal Mistakes theme, then rename the repo to USERNAME.github.io — replacing USERNAME with your GitHub username.
GitHub Pages Alternatives: Looking to host your site for free and install/update the theme painlessly? Netflify, GitLab Pages, and Continuous Integration (CI) services have you covered. In most cases all you need to do is connect your repository to them, create a simple configuration file, and install the theme following the Ruby Gem Method above.
Remove the Unnecessary
If you forked or downloaded the
minimal-mistakes-jekyll repo you can safely remove the following folders and files:
Note: If forking the theme be sure to update
Gemfile as well. The one found at the root of the project is for building the theme’s Ruby gem and is missing dependencies. To properly setup a
Gemfile with the theme, consult the “Install Dependencies” section.
Setup Your Site
Depending on the path you took installing Minimal Mistakes you’ll setup things a little differently.
ProTip: The source code and content files for this site can be found in the
/docs folder if you want to copy or learn from them.
v4.5.0 onwards, Minimal Mistakes theme-gem comes bundled with the necessary data files and will automatically use them via the
jekyll-data plugin. So you no longer need to maintain a copy of these data files at your project directory.
However like all other bundled files, you’ll need to create and edit these data files to customize them. The bundled data files are:
Scaffolding out a site with the
jekyll new command requires you to modify a few files that it creates.
<site root>/index.mdwith a modified Minimal Mistakes
index.html. Be sure to enable pagination if using the
homelayout by adding the necessary lines to _config.yml.
about.md, or at the very least change
layout: singleand remove references to
icon-github.html(or copy to your
_includesif using it).
Migrating to Gem Version
If you’re migrating a site already using Minimal Mistakes and haven’t customized any of the theme files things upgrading will be easier for you.
Start by removing the following folders and any files within them:
├── _includes ├── _layouts ├── _sass ├── assets | ├── css | ├── fonts | └── js
You won’t need these anymore as they’re bundled with the theme gem — unless you intend to override them.
Note: When clearing out the
v4.5.0 onwards, you don’t have to maintain a copy of the default data files viz.
The default files are read-in automatically via the
If you customized any of these files leave them alone, and only remove the untouched ones. If done correctly your modified versions should override the versions bundled with the theme and be used by Jekyll instead.
gem "github-pages or
gem "jekyll" with
gem "jekyll", "~> 3.5". You’ll need the latest version of Jekyll2 for Minimal Mistakes to work and load all of the theme’s assets properly, this line forces Bundler to do that.
Add the Minimal Mistakes theme gem:
When finished your
Gemfile should look something like this:
source "https://rubygems.org" gem "jekyll", "~> 3.5" gem "minimal-mistakes-jekyll"
bundle update and add
theme: minimal-mistakes-jekyll to your
v4 Breaking Change: Paths for image headers, overlays, teasers, galleries, and feature rows have changed and now require a full path. Instead of just
image: filename.jpg you’ll need to use the full path eg:
image: /assets/images/filename.jpg. The preferred location is now
/assets/images/ but can be placed elsewhere or externally hosted. This applies to image references in
author.yml as well.
That’s it! If all goes well running
bundle exec jekyll serve should spin-up your site.