📐 Jekyll theme for building a personal site, blog, project documentation, or portfolio.
Find a file
Tony Ho ab6c416e7e Fix system font rendering in Chrome on macOS/OS X (#1290)
Use `BlinkMacSystemFont` instead of private font name.

Closes #1289
2017-10-03 08:29:33 -04:00
.github Update stale bot message 2017-09-23 22:21:06 -04:00
_data Fix param name from pt-BR locale (#1279) 2017-09-28 14:16:07 -04:00
_includes Add alt description to avatar image 2017-09-20 15:56:08 -04:00
_layouts Release 4.6.0 💎 2017-09-12 14:59:06 -04:00
_sass Fix system font rendering in Chrome on macOS/OS X (#1290) 2017-10-03 08:29:33 -04:00
assets Release 4.6.0 💎 2017-09-12 14:59:06 -04:00
docs New comment. (#1283) 2017-10-02 16:14:46 -04:00
test Color "skins" (#1242) 2017-09-12 12:01:43 -04:00
.editorconfig Add editor config file 2016-02-24 16:15:19 -05:00
.gitattributes Try to get Linguist to ignore vendor files 2016-03-09 12:16:54 -05:00
.gitignore Update files and directories ignored by Git 2016-09-21 21:43:02 -04:00
_config.yml Color "skins" (#1242) 2017-09-12 12:01:43 -04:00
banner.js Remove blank YAML Front Matter from JavaScript banner 2017-08-06 10:43:36 -04:00
CHANGELOG.md Update CHANGELOG and history 2017-09-27 12:47:16 -04:00
Gemfile Update Gemfile 2016-09-21 21:43:43 -04:00
index.html Add default config and home index page 2016-10-10 11:47:44 -04:00
LICENSE.txt Update year 2017-03-22 09:53:37 -04:00
minimal-mistakes-jekyll.gemspec Release 4.6.0 💎 2017-09-12 14:59:06 -04:00
package.json Release 4.6.0 💎 2017-09-12 14:59:06 -04:00
Rakefile Use a plugin to read data files from gem 2017-07-19 09:55:45 +05:30
README.md Use archive page screenshots instead of post 2017-09-12 15:39:16 -04:00
screenshot-layouts.png Update README 2016-10-06 21:13:40 -04:00
screenshot.png Add theme screenshot 2016-09-21 21:10:03 -04:00

Minimal Mistakes Jekyll Theme

GitHub release GitHub license

Minimal Mistakes is a flexible two-column Jekyll theme. Perfect for hosting your personal site, blog, or portfolio on GitHub or self-hosting on your own server. As the name implies --- styling is purposely minimalistic to be enhanced and customized by you 😄.

See what's new in the CHANGELOG.

Minimal Mistakes live preview

layout examples

Notable Features

Skins (Color Variations)

This theme comes in seven different skins (including the default one).

air contrast dark
air skin contrast skin dark skin
dirt mint sunrise
dirt skin mint skin sunrise skin

Demo Pages

Name Description
Post with Header Image A post with a large header image.
HTML Tags and Formatting Post A variety of common markup showing how the theme styles them.
Syntax Highlighting Post Post displaying highlighted code.
Post with a Gallery A post showing several images wrapped in <figure> elements.
Sample Collection Page Single page from a collection.
Categories Archive Posts grouped by category.
Tags Archive Posts grouped by tag.

Additional sample posts are available under posts archive on the demo site. Source files for these (and the entire demo site) can be found in /docs.

Usage

For detailed instructions on how to configure, customize, add content, and more read the theme's documentation.

Note: Gem version of the theme requires Jekyll v3.3+ and is not currently supported on GitHub Pages. You can still use the theme with GitHub Pages, you'll just need to install using the old "repo fork method".

Quick Start

Add this line to your Jekyll site's Gemfile:

gem "minimal-mistakes-jekyll"

Add this line to your Jekyll site's _config.yml file:

theme: minimal-mistakes-jekyll

Then run Bundler to install the theme gem and dependencies:

bundle install

To update the theme run bundle update.


Contributing

Having trouble working with the theme? Found a typo in the documentation? Interested in adding a feature or fixing a bug? Then by all means submit an issue or pull request. If this is your first pull request, it may be helpful to read up on the GitHub Flow first.

Minimal Mistakes has been designed as a base for you to customize and fit your site's unique needs. Please keep this in mind when requesting features and/or submitting pull requests. If it's not something that most people will use, I probably won't consider it. When in doubt ask.

This goes for author sidebar links and "share button" additions -- I have no intention of merging in every possibly option, the essentials are there to get you started 😄.

Pull Requests

When submitting a pull request:

  1. Clone the repo.
  2. Create a branch off of master and give it a meaningful name (e.g. my-awesome-new-feature) and describe the feature or fix.
  3. Open a pull request on GitHub.

Theme documentation and demo pages can be found in the /docs if submitting improvements, typo corrections, etc.

Development

To set up your environment to develop this theme, run bundle install.

To test the theme, run bundle exec rake preview and open your browser at http://localhost:4000/test/. This starts a Jekyll server using content in the test/ directory. As modifications are made to the theme and test site, it will regenerate and you should see the changes in the browser after a refresh.


Credits

Creator

Michael Rose

Icons + Demo Images:

Other:


License

The MIT License (MIT)

Copyright (c) 2017 Michael Rose

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.