diff --git a/_config.dev.yml b/_config.dev.yml
deleted file mode 100644
index a1b40341..00000000
--- a/_config.dev.yml
+++ /dev/null
@@ -1,6 +0,0 @@
-# Develop override settings
-
-url: http://localhost:4000
-
-analytics:
- provider: false
\ No newline at end of file
diff --git a/_config.yml b/_config.yml
index b6499c46..57ff92c8 100644
--- a/_config.yml
+++ b/_config.yml
@@ -7,20 +7,20 @@
# Site Settings
locale : "en-US"
-title : "Minimal Mistakes"
+title : "Site Title"
title_separator : "-"
-name : &name "Michael Rose"
-description : &description "A flexible Jekyll theme for your blog or site with a minimalist aesthetic."
-url : # the base hostname & protocol for your site e.g. "//github.io.mmistakes"
-baseurl : "/minimal-mistakes" # the subpath of your site, e.g. "/blog"
-gh_repo : "https://github.com/mmistakes/minimal-mistakes"
+name : "Your Name"
+description : "An amazing website."
+url : # the base hostname & protocol for your site e.g. "https://github.io.mmistakes"
+baseurl : # the subpath of your site, e.g. "/blog"
+gh_repo :
teaser : # filename of teaser fallback teaser image placed in /images/, .e.g. "500x300.png"
-breadcrumbs : true # true, false (default)
-words_per_minute : 200
+# breadcrumbs : false # true, false (default)
+# words_per_minute : 200
comments:
- provider : "disqus" # false (default), "disqus", "facebook", "google-plus", custom"
+ provider : # false (default), "disqus", "facebook", "google-plus", custom"
disqus:
- shortname : "mmistakes-dev" # https://help.disqus.com/customer/portal/articles/466208-what-s-a-shortname-
+ shortname : # https://help.disqus.com/customer/portal/articles/466208-what-s-a-shortname-
facebook:
# https://developers.facebook.com/docs/plugins/comments
appid :
@@ -28,33 +28,31 @@ comments:
colorscheme : # "light" (default), "dark"
# SEO Related
-google_site_verification : "UQj93ERU9zgECodaaXgVpkjrFn9UrDMEzVamacSoQ8Y"
+google_site_verification :
bing_site_verification :
alexa_site_verification :
yandex_site_verification :
# Social Sharing
twitter:
- username : &twitter "mmistakes"
+ username :
facebook:
- username : &facebook "michaelrose"
+ username :
app_id :
publisher :
-og_image : "site-logo.png" # Open Graph/Twitter default site image
+og_image : # Open Graph/Twitter default site image
# For specifying social profiles
# - https://developers.google.com/structured-data/customize/social-profiles
social:
type : # Person or Organization (defaults to Person)
name : # If the user or organization name differs from the site's name
links: # An array of links to social media profiles
- - "https://twitter.com/mmistakes"
- - "https://facebook.com/michaelrose"
# Analytics
analytics:
- provider : "google-universal" # false (default), "google", "google-universal", "custom"
+ provider : false # false (default), "google", "google-universal", "custom"
google:
- tracking_id : "UA-2011187-3"
+ tracking_id :
# Google AdSense
google_ad_client :
@@ -63,22 +61,22 @@ google_ad_slot :
# Site Author
author:
- name : *name
+ name : "Your Name"
avatar : "bio-photo.jpg"
- bio : *description
- location : "Buffalo, NY"
- email : *email
- uri : "https://mademistakes.com"
+ bio : "I am an amazing person."
+ location : "Somewhere"
+ email :
+ uri :
bitbucket :
codepen :
dribbble :
flickr :
- facebook : *facebook
+ facebook :
foursquare :
- github : "mmistakes"
+ github :
google_plus :
keybase :
- instagram : "mmistakes"
+ instagram :
lastfm :
linkedin :
pinterest :
@@ -86,7 +84,7 @@ author:
stackoverflow : # http://stackoverflow.com/users/123456/username
steam :
tumblr :
- twitter : *twitter
+ twitter :
vine :
weibo :
xing :
@@ -147,85 +145,11 @@ kramdown:
enable_coderay: false
-# Collections
-collections:
- docs:
- output: true
- permalink: /:collection/:path/
- recipes:
- output: true
- permalink: /:collection/:path/
- pets:
- output: true
- permalink: /:collection/:path/
- portfolio:
- output: true
- permalink: /:collection/:path/
-
-
-# Defaults
-defaults:
- # _posts
- - scope:
- path: ""
- type: posts
- values:
- layout: single
- author_profile: true
- read_time: true
- comments: true
- share: true
- related: true
- # _pages
- - scope:
- path: ""
- type: pages
- values:
- layout: single
- author_profile: true
- # _docs
- - scope:
- path: ""
- type: docs
- values:
- layout: single
- read_time: false
- author_profile: false
- share: false
- comments: false
- # _recipes
- - scope:
- path: ""
- type: recipes
- values:
- layout: single
- author_profile: true
- share: true
- comments: true
- # _pets
- - scope:
- path: ""
- type: pets
- values:
- layout: single
- author_profile: true
- share: true
- comment: true
- # _portfolio
- - scope:
- path: ""
- type: portfolio
- values:
- layout: single
- author_profile: false
- share: true
-
-
# Outputting
permalink: /:categories/:title/
paginate: 5 # amount of posts to show
paginate_path: /page:num/
-timezone: America/New_York # http://en.wikipedia.org/wiki/List_of_tz_database_time_zones
+timezone: # http://en.wikipedia.org/wiki/List_of_tz_database_time_zones
# Plugins
@@ -235,8 +159,6 @@ gems:
- jekyll-gist
- jekyll-feed
- jemoji
- - jekyll-redirect-from
- # - jekyll-archives
# mimic GitHub Pages with --safe
whitelist:
@@ -245,7 +167,6 @@ whitelist:
- jekyll-gist
- jekyll-feed
- jemoji
- - jekyll-redirect-from
# Archives
diff --git a/_data/authors.yml b/_data/authors.yml
deleted file mode 100644
index 0ea8a64a..00000000
--- a/_data/authors.yml
+++ /dev/null
@@ -1,18 +0,0 @@
-# Authors
-
-Billy Rick:
- name : "Billy Rick"
- uri : "http://thewhip.com"
- email : "billy@rick.com"
- bio : "What do you want, jewels? I am a very extravagant man."
- avatar : "bio-photo-2.jpg"
- twitter : "extravagantman"
- google_plus : "BillyRick"
-
-Cornelius Fiddlebone:
- name : "Cornelius Fiddlebone"
- email : "cornelius@thewhip.com"
- bio : "I ordered what?"
- avatar : "bio-photo.jpg"
- twitter : "rhymeswithsackit"
- google_plus : "CorneliusFiddlebone"
\ No newline at end of file
diff --git a/_data/navigation.yml b/_data/navigation.yml
index de39d6c9..fee066fc 100644
--- a/_data/navigation.yml
+++ b/_data/navigation.yml
@@ -1,77 +1,16 @@
# main links links
main:
- title: "Quick-Start Guide"
- url: /docs/quick-start-guide/
+ url: https://mmistakes.github.io/minimal-mistakes/docs/quick-start-guide/
- - title: "Posts"
- url: /year-archive/
+ - title: "About"
+ url: https://mmistakes.github.io/minimal-mistakes/
- - title: "Categories"
- url: /categories/
+ - title: "Sample Posts"
+ url: https://mmistakes.github.io/minimal-mistakes/year-archive/
- - title: "Tags"
- url: /tags/
+ - title: "Sample Pages"
+ url: https://mmistakes.github.io/minimal-mistakes/page-archive/
- - title: "Pages"
- url: /page-archive/
-
- - title: "Collections"
- url: /collection-archive/
-
-
-# documentation links
-docs:
- - title: Getting Started
- children:
- - title: "Quick-Start Guide"
- path: quick-start-guide
- - title: "Structure"
- path: structure
- - title: "Installation"
- path: installation
- - title: "Upgrading"
- path: upgrading
-
- - title: Customization
- children:
- - title: "Configuration"
- path: configuration
- - title: "Navigation"
- path: navigation
- - title: "UI Text"
- path: ui-text
- - title: "Authors"
- path: authors
- - title: "Layouts"
- path: layouts
-
- - title: Content
- children:
- - title: "Working with Posts"
- path: posts
- - title: "Working with Pages"
- path: pages
- - title: "Working with Collections"
- path: collections
- - title: "Helpers"
- path: helpers
- - title: "Utility Classes"
- path: utility-classes
-
- - title: Extras
- children:
- - title: "Stylesheets"
- path: stylesheets
- - title: "JavaScript"
- path: javascript
-
- - title: Meta
- children:
- - title: "History"
- path: history
- - title: "Contributing"
- path: contributing
- - title: "Old 2.2 Docs"
- path: docs-2-2
- - title: "License"
- path: license
\ No newline at end of file
+ - title: "Sample Collections"
+ url: https://mmistakes.github.io/minimal-mistakes/collection-archive/
\ No newline at end of file
diff --git a/_docs/01-quick-start-guide.md b/_docs/01-quick-start-guide.md
deleted file mode 100644
index 1a2fad57..00000000
--- a/_docs/01-quick-start-guide.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title: "Quick-Start Guide"
-permalink: /docs/quick-start-guide/
-excerpt: "How to quickly install and setup Minimal Mistakes for use with GitHub Pages."
-sidebar:
- title: "v3.0"
- nav: docs
-modified: 2016-04-13T15:54:02-04:00
----
-
-{% include base_path %}
-
-Minimal Mistakes has been developed to be 100% compatible with hosting a site on [GitHub Pages](https://pages.github.com/). To get up and running with a new GitHub repository quickly, follow these steps or jump ahead to the [full installation guide]({{ base_path }}/docs/installation/).
-
-## Fork the Theme
-
-Fork the [Minimal Mistakes theme]({{ site.gh_repo }}/fork), then rename the repo to **USERNAME.github.io** --- replacing **USERNAME** with your GitHub username.
-
-
-
-**Note:** Your Jekyll site should be viewable immediately at . If it's not, you can force a rebuild by **Customizing Your Site** (see below for more details).
-{: .notice--warning}
-
-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](https://help.github.com/articles/user-organization-and-project-pages/).
-
-
-
-**ProTip:** Be sure to [delete](https://github.com/blog/1377-create-and-delete-branches) the `gh-pages` branch if you forked Minimal Mistakes. This branch contains the documentation and demo site for the theme and you probably don't want that showing up in your repo.
-{: .notice--info}
-
-## Customize Your Site
-
-Open up `_config.yml` found in the root of the repo and edit anything under **Site Settings**. For a full explanation of every setting be sure to read the [**Configuration**]({{ base_path }}/docs/configuration/) section, but for now let's just change the site's title.
-
-
-
-Committing a change to `_config.yml` (or any file in your repository) will force GitHub Pages to rebuild your site with Jekyll. It should then be viewable a few seconds later at `https://USERNAME.github.io`.
-
----
-
-Congratulations! You've successfully forked the theme and are up an running with GitHub Pages. Now you're ready to add content and customize the site further.
\ No newline at end of file
diff --git a/_docs/02-structure.md b/_docs/02-structure.md
deleted file mode 100644
index dc08e734..00000000
--- a/_docs/02-structure.md
+++ /dev/null
@@ -1,57 +0,0 @@
----
-title: "Structure"
-permalink: /docs/structure/
-excerpt: "How the theme is organized and what all of the files are for."
-sidebar:
- title: "v3.0"
- nav: docs
-modified: 2016-04-13T15:54:02-04:00
----
-
-Nothing clever here :wink:. Layouts, data files, and includes are all placed in their default locations. Stylesheets and scripts in `assets`, and a few development related files in the project's root directory.
-
-```bash
-minimal-mistakes
-├── _data # data files for customizing the theme
-| ├── navigations.yml # main navigation links
-| └── ui-text.yml # text used throughout the theme's UI
-├── _includes
-| ├── analytics-providers # snippets for analytics (Google and custom)
-| ├── comments-providers # snippets for comments (Disqus, Facebook, Google+, and custom)
-| ├── footer # custom snippets to add to site footer
-| ├── head # custom snippets to add to site head
-| ├── base_path # site.url + site.baseurl shortcut
-| ├── feature_row # feature row helper
-| ├── gallery # image gallery helper
-| ├── group-by-array # group by array helper for archives
-| ├── nav_list # navigation list helper
-| ├── toc # table of contents helper
-| └── ...
-├── _layouts
-| ├── archive-taxonomy.html # tag/category archive for Jekyll Archives plugin
-| ├── archive.html # archive listing documents in an array
-| ├── compress.html # compresses HTML in pure Liquid
-| ├── default.html # base for all other layouts
-| ├── single.html # single document (post/page/etc)
-| └── splash.html # splash page
-├── assets
-| ├── _scss # stylesheet source files
-| | ├── vendor # vendor SCSS partials
-| | ├── main.scss # imports all SCSS partials
-| | └── ... # theme SCSS partials
-| ├── css
-| | └── main.css # optimized stylesheet loaded in
-| ├── fonts
-| | └── fontawesome-webfont # Font Awesome webfonts
-| ├── js
-| | ├── plugins # jQuery plugins
-| | ├── vendor # vendor scripts
-| | ├── _main.js # plugin settings and other scripts to load after jQuery
-| | └── main.min.js # optimized and concatenated script file loaded before
-├── images # image assets for posts/pages/collections/etc.
-├── _config.yml # site configuration
-├── Gemfile # gem file dependencies
-├── Gemfile.lock # gem file dependencies
-├── index.html # paginated home page showing recent posts
-└── package.json # NPM build scripts
-```
\ No newline at end of file
diff --git a/_docs/03-installation.md b/_docs/03-installation.md
deleted file mode 100644
index 0dc82a98..00000000
--- a/_docs/03-installation.md
+++ /dev/null
@@ -1,80 +0,0 @@
----
-title: "Installation"
-permalink: /docs/installation/
-excerpt: "Instructions for installing the theme for new and existing Jekyll based sites."
-sidebar:
- title: "v3.0"
- nav: docs
-modified: 2016-04-13T15:54:02-04:00
----
-
-{% include base_path %}
-
-## Install the Theme
-
-There are several ways to install the theme:
-
-**1.** For a **new site**, fork the Minimal Mistakes repo on GitHub. If you plan on hosting your site with GitHub Pages follow the steps outlined in the [*Quick-Start Guide*]({{ base_path }}/docs/quick-start-guide/).
-
-**2.** For an **existing site** you have some more work ahead of you. What I suggest is to fork and rename the theme's repo as before, then clone it locally by running `git clone https://github.com/USERNAME/REPONAME.git` --- replacing **USERNAME** and **REPONAME** with your own.
-
-
-
-**3.** And for those who don't want to mess with Git, you can download the theme as a ZIP file to work with locally.
-
-[ Download Minimal Mistakes Theme]({{ site.gh_repo }}/archive/master.zip){: .btn .btn--success}
-
-**ProTip:** Be sure to [delete](https://github.com/blog/1377-create-and-delete-branches) the `gh-pages` branch if you forked Minimal Mistakes. This branch contains the documentation and demo site for the theme and you probably don't want that showing up in your repo.
-{: .notice--info}
-
----
-
-To move over any existing content you'll want to copy the contents of your `_posts` folder to the new site. Along with any pages, collections, data files, images, or other assets you may have.
-
-Next you'll need to convert posts and pages to use the proper layouts and settings. In most cases you simply need to update `_config.yml` to your liking and set the correct `layout` in their YAML Front Matter.
-
-[**Front Matter defaults**](https://jekyllrb.com/docs/configuration/#front-matter-defaults) are your friend and I encourage you to leverage them instead of setting a layout and other global options in each post/page's YAML Front Matter.
-
-Posts can be configured to use the `single` layout --- with reading time, comments, social sharing links, and related posts enabled. Adding the following to `_config.yml` will set these defaults for all posts:
-
-```yaml
-defaults:
- # _posts
- - scope:
- path: ""
- type: posts
- values:
- layout: single
- read_time: true
- comments: true
- share: true
- related: true
-```
-
-**Post/Page Settings**: Be sure to read through the "Working with..." documentation to learn about all the options available to you. The theme has been designed to be flexible --- with numerous settings for each.
-{: .notice--info}
-
-## Install Dependencies
-
-If this is your first time using Jekyll be sure to read through the [official documentation](https://jekyllrb.com/docs/home/) before jumping in. This guide assumes you have Ruby v2 installed and a basic understanding of how Jekyll works.
-
-To keep your sanity and better manage dependencies I strongly urge you to [install Bundler](http://bundler.io/) with `gem install bundler` and use the included [`Gemfile`]({{ site.gh_repo }}/blob/master/Gemfile). The theme's Gemfile includes the `github-pages` gem to maintain a local Jekyll environment in sync with GitHub Pages.
-
-If you're not planning on hosting with GitHub Pages and want to leverage features found in the latest version of Jekyll, replace `gem "github-pages"` with `gem "jekyll"` in your `Gemfile`. In either case run the following:
-
-```bash
-$ bundle install
-```
-
-
-
-Depending on what gems you already have installed you may have to run `bundle update` to clear up any dependency issues. Bundler is usually pretty good at letting you know what gems need updating or have issues installing, to further investigate.
-
-When using Bundler to manage gems you'll want to run Jekyll using `bundle exec jekyll serve` and `bundle exec jekyll build`.
-
-Doing so executes the gem versions specified in `Gemfile.lock`. Sure you can test your luck with a naked `jekyll serve`, but I wouldn't suggest it. A lot of Jekyll errors originate from outdated or conflicting gems fighting with each other. So do yourself a favor and just use Bundler.
\ No newline at end of file
diff --git a/_docs/04-upgrading.md b/_docs/04-upgrading.md
deleted file mode 100644
index f29332b9..00000000
--- a/_docs/04-upgrading.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: "Upgrading"
-permalink: /docs/upgrading/
-excerpt: "Instructions and suggestions for upgrading the theme."
-sidebar:
- title: "v3.0"
- nav: docs
-modified: 2016-04-13T15:54:02-04:00
----
-
-{% include base_path %}
-
-Currently there is no good way of upgrading the theme without doing a bit of manual work. The future looks promising with [**gem based themes**](https://github.com/jekyll/jekyll/pull/4595) on the horizon, but for now here's some suggestions on how handle theme updates.
-
-## Use Git
-
-If you want to get the most out of the Jekyll + GitHub Pages workflow, then you'll need to utilize Git. To pull down theme updates you must first ensure there's an upstream remote. If you forked the theme's repo then you're likely good to go.
-
-To double check, run `git remote -v` and verify that you can fetch from `origin {{ site.gh_repo }}/minimal-mistakes.git`.
-
-To add it you can do the following:
-
-```bash
-$ git remote add upstream {{ site.gh_repo }}/minimal-mistakes.git
-```
-
-### Pull Down Updates
-
-Now you can pull any commits made to theme's `master` branch with:
-
-```bash
-$ git pull upstream master
-```
-
-Depending on the amount of customizations you've made after forking, there's likely to be merge conflicts. Work through any conflicting files Git flags, stagging the changes you wish to keep, and then commit them.
-
-## Update Files Manually
-
-Another way of dealing with updates is [downloading the theme]({{ site.gh_repo }}/archive/master.zip) --- replacing your layouts, includes, and assets with the newer ones manually. To be sure that you don't miss any changes it's probably a good idea to review the theme's [commit history]({{ site.gh_repo }}/commits/master) to see what's changed since.
-
-Here's a quick checklist of the important folders/files you'll want to be mindful of:
-
-| Name | |
-| ---- | --- |
-| `_layouts` | Replace all. Apply edits if you customized any layouts. |
-| `_includes` | Replace all. Apply edits if you customized any includes. |
-| `assets` | Replace all. Apply edits if you customized stylesheets or scripts. |
-| `_data/navigation.yml` | Safe to keep. Verify that there were no major structural changes or additions. |
-| `_data/ui-text.yml` | Safe to keep. Verify that there were no major structural changes or additions. |
-| `_config.yml` | Safe to keep. Verify that there were no major structural changes or additions. |
\ No newline at end of file
diff --git a/_docs/05-configuration.md b/_docs/05-configuration.md
deleted file mode 100644
index 128c951b..00000000
--- a/_docs/05-configuration.md
+++ /dev/null
@@ -1,515 +0,0 @@
----
-title: "Configuration"
-permalink: /docs/configuration/
-excerpt: "Settings for configuring and customizing the theme."
-sidebar:
- title: "v3.0"
- nav: docs
-modified: 2016-04-13T15:54:02-04:00
----
-
-{% include base_path %}
-
-Settings that affect your entire site can be changed in [Jekyll's configuration file](https://jekyllrb.com/docs/configuration/): `_config.yml`, found in the root of your project.
-
-**Note:** for technical reasons, `_config.yml` is NOT reloaded automatically when used with `jekyll serve`. If you make any changes to this file, please restart the server process for them to be applied.
-{: .notice--warning}
-
-Take a moment to look over the configuration file included with the theme. Comments have been added to provide examples and default values for most settings. Detailed explanations of each can be found below.
-
-## Site Settings
-
-### Site Locale
-
-`site.locale` is used to declare the primary language for each web page within the site.
-
-*Example:* `locale: "en-US"` sets the `lang` attribute for the site to the *United States* flavor of English, while `en-GB` would be for the `United Kingdom` style of English. Country codes are optional and the shorter `locale: "en"` is also acceptable. To find your language and country codes check this [reference table](https://msdn.microsoft.com/en-us/library/ee825488(v=cs.20).aspx).
-
-Properly setting the locale is important for associating localized text found in the [**UI Text**]({{ base_path }}/docs/ui-text/) data file. For more information on that see below.
-
-### Site Title
-
-The name of your site. Is used throughout the theme in places like the site masthead and `` tags.
-
-*Example:* `title: "My Awesome Site"`
-
-You also have the option of customizing the separation character used in SEO-friendly page titles.
-
-*Example:* `title_separator: "|"` would produce page titles like `Sample Page | My Awesome Site`.
-
-### Site Name
-
-Used to assign a site author. Don't worry, you can override the site author with different ones on specific posts, pages, or collection documents.
-
-*Example:* `name: "Michael Rose"`.
-
-**ProTip:** If you want to get crafty with your YAML you can use [anchors](http://www.yaml.org/spec/1.2/spec.html#id2785586) to reuse values. For example `foo: &var "My String"` allows you to reuse `"My String"` elsewhere in `_config.yml` like so... `bar: *var`. You'll see a few examples of this in the provided Jekyll config.
-{: .notice--info}
-
-### Site Description
-
-Fairly obvious. `site.description` describes the site. Used predominantly in meta descriptions as part of SEO efforts.
-
-*Example:* `description: "A flexible Jekyll theme for your blog or site with a minimalist aesthetic."`
-
-### Site URL
-
-The base hostname and protocol for your site. If you're hosting with GitHub Pages this will be something like `url: "http://github.io.mmistakes"` or `url: "https://mademistakes.com"` if you have a custom domain name.
-
-**Note:** It's important to remember that when testing locally you need to change the `site.url`. Ideally you'd use [multiple config files](https://mademistakes.com/articles/using-jekyll-2016/#environments-and-configurations) with `bundle exec jekyll serve --config _config.yml,_config.dev.yml` to apply development overrides. Simply commenting out the line works as well `# url: "http://mmistakes.github.io"`. Just remember to uncomment it before pushing or else you'll have broken assets and links all over the place!
-{: .notice--warning}
-
-**ProTip:** GitHub serves pages over `http://` and `https://` so to take advantage of that go protocol-less like so `url: "//github.io.mmistakes"`. Mre info on serving your GitHub Pages hosted site over https can be [found here](https://konklone.com/post/github-pages-now-sorta-supports-https-so-use-it).
-{: .notice--info}
-
-### Site Base URL
-
-This little option causes all kinds of confusion in the Jekyll community. If you're not hosting your site as a GitHub Pages Project or in a subfolder (eg: `/blog`), then don't mess with it.
-
-In the case of the Minimal Mistakes demo site it's hosted on GitHub at . To correctly set this base path I'd use `url: "https://mmistakes.github.io"` and `baseurl: "/minimal-mistakes"`.
-
-For more information on how to properly use `site.url` and `site.baseurl` as intended by the Jekyll maintainers, check [Parker Moore's post on the subject](https://byparker.com/blog/2014/clearing-up-confusion-around-baseurl/).
-
-**Note:** When using `baseurl` remember to include it as part of your path when testing your site locally. Values of `url: ` and `baseurl: "/blog"` would make your local site visible at `http://localhost:4000/blog` and not `http://localhost:4000`.
-{: .notice--warning}
-
-### Site Default Teaser Image
-
-To assign a fallback teaser image used in the "**Related Posts**" module, place a graphic in the `/images/` directory and add the filename to `_config.yml` like so:
-
-```yaml
-teaser: "500x300.png"
-```
-
-This image can be overridden at anytime by applying the following to a document's YAML Front Matter.
-
-```yaml
-header:
- teaser: my-awesome-post-teaser.jpg
-```
-
-
-
-### Breadcrumb Navigation (Beta)
-
-Enable breadcrumb links to help visitors better navigate deep sites. Because of the fragile method of implementing them they don't always produce accurate links reliably. For best results:
-
-1. Use a category based permalink structure e.g. `permalink: /:categories/:title/`
-2. Manually create pages for each category or use a plugin like [jekyll-archives][jekyll-archives] to auto-generate them. If these pages don't exist breadcrumb links to them will be broken.
-
-![breadcrumb navigation example]({{ base_path }}/images/mm-breadcrumbs-example.jpg)
-
-```yaml
-breadcrumbs: true # disabled by default
-```
-
-Breadcrumb start link text and separator character can both be changed in the [UI Text data file]({{ base_path }}/docs/ui-text/).
-
-### Reading Time
-
-Enable estimated reading time snippets with `read_time: true` in YAML Front Matter. `200` has been set as the default words per minute value --- which can be changed by adjusting `words_per_minutes: ` in `_config.yml`.
-
-![reading time example]({{ base_path }}/images/mm-read-time-example.jpg)
-
-Instead of adding `read_time: true` to each post, apply as a default in `_config.yml` like so:
-
-```yaml
-defaults:
- # _posts
- - scope:
- path: ""
- type: posts
- values:
- read_time: true
-```
-
-To disable reading time for a post, add `read_time: false` its YAML Front Matter to override what was set in `_config.yml`.
-
-### Comments
-
-Commenting for [**Disqus**](https://disqus.com/), [**Facebook**](https://developers.facebook.com/docs/plugins/comments), and **Google+** are built into the theme. First set the comment provider you'd like to use:
-
-| Name | Comment Provider |
-| ---- | ---------------- |
-| **disqus** | Disqus |
-| **facebook** | Facebook Comments |
-| **google-plus** | Google+ Comments |
-| **custom** | Other |
-
-Then add `comments: true` to each document you want comments visible on.
-
-Instead of adding YAML Front Matter to each document, apply as a default in `_config.yml`. To enable comments for all posts:
-
-```yaml
-defaults:
- # _posts
- - scope:
- path: ""
- type: posts
- values:
- comments: true
-```
-
-If you add `comments: false` to a post's YAML Front Matter it will override the default and disable comments for just that post.
-
-##### Disqus
-
-To use Disqus you'll need to create an account and [shortname](https://help.disqus.com/customer/portal/articles/466208-what-s-a-shortname-). Once you have both update `_config.yml` to:
-
-```yaml
-comments:
- provider: "disqus"
- disqus:
- shortname: "your-disqus-shortname"
-```
-
-##### Facebook Comments
-
-To enable Facebook Comments choose how many comments you'd like visible per post and the color scheme of the widget.
-
-```yaml
-comments:
- provider : "facebook"
- facebook:
- appid : # optional
- num_posts : # 5 (default)
- colorscheme : # "light" (default), "dark"
-```
-
-##### Other Comment Providers
-
-To use another provider not included with the theme set `provider: "custom"` then add their embed code to `_includes/comments-providers/custom.html`.
-
-### SEO, Social Sharing, and Analytics Settings
-
-All optional, but a good idea to take the time setting up to improve SEO and links shared from the site.
-
-#### Google Search Console
-
-Formerly known as [Google Webmaster Tools](https://www.google.com/webmasters/tools/), add your [verification code](https://support.google.com/analytics/answer/1142414?hl=en) like so: `google_site_verification: "yourVerificationCode"`.
-
-**Note:** You likely won't have to do this if you verify site ownership through **Google Analytics** instead.
-{: .notice--warning}
-
-#### Bing Webmaster Tools
-
-There are several ways to [verify site ownership](https://www.bing.com/webmaster/help/how-to-verify-ownership-of-your-site-afcfefc6) --- the easiest adding an authentication code to your config file.
-
-Copy and paste the string inside of `content`:
-
-```html
-
-```
-
-Into `_config.yml`
-
-```yaml
-bing_site_verification: "0FC3FD70512616B052E755A56F8952D"
-```
-
-#### Alexa
-
-To [claim your site](http://www.alexa.com/siteowners/claim) with Alexa add the provided verification ID `alexa_site_verification: "yourVerificationID"`.
-
-#### Yandex
-
-To verify site ownership copy and paste the string inside of `name`:
-
-```html
-
-```
-
-Into `_config.yml`
-
-```yaml
-yandex_site_verification: "2132801JL"
-```
-
-#### Twitter Cards and Facebook Open Graph
-
-To improve the appearance of links shared from your site to social networks like Twitter and Facebook be sure to configure the following.
-
-##### Site Twitter Username
-
-Twitter username for the site. For pages that have custom author Twitter accounts assigned in their YAML Front Matter or data file, they will be attributed as a **creator** in the Twitter Card.
-
-For example if my site's Twitter account is `@mmistakes-theme` I would add the following to `_config.yml`
-
-```yaml
-twitter:
- username: "mmistakes-theme"
-```
-
-And if I assign `@mmistakes` as an author account it will appear in the Twitter Card along with `@mmistakes-theme`, attributed as a creator of the page being shared.
-
-**Note**: You need to [apply for Twitter Cards](https://dev.twitter.com/docs/cards) and validate they're working on your site before they will begin showing up.
-{: .notice--warning}
-
-##### Facebook Open Graph
-
-If you have a Facebook ID or publisher page add them:
-
-```yaml
-facebook:
- app_id: # A Facebook app ID
- publisher: # A Facebook page URL or ID of the publishing entity
-```
-
-While not part a part of Open Graph, you can also add your Facebook username for use in the sidebar and footer.
-
-```yaml
-facebook:
- username: "michaelrose" # https://www.facebook.com/michaelrose
-```
-
-**ProTip:** To debug Open Graph data use [this tool](https://developers.facebook.com/tools/debug/og/object?q=https%3A%2F%2Fmademistakes.com) to test your pages. If content changes aren't reflected you will probably have to hit the **Fetch new scrape information** button to refresh.
-{: .notice--info}
-
-##### Open Graph Default Image
-
-For pages that don't have a `header.image` assigned in their YAML Front Matter, `site.og_image` will be used as a fallback. Use you logo, icon, avatar or something else that is meaningful. Just make sure it is place in the `/images/` folder, a minimum size of 120px by 120px, and less than 1MB in file size.
-
-```yaml
-og_image: "site-logo.png"
-```
-
-
-
-Documents who have a `header.image` assigned in their YAML Front Matter will appear like this when shared on Twitter and Facebook.
-
-
-
-
-
-##### Include your social profile in search results
-
-Use markup on your official website to add your [social profile information](https://developers.google.com/structured-data/customize/social-profiles#adding_structured_markup_to_your_site) to the Google Knowledge panel in some searches. Knowledge panels can prominently display your social profile information.
-
-```yaml
-social:
- type: # Person or Organization (defaults to Person)
- name: # If the user or organization name differs from the site's name
- links:
- - "https://twitter.com/yourTwitter"
- - "https://facebook.com/yourFacebook"
- - "https://instagram.com/yourProfile"
- - "https://www.linkedin.com/in/yourprofile"
- - "https://plus.google.com/your_profile"
-```
-
-#### Analytics
-
-Analytics is disabled by default. To enable globally select one of the following:
-
-| Name | Analytics Provider |
-| ---- | ------------------ |
-| **google** | [Google Standard Analytics](https://www.google.com/analytics/) |
-| **google-universal** | [Google Universal Analytics](https://www.google.com/analytics/) |
-| **custom** | Other analytics providers |
-
-For Google Analytics add your Tracking Code:
-
-```yaml
-analytics:
- provider: "google-universal"
- tracking_id: "UA-1234567-8"
-```
-
-To use another provider not included with the theme set `provider: "custom"` then add their embed code to `_includes/analytics-providers/custom.html`.
-
-## Site Author
-
-Used as the defaults for defining what appears in the author sidebar.
-
-![author sidebar example]({{ base_path }}/images/mm-author-sidebar-example.jpg)
-
-**Note:** For sites with multiple authors these values can be overridden post by post with custom YAML Front Matter and a data file. For more information on how that works see below.
-{: .notice--info}
-
-```yaml
-author:
- name : "Your Name"
- avatar : "bio-photo.jpg" # placed in /images/
- bio : "My awesome biography constrained to a sentence or two goes here."
- email : # optional
- uri : "http://your-site.com"
-```
-
-Social media links are all optional, include the ones you want visible. In most cases you just need to add the username. If you're unsure double check `_includes/author-profile.html` to see how the URL is constructed.
-
-## Reading Files
-
-Nothing out of the ordinary here. `include` and `exclude` may be the only things you need to alter.
-
-## Conversion and Markdown Processing
-
-Again nothing out of the ordinary here as the theme adheres to the defaults used by GitHub Pages. [**Kramdown**](http://kramdown.gettalong.org/) for Markdown conversion, [**Rouge**](http://rouge.jneen.net/) syntax highlighting, and incremental building disabled. Change them if you need to.
-
-## Front Matter Defaults
-
-To save yourself time setting [Front Matter Defaults](https://jekyllrb.com/docs/configuration/#front-matter-defaults) for posts, pages, and collections is the way to go. Sure you can assign layouts and toggle settings like **reading time**, **comments**, and **social sharing** in each file, but that's not ideal.
-
-Using the `default` key in `_config.yml` you could set the layout and enable author profiles, reading time, comments, social sharing, and related posts for all posts --- in one shot.
-
-```yaml
-defaults:
- # _posts
- - scope:
- path: ""
- type: posts
- values:
- layout: single
- author_profile: true
- read_time: true
- comments: true
- share: true
- related: true
-```
-
-Pages Front Matter defaults can be scoped like this:
-
-```yaml
-defaults:
- # _pages
- - scope:
- path: ""
- type: pages
- values:
- layout: single
-```
-
-And collections like this:
-
-```yaml
-defaults:
- # _foo
- - scope:
- path: ""
- type: foo
- values:
- layout: single
-```
-
-And of course any default value can be overridden by settings in a post, page, or collection file. All you need to do is specify the settings in the YAML Front Matter. For more examples be sure to check out the demo site's [`_config.yml`]({{ site.gh_repo }}/blob/gh-pages/_config.yml).
-
-## Outputting
-
-The default permalink style used by the theme is `permalink: /:categories/:title/`. If you have a post named `2016-01-01-my-post.md` with `categories: foo` in the YAML Front Matter, Jekyll will generate `_site/foo/my-post/index.html`.
-
-**Note:** If you plan on enabling breadcrumb links --- including category names in permalinks is a big part of how those are created.
-{: .notice--warning}
-
-### Paginate
-
-If [using pagination](https://github.com/jekyll/jekyll-paginate) on the homepage you can change the amount of posts shown with:
-
-```yaml
-paginate: 5
-```
-
-You'll also need to include some Liquid and HTML to properly use the paginator, which you can find in the **Layouts** section under [Home Page]({{ base_path }}/docs/layouts/#home-page).
-
-### Timezone
-
-This sets the timezone environment variable, which Ruby uses to handle time and date creation and manipulation. Any entry from the [IANA Time Zone Database](http://en.wikipedia.org/wiki/List_of_tz_database_time_zones) is valid. The default is the local time zone, as set by your operating system.
-
-```yaml
-timezone: America/New_York
-```
-
-## Plugins
-
-When hosting with GitHub Pages a small [set of gems](https://pages.github.com/versions/) have been whitelisted for use. The theme uses a few of them which can be found under `gems`. Additional settings and configurations are documented in the links below.
-
-| Plugin | Description |
-| ------ | ----------- |
-| [jekyll-paginate][jekyll-paginate] | Pagination Generator for Jekyll. |
-| [jekyll-sitemap][jekyll-sitemap] |Jekyll plugin to silently generate a sitemaps.org compliant sitemap for your Jekyll site. |
-| [jekyll-gist][jekyll-gist] | Liquid tag for displaying GitHub Gists in Jekyll sites. |
-| [jekyll-feed][jekyll-feed] | A Jekyll plugin to generate an Atom (RSS-like) feed of your Jekyll posts. |
-| [jemoji][jemoji] | GitHub-flavored emoji plugin for Jekyll. |
-
-[jekyll-paginate]: https://github.com/jekyll/jekyll-paginate
-[jekyll-sitemap]: https://github.com/jekyll/jekyll-sitemap
-[jekyll-gist]: https://github.com/jekyll/jekyll-gist
-[jekyll-feed]: https://github.com/jekyll/jekyll-feed
-[jemoji]: https://github.com/jekyll/jemoji
-
-If you're hosting elsewhere then you don't really have to worry about what is whitelisted as you are free to include whatever [Jekyll plugins](https://jekyllrb.com/docs/plugins/) you desire.
-
-## Archive Settings
-
-The theme ships with support for taxonomy (category and tag) pages. GitHub Pages hosted sites need to use a *Liquid only* approach while those hosted elsewhere can use plugins like [**jekyll-archives**][jekyll-archives] to generate these pages automatically.
-
-[jekyll-archives]: https://github.com/jekyll/jekyll-archives
-
-The default `type` is set to use Liquid.
-
-```yaml
-categories:
- type: liquid
- path: /categories/
-tags:
- type: liquid
- path: /tags/
-```
-
-Which would create category and tag links in the breadcrumbs and page meta like: `/categories/#foo` and `/tags/#foo`.
-
-**Note:** for these links to resolve properly, category and tag index pages need to exist at [`/categories/index.html`]({{ site.gh_repo }}/blob/gh-pages/_pages/category-archive.html) and [`/tags/index.html`]({{ site.gh_repo }}/blob/gh-pages/_pages/tag-archive.html). The necessary Liquid code to build these pages can be taken from the demo site.
-{: .notice--warning}
-
-If you have the luxury of using Jekyll Plugins then [**jekyll-archives**][jekyll-archives] will make your life much easier as category and tag pages are created for you.
-
-Change `type` to `jekyll-archives` and apply the following [configurations](https://github.com/jekyll/jekyll-archives/blob/master/docs/configuration.md):
-
-```yaml
-categories:
- type: jekyll-archives
- path: /categories/
-tags:
- type: jekyll-archives
- path: /tags/
-jekyll-archives:
- enabled:
- - categories
- - tags
- layouts:
- category: archive-taxonomy
- tag: archive-taxonomy
- permalinks:
- category: /categories/:name/
- tag: /tags/:name/
-```
-
-**Note:** The `archive-taxonomy` layout used by jekyll-archives is provided with the theme and can be found in the `_layouts` folder.
-{: .notice--info}
-
-## HTML Compression
-
-If you care at all about performance (and really who doesn't) compressing the HTML files generated by Jekyll is a good thing to do.
-
-If you're hosting with GitHub Pages there aren't many options afforded to you for optimizing the HTML Jekyll generates. Thankfully there is some Liquid wizardry you can use to strip whitespace and comments to reduce file size.
-
-There's a variety of configurations and cavets to using the `compress` layout, so be sure to read through the [documentation](http://jch.penibelst.de/) if you decide to make change the defaults set in the theme's `_config.yml`.
-
-```yaml
-compress_html:
- clippings: all
- ignore:
- envs: development # disable compression in dev environment
-```
-
-**Caution:** Inline JavaScript comments can cause problems with `compress.html`, so be sure to `/* comment this way */` and avoid `// these sorts of comments`.
\ No newline at end of file
diff --git a/_docs/06-navigation.md b/_docs/06-navigation.md
deleted file mode 100644
index ba09c2fb..00000000
--- a/_docs/06-navigation.md
+++ /dev/null
@@ -1,75 +0,0 @@
----
-title: "Navigation"
-permalink: /docs/navigation/
-excerpt: "Instructions on how to customize the main navigation and enabling breadcrumb links."
-sidebar:
- title: "v3.0"
- nav: docs
-modified: 2016-04-13T15:54:02-04:00
----
-
-{% include base_path %}
-
-## Masthead
-
-The masthead links use a "priority plus" design pattern. Meaning, show as many navigation items that will fit horizontally with a toggle to reveal the rest.
-
-To define these links add titles and URLs under the `main` key in `_data/navigation.yml`:
-
-```yaml
-main:
- - title: "Quick-Start Guide"
- url: /docs/quick-start-guide/
-
- - title: "Posts"
- url: /year-archive/
-
- - title: "Categories"
- url: /categories/
-
- - title: "Tags"
- url: /tags/
-
- - title: "Pages"
- url: /page-archive/
-
- - title: "Collections"
- url: /collection-archive/
-
- - title: "External Link"
- url: https://google.com
-```
-
-Which will give you a responsive masthead similar to this:
-
-![priority plus masthead animation]({{ base_path }}/images/mm-priority-plus-masthead.gif)
-
-**ProTip:** Put the most important links first so they're always visible and not hidden behind the **menu toggle**.
-{: .notice--info}
-
-## Breadcrumbs (Beta)
-
-Enable breadcrumb links to help visitors better navigate deep sites. Because of the fragile method of implementing them they don't always produce accurate links reliably. For best results:
-
-1. Use a category based permalink structure e.g. `permalink: /:categories/:title/`
-2. Manually create pages for each category or use a plugin like [jekyll-archives](https://github.com/jekyll/jekyll-archives) to auto-generate them. If these pages don't exist breadcrumb links to them will be broken.
-
-![breadcrumb navigation example]({{ base_path }}/images/mm-breadcrumbs-example.jpg)
-
-```yaml
-breadcrumbs: true # disabled by default
-```
-
-Breadcrumb start link text and separator character can both be changed in `_data/ui-text.yml`.
-
-```yaml
-breadcrumb_home_label : "Home"
-breadcrumb_separator : "/"
-```
-
-For breadcrumbs that resemble something like `Start > Blog > My Awesome Post` you'd apply these settings:
-
-```yaml
-breadcrumb_home_label : "Start"
-breadcrumb_separator : ">"
-```
\ No newline at end of file
diff --git a/_docs/07-ui-text.md b/_docs/07-ui-text.md
deleted file mode 100644
index 3f99dfb0..00000000
--- a/_docs/07-ui-text.md
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: "UI Text"
-permalink: /docs/ui-text/
-excerpt: "Text for customizing various user interface elements found in the theme."
-sidebar:
- title: "v3.0"
- nav: docs
-modified: 2016-04-13T15:54:02-04:00
----
-
-{% include base_path %}
-
-Text for various UI elements, `_layouts`, and `_includes` have all been grouped together as a set of translation keys. This is by no means a full-on i18n solution, but it does help make customizing things a bit easier.
-
-Currently all of the keys in `_data/ui-text.yml` are English only. If you're are interested in localizing them into other languages feel free to submit a pull request and I will be happy to look it over
-
-Many of the label based keys like `meta_label`, `categories_label`, `tags_label`, `share_on_label`, and `follow_label` can be left blank if you'd like to omit them from view. It really depends on you and if you want an even more minimal look to your site.
-
-![UI text labels]({{ base_path }}/images/mm-ui-text-labels.jpg)
\ No newline at end of file
diff --git a/_docs/08-authors.md b/_docs/08-authors.md
deleted file mode 100644
index 57b1ddfa..00000000
--- a/_docs/08-authors.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: "Authors"
-permalink: /docs/authors/
-excerpt: "Instructions and settings for working with multiple site authors."
-sidebar:
- title: "v3.0"
- nav: docs
-modified: 2016-04-13T15:54:02-04:00
----
-
-{% include base_path %}
-
-Sites that may have content authored from various individuals can be accommodated by using [data files](https://jekyllrb.com/docs/datafiles/).
-
-To assign an author to a post or page that is different from the site author specified in `_config.yml`:
-
-**Step 1.** Create `_data/authors.yml` and add authors using the following format. Any variables found under `author:` in `_config.yml` can be used (e.g. `name`, `avatar`, `uri`, social media profiles, etc.).
-
-```yaml
-# /_data/authors.yml
-
-Billy Rick:
- name: "Billy Rick"
- uri: "http://thewhip.com"
- email: "billy@rick.com"
- bio: "What do you want, jewels? I am a very extravagant man."
- avatar: "bio-photo-2.jpg"
- twitter: "extravagantman"
-
-Cornelius Fiddlebone:
- name: "Cornelius Fiddlebone"
- email: "cornelius@thewhip.com"
- bio: "I ordered what?"
- avatar: "bio-photo.jpg"
- twitter: "rhymeswithsackit"
-```
-
-**Step 2.** Assign one of the authors in `authors.yml` to a post or page you wish to override the `site.author` with.
-
-Example: To assign `Billy Rick` as an author for a post the following YAML Front Matter would be applied:
-
-```yaml
-author: Billy Rick
-```
diff --git a/_docs/09-layouts.md b/_docs/09-layouts.md
deleted file mode 100644
index a1d9880e..00000000
--- a/_docs/09-layouts.md
+++ /dev/null
@@ -1,311 +0,0 @@
----
-title: "Layouts"
-permalink: /docs/layouts/
-excerpt: "Descriptions and samples of all layouts included with the theme and how to best use them."
-sidebar:
- title: "v3.0"
- nav: docs
-single_layout_gallery:
- - image_path: mm-layout-single-header.png
- alt: "single layout with header example"
- - image_path: mm-layout-single-meta.png
- alt: "single layout with comments and related posts"
-modified: 2016-04-13T15:54:02-04:00
----
-
-{% include base_path %}
-{% include toc icon="columns" title="Included Layouts" %}
-
-The bread and butter of any theme. Below you'll find the layouts included with Minimal Mistakes, what they look like and the type of content they've been built for.
-
-## Default Layout
-
-The base layout all other layouts inherit from. There's not much to this layout apart from pulling in several `_includes`:
-
-* `` elements
-* masthead navigation links
-* {% raw %}`{{ content }}`{% endraw %}
-* page footer
-* scripts
-
-**Note:** You won't ever assign this layout directly to a post or page. Instead all other layouts will build off of it by setting `layout: default` in their YAML Front Matter.
-{: .notice--warning}
-
-## Compress Layout
-
-A Jekyll layout that compresses HTML in pure Liquid.
-
-* [Documentation](http://jch.penibelst.de/)
-
-## Single Layout
-
-The layout you'll likely use the most --- sidebar and main content combo.
-
-**Includes:**
-
-* Optional header image with caption
-* Optional header overlay (solid color/image) + text and optional "call to action" button
-* Optional social sharing links module
-* Optional comments module
-* Optional related posts module
-
-{% include gallery id="single_layout_gallery" caption="Image header and meta info examples for `single` layout" %}
-
-Assign with `layout: single`, or better yet apply as a [Front Matter default]({{ base_path }}/docs/configuration/#front-matter-defaults) in `_config.yml`.
-
-## Archive Layout
-
-Essentially the same as `single` with markup adjustments and some modules removed.
-
-**Includes:**
-
-* Optional header image with caption
-* Optional header overlay (solid color/image) + text and optional "call to action" button
-* List and grid views
-
-
-
-Below are sample archive pages you can easily drop into your project, taking care to rename `permalink`, `title`, or the filename to fit your site. Each is 100% compatible with GitHub Pages.
-
-* [All Posts Grouped by Category -- List View][posts-categories]
-* [All Posts Grouped by Tags -- List View][posts-tags]
-* [All Posts Grouped by Year -- List View][posts-year]
-* [All Posts Grouped by Collection -- List View][posts-collection]
-* [Portfolio Collection -- Grid View][portfolio-collection]
-
-[posts-categories]: {{ site.gh_repo }}/gh-pages/_pages/category-archive.html
-[posts-tags]: {{ site.gh_repo }}/gh-pages/_pages/tag-archive.html
-[posts-year]: {{ site.gh_repo }}/gh-pages/_pages/year-archive.html
-[posts-collection]: {{ site.gh_repo }}/gh-pages/_pages/collection-archive.html
-[portfolio-collection]: {{ site.gh_repo }}/gh-pages/_pages/portfolio-archive.html
-
-Post and page excerpts are auto-generated by Jekyll which grabs the first paragraph of text. To override this text with something more specific use the following YAML Front Matter:
-
-```yaml
-excerpt: "A unique line of text to describe this post that will display in an archive listing and meta description with SEO benefits."
-```
-
-### Grid View
-
-Adding `type=grid` to the `archive-single` helper will display archive posts in a 4 column grid. For example to create an archive displaying all documents in the portfolio collection:
-
-**Step 1:** Create a portfolio archive page (eg. `_pages/portfolio-archive.html`) with the following YAML Front Matter:
-
-```yaml
----
-layout: archive
-title: "Portfolio"
-permalink: /portfolio/
-author_profile: false
----
-```
-
-**Step 2:** Loop over all documents in the portfolio collection and output in a grid:
-
-```html
-{% raw %}{% include base_path %}
-
-
- {% for post in site.portfolio %}
- {% include archive-single.html type="grid" %}
- {% endfor %}{% endraw %}
-
-```
-
-To produce something like this:
-
-
-
-**Note:** More information on using this `_include` can be found under [**Helpers**]({{ base_path }}/docs/helpers/).
-{: .notice--info}
-
-### Taxonomy Archive
-
-If you have the luxury of using Jekyll plugins the creation of category and tag archives is greatly simplified. Enable support for the [`jekyll-archives`](https://github.com/jekyll/jekyll-archives) plugin with a few `_config.yml` settings as noted in the [**Configuration**]({{ base_path }}/docs/configuration/#archive-settings) section.
-
-![archive taxonomy layout example]({{ base_path }}/images/mm-layout-archive-taxonomy.png)
-
-### Home Page
-
-Minimal Mistakes ships with an [`index.html`]({{ site.gh_repo }}/blob/master/index.html) in the root of the project for displaying recent posts.
-
-**Includes:**
-
-* Optional header image with caption
-* Optional header overlay (solid color/image) + text and optional "call to action" button
-* Paginated posts
-
-Post pagination is achieved by assigning `layout: archive` in the YAML Front Matter and including the following Liquid in the body:
-
-```html
-{% raw %}
-{% include base_path %}
-
-
Recent Posts
-
-{% for post in paginator.posts %}
- {% include archive-single.html %}
-{% endfor %}
-
-{% include paginator.html %}
-{% endraw %}
-```
-
-
-
-**Note:** For more pagination related settings check the [**Configuration**]({{ base_path }}/docs/configuration/#paginate) section.
-{: .notice--info}
-
-## Splash Page Layout
-
-For full-width landing pages that need a little something extra add `layout: splash` to the YAML Front Matter.
-
-**Includes:**
-
-* Optional header image with caption
-* Optional header overlay (solid color/image) + text and optional "call to action" button
-* Feature blocks (`left`, `center`, and `right` alignment options)
-
-![splash page layout example]({{ base_path }}/images/mm-layout-splash.png)
-
-Feature blocks can be assigned and aligned to the `left`, `right`, or `center` with a sprinkling of YAML. For full details on how to use the `feature_row` helper check the [**Content**]({{ base_path }}/docs/helpers-and-shortcodes/) section or review a [sample splash page]({{ site.gh_repo }}/gh-pages/_pages/splash-page.md).
-
-
----
-
-## Headers
-
-To add some visual punch to a post or page, a large full-width header image can be included.
-
-**Note:** Be sure to resize your header images. `~1280px` is a good width if you aren't [responsively serving up images](http://alistapart.com/article/responsive-images-in-practice). Through the magic of CSS they will scale up or down to fill the container. If you go with something too small it will look like garbage when upscaled, and something too large will hurt performance.
-{: .notice--warning}
-
-![single layout header image example]({{ base_path }}/images/mm-single-header-example.jpg)
-
-Place your images in the `/images/` folder and add the following YAML Front Matter:
-
-```yaml
-header:
- image: image-filename.jpg
-```
-
-For externally hosted images include the full image path instead of just the filename:
-
-```yaml
-header:
- image: http://some-site.com/image.jpg
-```
-
-To include a caption or attribution for the image:
-
-```yaml
-header:
- image: unsplash-image-1.jpg
- caption: "Photo credit: [**Unsplash**](https://unsplash.com)"
-```
-
-**ProTip:** Captions written in Markdown are supported, so feel free to add links, or style text. Just be sure to wrap it in quotes.
-{: .notice--info}
-
-### Header Overlay
-
-To overlay text on top of a header image you have a few more options:
-
-| Name | Description | Default |
-| ---- | ----------- | ------- |
-| **overlay_image** | Header image you'd like to overlay. Same rules as `header.image` from above. | |
-| **excerpt** | Auto-generated page excerpt is added to the overlay text or can be overridden. | |
-| **cta_label** | Call to action button text label. | `more_label` in UI Text data file |
-| **cta_url** | Call to action button URL. | |
-
-With this YAML Front Matter:
-
-```yaml
-excerpt: "This post should display a **header with an overlay image**, if the theme supports it."
-header:
- overlay_image: unsplash-image-1.jpg
- caption: "Photo credit: [**Unsplash**](https://unsplash.com)"
- cta_label: "More Info"
- cta_url: "https://unsplash.com"
-```
-
-You'd get a header image overlaid with text and a call to action button like this:
-
-![single layout header overlay example]({{ base_path }}/images/mm-single-header-overlay-example.jpg)
-
-You also have the option of specifying a solid background-color to use instead of an image.
-
-![single layout header overlay with background fill]({{ base_path }}/images/mm-single-header-overlay-fill-example.jpg)
-
-```yaml
-excerpt: "This post should display a **header with a solid background color**, if the theme supports it."
-header:
- overlay_color: "#333"
-```
-
----
-
-## Sidebars
-
-The space to the left of a page's main content is blank by default, but has the ability to show an author profile (name, short biography, social media links), custom content, or both.
-
-### Author Profile
-
-Add `author_profile: true` to a post or page's YAML Front Matter.
-
-![single layout example]({{ base_path }}/images/mm-layout-single.png)
-
-Better yet, enable it with Front Matter Defaults set in `_config.yml`.
-
-```yaml
-defaults:
- # _posts
- - scope:
- path: ""
- type: posts
- values:
- author_profile: true
-```
-
-**Note:** To disable the author sidebar profile for a specific post or page, add `author_profile: false` to the YAML Front Matter instead.
-{: .notice--warning}
-
-### Custom Sidebar Content
-
-Blocks of content can be added by using the following under `sidebar`:
-
-| Name | Description |
-| ---- | ----------- |
-| **title** | Title or heading. |
-| **image** | Image path placed in `/images/` folder or an external URL. |
-| **image_alt** | Alternate description for image. |
-| **text** | Text. Markdown is allowed. |
-
-Multiple blocks can also be added by following the example below:
-
-```yaml
-sidebar:
- - title: "Title"
- image: http://placehold.it/350x250
- image_alt: "image"
- text: "Some text here."
- - title: "Another Title"
- text: "More text here."
-```
-
-
-
-**ProTip:** Custom sidebar content added to a post or page's YAML Front Matter will appear above the author profile if enabled with `author_profile: true`.
-{: .notice--info}
\ No newline at end of file
diff --git a/_docs/10-posts.md b/_docs/10-posts.md
deleted file mode 100644
index e2cae5c1..00000000
--- a/_docs/10-posts.md
+++ /dev/null
@@ -1,35 +0,0 @@
----
-title: "Working with Posts"
-permalink: /docs/posts/
-excerpt: "Suggestions and Front Matter defaults for working with posts."
-sidebar:
- title: "v3.0"
- nav: docs
-modified: 2016-04-13T15:54:02-04:00
----
-
-{% include base_path %}
-
-Posts are stored in the `_posts` directory and named according to the `YEAR-MONTH-DAY-title.MARKUP` format as per [the usual](https://jekyllrb.com/docs/posts/).
-
-**Recommended Front Matter Defaults:**
-
-```yaml
-defaults:
- # _posts
- - scope:
- path: ""
- type: posts
- values:
- layout: single
- author_profile: true
- read_time: true
- comments: true
- share: true
- related: true
-```
-
-Adding the above to `_config.yml` will assign the `single` layout and enable: *author profile*, *reading time*, *comments*, *social sharing links*, and *related posts*, for all posts.
-
-**ProTip:** Remember to write unique `excerpt` descriptions for each post for improved SEO and archive listings.
-{: .notice--info}
\ No newline at end of file
diff --git a/_docs/11-pages.md b/_docs/11-pages.md
deleted file mode 100644
index fd0a260e..00000000
--- a/_docs/11-pages.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title: "Working with Pages"
-permalink: /docs/pages/
-excerpt: "Suggestions and Front Matter defaults for working with pages."
-sidebar:
- title: "v3.0"
- nav: docs
-modified: 2016-04-13T15:54:02-04:00
----
-
-{% include base_path %}
-
-To better organize all of your pages you can centralize them into a single location similar to posts and collections.
-
-**Step 1:** Start by placing pages (`.md` or `.html` files) into a `_pages` directory. Meaningfully naming files should be the goal. Avoid patterns like `/about/index.md` as it makes distinguishing between multiple `index.md` files harder.
-
-```bash
-sample-project
-└── _pages/
- ├── 404.md # custom 404 page
- ├── about.md # about page
- └── contact.md # contact page
-```
-
-**Step 2:** Include pages to be sure Jekyll "sees" and processes the files inside of `_pages`. Add `include: ["_pages"]` to `_config.yml`.
-
-**Step 3:** Assign permalink overrides in the YAML Front Matter of each.
-
-Examples:
-
-| filename | permalink |
-| -------- | --------- |
-| _pages/about.md | `permalink: /about/` |
-| _pages/home.md | `permalink: /` |
-| _pages/contact.md | `permalink: /contact/` |
-
-**Recommended Front Matter Defaults:**
-
-```yaml
-defaults:
- # _pages
- - scope:
- path: ""
- type: pages
- values:
- layout: single
- author_profile: true
-```
\ No newline at end of file
diff --git a/_docs/12-collections.md b/_docs/12-collections.md
deleted file mode 100644
index 82941fba..00000000
--- a/_docs/12-collections.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: "Working with Collections"
-permalink: /docs/collections/
-excerpt: "Suggestions and Front Matter defaults for working with collections."
-sidebar:
- title: "v3.0"
- nav: docs
-modified: 2016-04-13T15:54:02-04:00
----
-
-{% include base_path %}
-
-Collections like posts and pages work as you'd expect. If you're new to them be sure to read [Jekyll's documentation](https://jekyllrb.com/docs/collections/).
-
-The theme has been built with collections in mind and you will find [several examples]({{ base_path }}/collection-archive/) on the demo site ([portfolio]({{ base_path }}/portfolio/), [recipes]({{ base_path }}/recipes/), pets).
-
-**Collections in the Wild:** This set of documentation is also [built as a collection]({{ site.gh_repo }}/gh-pages/_docs/) if you're looking for a fully fleshed out example to inspect.
-{: .notice--info}
-
----
-
-A popular use case for collections is to build a portfolio section as part of one's personal site. Let's quickly walk through the steps to do that.
-
-**Step 1:** Configure the portfolio collection by adding the following to `_config.yml`.
-
-```yaml
-collections:
- portfolio:
- output: true
- permalink: /:collection/:path/
-```
-
-These settings essentially say output `index.html` files for each portfolio document in `_portfolio` at `_site/portfolio//`.
-
-Just like posts and pages you'll probably want to set some defaults for the Front Matter:
-
-```yaml
-defaults:
- # _portfolio
- - scope:
- path: ""
- type: portfolio
- values:
- layout: single
- author_profile: false
- share: true
-```
-
-And then create portfolio content like [`_portfolio/foo-bar-website.md`]({{ site.gh_repo }}/gh-pages/_portfolio/foo-bar-website.md), to end up with something like this.
-
-![portfolio collection example]({{ base_path }}/images/mm-portfolio-collection-example.jpg)
\ No newline at end of file
diff --git a/_docs/13-helpers.md b/_docs/13-helpers.md
deleted file mode 100644
index 4be92939..00000000
--- a/_docs/13-helpers.md
+++ /dev/null
@@ -1,179 +0,0 @@
----
-title: "Helpers"
-permalink: /docs/helpers/
-excerpt: "Jekyll `_includes` and other helpers to use as shortcuts for creating archives, galleries, table of contents, and more."
-sidebar:
- title: "v3.0"
- nav: docs
-gallery:
- - url: unsplash-gallery-image-1.jpg
- image_path: unsplash-gallery-image-1-th.jpg
- alt: "placeholder image 1"
- - url: unsplash-gallery-image-2.jpg
- image_path: unsplash-gallery-image-2-th.jpg
- alt: "placeholder image 2"
- - url: unsplash-gallery-image-3.jpg
- image_path: unsplash-gallery-image-3-th.jpg
- alt: "placeholder image 3"
-feature_row:
- - image_path: unsplash-gallery-image-1-th.jpg
- alt: "placeholder image 1"
- title: "Placeholder 1"
- excerpt: "This is some sample content that goes here with **Markdown** formatting."
- - image_path: unsplash-gallery-image-2-th.jpg
- alt: "placeholder image 2"
- title: "Placeholder 2"
- excerpt: "This is some sample content that goes here with **Markdown** formatting."
- url: "#test-link"
- btn_label: "Read More"
- btn_class: "btn--inverse"
- - image_path: unsplash-gallery-image-3-th.jpg
- title: "Placeholder 3"
- excerpt: "This is some sample content that goes here with **Markdown** formatting."
-modified: 2016-04-13T15:54:02-04:00
----
-
-{% include base_path %}
-{% include toc icon="gears" title="Helpers" %}
-
-You can think of these Jekyll helpers as little shortcuts. Since GitHub Pages doesn't allow most plugins --- [custom tags](https://jekyllrb.com/docs/plugins/#tags) are out. Instead the theme leverages [**includes**](https://jekyllrb.com/docs/templates/#includes) to do something similar.
-
-## Base Path
-
-Instead of repeating `{% raw %}{{ site.url }}{{ site.baseurl }}{% endraw %}` over and over again to create absolute URLs, you can use `{% raw %}{{ base_path }}{% endraw %}` instead. Simply add `{% raw %}{% include base_path %}{% endraw %}` to layouts, posts, pages, collections, or other includes and you're good to go.
-
-**ProTip:** It's a good practice to prepend all assets links (especially post images) with `{% raw %}{{ base_path }}{% endraw %}` so they correctly resolve in the site's XML feeds.
-{: .notice--info}
-
-## Group by Array
-
-[Jekyll Group-By-Array](https://github.com/mushishi78/jekyll-group-by-array) by [Max White](mushishi78@gmail.com).
-
- A liquid include file for Jekyll that allows an object to be grouped by an array.
-
-The Liquid based taxonomy archives found amongst the demo pages rely on this helper.
-
-| Description | | |
-| ----------- | ------------------------ | --------------------------- |
-| All posts grouped by category | [Source][category-array] | [Demo][category-array-demo] |
-| All posts grouped by tags | [Source][tag-array] | [Demo][tag-array-demo] |
-
-[category-array]: {{ site.gh_repo }}/gh-pages/_pages/category-archive.html
-[category-array-demo]: {{ base_path }}/categories/
-[tag-array]: {{ site.gh_repo }}/gh-pages/_pages/tag-archive.html
-[tag-array-demo]: {{ base_path }}/tags/
-
-## Gallery
-
-Generate a `
` element with optional caption of arrays with two or more images.
-
-To place a gallery add the necessary YAML Front Matter.
-
-| Name | Required | Description |
-| ---- | -------- | ----------- |
-| **url** | Optional | URL to link gallery image to (eg. a larger detail image). |
-| **image_path** | **Required** | For images placed in the `/images/` directory just add the filename and extension. Use absolute URLS for those hosted externally. |
-| **alt** | Optional | Alternate text for image. |
-
-```yaml
-gallery:
- - url: unsplash-gallery-image-1.jpg
- image_path: unsplash-gallery-image-1-th.jpg
- alt: "placeholder image 1"
- - url: unsplash-gallery-image-2.jpg
- image_path: unsplash-gallery-image-2-th.jpg
- alt: "placeholder image 2"
- - url: unsplash-gallery-image-3.jpg
- image_path: unsplash-gallery-image-3-th.jpg
- alt: "placeholder image 3"
-```
-
-And then drop-in the gallery include in the body where you'd like it to appear.
-
-| Include Parameter | Required | Description | Default |
-| ----------------- | -------- | ----------- | ------- |
-| **id** | Optional | To add multiple galleries to a document uniquely name them in the YAML Front Matter and reference in `{% raw %}{% include gallery id="gallery_id" %}{% endraw %}` | `gallery` |
-| **class** | Optional | Use to add a `class` attribute to the surrounding `
` element for additional styling needs. | |
-| **caption** | Optional | Gallery caption description. Markdown is allowed. | |
-
-```liquid
-{% raw %}{% include gallery caption="This is a sample gallery with **Markdown support**." %}{% endraw %}
-```
-
-**Gallery example with caption:**
-
-{% include gallery caption="This is a sample gallery with **Markdown support**." %}
-
-**More Gallery Goodness:** A [few more examples]({{ base_path }}{% post_url 2010-09-09-post-gallery %}) and [source code]({{ site.gh_repo }}/gh-pages/_posts/2010-09-09-post-gallery.md) can be seen in the demo site.
-{: .notice--info}
-
-## Feature Row
-
-Designed to compliment the [`splash`]({{ base_path }}/docs/layouts/#splash-page-layout) page layout as a way of arranging and aligning "feature blocks" containing text or image.
-
-To add a feature row containing three content blocks with text and image, add the following YAML Front Matter
-
-| Name | Required | Description | Default |
-| ---- | ----------- | ----------- | ------- |
-| **image_path** | **Required** | For images placed in the `/images/` directory just add the filename and extension. Use absolute URLS for those hosted externally. | |
-| **alt** | Optional | Alternate text for image. | |
-| **title** | Optional | Content block title. | |
-| **excerpt** | Optional | Content block excerpt text. Markdown is allowed. | |
-| **url** | Optional | URL that the button should link to. | |
-| **btn_label** | Optional | Button text label. | `more_label` in UI Text data file. |
-| **btn_class** | Optional | Button style. See [utility classes]({{ base_path }}/docs/utility-classes/#buttons) for options. | `btn` |
-
-```yaml
-feature_row:
- - image_path: unsplash-gallery-image-1-th.jpg
- alt: "placeholder image 1"
- title: "Placeholder 1"
- excerpt: "This is some sample content that goes here with **Markdown** formatting."
- - image_path: unsplash-gallery-image-2-th.jpg
- alt: "placeholder image 2"
- title: "Placeholder 2"
- excerpt: "This is some sample content that goes here with **Markdown** formatting."
- url: "#test-link"
- btn_label: "Read More"
- btn_class: "btn--inverse"
- - image_path: unsplash-gallery-image-3-th.jpg
- title: "Placeholder 3"
- excerpt: "This is some sample content that goes here with **Markdown** formatting."
-```
-
-And then drop-in the feature row include in the body where you'd like it to appear.
-
-| Include Parameter | Required | Description | Default |
-| ----------------- | -------- | ----------- | ------- |
-| **id** | Optional | To add multiple rows to a document uniquely name them in the YAML Front Matter and reference in `{% raw %}{% include feature_row id="row2" %}{% endraw %}` | `feature_row` |
-| **type** | Optional | Alignment of the featured blocks in the row. Options include: `left`, `center`, or `right` aligned. | |
-
-```liquid
-{% raw %}{% include feature_row %}{% endraw %}
-```
-
-{% include feature_row %}
-
-**More Feature Row Goodness:** A [few more examples]({{ base_path }}/splash-page/) and [source code]({{ site.gh_repo }}/gh-pages/_pages/splash-page.md) can be seen in the demo site.
-{: .notice--info}
-
-## Table of Contents
-
-To include an [auto-generated table of contents](http://kramdown.rubyforge.org/converter/html.html#toc) for posts and pages, add the following helper before any actual content in your post or page.
-
-```liquid
-{% raw %}{% include toc %}{% endraw %}
-```
-
-![table of contents example]({{ base_path }}/images/mm-toc-helper-example.jpg)
-
-| Parameter | Required | Description | Default |
-| --------- | -------- | ----------- | ------- |
-| **title** | Optional | Table of contents title. | `toc_label` in UI Text data file. |
-| **icon** | Optional | Table of contents icon (shows before the title). | [Font Awesome](https://fortawesome.github.io/Font-Awesome/icons/) **file-text** icon. Any other FA icon can be used instead. |
-
-**TOC example with custom title and icon**
-
-```liquid
-{% raw %}{% include toc icon="gears" title="My Table of Contents" %}{% endraw %}
-```
\ No newline at end of file
diff --git a/_docs/14-utility-classes.md b/_docs/14-utility-classes.md
deleted file mode 100644
index 4f74d633..00000000
--- a/_docs/14-utility-classes.md
+++ /dev/null
@@ -1,179 +0,0 @@
----
-title: "Utility Classes"
-permalink: /docs/utility-classes/
-excerpt: "CSS classes for aligning text/image, styling buttons and notices, and more."
-sidebar:
- title: "v3.0"
- nav: docs
-modified: 2016-04-13T15:54:02-04:00
----
-
-{% include base_path %}
-{% include toc icon="gears" title="Utility Classes" %}
-
-Using the Kramdown Markdown renderer with Jekyll allows you to add [block](http://kramdown.gettalong.org/quickref.html#block-attributes) and [inline attributes](http://kramdown.gettalong.org/quickref.html#inline-attributes). This is nice if you want to add custom styling to text and image, and still write in Markdown.
-
-**Jekyll 3:** Kramdown is the default for `jekyll new` sites and those hosted on GitHub Pages. Not using Kramdonw? That's OK. The following classes are still available when used with standard HTML.
-{: .notice--warning}
-
-## Text Alignment
-
-Align text blocks with the following classes.
-
-Left aligned text `.text-left`
-{: .text-left}
-
-```markdown
-Left aligned text
-{: .text-left}
-```
-
----
-
-Center aligned text. `.text-center`
-{: .text-center}
-
-```markdown
-Center aligned text.
-{: .text-center}
-```
-
----
-
-Right aligned text. `.text-right`
-{: .text-right}
-
-```markdown
-Right aligned text.
-{: .text-right}
-```
-
----
-
-**Justified text.** `.text-justify` Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque vel eleifend odio, eu elementum purus. In hac habitasse platea dictumst. Fusce sed sapien eleifend, sollicitudin neque non, faucibus est. Proin tempus nisi eu arcu facilisis, eget venenatis eros consequat.
-{: .text-justify}
-
-```markdown
-Justified text.
-{: .text-justify}
-```
-
----
-
-No wrap text. `.text-nowrap`
-{: .text-nowrap}
-
-```markdown
-No wrap text.
-{: .text-nowrap}
-```
-
-## Image Alignment
-
-Position images with the following classes.
-
-![image-center]({{ site.url }}{{ site.baseurl }}/images/image-alignment-580x300.jpg){: .align-center}
-
-The image above happens to be **centered**.
-
-```markdown
-![image-center](/images/filename.jpg){: .align-center}
-```
-
----
-
-![image-left]({{ site.url }}{{ site.baseurl }}/images/image-alignment-150x150.jpg){: .align-left} The rest of this paragraph is filler for the sake of seeing the text wrap around the 150×150 image, which is **left aligned**. There should be plenty of room above, below, and to the right of the image. Just look at him there --- Hey guy! Way to rock that left side. I don't care what the right aligned image says, you look great. Don't let anyone else tell you differently.
-
-```markdown
-![image-left](/images/filename.jpg){: .align-left}
-```
-
----
-
-![image-right]({{ site.url }}{{ site.baseurl }}/images/image-alignment-300x200.jpg){: .align-right}
-
-And now we're going to shift things to the **right align**. Again, there should be plenty of room above, below, and to the left of the image. Just look at him there --- Hey guy! Way to rock that right side. I don't care what the left aligned image says, you look great. Don't let anyone else tell you differently.
-
-```markdown
-![image-right](/images/filename.jpg){: .align-right}
-```
-
----
-
-![full]({{ site.url }}{{ site.baseurl }}/images/image-alignment-1200x4002.jpg)
-{: .full}
-
-The image above should extend outside of the parent container on right.
-
-```markdown
-![full](/images/filename.jpg)
-{: .full}
-```
-
-## Buttons
-
-Make any link standout more when applying the `.btn` class.
-
-```html
-Link Text
-```
-
-| Button Type | Example | Class | Kramdown |
-| ------ | ------- | ----- | ------- |
-| Default | [Text](#link){: .btn} | `.btn` | `[Text](#link){: .btn}` |
-| Success | [Text](#link){: .btn .btn--success} | `.btn .btn--success` | `[Text](#link){: .btn .btn--success}` |
-| Warning | [Text](#link){: .btn .btn--warning} | `.btn .btn--warning` | `[Text](#link){: .btn .btn--warning}` |
-| Danger | [Text](#link){: .btn .btn--danger} | `.btn .btn--danger` | `[Text](#link){: .btn .btn--danger}` |
-| Info | [Text](#link){: .btn .btn--info} | `.btn .btn--info` | `[Text](#link){: .btn .btn--info}` |
-| Inverse | [Text](#link){: .btn .btn--inverse} | `.btn .btn--inverse` | `[Text](#link){: .btn .btn--inverse}` |
-| Light Outline | [Text](#link){: .btn .btn--light-outline} | `.btn .btn--light-outline` | `[Text](#link){: .btn .btn--light-outline}` |
-
-| Button Size | Example | Class | Kramdown |
-| ----------- | ------- | ----- | -------- |
-| X-Large | [X-Large Button](#){: .btn .btn--x-large} | `.btn .btn--x-large` | `[Text](#link){: .btn .btn--x-large}` |
-| Large | [Large Button](#){: .btn .btn--large} | `.btn .btn--large` | `[Text](#link){: .btn .btn--large}` |
-| Default | [Default Button](#){: .btn} | `.btn` | `[Text](#link){: .btn}` |
-| Small | [Small Button](#){: .btn .btn--small} | `.btn .btn--small` | `[Text](#link){: .btn .btn--small}` |
-
-## Notices
-
-Call attention to a block of text.
-
-| Notice Type | Class |
-| ----------- | ----- |
-| Default | `.notice` |
-| Primary | `.notice--primary` |
-| Info | `.notice--info` |
-| Warning | `.notice--warning` |
-| Success | `.notice--success` |
-| Danger | `.notice--danger` |
-
-**Watch out!** This paragraph of text has been emphasized with the `{: .notice}` class.
-{: .notice}
-
-**Watch out!** This paragraph of text has been emphasized with the `{: .notice--primary}` class.
-{: .notice--primary}
-
-**Watch out!** This paragraph of text has been emphasized with the `{: .notice--info}` class.
-{: .notice--info}
-
-**Watch out!** This paragraph of text has been emphasized with the `{: .notice--warning}` class.
-{: .notice--warning}
-
-**Watch out!** This paragraph of text has been emphasized with the `{: .notice--success}` class.
-{: .notice--success}
-
-**Watch out!** This paragraph of text has been emphasized with the `{: .notice--danger}` class.
-{: .notice--danger}
-
-{% capture notice-text %}
-You can also add the `.notice` class to a `
` element.
-
-* Bullet point 1
-* Bullet point 2
-{% endcapture %}
-
-
-
Notice Headline:
- {{ notice-text | markdownify }}
-
\ No newline at end of file
diff --git a/_docs/15-stylesheets.md b/_docs/15-stylesheets.md
deleted file mode 100644
index a3c2143f..00000000
--- a/_docs/15-stylesheets.md
+++ /dev/null
@@ -1,150 +0,0 @@
----
-title: "Stylesheets"
-permalink: /docs/stylesheets/
-excerpt: "Instructions for customizing and building the theme's stylesheets."
-sidebar:
- title: "v3.0"
- nav: docs
-modified: 2016-04-13T15:54:02-04:00
----
-
-{% include base_path %}
-
-The theme's `main.css` stylesheet is built from several SCSS partials located in `/assets/_scss/` and are structured as follows:
-
-```bash
-minimal mistakes
-├── assets
-| ├── _scss
-| | ├── vendor # vendor SCSS partials
-| | | ├── breakpoint # media query mixins
-| | | ├── font-awesome # Font Awesome icons
-| | | ├── magnific-popup # Magnific Popup lightbox
-| | | └── susy # Susy grid system
-| | ├── _animations.scss # animations
-| | ├── _archive.scss # archives (list, grid, feature views)
-| | ├── _base.scss # base HTML elements
-| | ├── _buttons.scss # buttons
-| | ├── _footer.scss # footer
-| | ├── _masthead.scss # masthead
-| | ├── _mixins.scss # mixins (em function, clearfix)
-| | ├── _navigation.scss # nav links (breadcrumb, priority+, toc, pagination, etc.)
-| | ├── _notices.scss # notices
-| | ├── _page.scss # pages
-| | ├── _print.scss # print styles
-| | ├── _reset.scss # reset
-| | ├── _sidebar.scss # sidebar
-| | ├── _syntax.scss # syntax highlighting
-| | ├── _tables.scss # tables
-| | ├── _utilities.scss # utility classes (text/image alignment)
-| | ├── _variables.scss # theme defaults (fonts, colors, etc.)
-| | └── main.scss # all SCSS partials are imported here
-| ├── css
-| | └── main.css # compiled theme stylesheet
-```
-
-## Customizing
-
-The settings in `/assets/_scss/_variables.scss` can modify the following aspects of the theme:
-
-### Paragraph Indention
-
-To mimic the look of type set in a printed book or manuscript you may want to enable paragraph indention. When `$paragraph-indent` is set to `true` indents are added to each sibling and the margin below each paragraph is removed.
-
-
-
-The size of the indent can also be customized by changing the value of `$indent-var`.
-
-### Font Stacks
-
-By default the theme uses [system fonts](https://medium.com/designing-medium/system-shock-6b1dc6d6596f#.rb81vgn7i) for all of the font stacks (serif, sans-serif, and monospace). This is done in part to provide a clean base for you to build off of and to improve performance since we aren't loading any custom webfonts[^font-awesome] by default.
-
-```scss
-/* system typefaces */
-$serif : Georgia, Times, serif;
-$sans-serif : -apple-system, ".SFNSText-Regular", "San Francisco", "Roboto", "Segoe UI", "Helvetica Neue", "Lucida Grande", Arial, sans-serif;
-$monospace : Monaco, Consolas, "Lucida Console", monospace;
-```
-
-[^font-awesome]: Apart from [Font Awesome](https://fortawesome.github.io/Font-Awesome/) icon webfonts.
-
-Sans-serif fonts have been used for most of the type, with serifs reserved for captions. If you wish to change this you'll need to poke around the various `SCSS` partials and modify `font-family` declarations.
-
-**ProTip:** To use webfonts from services like [Adobe TypeKit](https://typekit.com/) or [Google Fonts](https://www.google.com/fonts) simply update the font stacks and then add their scripts to `_includes/head/custom.html`.
-{: .notice--info}
-
-### Type Scale
-
-Wherever possible type scale variables have been used instead of writing out fixed sizes. This makes updating much easier by changing values in one file, `_variables.scss`.
-
-Example:
-
-```scss
-.page__lead {
- font-family: $global-font-family;
- font-size: $type-size-4;
-}
-```
-
-Type sizes are set in ems to proportional scale as the screen size changes. Large headlines that look great on desktop monitors will shrink ever so slightly as to not be too big on mobile devices. To adjust this hierarchy simply edit the default values:
-
-```scss
-/* type scale */
-$type-size-1 : 2.441em; // ~39.056px
-$type-size-2 : 1.953em; // ~31.248px
-$type-size-3 : 1.563em; // ~25.008px
-$type-size-4 : 1.25em; // ~20px
-$type-size-5 : 1em; // ~16px
-$type-size-6 : 0.75em; // ~12px
-$type-size-7 : 0.6875em; // ~11px
-$type-size-8 : 0.625em; // ~10px
-```
-
-### Colors
-
-Change the mood of your site by altering a few color variables. `$body-color`, `$background-color`, `$text-color`, `$link-color`, and `$masthead-link-color` will have the most affect when changed.
-
-### Breakpoints and Grid Stuff
-
-Probably won't need to touch these, but they're there if you need to. Width variables are used with the [`@include breakpoint()`](http://breakpoint-sass.com/) mixin to adapt the design of certain elements.
-
-And `$susy` is used for setting [the grid](http://susy.oddbird.net/) the theme uses. Uncommenting the lines under `debug` can be useful if you want to show the columns when adjusting the layout.
-
-
-
----
-
-The theme does not leverage Jekyll's [built-in support for preprocessing Sass](https://jekyllrb.com/docs/assets/#sassscss) files. Why is that you ask? [**Autoprefixer**](https://github.com/postcss/autoprefixer)! As part of a build step the stylesheet is post processed with Autoprefixer to add vendor prefixes --- something not currently possible without a plugin[^jekyll-assets].
-
-[^jekyll-assets]: A better solution would be to use the fantastic [jekyll-assets](https://github.com/jekyll/jekyll-assets) plugin to manage your assets if you aren't hosting with GitHub Pages. Autoprefixer support is built-in :smile:.
-
-If you plan on making any changes to the `.scss` partials you will need to rebuild the stylesheet outside of the normal Jekyll workflow.
-
-**Sass/SCSS files:** You can of course modify the structure of the CSS files to have Jekyll natively process `main.scss` for you. Just be sure to update the partials to include any vendor prefixes or else things may look off in older browsers.
-{: .notice--info}
-
-## Build Process
-
-In an effort to reduce dependencies a set of [**npm scripts**](https://css-tricks.com/why-npm-scripts/) are used to build the CSS instead of task runners like [Gulp](http://gulpjs.com/) or [Grunt](http://gruntjs.com/). If those tools are more your style then by all means use them instead :wink:.
-
-To get started:
-
-1. Install [Node.js](http://nodejs.org/).
-2. `cd` to the root of your project.
-3. Install all of the dependencies by running `npm install`.
-
-**Note:** If you upgraded from a previous version of the theme be sure you copied over [`package.json`]({{ site.gh_repo }}/master/package.json) prior to running `npm install`.
-{: .notice--warning}
-
-If all goes well, running `npm build:css` will process all SCSS files into `main.css`, which should then pipe through Autoprefixer.
-
-```
-Rendering Complete, saving .css file...
-Wrote CSS to \assets\css\main.css
-```
diff --git a/_docs/16-javascript.md b/_docs/16-javascript.md
deleted file mode 100644
index ace62c17..00000000
--- a/_docs/16-javascript.md
+++ /dev/null
@@ -1,53 +0,0 @@
----
-title: "JavaScript"
-permalink: /docs/javascript/
-excerpt: "Instructions for customizing and building the theme's scripts."
-sidebar:
- title: "v3.0"
- nav: docs
-modified: 2016-04-13T15:54:02-04:00
----
-
-{% include base_path %}
-
-The theme's `main.js` script is built from several vendor, jQuery plugins, and other scripts found in `/assets/js/`.
-
-```bash
-minimal mistakes
-├── assets
-| ├── js
-| | ├── plugins
-| | | ├── jquery.fitvids.js # fluid width video embeds
-| | | ├── jquery.greedy-navigation.js # priority plus navigation
-| | | ├── jquery.magnific-popup.js # responsive lightbox
-| | | ├── jquery.smooth-scroll.min.js # make same-page links scroll smoothly
-| | | └── stickyfill.min.js # `position: sticky` polyfill
-| | ├── vendor
-| | | └── jquery
-| | | └── jquery-1.12.1.min.js
-| | ├── _main.js # jQuery plugin settings and other scripts
-| | └── main.min.js # concatenated and minified scripts
-```
-
-## Customizing
-
-To modify or add your own scripts include them in `/assets/js/_main.js` and then rebuild using `npm run build:js`. See below for more details.
-
-If you add additional scripts to `/assets/js/plugins/` and would like them concatenated with the others, be sure to update the `uglify` script in `package.json`. Same goes for scripts that you remove.
-
----
-
-## Build Process
-
-In an effort to reduce dependencies a set of [**npm scripts**](https://css-tricks.com/why-npm-scripts/) are used to build `main.min.js` instead of task runners like [Gulp](http://gulpjs.com/) or [Grunt](http://gruntjs.com/). If those tools are more your style then by all use them instead :wink:.
-
-To get started:
-
-1. Install [Node.js](http://nodejs.org/).
-2. `cd` to the root of your project.
-3. Install all of the dependencies by running `npm install`.
-
-**Note:** If you upgraded from a previous version of the theme be sure you copied over [`package.json`]({{ site.gh_repo }}/master/package.json) prior to running `npm install`.
-{: .notice--warning}
-
-If all goes well, running `npm build:js` will compress/concatenate `_main.js` and all plugin scripts into `main.min.js`.
\ No newline at end of file
diff --git a/_docs/17-history.md b/_docs/17-history.md
deleted file mode 100644
index 20a81888..00000000
--- a/_docs/17-history.md
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title: "History"
-permalink: /docs/history/
-excerpt: "Changelog of enhancements and bug fixes made to the theme."
-sidebar:
- title: "v3.0"
- nav: docs
-modified: 2016-04-13T15:27:39-04:00
----
-
-## [1.2.0](https://github.com/mmistakes/minimal-mistakes/releases/tag/1.2.0)
-
-### Bug Fixes
-
-- Table weren't filling the entire width of the content container. They now scale at 100%. Thanks [@dhruvbhatia](https://github.com/dhruvbhatia)
-
-### Enhancements
-
-- Decreased spacing between Markdown footnotes
-- Removed dark background on footer
-- Removed UPPERCASE styling on post titles in the index listing
-
-## [1.1.4](https://github.com/mmistakes/minimal-mistakes/releases/tag/1.1.4)
-
-### Bug Fixes
-
-- Fix top navigation bug issue ([#10](https://github.com/mmistakes/minimal-mistakes/issues/10)) for real this time. Remember to clear your floats kids.
-
-## [1.1.3](https://github.com/mmistakes/minimal-mistakes/releases/tag/1.1.3)
-
-### Bug Fixes
-
-- Fix top navigation links that weren't click able on small viewports (Issue [#10](https://github.com/mmistakes/minimal-mistakes/issues/10)).
-- Remove line wrap from top navigation links that may span multiple lines.
-
-## [1.1.2](https://github.com/mmistakes/minimal-mistakes/releases/tag/1.1.2)
-
-### Enhancements
-
-- Added Grunt build script for compiling Less/JavaScript and optimizing image assets.
-- Added support for large image summary Twitter card.
-- Stylesheet adjustments
-
-## [1.1.1](https://github.com/mmistakes/minimal-mistakes/releases/tag/1.1.1)
-
-### Bug Fixes
-
-- Removed [Typeplate](http://typeplate.com/) styles. Was [causing issues with newer versions of Less](https://github.com/typeplate/typeplate.github.io/issues/108) and is no longer maintained.
-
-### Enhancements
-
-- Added [image attribution](http://mmistakes.github.io/minimal-mistakes/theme-setup/#feature-images) for post and page feature images.
-- Added [404 page](http://mmistakes.github.io/minimal-mistakes/404.html).
-- Cleaned up various Less variables to better align with naming conventions used in other MM Jekyll themes.
-- Removed Chrome Frame references.
-- Added global CSS3 transitions to text and block elements.
-- Improved typography in a few places.
-
-## [1.0.2](https://github.com/mmistakes/minimal-mistakes/releases/tag/v1.0.2)
-
-### Enhancements
-
-- Google Analytics, Google Authorship, webmaster verifies, and Twitter card meta are now optional.
-
-## [1.0.1](https://github.com/mmistakes/minimal-mistakes/releases/tag/v1.0.1)
\ No newline at end of file
diff --git a/_docs/18-contributing.md b/_docs/18-contributing.md
deleted file mode 100644
index 29083c48..00000000
--- a/_docs/18-contributing.md
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: "Contributing"
-permalink: /docs/contributing/
-excerpt: "How you can contribute to make this theme better."
-sidebar:
- title: "v3.0"
- nav: docs
-modified: 2016-04-13T15:54:02-04:00
----
-
-Having trouble working with the theme? Found a typo in the documentation? Interested in adding a feature or [fixing a bug]({{ site.gh_repo }}/issues)? Then by all means [submit an issue]({{ site.gh_repo }}/issues/new) or [pull request]({{ site.gh_repo }}/compare). If this is your first pull request, it may be helpful to read up on the [GitHub Flow](https://guides.github.com/introduction/flow/) first.
-
-As the theme's name implies strives to keep things as minimal as possible. It has been designed as a base for you to build off of.
-
-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 :smile:.
\ No newline at end of file
diff --git a/_docs/19-docs-2-2.md b/_docs/19-docs-2-2.md
deleted file mode 100644
index adeae18c..00000000
--- a/_docs/19-docs-2-2.md
+++ /dev/null
@@ -1,305 +0,0 @@
----
-title: "2.2 Documentation"
-permalink: /docs/docs-2-2/
-excerpt: "Setup and installation instructions for Minimal Mistakes 2.2 (deprecated)."
-sidebar:
- title: "v3.0"
- nav: docs
-modified: 2016-04-13T15:54:02-04:00
----
-
-{% include base_path %}
-{% include toc %}
-
-## Installation
-
-Minimal Mistakes now requires [Jekyll](http://jekyllrb.com/) 3.0. Make sure to run `bundle update` if you aren't on the latest version to update all gem dependencies.
-
-If you are creating a new Jekyll site using Minimal Mistakes follow these steps:
-
-1. Fork the [Minimal Mistakes repo](http://github.com/mmistakes/minimal-mistakes/fork).
-2. Clone the repo you just forked and rename it.
-3. [Install Bundler](http://bundler.io) `gem install bundler` and Run `bundle install` to install all dependencies (Jekyll, [Jekyll-Sitemap](https://github.com/jekyll/jekyll-sitemap), [Octopress](https://github.com/octopress/octopress), etc)
-4. Update `config.yml`, add navigation, and replace demo posts and pages with your own. Full details below.
-
-If you want to use Minimal Mistakes with an existing Jekyll site follow these steps:
-
-1. [Download Minimal Mistakes](https://github.com/mmistakes/minimal-mistakes/releases/tag/2.2.1) and unzip.
-2. Rename `minimal-mistakes-master` to something meaningful ie: `new-site`
-3. Run `bundle install` to install all dependencies (Jekyll, [Jekyll-Sitemap](https://github.com/jekyll/jekyll-sitemap), [Octopress](https://github.com/octopress/octopress), etc)
-4. Remove demo posts/pages and replace with your own posts, pages, and any other content you want to move over.
-5. Update posts' and pages' YAML to match variables used by Minimal Mistakes. Full details below.
-6. Update `_config.yml` and add navigation links. Full details below.
-
-**Pro-tip:** Delete the `gh-pages` branch after cloning and start fresh by branching off `master`. There is a bunch of garbage in `gh-pages` used for the theme's demo site that I'm guessing you won't want.
-{: .notice}
-
-## Running Jekyll
-
-The preferred method for running Jekyll is with `bundle exec`, but if you're willing to deal gem conflicts feel free to go cowboy with a `jekyll serve` or `jekyll build`.
-
-> In some cases, running executables without bundle exec may work, if the executable happens to be installed in your system and does not pull in any gems that conflict with your bundle.
->
->However, this is unreliable and is the source of considerable pain. Even if it looks like it works, it may not work in the future or on another machine.
-
-```bash
-bundle exec jekyll serve
-```
-
-## Scaffolding
-
-How Minimal Mistakes is organized and what the various files are. All posts, layouts, includes, stylesheets, assets, and whatever else is grouped nicely under the root folder. The compiled Jekyll site outputs to `_site/`.
-
-```bash
-minimal-mistakes/
-├── _includes/
-| ├── author-bio.html # bio stuff layout. pulls optional owner data from _config.yml
-| ├── browser-upgrade # prompt to install a modern browser for < IE9
-| ├── disqus-comments # Disqus comments script
-| ├── footer # site footer
-| ├── head # site head
-| ├── navigation # site top navigation
-| ├── open-graph.html # Twitter Cards and Open Graph meta data
-| └── scripts # site scripts
-├── _layouts/
-| ├── home.html # homepage layout
-| ├── page.html # page layout
-| ├── post-index.html # post index layout
-| └── post.html # single post layout
-├── _posts/ # MarkDown formatted posts
-├── _sass/ # Sass stylesheets
-├── _templates/ # used by Octopress to define YAML variables for new posts/pages
-├── about/ # sample about page
-├── assets/
-| ├── css/ # compiled stylesheets
-| ├── fonts/ # webfonts
-| ├── js/
-| | ├── _main.js # main JavaScript file, plugin settings, etc
-| | ├── plugins/ # scripts and jQuery plugins to combine with _main.js
-| | ├── scripts.min.js # concatenated and minified _main.js + plugin scripts
-| | └── vendor/ # vendor scripts to leave alone and load as is
-| └── less/
-├── images/ # images for posts and pages
-├── 404.md # 404 page
-├── feed.xml # Atom feed template
-├── index.md # sample homepage. lists 5 latest posts
-├── posts/ # sample post index page. lists all posts in reverse chronology
-└── theme-setup/ # theme setup page. safe to remove
-```
-
-## Site Setup
-
-A quick checklist of the files you'll want to edit to get up and running.
-
-### Site Wide Configuration
-
-`_config.yml` is your friend. Open it up and personalize it. Most variables are self explanatory but here's an explanation of each if needed:
-
-#### title
-
-The title of your site... shocker!
-
-Example `title: My Awesome Site`
-
-#### url
-
-Used to generate absolute urls in `sitemap.xml`, `feed.xml`, and for generating canonical URLs in ``. When developing locally either comment this out or use something like `http://localhost:4000` so all assets load properly. *Don't include a trailing `/`*.
-
-Examples:
-
-```yaml
-url: http://mmistakes.github.io/minimal-mistakes
-url: http://localhost:4000
-url: //cooldude.github.io
-url:
-```
-
-#### Google Analytics and Webmaster Tools
-
-Google Analytics UA and Webmaster Tool verification tags can be entered under `owner` in `_config.yml`. For more information on obtaining these meta tags check [Google Webmaster Tools](http://support.google.com/webmasters/bin/answer.py?hl=en&answer=35179) and [Bing Webmaster Tools](https://ssl.bing.com/webmaster/configure/verify/ownership) support.
-
-### Navigation Links
-
-To set what links appear in the top navigation edit `_data/navigation.yml`. Use the following format to set the URL and title for as many links as you'd like. *External links will open in a new window.*
-
-```yaml
-- title: Portfolio
- url: /portfolio/
-
-- title: Made Mistakes
- url: http://mademistakes.com
-```
-
-## Adding New Content with Octopress
-
-While completely optional, I've included Octopress and some starter templates to automate the creation of new posts and pages. To take advantage of it start by installing the [Octopress](https://github.com/octopress/octopress) gem if it isn't already.
-
-```bash
-$ gem install octopress
-```
-
-### New Post
-
-Default command
-
-```bash
-$ octopress new post "Post Title"
-```
-
-Default works great if you want all your posts in one directory, but if you're like me and want to group them into subfolders like `/posts`, `/portfolio`, etc. Then this is the command for you. By specifying the DIR it will create a new post in that folder and populate the `categories:` YAML with the same value.
-
-```bash
-$ octopress new post "New Portfolio Post Title" --dir portfolio
-```
-
-### New Page
-
-To create a new page use the following command.
-
-```bash
-$ octopress new page new-page/
-```
-
-This will create a page at `/new-page/index.md`
-
-## Layouts and Content
-
-Explanations of the various `_layouts` included with the theme and when to use them.
-
-### Post and Page
-
-These two layouts are very similar. Both have an author sidebar, allow for large feature images at the top, and optional Disqus comments. The only real difference is the post layout includes related posts at the end of the page.
-
-### Post Index Page
-
-A [sample index page]({{ site.url }}/posts/) listing all posts grouped by the year they were published has been provided. The name can be customized to your liking by editing a few references. For example, to change **Posts** to **Writing** update the following:
-
-In `_config.yml` under `links:` rename the title and URL to the following:
-
-```yaml
- links:
- - title: Writing
- url: /writing/
-```
-
-* Rename `posts/index.md` to `writing/index.md` and update the YAML front matter accordingly.
-* Update the **View all posts** link in the `post.html` layout found in `_layouts` to match title and URL set previously.
-
-### Feature Images
-
-A good rule of thumb is to keep feature images nice and wide so you don't push the body text too far down. An image cropped around around 1024 x 256 pixels will keep file size down with an acceptable resolution for most devices. If you want to serve these images responsively I'd suggest looking at the [Jekyll Picture Tag](https://github.com/robwierzbowski/jekyll-picture-tag) plugin[^plugins].
-
-[^plugins]: If you're using GitHub Pages to host your site be aware that plugins are disabled. You'll need to build your site locally and then manually deploy if you want to use this sweet plugin.
-
-The post and page layouts make the assumption that the feature images live in the `images/` folder. To add a feature image to a post or page just include the filename in the front matter like so. It's probably best to host all your images from this folder, but you can hotlink from external sources if you desire.
-
-```yaml
-image:
- feature: feature-image-filename.jpg
- thumb: thumbnail-image.jpg #keep it square 200x200 px is good
-```
-
-To add attribution to a feature image use the following YAML front matter on posts or pages. Image credits appear directly below the feature image with a link back to the original source if supplied.
-
-```yaml
-image:
- feature: feature-image-filename.jpg
- credit: Michael Rose #name of the person or site you want to credit
- creditlink: http://mademistakes.com #url to their site or licensing
-```
-
-### Thumbnails for OG and Twitter Cards
-
-Feature and thumbnail images are used by [Open Graph](https://developers.facebook.com/docs/opengraph/) and [Twitter Cards](https://dev.twitter.com/docs/cards) as well. If you don't assign a thumbnail the default graphic *(default-thumb.png)* is used. I'd suggest changing this to something more meaningful --- your logo or avatar are good options.
-
-**Pro-Tip**: You need to [apply for Twitter Cards](https://dev.twitter.com/docs/cards) before they will begin showing up when links to your site are shared.
-{:.notice}
-
-### Author Override
-
-By making use of data files you can assign different authors for each post.
-
-Start by modifying `authors.yml` file in the `_data` folder and add your authors using the following format.
-
-```yaml
-# Authors
-
-billy_rick:
- name : "Billy Rick"
- web : "http://thewhip.com"
- email : "billy@rick.com"
- bio : "What do you want, jewels? I am a very extravagant man."
- avatar : "bio-photo-2.jpg"
- twitter : "extravagantman"
- google_plus : "BillyRick"
-
-cornelius_fiddlebone:
- name : "Cornelius Fiddlebone"
- email : "cornelius@thewhip.com"
- bio : "I ordered what?"
- avatar : "bio-photo.jpg"
- twitter : "rhymeswithsackit"
- google_plus : "CorneliusFiddlebone"
-```
-
-To assign Billy Rick as an author for our post. We'd add the following YAML front matter to a post:
-
-```yaml
-author: billy_rick
-```
-
-### Kramdown Table of Contents
-
-To include an auto-generated **table of contents** for posts and pages, add the following `_include` before the actual content. [Kramdown will take care of the rest](http://kramdown.rubyforge.org/converter/html.html#toc) and convert all headlines into list of links.
-
-```html
-{% raw %}{% include toc.html %}{% endraw %}
-```
-
-### Paragraph Indentation
-
-By default the margin below paragraphs has been removed and indent added to each. This is an intentional design decision to mimic the look of type set in a printed book or manuscript.
-
-
-
-To disable the indents and add spacing between paragraphs change the following line in `_sass/variables.scss` from `true !default` to `false` like so.
-
-```scss
-$paragraph-indent: false;
-```
-
-
-
-### Videos
-
-Video embeds are responsive and scale with the width of the main content block with the help of [FitVids](http://fitvidsjs.com/).
-
-Not sure if this only effects Kramdown or if it's an issue with Markdown in general. But adding YouTube video embeds causes errors when building your Jekyll site. To fix add a space between the `