Vita Black Dolce Quimby DV Women's by ETgw8
  • Site Author
  • Reading Files
  • Conversion and Markdown Processing
  • Front Matter Defaults
  • Outputting
  • Plugins
  • Archive Settings
  • HTML Compression
  • Settings that affect your entire site can be changed in Jekyll’s configuration file: _config.yml, found in the root of your project. If you don’t have this file you’ll need to copy or create one using the theme’s default _config.yml as a base.

    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.

    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

    Theme

    If you’re using the Ruby gem version of the theme you’ll need this line to activate it:

    themeB Bumud 7 Winter Boots Snow Women's M Sneaker Flat US Lined Shoes Black Warm Fur : minimal-mistakes-jekyll
    

    Skin

    Easily change the color scheme of the theme using one of the provided “skins”:

    minimal_mistakes_skin: "default" # "air", "aqua", "contrast", "dark", "dirt", "neon", "mint", "plum" "sunrise"
    

    Note: If you have made edits to the theme’s CSS files be sure to update /assets/css/main.scss to include @import "minimal-mistakes/skins/default"; // skin before the minimal-mistakes import.

    Air skin: air

    Calm and blue.

    Aqua skin: aqua

    Just like water.

    Contrast skin: contrast

    Retro feel with bold blue links and inverted footer.

    Dark skin: dark

    Vapor Pink Coral Vapor Converse Ox Women's Star Shoe Taylor Casual All Chuck xwwFTqzO
    Inverted palette, white text on a dark background.

    Dirt skin: Sneaker M Shoes Winter B Women's Lined US Snow Warm Flat Bumud Boots Black Fur 7 dirt

    Earthy tones.

    Mint skin: mint

    Minty fresh green.

    Neon skin: neon

    Inverted palette, white text on a dark background.

    Neon skin: plum

    Purple reigns supreme.

    Sunrise skin: sunrise

    Oranges and red.

    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 variation locale: "en" is also acceptable. To find your language and country codes check this reference table.

    Properly setting the locale is important for associating localized text found in the UI Text data file. An improper match will cause parts of the UI to disappear (eg. button labels, section headings, etc).

    Note: The theme comes with localized text in English (en, en-US, en-GB). If you change locale in _config.yml to something else, most of the UI text will go blank. Be sure to add the corresponding locale key and translated text to _data/ui-text.yml to avoid this.

    Site Title

    The name of your site. Is used throughout the theme in places like the site masthead and </code> tags.</p> <p><em>Example:</em> <code class="highlighter-rouge">title: "My Awesome Site"</code></p> <p>You also have the option of customizing the separation character used in SEO-friendly page titles.</p> <p><em>Example:</em> <code class="highlighter-rouge">title_separator: "|"</code> would produce page titles like <code class="highlighter-rouge">Sample Page | My Awesome Site</code>.</p> <p class="notice--warning"><strong>Note:</strong> Long site titles have been known to break the masthead layout. Avoid adding a long “tagline” to the title prevent this from happening eg. `My Awesome Site is the Best Because I Say So”.</p> <h3 id="site-name">Site Name</h3> <p>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.</p> <p><em>Example:</em> <code class="highlighter-rouge">name: "Michael Rose"</code>.</p> <p class="notice--info"><strong>ProTip:</strong> If you want to get crafty with your YAML you can use <a href="/html#id2785586">anchors</a> to reuse values. For example <code class="highlighter-rouge">foo: &var "My String"</code> allows you to reuse <code class="highlighter-rouge">"My String"</code> elsewhere in <code class="highlighter-rouge">_config.yml</code> like so… <code class="highlighter-rouge">bar: *var</code>. You’ll see a few examples of this in the provided Jekyll config.</p><a href="http://www.dopplegangerchronicles.com/homeWomen's_Sam_Rose_by_Boot_Ankle_Holt_Taupe_Edelman_Circus_4tOxwRq1-qewe-43.html" title="Women's Sam Rose by Boot Ankle Holt Taupe Edelman Circus 4tOxwRq1">Women's Sam Rose by Boot Ankle Holt Taupe Edelman Circus 4tOxwRq1</a> <h3 id="site-description">Site Description</h3> <p>Fairly obvious. <code class="highlighter-rouge">site.description</code> describes the site. Used predominantly in meta descriptions for improving SEO.</p> <p><em>Example:</em> <code class="highlighter-rouge">description: "A flexible Jekyll theme for your blog or site with a minimalist aesthetic."</code></p> <h3 id="site-url">Site URL</h3> <p>The base hostname and protocol for your site. If you’re hosting with GitHub Pages this will be something like <code class="highlighter-rouge">url: "https://github.io.mmistakes"</code> or <code class="highlighter-rouge">url: "https://mademistakes.com"</code> if you have a custom domain name.</p> <p>GitHub Pages now <a href="/articles">forces <code class="highlighter-rouge">https://</code> for new sites</a> so be mindful of that when setting your URL to avoid mixed-content warnings.</p> <p class="notice--warning"><strong>Note:</strong> Jekyll 3.3 overrides this value with <code class="highlighter-rouge">url: http://localhost:4000</code> when running <code class="highlighter-rouge">jekyll serve</code> locally in development. If you want to avoid this behavior set <code class="highlighter-rouge">JEKYLL_ENV=production</code> to <a href="/docs">force the environment</a> to production.</p> <h3 id="site-base-url">Site Base URL</h3> <p>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: <code class="highlighter-rouge">/blog</code>), then don’t mess with it.</p> <p>In the case of the Minimal Mistakes demo site it’s hosted on GitHub at <a href="/minimal-mistakes">https://mmistakes.github.io/minimal-mistakes</a>. To correctly set this base path I’d use <code class="highlighter-rouge">url: "https://mmistakes.github.io"</code> and <code class="highlighter-rouge">baseurl: "/minimal-mistakes"</code>.</p> <p>For more information on how to properly use <code class="highlighter-rouge">site.url</code> and <code class="highlighter-rouge">site.baseurl</code> as intended by the Jekyll maintainers, check <a href="/blog">Parker Moore’s post on the subject</a>.</p> <p class="notice--warning"><strong>Note:</strong> When using <code class="highlighter-rouge">baseurl</code> remember to include it as part of your path when testing your site locally. Values of <code class="highlighter-rouge">url:</code> and <code class="highlighter-rouge">baseurl: "/blog"</code> would make your local site visible at <code class="highlighter-rouge">http://localhost:4000/blog</code> and not <code class="highlighter-rouge">http://localhost:4000</code>.</p> <h3 id="site-repository">Site Repository</h3> <p>Add your repository name with organization to your site’s configuration file, <code class="highlighter-rouge">_config.yml</code>.</p> <div class="language-yaml highlighter-rouge"> <div class="highlight"> <pre class="highlight"><code><span class="na">repository</span><span class="pi">:</span> <span class="s2">"</span><span class="s">username/repo-name"</span> </code></pre> </div> </div> <p>“NWO” stands for “name with owner.” It is GitHub lingo for the username of the owner of the repository plus a forward slash plus the name of the repository, e.g. <code class="highlighter-rouge">mmistakes/minimal-mistakes</code>, where <strong>mmistakes</strong> is the owner and <strong>minimal-mistakes</strong> is the repository name.</p> <p>Your <code class="highlighter-rouge">site.github.*</code> fields should fill in like normal. If you run Jekyll with the –verbose flag, you should be able to see all the API calls made.</p> <p>If you don’t set <code class="highlighter-rouge">repository</code> correctly you may see the following error when trying to <code class="highlighter-rouge">serve</code> or <code class="highlighter-rouge">build</code> your Jekyll site:</p> <p class="notice--danger"><strong>Liquid Exceptions:</strong> No repo name found. Specify using <code class="highlighter-rouge">PAGES_REPO_NWO</code> environment variables, <code class="highlighter-rouge">repository</code> in your configuration, or set up <code class="highlighter-rouge">origin</code> git remote pointing to your github.com repository.</p> <p>For more information on how <code class="highlighter-rouge">site.github</code> data can be used with Jekyll check out <a href="/jekyll"><code class="highlighter-rouge">github-metadata</code>’s documentation</a>.</p> <h3 id="site-scripts">Site Scripts</h3> <p>Add scripts to the <code class="highlighter-rouge"><head></code> or closing <code class="highlighter-rouge"></body></code> elements by assigning paths to either <code class="highlighter-rouge">head_scripts</code> and/or <code class="highlighter-rouge">footer_scripts</code>.</p> <p>For example, to add a CDN version of jQuery to page’s head along with a custom script you’d do the following:</p> <div class="language-yaml highlighter-rouge"> <div class="highlight"> <pre class="highlight"><code><span class="na">head_scripts</span><span class="pi">:</span> <span class="pi">-</span> <span class="s"><em>Warm Fur 7 Bumud US M Sneaker Shoes Women's B Black Snow Winter Lined Boots Flat</em> https://code.jquery.com/jquery-3.2.1.min.js</span> <span class="pi">-</span> <span class="s">/assets/js/your-custom-head-script.js</span> </code></pre> </div> </div> <p class="notice--info">Consult the for more information on working with theme scripts.</p> <h3 id="site-default-teaser-image">Site Default Teaser Image</h3> <p>To assign a fallback teaser image used in the “<strong>Related Posts</strong>” module, place a graphic in the <code class="highlighter-rouge">/assets/images/</code> directory and add the filename to <code class="highlighter-rouge">_config.yml</code> like so:</p> <div class="language-yaml highlighter-rouge"> <div class="highlight"> <pre class="highlight"><code><span class="na">teaser</span><span class="pi">:</span> <span class="s">/assets/images/500x300.png</span> </code></pre> </div><a href="http://www.dopplegangerchronicles.com/homeBlack_PROPEL_Shoes_Grey_Running_Heelys_Red_Kids_2_0_5w6XYR-sove-15.html" title="Black PROPEL Shoes Grey Running Heelys Red Kids 2 0 5w6XYR">Black PROPEL Shoes Grey Running Heelys Red Kids 2 0 5w6XYR</a> </div> <p>This image can be overridden at anytime by applying the following to a document’s YAML Front Matter.</p> <div class="language-yaml highlighter-rouge"> <div class="highlight"> <pre class="highlight"><code><span class="na">header</span><span class="pi">:</span> <span class="na">teaser</span><span class="pi">:</span> <span class="s">/assets/images/my-awesome-post-teaser.jpg</span> </code></pre> </div> </div> <figure> <figcaption> <big>Boots 7 Bumud US Snow Flat Women's M Warm Sneaker Fur B Black Lined Shoes Winter</big> Example of teaser images found in the related posts module. </figcaption> </figure> <h3 id="breadcrumb-navigation-beta">Breadcrumb Navigation (Beta)</h3> <p>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:</p> <ol> <li>Use a category based permalink structure e.g. <code class="highlighter-rouge">permalink: /:categories/:title/</code></li> <li>Manually create pages for each category or use a plugin like <a href="/jekyll">jekyll-archives</a> to auto-generate them. If these pages don’t exist breadcrumb links to them will be broken.</li> </ol> <p></p> <div class="language-yaml highlighter-rouge"> <div class="highlight"> <pre class="highlight"><code><span class="na">breadcrumbs</span><span class="pi">:</span> <span class="no">true</span> <span class="c1"># disabled by default</span> </code></pre> </div> </div> <p>Breadcrumb start link text and separator character can both be changed in the <a href="/minimal-mistakes/docs/ui-text/">UI Text data file</a>.</p> <h3 id="reading-time">Reading Time</h3> <p>Enable estimated reading time snippets with <code class="highlighter-rouge">read_time: true</code> in YAML Front Matter. <code class="highlighter-rouge">200</code> has been set as the default words per minute value — which can be changed by adjusting <code class="highlighter-rouge">words_per_minute:</code> in <code class="highlighter-rouge">_config.yml</code>.</p> <p></p> <p>Instead of adding <code class="highlighter-rouge">read_time: true</code> to each post, apply as a default in <code class="highlighter-rouge">_config.yml</code> like so:</p> <div class="language-yaml highlighter-rouge"> <div class="highlight"> <pre class="highlight"><code><span class="na">defaults</span><span class="pi">:</span> <span class="c1"># _posts</span> <span class="pi">-</span> <span class="na">scope</span><span class="pi">:</span> <span class="na">path</span><span class="pi">:</span> <span class="s2">"</span><span class="s">"</span> <span class="na">type</span><span class="pi">:</span> <span class="s">posts</span> <span class="na">values</span><span class="pi">:</span> <span class="na">read_time</span><span class="pi">:</span> <span class="no">true</span> </code></pre> </div> </div> <p>To disable reading time for a post, add <code class="highlighter-rouge">read_time: false</code> its YAML Front Matter to override what was set in <code class="highlighter-rouge">_config.yml</code>.</p> <h3 id="comments">Comments</h3> <p><a href="http://www.dopplegangerchronicles.com/homeTAOFFEN_Sandals_Shoes_Court_Block_Women's_White_Heel_rxqtrpSwZ-nqsp-10.html" title="TAOFFEN Sandals Shoes Court Block Women's White Heel rxqtrpSwZ">TAOFFEN Sandals Shoes Court Block Women's White Heel rxqtrpSwZ</a>, <a href="/"><strong>Discourse</strong></a>, <a href="http://www.dopplegangerchronicles.com/homeamp;_Murphy_Arlene_Johnston_Natural_Espadrille_Sandal_Women's_qgdBx8H-lxal-29.html" title="amp; Murphy Arlene Johnston Natural Espadrille Sandal Women's qgdBx8H">amp; Murphy Arlene Johnston Natural Espadrille Sandal Women's qgdBx8H</a>, <strong>Google+</strong>, and static-based commenting via <a href="/"><strong>Staticman</strong></a> are built into the theme. First set the comment provider you’d like to use:</p> <table> <thead> <tr> <th>Name</th> <th>Comment Provider</th> </tr> </thead> <tbody> <tr> <td><strong>disqus</strong></td> <td>Disqus</td> </tr> <tr> <td><strong>discourse</strong></td> <td>Discourse</td> </tr> <tr> <td><strong>facebook</strong></td> <td>Facebook Comments</td> </tr> <tr> <td><strong>google-plus</strong></td> <td>Google+ Comments</td> </tr> <tr> <td><strong>staticman_v2</strong></td> <td>Staticman v2</td> </tr> <tr> <td><strong>staticman</strong></td> <td>Staticman v1 (deprecated)</td> </tr> <tr> <td><strong>custom</strong></td> <td>Other</td> </tr> </tbody> </table> <p>Then add <code class="highlighter-rouge">comments: true</code> to each document you want comments visible on.</p> <p>Instead of adding YAML Front Matter to each document, apply as a default in <code class="highlighter-rouge">_config.yml</code>. To enable comments for all posts:</p> <div class="language-yaml highlighter-rouge"> <div class="highlight"> <pre class="highlight"><code><span class="na">defaults</span><span class="pi">:</span> <span class="c1"># _posts</span> <span class="pi">-</span> <span class="na">scope</span><span class="pi">:</span> <span class="na">path</span><span class="pi">:</span> <span class="s2">"</span><span class="s">"</span> <span class="na">type</span><span class="pi">:</span> <span class="s">posts</span> <span class="na">values</span><span class="pi">:</span> <span class="na">comments</span><span class="pi">:</span> <span class="no">true</span> </code></pre> </div> </div> <p>If you add <code class="highlighter-rouge">comments: false</code> to a post’s YAML Front Matter it will override the default and disable comments for just that post.</p> <p class="notice--info"><strong>Note:</strong> Comments are disabled by default in <code class="highlighter-rouge">development</code>. To enable when testing/building locally be sure to set <code class="highlighter-rouge">JEKYLL_ENV=production</code> to <a href="/docs">force the environment</a> to production.</p> <h4 id="disqus">Disqus</h4> <p>To use Disqus you’ll need to create an account and <a href="/customer">shortname</a>. Once you have both update <code class="highlighter-rouge">_config.yml</code> to:</p> <div class="language-yaml highlighter-rouge"> <div class="highlight"> <pre class="highlight"><code><span class="na">comments</span><span class="pi">:</span> <span class="na">provider</span><span class="pi">:</span> <span class="s2">"</span><span class="s">disqus"</span> <span class="na">disqus</span><span class="pi">:</span> <span class="na">shortname</span><span class="pi">:</span> <span class="s2">"</span><span class="s">your-disqus-shortname"</span> </code></pre> </div> </div> <h4 id="discourse">Discourse</h4> <p>For guidance on how to set up Discourse for embedding comments from a topic on a post page, .</p> <div class="language-yaml highlighter-rouge"> <div class="highlight"> <pre class="highlight"><code><span class="na">comments</span><span class="pi">:</span> <span class="na">provider </span><span class="pi">:</span> <span class="s2">"</span><span class="s">discourse"</span> <span class="na">discourse</span><span class="pi">:</span> <span class="na">server </span><span class="pi">:</span> <span class="c1"># meta.discourse.org</span> </code></pre> </div> </div> <p class="notice--info"><strong>Note:</strong> Do not include <code class="highlighter-rouge">http://</code> or <code class="highlighter-rouge">https://</code> when setting your Discourse <code class="highlighter-rouge">server</code>. The theme automatically prepends the URL <code class="highlighter-rouge">//</code>, following a scheme-less pattern.</p> <h4 id="facebook-comments">Facebook Comments</h4> <p>To enable Facebook Comments choose how many comments you’d like visible per post and the color scheme of the widget.</p> <div class="language-yaml highlighter-rouge"> <div class="highlight"> <pre class="highlight"><code><span class="na">comments</span><span class="pi">:</span> <span class="na">provider </span><span class="pi">:</span> <span class="s2">"</span><span class="s">facebook"</span> <span class="na">facebook</span><span class="pi">:</span> <span class="na">appid </span><span class="pi">:</span> <span class="c1"># optional</span> <span class="na">num_posts </span><span class="pi">:</span> <span class="c1"># 5 (default)</span> <span class="na">colorscheme </span><span class="pi">:</span> <span class="c1"># "light" (default), "dark"</span> </code></pre> </div> </div> <h4 id="static-based-comments-via-staticman">Static-Based Comments via Staticman</h4> <p>Transform user comments into <code class="highlighter-rouge">_data</code> files that live inside of your GitHub repository by enabling Staticman.</p> <p class="notice--info"><strong>Note:</strong> Looking to migrate comments from a WordPress based site? Give <a href="/arthurlacoste">this tool</a> a try.</p> <h5 id="add-staticman-as-a-collaborator">Add Staticman as a Collaborator</h5> <ol> <li>Allow Staticman push access to your GitHub repository by clicking on <strong>Settings</strong>, then the <strong>Collaborators</strong> tab and adding <code class="highlighter-rouge">staticmanapp</code> as a collaborator.</li> <li>To accept the pending invitation visit: <code class="highlighter-rouge">https://api.staticman.net/v2/connect/{your GitHub username}/{your repository name}</code>. Consult the Staticman “<a href="/html">Get Started</a>” guide for more info.</li> </ol> <h5 id="configure-staticman">Configure Staticman</h5> <p><strong>Staticman v2</strong></p> <p>Default settings have been provided in <a href="/yml"><code class="highlighter-rouge">staticman.yml</code></a> and are commented to guide you through setup. View the <a href="/docs">full list of configurations</a>.</p> <div class="language-yaml highlighter-rouge"> <div class="highlight"> <pre class="highlight"><code><span class="c1"># staticman.yml (defaults)</span> <span class="na">comments</span><span class="pi">:</span> <span class="na">allowedFields </span><span class="pi">:</span> <span class="pi">[</span><a href="http://www.dopplegangerchronicles.com/homeRed_Women's_Johnson_Betsey_Bestie_Multi_qOBHwt-ixny-30.html" title="Red Women's Johnson Betsey Bestie Multi qOBHwt">Red Women's Johnson Betsey Bestie Multi qOBHwt</a><span class="s2">"</span><span class="s">name"</span><span class="pi">,</span> <span class="s2">"</span><span class="s">email"</span><span class="pi">,</span> <span class="s2">"</span><span class="s">url"</span><span class="pi">,</span> <span class="s2">"</span><span class="s">message"</span><span class="pi">]</span> <span class="na">branch </span><span class="pi">:</span> <span class="s2">"</span><span class="s">master"</span> <span class="na">commitMessage </span><span class="pi">:</span> <span class="s2">"</span><span class="s">New</span><span class="nv"> </span><span class="s">comment</span><span class="nv"> </span><span class="s">by</span><span class="nv"> </span><span class="s">{fields.name}"</span> <span class="na">filename </span><span class="pi">:</span> <span class="s2">"</span><span class="s">comment-{@timestamp}"</span> <span class="na">format </span><span class="pi">:</span> <span class="s2">"</span><span class="s">yaml"</span> <span class="na">generatedFields</span><span class="pi">:</span> <span class="na">date</span><span class="pi">:</span> <span class="na">type </span><span class="pi">:</span> <span class="s2">"</span><span class="s">date"</span> <span class="na">options</span><span class="pi">:</span> <span class="na">format </span><span class="pi">:</span> <span class="s2">"</span><span class="s">iso8601"</span> <span class="na">moderation </span><span class="pi">:</span> <span class="no">true</span> <span class="na">path </span><span class="pi">:</span> <span class="s2">"</span><span class="s">_data/comments/{options.slug}"</span> <span class="na">requiredFields </span><span class="pi"><em>Women's Lined Snow Boots Flat Black Shoes Sneaker US Bumud Warm B M Winter Fur 7</em> :</span> <span class="pi">[</span><span class="s2">"</span><span class="s">name"</span><span class="pi">,</span> <span class="s2">"</span><span class="s">email"</span><span class="pi">,</span> <span class="s2">"</span><span class="s">message"</span><span class="pi">]</span> <span class="na">transforms</span><span class="pi">:</span> <span class="na">email </span><span class="pi">:</span> <span class="s">md5</span> </code></pre> </div> </div> <p>These settings need to be added to your <code class="highlighter-rouge">_config.yml</code> file as well:</p> <div class="language-yaml highlighter-rouge"> <div class="highlight"> <pre class="highlight"><code><span class="c1"># _config.yml (defaults)</span> <span class="na">repository </span><span class="pi">:</span> <span class="c1"># GitHub username/repo-name e.g. "mmistakes/minimal-mistakes"</span> <span class="na">comments</span><span class="pi">:</span> <span class="na">provider </span><span class="pi">:</span> <span class="s2">"</span><span class="s">staticman_v2"</span> <span class="na">staticman</span><span class="pi">:</span> <span class="na">branch </span><span class="pi">:</span> <span class="s2">"</span><span class="s">master"</span> </code></pre> </div> </div> <p class="notice--info"><strong>Branch setting:</strong> This is the branch comment files will be sent to via pull requests. If you host your site on GitHub Pages it will likely be <code class="highlighter-rouge">master</code> unless your repo is setup as a project — use <code class="highlighter-rouge">gh-pages</code> in that case.</p> <p class="notice--warning"><strong>Note:</strong> Staticman is currently only compatible with GitHub based repositories. <a href="/eduardoboucas">Support for GitLab Pages</a> is planned but not available yet.</p> <p><strong>Staticman v1 (deprecated)</strong></p> <p>Default settings have been provided in <code class="highlighter-rouge">_config.yml</code>. The important ones to set are <code class="highlighter-rouge">provider: "staticman"</code>, <code class="highlighter-rouge">branch</code>, and <code class="highlighter-rouge">path</code>. View the <a href="/docs">full list of configurations</a>.</p> <div class="language-yaml highlighter-rouge"> <div class="highlight"> <pre class="highlight"><code><span class="c1"># _config.yml (defaults)</span> <span class="na">comments</span><span class="pi">:</span> <span class="na">provider</span><span class="pi">:</span> <span class="s2">"</span><span class="s">staticman"</span> <span class="na">staticman</span><span class="pi">:</span> <span class="na">allowedFields </span><span class="pi">:</span> <span class="pi">[</span><span class="s1">'</span><span class="s">name'</span><span class="pi">,</span> <span class="s1">'</span><span class="s">email'</span><span class="pi">,</span> <span class="s1">'</span><span class="s">url'</span><span class="pi">,</span> <span class="s1">'</span><span class="s">message'</span><span class="pi">]</span> <span class="na">branch </span><span class="pi">:</span> <span class="s2">"</span><span class="s">master"</span> <span class="na">commitMessage </span><span class="pi">:</span> <span class="s2">"</span><span class="s">New</span><span class="nv"> </span><span class="s">comment</span><span class="nv"> </span><span class="s">by</span><span class="nv"> </span><span class="s">{fields.name}"</span> <span class="na">filename </span><span class="pi">:</span> <span class="s">comment-{@timestamp}</span> <span class="na">format </span><span class="pi">:</span> <span class="s2">"</span><span class="s">yml"</span> <span class="na">moderation </span><span class="pi">:</span> <span class="no">true</span> <span class="na">path </span><span class="pi">:</span> <span class="s2">"</span><span class="s">_data/comments/{options.slug}"</span> <span class="na">requiredFields </span><span class="pi">:</span> <span class="pi">[</span><span class="s1">'</span><span class="s">name'</span><span class="pi">,</span> <span class="s1">'</span><span class="s">email'</span><span class="pi">,</span> <span class="s1">'</span><span class="s">message'</span><span class="pi">]</span> <span class="na">transforms</span><span class="pi">:</span> <span class="na">email </span><span class="pi">:</span> <span class="s2">"</span><span class="s">md5"</span> <span class="na">generatedFields</span><span class="pi">:</span><a href="http://www.dopplegangerchronicles.com/homeWomen's_Pebble_Polyurethane_Red_Ram_Sandal_Rampage_Janda_Heeled_7xY0q8HYgd-ruxr-19.html" title="Women's Pebble Polyurethane Red Ram Sandal Rampage Janda Heeled 7xY0q8HYgd">Women's Pebble Polyurethane Red Ram Sandal Rampage Janda Heeled 7xY0q8HYgd</a> <span class="na">date</span><span class="pi">:</span> <span class="na">type </span><span class="pi">:</span> <span class="s2">"</span><span class="s">date"</span> <span class="na">options</span><span class="pi">:</span> <span class="na">format </span><span class="pi">:</span> <span class="s2">"</span><span class="s">iso8601"</span> <span class="c1"># "iso8601" (default), "timestamp-seconds", "timestamp-milliseconds"</span> </code></pre> </div> </div> <h5 id="comment-moderation">Comment Moderation</h5> <p>By default comment moderation is enabled in <code class="highlighter-rouge">staticman.yml</code>. As new comments are submitted Staticman will send a pull request. Merging these in will approve the comment, close the issue, and automatically rebuild your site (if hosted on GitHub Pages).</p> <p>To skip this moderation step simply set <code class="highlighter-rouge">moderation: false</code>.</p> <p class="notice--info"><strong>ProTip:</strong><a href="http://www.dopplegangerchronicles.com/home1XZ222_Prada_Women's_F0A48_4OX_Sandals_Leather_A5cx5qCwrH-ithk-11.html" title="1XZ222 Prada Women's F0A48 4OX Sandals Leather A5cx5qCwrH">1XZ222 Prada Women's F0A48 4OX Sandals Leather A5cx5qCwrH</a> Create a GitHub webhook that sends a <code class="highlighter-rouge">POST</code> request to the following payload URL <code class="highlighter-rouge">https://api.staticman.net/v2/webhook</code> and triggers a “Pull request” event to delete Staticman branches on merge.</p> <p></p> <h5 id="recaptcha-support-v2-only">reCAPTCHA Support (v2 only)</h5> <p>To enable Google’s reCAPTCHA to aid in spam detection you’ll need to:</p> <ol> <li>Apply for <a href="/recaptcha">reCAPTCHA API</a> keys and register your site using the reCAPTCHA V2 type.</li> <li>Add your site and secret keys to <code class="highlighter-rouge">staticman.yml</code> and <code class="highlighter-rouge">_config.yml</code>. Be sure to properly encrypt your secret key using <a href="/docs">Staticman’s encrypt endpoint</a>.</li> </ol> <div class="language-yaml highlighter-rouge"> <div class="highlight"> <pre class="highlight"><code><span class="na">reCaptcha</span><span class="pi">:</span> <span class="na">enabled</span><span class="pi">:</span> <span class="no">true</span> <span class="na">siteKey</span><span class="pi">:</span> <span class="c1"># "6LdRBykTAAAAAFB46MnIu6ixuxwu9W1ihFF8G60Q"</span> <span class="na">secret</span><span class="pi">:</span> <span class="c1"># "PznnZGu3P6eTHRPLORniSq+J61YEf+A9zmColXDM5icqF49gbunH51B8+h+i2IvewpuxtA9TFoK68TuhUp/X3YKmmqhXasegHYabY50fqF9nJh9npWNhvITdkQHeaOqnFXUIwxfiEeUt49Yoa2waRR7a5LdRAP3SVM8hz0KIBT4="</span> </code></pre> </div> </div> <h4 id="other-comment-providers">Other Comment Providers</h4> <p>To use another provider not included with the theme set <code class="highlighter-rouge">provider: "custom"</code> then add their embed code to <code class="highlighter-rouge">_includes/comments-providers/custom.html</code>.</p> <h3 id="custom-feed-url">Custom Feed URL</h3> <p>By default the theme links to <code class="highlighter-rouge">feed.xml</code> generated in the root of your site by the <strong>jekyll-feed</strong> plugin. To link to an externally hosted feed update <code class="highlighter-rouge">atom_feed</code> in <code class="highlighter-rouge">_config.yml</code> like so:</p><a href="http://www.dopplegangerchronicles.com/homeTropical_up_Zebra_Shoes_Lace_Canvas_Ankle_U_Top_Design_Sneakers_Floral_High_FOR_Women_DESIGNS_ZwP0aqcH-xrpbf-43.html" title="Tropical up Zebra Shoes Lace Canvas Ankle U Top Design Sneakers Floral High FOR Women DESIGNS ZwP0aqcH">Tropical up Zebra Shoes Lace Canvas Ankle U Top Design Sneakers Floral High FOR Women DESIGNS ZwP0aqcH</a> <div class="language-yaml highlighter-rouge"> <div class="highlight"> <pre class="highlight"><code><span class="na">atom_feed</span><span class="pi">:</span> <span class="na">path</span><span class="pi">:</span> <span class="s2">"</span><span class="s">http://feeds.feedburner.com/youFeedname"</span> </code></pre> </div> </div> <p class="notice--info"><strong>Note:</strong> By default the site feed is linked in two locations: inside the <a href="/html"><code class="highlighter-rouge"><head></code> element</a> and at the bottom of every page in the <a href="/html">site footer</a>.</p> <h3 id="site-search">Site Search</h3> <p>To enable site-wide search add <code class="highlighter-rouge">search: true</code> to your <code class="highlighter-rouge">_config.yml</code>.</p> <p></p> <h4 id="lunr-default">Lunr (default)</h4> <p>The default search uses <a href="/"><strong>Lunr</strong></a> to build a search index of all your documents. This method is 100% compatible with sites hosted on GitHub Pages.</p> <p class="notice--warning"><strong>Note:</strong> Only the first 50 words of a post or page’s body content is added to the Lunr search index. Setting <code class="highlighter-rouge">search_full_content</code> to <code class="highlighter-rouge">true</code> in your <code class="highlighter-rouge">_config.yml</code><a href="http://www.dopplegangerchronicles.com/homeNappa_Up_Oxford_Comfort_Finn_Men's_Lace_Vaasa_White_70Ixpqw-esdad-21.html" title="Nappa Up Oxford Comfort Finn Men's Lace Vaasa White 70Ixpqw">Nappa Up Oxford Comfort Finn Men's Lace Vaasa White 70Ixpqw</a> will override this and could impact page load performance.</p> <h4 id="algolia">Algolia</h4> <p>For faster and more relevant search (<a href="/minimal-mistakes-algolia-search">see demo</a>):</p> <ol> <li> <p>Add the <a href="/algolia"><code class="highlighter-rouge">jekyll-algolia</code></a> gem to your <code class="highlighter-rouge">Gemfile</code>, in the <code class="highlighter-rouge">:jekyll_plugins</code> section.</p> <div class="language-ruby highlighter-rouge"> <div class="highlight"> <pre class="highlight"><code><span class="n">group</span> <span class="ss">:jekyll_plugins</span> <span class="k">do</span> <span class="n">gem</span> <span class="s2">"jekyll-feed"</span> <span class="n">gem</span> <span class="s2">"jekyll-seo-tag"</span> <span class="n">gem</span> <span class="s2">"jekyll-sitemap"</span> <span class="n">gem</span> <span class="s2">"jekyll-paginate"</span> <span class="n">gem</span> <span class="s2">"jekyll-algolia"</span> <span class="k">end</span> </code></pre> </div> </div> <p>Once this is done, download all dependencies by running <code class="highlighter-rouge">bundle install</code>.</p> </li> <li> <p>Switch search providers from <code class="highlighter-rouge">lunr</code> to <code class="highlighter-rouge">algolia</code> in your <code class="highlighter-rouge">_config.yml</code> file:</p> <div class="language-yaml highlighter-rouge"> <div class="highlight"> <pre class="highlight"><code><span class="na">search_provider</span><span class="pi">:</span> <span class="s">algolia</span> </code></pre> </div> </div> </li> <li> <p>Add the following Algolia credentials to your <code class="highlighter-rouge">_config.yml</code> file. <em>If you don’t have an Algolia account, you can open a free <a href="/users">Community plan</a>. Once signed in, you can grab your credentials from <a href="/licensing">your dashboard</a>.</em></p> <div class="language-yaml highlighter-rouge"> <div class="highlight"> <pre class="highlight"><code><span class="na">algolia</span><span class="pi">:</span> <span class="na">application_id</span><span class="pi">:</span> <span class="c1"># YOUR_APPLICATION_ID</span> <span class="na">index_name</span><span class="pi">:</span> <span class="c1"># YOUR_INDEX_NAME</span> <span class="na">search_only_api_key</span><span class="pi">:</span> <span class="c1"># YOUR_SEARCH_ONLY_API_KEY</span> <span class="na">powered_by</span><span class="pi">:</span> <span class="c1"># true (default), false</span> </code></pre> </div> </div> </li> <li> <p>Once your credentials are setup, you can run the indexing with the following command:</p> <div class="highlighter-rouge"> <div class="highlight"> <pre class="highlight"><code>ALGOLIA_API_KEY=your_admin_api_key bundle exec jekyll algolia </code></pre> </div> </div> <p>For Windows users you will have to use <code class="highlighter-rouge">set</code> to assigned the <code class="highlighter-rouge">ALGOLIA_API_KEY</code> environment variable.</p> <div class="highlighter-rouge"> <div class="highlight"> <pre class="highlight"><code>set ALGOLIA_API_KEY=your_admin_api_key bundle exec jekyll algolia </code></pre> </div> </div> <p>Note that <code class="highlighter-rouge">ALGOLIA_API_KEY</code> should be set to your admin API key.</p> </li> </ol> <p>To use the Algolia search with GitHub Pages hosted sites follow <a href="/html">this deployment guide</a>. Or this guide for <a href="/html">deploying on Netlify</a>.</p> <p class="notice--info"><strong>Note:</strong> The Jekyll Algolia plugin can be configured in several ways. Be sure to check out <a href="/html" title="Algolia configuration">their full documentation</a> on how to exclude files and other valuable settings.</p> <h4 id="google-custom-search-engine"><big>Sneaker Boots 7 Shoes M Fur B Lined Women's Bumud Snow Flat Warm Black US Winter</big> Google Custom Search Engine</h4> <p>Add a Google search box to your site.</p> <ol> <li> <p>Create a <strong>New search engine</strong> in <a href="/cse">Google Custom Search Engine</a>, give it an appropriate name and setup “Sites to search” to your liking.</p> </li> <li> <p>Under <strong>Look and feel</strong> choose the “Results only” layout and a theme (<em>Minimalist</em> is a good choice to match the default look of the Minimal Mistakes).</p> <p></p> </li> <li> <p>Select “Save & Get Code” and grab your search engine ID from the line that begins with <code class="highlighter-rouge">var cx = 'YOUR_SEARCH_ENGINE_ID'</code>.</p> </li> <li> <p>Add your search engine ID to <code class="highlighter-rouge">_config.yml</code> like so:</p> <div class="language-yaml highlighter-rouge"> <div class="highlight"> <pre class="highlight"><code><span class="na">google</span><span class="pi">:</span> <span class="na">search_engine_id</span><span class="pi">:</span> <span class="s">YOUR_SEARCH_ENGINE_ID</span> </code></pre> </div> </div> </li> </ol> <p class="notice--info"><strong>Note:</strong> If your site is new and hasn’t been indexed by Google yet, search will be incomplete and won’t provide accurate results.</p> <h3 id="seo-social-sharing-and-analytics-settings">SEO, Social Sharing, and Analytics Settings</h3> <p>All optional, but a good idea to take the time setting up to improve SEO and links shared from the site.</p> <h4 id="google-search-console">Google Search Console</h4> <p>Formerly known as <a href="/webmasters">Google Webmaster Tools</a>, add your <a href="/analytics">verification code</a> like so: <code class="highlighter-rouge">google_site_verification: "yourVerificationCode"</code>.</p> <p class="notice--warning"><strong>Note:</strong> You likely won’t have to do this if you verify site ownership through <strong>Google Analytics</strong> instead.</p> <h4 id="bing-webmaster-tools">Bing Webmaster Tools</h4> <p>There are several ways to <a href="http://www.dopplegangerchronicles.com/homeSoft_Women's_Color_WeenFashion_Material_Heels_Wedges_Open_Sandals_Pink_Zipper_Assorted_Toe_Low_wACqCT5n-qurxd-0.html" title="Soft Women's Color WeenFashion Material Heels Wedges Open Sandals Pink Zipper Assorted Toe Low wACqCT5n">Soft Women's Color WeenFashion Material Heels Wedges Open Sandals Pink Zipper Assorted Toe Low wACqCT5n</a> — the easiest adding an authentication code to your config file.</p> <p>Copy and paste the string inside of <code class="highlighter-rouge">content</code>:</p> <div class="language-html highlighter-rouge"> <div class="highlight"> <pre class="highlight"><code><span class="nt"><meta</span> <span class="na">name=</span><span class="s">"msvalidate.01"</span> <span class="na">content=</span><span class="s">"0FC3FD70512616B052E755A56F8952D"</span> <span class="nt"><em>B Women's Bumud Black Fur Winter Sneaker Shoes Flat Lined Boots Snow Warm 7 M US</em> /></span> </code></pre> </div> </div> <p>Into <code class="highlighter-rouge">_config.yml</code></p> <div class="language-yaml highlighter-rouge"> <div class="highlight"> <pre class="highlight"><code><span class="na">bing_site_verification</span><span class="pi">:</span> <span class="s2">"</span><span class="s">0FC3FD70512616B052E755A56F8952D"</span> </code></pre> </div> </div> <h4 id="naver-webmaster-tools"><b>B Sneaker M Fur Flat Boots Bumud Snow 7 Women's Shoes Winter Warm Black US Lined</b> Naver Webmaster Tools</h4> <p>To verify site ownership you will need to <a href="/nhn?lang=en_us&m=init">create a Naver account</a> and then <strong>Add your site</strong> via <a href="/">Naver Webmaster Tools</a>.</p> <p>Much like Google and Bing you’ll be provided with a meta description:</p> <div class="language-html highlighter-rouge"> <div class="highlight"> <pre class="highlight"><code><span class="nt"><meta</span> <span class="na">name=</span><span class="s">"naver-site-verification"</span> <span class="na">content=</span><span class="s">"6BF5A01C0E650B479B612AC5A2184144"</span><span class="nt">></span>` </code></pre> </div> </div> <p>Which you can add to your <code class="highlighter-rouge">_config.yml</code> like so:</p> <div class="language-yaml highlighter-rouge"> <div class="highlight"> <pre class="highlight"><code><span class="na">naver_site_verification</span><span class="pi">:</span> <span class="s2">"</span><span class="s">6BF5A01C0E650B479B612AC5A2184144"</span> </code></pre> </div> </div> <h4 id="yandex">Yandex</h4> <p>To verify site ownership copy and paste the string inside of <code class="highlighter-rouge">content</code>:</p> <div class="language-html highlighter-rouge"> <div class="highlight"> <pre class="highlight"><code><span class="nt"><meta</span> <span class="na">name=</span><span class="s">'yandex-verification'</span> <span class="na">content=</span><span class="s">'2132801JL'</span> <span class="nt">/></span> </code></pre> </div> </div> <p>Into <code class="highlighter-rouge">_config.yml</code></p> <div class="language-yaml highlighter-rouge"> <div class="highlight"> <pre class="highlight"><code><span class="na">yandex_site_verification</span><span class="pi">:</span> <span class="s2">"</span><span class="s">2132801JL"</span> </code></pre> </div> </div> <h4 id="twitter-cards-and-facebook-open-graph">Twitter Cards and Facebook Open Graph</h4> <p>To improve the appearance of links shared from your site to social networks like Twitter and Facebook be sure to configure the following.</p> <h5 id="site-twitter-username">Site Twitter Username</h5> <p>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 <strong>creator</strong> in the Twitter Card.</p> <p>For example if my site’s Twitter account is <code class="highlighter-rouge">@mmistakes-theme</code> I would add the following to <code class="highlighter-rouge">_config.yml</code></p> <div class="language-yaml highlighter-rouge"> <div class="highlight"> <pre class="highlight"><code><span class="na">twitter</span><span class="pi">:</span> <span class="na">username</span><span class="pi">:</span> <span class="s2">"</span><span class="s">mmistakes-theme"</span> </code></pre> </div> </div> <p>And if I assign <code class="highlighter-rouge">@mmistakes</code> as an author account it will appear in the Twitter Card along with <code class="highlighter-rouge">@mmistakes-theme</code>, attributed as a creator of the page being shared.</p> <p class="notice--warning"><strong>Note</strong>: You need to <a href="/docs">apply for Twitter Cards</a> and validate they’re working on your site before they will begin showing up.</p> <h5 id="facebook-open-graph">Facebook Open Graph</h5> <p>If you have a Facebook ID or publisher page add them:</p> <div class="language-yaml highlighter-rouge"> <div class="highlight"> <pre class="highlight"><code><span class="na">facebook</span><span class="pi">:</span> <span class="na">app_id</span><span class="pi">:</span> <span class="c1"># A Facebook app ID</span> <span class="na">publisher</span><span class="pi">:</span> <span class="c1"># A Facebook page URL or ID of the publishing entity</span> </code></pre> </div> </div> <p>While not part a part of Open Graph, you can also add your Facebook username for use in the sidebar and footer.</p> <div class="language-yaml highlighter-rouge"> <div class="highlight"> <pre class="highlight"><code><span class="na">facebook</span><span class="pi">:</span> <span class="na">username</span><span class="pi">:</span> <span class="s2">"</span><span class="s">michaelrose"</span> <span class="c1"># https://www.facebook.com/michaelrose</span> </code></pre> </div> </div> <p class="notice--info"><strong>ProTip:</strong> To debug Open Graph data use <a href="/com">this tool</a> to test your pages. If content changes aren’t reflected you will probably have to hit the <strong>Fetch new scrape information</strong> button to refresh.</p> <h5 id="open-graph-default-image">Open Graph Default Image</h5> <p>For pages that don’t have a <code class="highlighter-rouge">header.image</code> assigned in their YAML Front Matter, <code class="highlighter-rouge">site.og_image</code> will be used as a fallback. Use your logo, icon, avatar or something else that is meaningful. Just make sure it is place in the <code class="highlighter-rouge">/assets/images/</code> folder, a minimum size of 120px by 120px, and less than 1MB in file size.</p> <div class="language-yaml highlighter-rouge"> <div class="highlight"> <pre class="highlight"><code><span class="na">og_image</span><span class="pi">:</span> <span class="s">/assets/images/site-logo.png</span> </code></pre> </div> </div> <figure> <figcaption> Example of a image placed in a Summary Card. </figcaption> </figure> <p>Documents who have a <code class="highlighter-rouge">header.image</code> assigned in their YAML Front Matter will appear like this when shared on Twitter and Facebook.</p> <figure> <figcaption> Shared page on Twitter with header image assigned. </figcaption> </figure> <figure> <figcaption> Shared page on Facebook with header image assigned. </figcaption> </figure> <h5 id="include-your-social-profile-in-search-results">Include your social profile in search results</h5> <p>Use markup on your official website to add your <a href="/structured-data">social profile information</a> to the Google Knowledge panel in some searches. Knowledge panels can prominently display your social profile information.</p> <div class="language-yaml highlighter-rouge"> <div class="highlight"> <pre class="highlight"><code><span class="na">social</span><span class="pi">:</span> <span class="na">type</span><span class="pi">:</span> <span class="c1"># Person or Organization (defaults to Person)</span> <span class="na">name</span><span class="pi">:</span> <span class="c1"># If the user or organization name differs from the site's name</span> <span class="na">links</span><span class="pi">:</span> <span class="pi">-</span> <span class="s2">"</span><span class="s"><strong>Winter Shoes Black Women's Flat US B 7 M Warm Sneaker Lined Bumud Fur Snow Boots</strong> https://twitter.com/yourTwitter"</span> <span class="pi">-</span> <span class="s2">"</span><span class="s">https://facebook.com/yourFacebook"</span> <span class="pi">-</span> <span class="s2">"</span><span class="s">https://instagram.com/yourProfile"</span> <span class="pi">-</span> <span class="s2">"</span><span class="s">https://www.linkedin.com/in/yourprofile"</span> <span class="pi">-</span> <span class="s2">"</span><span class="s">https://plus.google.com/your_profile"</span> </code></pre> </div> </div> <h4 id="analytics">Analytics</h4> <p>Analytics is disabled by default. To enable globally select one of the following:</p> <table> <thead> <tr> <th>Name</th> <th>Analytics Provider</th> </tr> </thead> <tbody> <tr> <td><strong>google</strong></td> <td><a href="/analytics">Google Standard Analytics</a></td> </tr> <tr> <td><strong>google-universal</strong></td> <td><a href="/analytics">Google Universal Analytics</a></td> </tr> <tr> <td><strong>google-gtag</strong></td> <td><a href="/analytics">Google Analytics Global Site Tag)</a></td> </tr> <tr> <td><strong>custom</strong></td> <td>Other analytics providers</td> </tr> </tbody> </table> <p>For Google Analytics add your Tracking Code:</p> <div class="language-yaml highlighter-rouge"> <div class="highlight"> <pre class="highlight"><code><span class="na"><b>Women's Shoes Sneaker Fur US 7 Black Bumud Snow Boots M B Winter Flat Warm Lined</b> analytics</span><span class="pi">:</span> <span class="na">provider</span><span class="pi">:</span> <span class="s2">"</span><span class="s">google-gtag"</span> <span class="na">google</span><span class="pi">:</span> <span class="na">tracking_id</span><span class="pi">:</span> <span class="s2">"</span><span class="s">UA-1234567-8"</span> <span class="na">anonymize_ip</span><span class="pi">:</span> <span class="no">false</span> <span class="c1"># default</span> </code></pre> </div> </div> <p>To use another provider not included with the theme set <code class="highlighter-rouge">provider: "custom"</code> then add their embed code to <code class="highlighter-rouge">_includes/analytics-providers/custom.html</code>.</p> <p class="notice--info"><strong>Note:</strong> Analytics are disabled by default in <code class="highlighter-rouge">development</code>. To enable when testing/building locally be sure to set <code class="highlighter-rouge">JEKYLL_ENV=production</code> to <a href="/docs">force the environment</a> to production.</p> <h2 id="site-author">Site Author</h2> <p>Used as the defaults for defining what appears in the author sidebar.</p> <p></p> <p class="notice--info"><strong>Note:</strong> 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.</p> <div class="language-yaml highlighter-rouge"> <div class="highlight"> <pre class="highlight"><code><span class="na">author</span><span class="pi">:</span> <span class="na">name </span><span class="pi">:</span> <span class="s2">"</span><span class="s">Your</span><span class="nv"> </span><span class="s">Name"</span> <span class="na">avatar </span><span class="pi">:</span> <span class="s2">"</span><span class="s">/assets/images/bio-photo.jpg"</span> <span class="na">bio </span><span class="pi">:</span> <span class="s2">"</span><span class="s">My</span><span class="nv"> </span><span class="s">awesome</span><span class="nv"> </span><span class="s">biography</span><span class="nv"> </span><span class="s">constrained</span><span class="nv"> </span><span class="s">to</span><span class="nv"> </span><span class="s">a</span><span class="nv"> </span><span class="s">sentence</span><span class="nv"> </span><span class="s">or</span><span class="nv"> </span><span class="s">two</span><span class="nv"> </span><span class="s">goes</span><span class="nv"> </span><span class="s">here."</span> <span class="na">email </span><span class="pi">:</span> <span class="c1"># optional</span> <span class="na">uri </span><span class="pi">:</span> <span class="s2">"</span><span class="s">http://your-site.com"</span> <span class="na">home </span><span class="pi">:</span> <span class="c1"># null (default), "absolute or relative url to link to author home"</span> </code></pre> </div> </div> <p>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 <code class="highlighter-rouge">_includes/author-profile.html</code> to see how the URL is constructed.</p> <p>To add social media links not included with the theme or customize the author sidebar further, read the full <a href="/minimal-mistakes/docs/layouts/#author-profile">layout documentation</a>.</p> <h2 id="reading-files">Reading Files</h2> <p>Nothing out of the ordinary here. <code class="highlighter-rouge">include</code> and <code class="highlighter-rouge">exclude</code> may be the only things you need to alter.</p> <h2 id="conversion-and-markdown-processing">Conversion and Markdown Processing</h2> <p>Again nothing out of the ordinary here as the theme adheres to the defaults used by GitHub Pages. <a href="/"><strong>Kramdown</strong></a> for Markdown conversion, <a href="/"><strong>Rouge</strong></a> syntax highlighting, and incremental building disabled. Change them if you need to.</p> <h2 id="front-matter-defaults">Front Matter Defaults</h2> <p>To save yourself time setting <a href="/docs">Front Matter Defaults</a> for posts, pages, and collections is the way to go. Sure you can assign layouts and toggle settings like <strong>reading time</strong>, <strong>comments</strong>, and <strong>social sharing</strong> in each file, but that’s not ideal.</p> <p>Using the <code class="highlighter-rouge">default</code> key in <code class="highlighter-rouge">_config.yml</code> you could set the layout and enable author profiles, reading time, comments, social sharing, and related posts for all posts — in one shot.</p> <div class="language-yaml highlighter-rouge"> <div class="highlight"> <pre class="highlight"><code><span class="na">defaults</span><span class="pi">:</span> <span class="c1"># _posts</span> <span class="pi">-</span> <span class="na">scope</span><span class="pi">:</span> <span class="na">path</span><span class="pi">:</span> <span class="s2">"</span><span class="s">"</span> <span class="na">type</span><span class="pi">:</span> <span class="s">posts</span> <span class="na">values</span><span class="pi">:</span> <span class="na">layout</span><span class="pi">:</span> <span class="s">single</span> <span class="na">author_profile</span><span class="pi">:</span> <span class="no">true</span> <span class="na">read_time</span><span class="pi">:</span> <span class="no">true</span> <span class="na">comments</span><span class="pi">:</span> <span class="no">true</span> <span class="na">share</span><span class="pi">:</span> <span class="no">true</span> <span class="na">related</span><span class="pi">:</span> <span class="no">true</span> </code></pre> </div> </div> <p>Pages Front Matter defaults can be scoped like this:</p> <div class="language-yaml highlighter-rouge"> <div class="highlight"> <pre class="highlight"><code><span class="na">defaults</span><span class="pi">:</span> <span class="c1"># _pages</span> <span class="pi">-</span> <span class="na">scope</span><span class="pi">:</span> <span class="na">path</span><span class="pi">:</span> <span class="s2">"</span><span class="s">"</span> <span class="na">type</span><span class="pi">:</span> <span class="s">pages</span> <span class="na">values</span><span class="pi">:</span> <span class="na">layout</span><span class="pi">:</span> <span class="s">single</span> </code></pre> </div> </div> <p>And collections like this:</p> <div class="language-yaml highlighter-rouge"> <div class="highlight"> <pre class="highlight"><code><span class="na">defaults</span><span class="pi">:</span> <span class="c1"># _foo</span> <span class="pi">-</span> <span class="na">scope</span><span class="pi">:</span> <span class="na">path</span><span class="pi">:</span> <span class="s2">"</span><span class="s">"</span> <span class="na">type</span><span class="pi">:</span> <span class="s">foo</span> <span class="na">values</span><span class="pi">:</span> <span class="na">layout</span><span class="pi">:</span> <span class="s">single</span> </code></pre> </div> </div> <p>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 <a href="http://www.dopplegangerchronicles.com/homeM_US_Low_Out_WHITE_8_All_BLACK_Zoom_Nike_VOLT_Men's_w6qWzxZacR-vzzvg-16.html" title="M US Low Out WHITE 8 All BLACK Zoom Nike VOLT Men's w6qWzxZacR">M US Low Out WHITE 8 All BLACK Zoom Nike VOLT Men's w6qWzxZacR</a>.</p> <h2 id="outputting">Outputting</h2> <p>The default permalink style used by the theme is <code class="highlighter-rouge">permalink: /:categories/:title/</code>. If you have a post named <code class="highlighter-rouge">2016-01-01-my-post.md</code> with <code class="highlighter-rouge">categories: foo</code> in the YAML Front Matter, Jekyll will generate <code class="highlighter-rouge">_site/foo/my-post/index.html</code>.</p> <p class="notice--warning"><strong>Note:</strong> If you plan on enabling breadcrumb links — including category names in permalinks is a big part of how those are created.</p> <h3 id="paginate">Paginate</h3> <p>If <a href="/jekyll">using pagination</a> on the homepage you can change the amount of posts shown with:</p> <div class="language-yaml highlighter-rouge"> <div class="highlight"> <pre class="highlight"><code><span class="na">paginate</span><span class="pi">:</span> <span class="s">5</span> </code></pre> </div> </div> <p>You’ll also need to include some Liquid and HTML to properly use the paginator, which you can find in the <strong>Layouts</strong> section under <a href="/minimal-mistakes/docs/layouts/#home-page">Home Page</a>.</p> <p>The paginator only works on files with name <code class="highlighter-rouge">index.html</code>. To use pagination in a subfolder — for example <code class="highlighter-rouge">/recent/</code>, create <code class="highlighter-rouge">/recent/index.html</code> and set the <code class="highlighter-rouge">paginate_path</code> in <code class="highlighter-rouge">_config.yml</code> to this:</p> <div class="language-yaml highlighter-rouge"> <div class="highlight"> <pre class="highlight"><code><span class="na">paginate_path</span><span class="pi">:</span> <span class="s">/recent/page:num/</span> </code></pre> </div> </div> <p class="notice--info"><strong>Please note:</strong> When using Jekyll’s default <a href="/docs">pagination plugin</a> <code class="highlighter-rouge">paginator.posts</code> can only be called once. If you’re looking for something more powerful that can paginate category, tag, and collection pages I suggest <a href="/sverrirs"><strong>jekyll-paginate-v2</strong></a>.</p> <h3 id="timezone">Timezone</h3> <p>This sets the timezone environment variable, which Ruby uses to handle time and date creation and manipulation. Any entry from the <a href="http://www.dopplegangerchronicles.com/homeBlack_White_Flyknit_Black_Low_W_Women's_Lunarepic_US_Nike_6_Racer_Blue_2_M_fSwxq80IS6-llxvu-19.html" title="Black White Flyknit Black Low W Women's Lunarepic US Nike 6 Racer Blue 2 M fSwxq80IS6">Black White Flyknit Black Low W Women's Lunarepic US Nike 6 Racer Blue 2 M fSwxq80IS6</a> is valid. The default is the local time zone, as set by your operating system.</p> <div class="language-yaml highlighter-rouge"> <div class="highlight"> <pre class="highlight"><code><span class="na">timezone</span><span class="pi">:</span> <span class="s">America/New_York</span> </code></pre> </div> </div> <h2 id="plugins">Plugins</h2> <p>When hosting with GitHub Pages a small <a href="/versions">set of gems</a> have been whitelisted for use. The theme uses a few of them which can be found under <code class="highlighter-rouge">gems</code>. Additional settings and configurations are documented in the links below.</p> <table> <thead> <tr> <th>Plugin</th> <th>Description</th> </tr> </thead> <tbody> <tr> <td><a href="/jekyll">jekyll-paginate</a></td> <td>Pagination Generator for Jekyll.</td> </tr> <tr> <td><a href="/jekyll">jekyll-sitemap</a></td> <td>Jekyll plugin to silently generate a sitemaps.org compliant sitemap for your Jekyll site.</td> </tr> <tr> <td><a href="/jekyll">jekyll-gist</a></td> <td>Liquid tag for displaying GitHub Gists in Jekyll sites.</td> </tr> <tr> <td><a href="/jekyll">jekyll-feed</a></td> <td>A Jekyll plugin to generate an Atom (RSS-like) feed of your Jekyll posts.</td> </tr> <tr> <td><a href="/jekyll">jemoji</a></td> <td>GitHub-flavored emoji plugin for Jekyll.</td> </tr> </tbody> </table> <p>If you’re hosting elsewhere then you don’t really have to worry about what is whitelisted as you are free to include whatever <a href="/docs">Jekyll plugins</a> you desire.</p> <h2 id="archive-settings">Archive Settings</h2> <p>The theme ships with support for taxonomy (category and tag) pages. GitHub Pages hosted sites need to use a <em>Liquid only</em> approach while those hosted elsewhere can use plugins like <a href="/jekyll"><strong>jekyll-archives</strong></a> to generate these pages automatically.</p> <p>The default <code class="highlighter-rouge">type</code> is set to use Liquid.</p> <p class="notice--danger"><strong>Note:</strong> <code class="highlighter-rouge">category_archive</code> and <code class="highlighter-rouge">tag_archive</code> were previously named <code class="highlighter-rouge">categories</code> and <code class="highlighter-rouge">tags</code>. Names were changed to avoid possible conflicts with <code class="highlighter-rouge">site.categories</code> and <code class="highlighter-rouge">site.tags</code>.</p> <div class="language-yaml highlighter-rouge"> <div class="highlight"> <pre class="highlight"><code><span class="na">category_archive</span><span class="pi">:</span> <span class="na">type</span><span class="pi">:</span> <span class="s">liquid</span> <span class="na">path</span><span class="pi">:</span> <span class="s">/categories/</span> <span class="na"><big>Flat Snow Bumud Sneaker Lined Winter Warm B Boots US Black M Fur Shoes 7 Women's</big> tag_archive</span><span class="pi">:</span> <span class="na">type</span><span class="pi">:</span> <span class="s">liquid</span> <span class="na">path</span><span class="pi">:</span> <span class="s">/tags/</span> </code></pre> </div> </div> <p>Which would create category and tag links in the breadcrumbs and page meta like: <code class="highlighter-rouge">/categories/#foo</code> and <code class="highlighter-rouge">/tags/#foo</code>.</p> <p class="notice--warning"><strong>Note:</strong> these are simply hash (fragment) links into the full taxonomy index pages. For them to resolve properly, the category and tag index pages need to exist at <a href="/md"><code class="highlighter-rouge">/categories/index.html</code></a> (copy to <code class="highlighter-rouge">_pages/category-archive.md</code>) and <a href="/md"><code class="highlighter-rouge">/tags/index.html</code></a> (copy to <code class="highlighter-rouge">_pages/tag-archive.md</code>).</p> <p>If you have the luxury of using Jekyll Plugins, then <a href="/jekyll"><strong>jekyll-archives</strong></a> will create a better experience as discrete taxonomy pages would be generated, and their corresponding links would be “real” (not just hash/fragment links into a larger index). However, the plugin will not generate the taxonomy index pages (<code class="highlighter-rouge">category-archive.md</code> and <code class="highlighter-rouge">tag-archive.md</code>) so you’d still need to manually create them if you’d like to have them (see note above).</p> <p>First, you’ll need to make sure that the <code class="highlighter-rouge"><b>Sneaker Boots 7 US Women's Bumud Fur Snow Flat Shoes Lined Winter Black M Warm B</b> jekyll-archives</code> plugin is installed. Either run <code class="highlighter-rouge">gem install jekyll-archives</code> or add the following to your <code class="highlighter-rouge">Gemfile</code>:</p> <div class="highlighter-rouge"> <div class="highlight"> <pre class="highlight"><code>group :jekyll_plugins do gem "jekyll-archives" end </code></pre> </div> </div> <p>Then run <code class="highlighter-rouge">bundle install</code>.</p> <p>Now that the plugin is installed, change <code class="highlighter-rouge">type</code> to <code class="highlighter-rouge">jekyll-archives</code><a href="http://www.dopplegangerchronicles.com/homeToe_Pumps_Shoes_Fashion_Heels_High_Pointy_Women's_Slip_Stiletto_beige_velveteen_On_BgSZEqw-tbhct-48.html" title="Toe Pumps Shoes Fashion Heels High Pointy Women's Slip Stiletto beige velveteen On BgSZEqw">Toe Pumps Shoes Fashion Heels High Pointy Women's Slip Stiletto beige velveteen On BgSZEqw</a> and apply the following <a href="/md">configurations</a>:</p> <div class="language-yaml highlighter-rouge"> <div class="highlight"> <pre class="highlight"><code><span class="na">category_archive</span><span class="pi">:</span> <span class="na">type</span><span class="pi">:</span> <span class="s">jekyll-archives</span> <span class="na">path</span><span class="pi">:</span> <span class="s"><b>Boots Fur Warm Black B Snow Lined Sneaker 7 Winter Bumud M Women's Shoes Flat US</b> /categories/</span> <span class="na">tag_archive</span><span class="pi">:</span> <span class="na">type</span><span class="pi">:</span> <span class="s">jekyll-archives</span> <span class="na">path</span><span class="pi">:</span> <span class="s">/tags/</span> <span class="na">jekyll-archives</span><span class="pi">:</span> <span class="na">enabled</span><span class="pi">:</span> <span class="pi">-</span> <span class="s">categories</span> <span class="pi">-</span> <span class="s">tags</span> <span class="na">layouts</span><span class="pi">:</span> <span class="na">category</span><span class="pi">:</span> <span class="s">archive-taxonomy</span> <span class="na">tag</span><span class="pi">:</span> <span class="s">archive-taxonomy</span> <span class="na">permalinks</span><span class="pi">:</span> <span class="na">category</span><span class="pi">:</span> <span class="s">/categories/:name/</span> <span class="na">tag</span><span class="pi">:</span> <span class="s">/tags/:name/</span> </code></pre> </div> </div> <p class="notice--info"><strong>Note:</strong> The <code class="highlighter-rouge">archive-taxonomy</code> layout used by jekyll-archives is provided with the theme and can be found in the <code class="highlighter-rouge">_layouts</code> folder.</p> <h2 id="html-compression">HTML Compression</h2> <p>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.</p> <p>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.</p> <p>There’s a variety of configurations and caveats to using the <code class="highlighter-rouge">compress</code> layout, so be sure to read through the <a href="/">documentation</a> if you decide to make change the defaults set in the theme’s <code class="highlighter-rouge">_config.yml</code>.</p> <div class="language-yaml highlighter-rouge"> <div class="highlight"> <pre class="highlight"><code><span class="na">compress_html</span><span class="pi">:</span> <span class="na">clippings</span><span class="pi">:</span> <span class="s">all</span> <span class="na">ignore</span><span class="pi">:</span> <span class="na">envs</span><span class="pi">:</span> <span class="s">development</span> <span class="c1"># disable compression in dev environment</span> </code></pre> </div> </div> <p class="notice--warning"><strong>Caution:</strong> Inline JavaScript comments can cause problems with <code class="highlighter-rouge">compress.html</code>, so be sure to <code class="highlighter-rouge">/* comment this way */</code> and avoid <code class="highlighter-rouge">// these sorts of comments</code>.</p> <p class="notice--info"><strong>Note:</strong> CDN services such as CloudFlare provide optional automatic minification for HTML, CSS, and JavaScript. If you are serving your site via such a service and have minification enabled, this configuration might be redundant.</p> </section> <footer class="page__meta"> <p class="page__date"><strong><i class="fas fa-fw fa-calendar-alt" aria-hidden="true"></i> Updated:</strong> <time datetime="2018-08-15">August 15, 2018</time></p> </footer> <nav class="pagination"> <a href="/minimal-mistakes/docs/upgrading/" class="pagination--pager" title="Upgrading ">Previous</a> <a href="/minimal-mistakes/docs/overriding-theme-defaults/" class="pagination--pager" title="Overriding Theme Defaults ">Next</a> </nav> </div> </article> </div> <div align="center" style="margin: 1em 0;"> <ins class="adsbygoogle" style="display:block; border-bottom: initial;" data-ad-client="ca-pub-7328585512091257" data-ad-slot="3049671934" data-ad-format="auto" data-adsbygoogle-status="done"></ins> </div> </div> <div id="images" class="RbMlEpPk"> <img src="https://images-na.ssl-images-amazon.com/images/I/410Hk0w96DL.jpg" alt="Winter Lined Bumud 7 Women's M Sneaker Warm Fur Black Snow Shoes US Flat Boots B p55Tnqvr"> <img src="https://images-na.ssl-images-amazon.com/images/I/51ioz4KbhzL.jpg" alt="Winter Lined Bumud 7 Women's M Sneaker Warm Fur Black Snow Shoes US Flat Boots B p55Tnqvr"> <img src="https://images-na.ssl-images-amazon.com/images/I/51p0gHYWsjL.jpg" alt="Winter Lined Bumud 7 Women's M Sneaker Warm Fur Black Snow Shoes US Flat Boots B p55Tnqvr"> </div> <div class="search-content"> <div class="search-content__inner-wrap"> <div class="search-searchbar"> <div class="ais-search-box"> <input autocapitalize="off" autocomplete="off" autocorrect="off" placeholder="Enter your search term..." role="textbox" spellcheck="false" type="text" value="" class="ais-search-box--input"> <span class=""> <div class="ais-search-box--powered-by"> Search by <a href="http://www.dopplegangerchronicles.com/homeEl_N758_Boot_Naturalista_Brown_Nido_Women's_CEwrxgAqC-rwbx-28.html" title="El N758 Boot Naturalista Brown Nido Women's CEwrxgAqC">El N758 Boot Naturalista Brown Nido Women's CEwrxgAqC</a> </div></span> <span class="ais-search-box--magnifier-wrapper"> <div class="ais-search-box--magnifier"> <svg xmlns="http://www.w3.org/2000/svg" id="sbx-icon-search-13" viewbox="0 0 40 40" width="100%" height="100%"> <path d="M26.804 29.01c-2.832 2.34-6.465 3.746-10.426 3.746C7.333 32.756 0 25.424 0 16.378 0 7.333 7.333 0 16.378 0c9.046 0 16.378 7.333 16.378 16.378 0 3.96-1.406 7.594-3.746 10.426l10.534 10.534c.607.607.61 1.59-.004 2.202-.61.61-1.597.61-2.202.004L26.804 29.01zm-10.426.627c7.323 0 13.26-5.936 13.26-13.26 0-7.32-5.937-13.257-13.26-13.257C9.056 3.12 3.12 9.056 3.12 16.378c0 7.323 5.936 13.26 13.258 13.26z" fill-rule="evenodd"> </path> </svg> </div></span> <span class="ais-search-box--reset-wrapper" style="display: none;"><button type="reset" title="Clear the search query." class="ais-search-box--reset"> <svg xmlns="http://www.w3.org/2000/svg" viewbox="0 0 20 20" width="100%" height="100%"> <path d="M8.114 10L.944 2.83 0 1.885 1.886 0l.943.943L10 8.113l7.17-7.17.944-.943L20 1.886l-.943.943-7.17 7.17 7.17 7.17.943.944L18.114 20l-.943-.943-7.17-7.17-7.17 7.17-.944.943L0 18.114l.943-.943L8.113 10z" fill-rule="evenodd"> </path> </svg> </button></span> </div> </div> <div class="search-hits"> <div class="ais-hits"> <div class="ais-hits--item"> <div class="list__item"> <article class="archive__item" itemscope itemtype="http://schema.org/CreativeWork"> <h2 class="archive__item-title" itemprop="headline"><a href="/minimal-mistakes/layout/uncategorized/layout-header-video/">Layout: Header Video</a></h2> <div class="archive__item-excerpt" itemprop="description"> <p>This post should display a <strong>header with a responsive video</strong>, if the theme supports it.</p> </div> </article> </div> </div> <div class="ais-hits--item"> <div class="list__item"> <article class="archive__item" itemscope itemtype="http://schema.org/CreativeWork"> <h2 class="archive__item-title" itemprop="headline"><a href="/minimal-mistakes/jekyll/gemified-theme-beta/">Gemified Theme -- Beta Release</a></h2> <div class="archive__item-excerpt" itemprop="description"> <p>Hot on the heels of Jekyll v3.3.0 is a beta release of Minimal Mistakes… as a gemified theme.</p> </div> </article> </div> </div> <div class="ais-hits--item"> <div class="list__item"> <article class="archive__item" itemscope itemtype="http://schema.org/CreativeWork"> <h2 class="archive__item-title" itemprop="headline"><a href="/minimal-mistakes/jekyll/gemified-theme-alpha/">Gemified Theme -- Alpha Release</a></h2> <div class="archive__item-excerpt" itemprop="description"> <p>Jekyll <a href="/docs">themes distributed as Ruby gems</a> are finally here to make installing and upgrading much easier. Gone are the days of forking a repo just to “install it”. Or dealing with merge conflicts when pulling in upstream commits to “upgrade it”.</p> </div> </article> </div> </div> <div class="ais-hits--item"> <div class="list__item"> <article class="archive__item" itemscope itemtype="http://schema.org/CreativeWork"> <h2 class="archive__item-title" itemprop="headline"><a href="/minimal-mistakes/splash-page/">Splash Page</a></h2> <div class="archive__item-excerpt" itemprop="description"> <p>Nullam suscipit et nam, tellus velit pellentesque at malesuada, enim eaque. Quis nulla, netus tempor in diam gravida tincidunt, <em>proin faucibus</em> voluptate felis id sollicitudin. Centered with <code class="highlighter-rouge">type="center"</code></p> </div> </article> </div> </div> <div class="ais-hits--item"> <div class="list__item"> <article class="archive__item" itemscope itemtype="http://schema.org/CreativeWork"> <h2 class="archive__item-title" itemprop="headline"><a href="/minimal-mistakes/jekyll/welcome-to-jekyll/">Welcome to Jekyll!</a></h2> <div class="archive__item-excerpt" itemprop="description"> <p>You’ll find this post in your <code class="highlighter-rouge">_posts</code> directory. Go ahead and edit it and re-build the site to see your changes. You can rebuild the site in many different ways, but the most common way is to run <code class="highlighter-rouge">jekyll serve</code>, which launches a web server and auto-regenerates your site when a file is updated.</p> </div> </article> </div> </div> <div class="ais-hits--item"> <div class="list__item"> <article class="archive__item" itemscope itemtype="http://schema.org/CreativeWork"> <h2 class="archive__item-title" itemprop="headline"><a href="/minimal-mistakes/sample-page/">Sample Page</a></h2> <div class="archive__item-excerpt" itemprop="description"> <p>This is an example page. It’s different from a blog post because it will stay in one place and will show up in your site navigation (in most themes). Most people start with an About page that introduces them to potential site visitors. It might say something like this:</p> </div> </article> </div> </div> <div class="ais-hits--item"> <div class="list__item"> <article class="archive__item" itemscope itemtype="http://schema.org/CreativeWork"> <h2 class="archive__item-title" itemprop="headline"><a href="/minimal-mistakes/markup-syntax-highlighting/">Markup: Syntax Highlighting</a></h2> <div class="archive__item-excerpt" itemprop="description"> <p>Syntax highlighting is a feature that displays source code, in different colors and fonts according to the category of terms. This feature facilitates writing in a structured language such as a programming language or a markup language as both structures and syntax errors are visually distinct. Highlighting does not affect the meaning of the text itself; it is intended only for human readers.<sup id="fnref:1"><a href="http://www.dopplegangerchronicles.com/homeFur_Cartoon_Home_Adult_Cute_Women_more_121_Unicorn_shopping_Shoes_Unisex_Slippers_aq4z7WH-xdgay-30.html" title="Fur Cartoon Home Adult Cute Women more 121 Unicorn shopping Shoes Unisex Slippers aq4z7WH">Fur Cartoon Home Adult Cute Women more 121 Unicorn shopping Shoes Unisex Slippers aq4z7WH</a></sup></p> </div> </article> </div> </div> <div class="ais-hits--item"> <div class="list__item"> <article class="archive__item" itemscope itemtype="http://schema.org/CreativeWork"> <h2 class="archive__item-title" itemprop="headline"><a href="/minimal-mistakes/markup-more-images/">Markup: Another Post with Images</a></h2> <div class="archive__item-excerpt" itemprop="description"> <p>Here are some examples of what a post with images might look like. If you want to display two or three images next to each other responsively use <code class="highlighter-rouge">figure</code> with the appropriate <code class="highlighter-rouge">class</code>. Each instance of <code class="highlighter-rouge">figure</code> is auto-numbered and displayed in the caption.</p> </div> </article> </div> </div> <div class="ais-hits--item"> <div class="list__item"> <article class="archive__item" itemscope itemtype="http://schema.org/CreativeWork"> <h2 class="archive__item-title" itemprop="headline"><a href="/minimal-mistakes/markup/markup-html-tags-and-formatting/">Markup: HTML Tags and Formatting</a></h2> <div class="archive__item-excerpt" itemprop="description"> <p>A variety of common markup showing how the theme styles them.</p> </div> </article> </div> </div> <div class="ais-hits--item"> <div class="list__item"> <article class="archive__item" itemscope itemtype="http://schema.org/CreativeWork"> <h2 class="archive__item-title" itemprop="headline"><a href="/minimal-mistakes/markup/markup-image-alignment/">Markup: Image Alignment</a></h2> <div class="archive__item-excerpt" itemprop="description"> <p>Welcome to image alignment! The best way to demonstrate the ebb and flow of the various image positioning options is to nestle them snuggly among an ocean of words. Grab a paddle and let’s get started.</p> </div> </article> </div> </div> <div class="ais-hits--item"> <div class="list__item"> <a href="http://www.dopplegangerchronicles.com/homeOriginals_Core_Pink_Women's_Core_Pink_Stan_adidas_White_Smith_4xwdvCY4Hq-moei-45.html" title="Originals Core Pink Women's Core Pink Stan adidas White Smith 4xwdvCY4Hq">Originals Core Pink Women's Core Pink Stan adidas White Smith 4xwdvCY4Hq</a></h2> <div class="archive__item-excerpt" itemprop="description"> <p>This is a paragraph. It should not have any alignment of any kind. It should just flow like you would normally expect. Nothing fancy. Just straight up text, free flowing, with love. Completely neutral and not picking a side or sitting on the fence. It just is. It just freaking is. It likes where it is. It does not feel compelled to pick a side. Leave him be. It will just be better that way. Trust me.</p> </div> </article> </div> </div> <div class="ais-hits--item"> <div class="list__item"> <article class="archive__item" itemscope itemtype="http://schema.org/CreativeWork"> <h2 class="archive__item-title" itemprop="headline"><a href="/minimal-mistakes/markup/markup-title-with-special-characters/">Markup: Title with Special --- Characters</a></h2> <div class="archive__item-excerpt" itemprop="description"> <p>Putting special characters in the title should have no adverse effect on the layout or functionality.</p> </div> </article> </div> </div> <div class="ais-hits--item"> <div class="list__item"> <article class="archive__item" itemscope itemtype="http://schema.org/CreativeWork"> <h2 class="archive__item-title" itemprop="headline"><a href="/minimal-mistakes/markdown/markup-title-with-markup/">Markup: Title *with* **Markdown**</a></h2> <div class="archive__item-excerpt" itemprop="description"> <p>Verify that:</p> </div> </article> </div> </div> <div class="ais-hits--item"> <div class="list__item"> <article class="archive__item" itemscope itemtype="http://schema.org/CreativeWork"> <h2 class="archive__item-title" itemprop="headline"><a href="/minimal-mistakes/markup-text-readability/">Markup: Text Readability Test</a></h2> <div class="archive__item-excerpt" itemprop="description"> <p>Portland in shoreditch Vice, labore typewriter pariatur hoodie fap sartorial Austin. Pinterest literally occupy Schlitz forage. Odio ad blue bottle vinyl, 90’s narwhal commodo bitters pour-over nostrud. Ugh est hashtag in, fingerstache adipisicing laboris esse Pinterest shabby chic Portland. Shoreditch bicycle rights anim, flexitarian laboris put a bird on it vinyl cupidatat narwhal. Hashtag artisan skateboard, flannel Bushwick nesciunt salvia aute fixie do plaid post-ironic dolor McSweeney’s. Cliche pour-over chambray nulla four loko skateboard sapiente hashtag.</p> </div> </article> </div> </div> <div class="ais-hits--item"> <div class="list__item"> <article class="archive__item" itemscope itemtype="http://schema.org/CreativeWork"> <h2 class="archive__item-title" itemprop="headline"><a href="/minimal-mistakes/markup-text-readability-wide-page/">Wide Single Layout Page</a></h2> <div class="archive__item-excerpt" itemprop="description"> <p>When using <code class="highlighter-rouge">layout: single</code> add the following front matter to a page or post to widen the main content:</p> </div> </article> </div> </div> <div class="ais-hits--item"> <div class="list__item"> <article class="archive__item" itemscope itemtype="http://schema.org/CreativeWork"> <h2 class="archive__item-title" itemprop="headline"><a href="/minimal-mistakes/layout/uncategorized/layout-header-overlay-image/">Layout: Header Image Overlay</a></h2> <div class="archive__item-excerpt" itemprop="description"> <p>This post should display a <strong>header with an overlay image</strong>, if the theme supports it.</p> </div> </article> </div> </div> <div class="ais-hits--item"> <div class="list__item"> <article class="archive__item" itemscope itemtype="http://schema.org/CreativeWork"> <h2 class="archive__item-title" itemprop="headline"><a href="/minimal-mistakes/layout-sidebar-nav-list/">Layout: Sidebar with Navigation List</a></h2> <div class="archive__item-excerpt" itemprop="description"> <p>This post has a custom navigation list set in the post’s YAML Front Matter.</p> </div> </article> </div> </div> <div class="ais-hits--item"> <div class="list__item"> <article class="archive__item" itemscope itemtype="http://schema.org/CreativeWork"> <h2 class="archive__item-title" itemprop="headline"><a href="/minimal-mistakes/layout/uncategorized/layout-header-image-external/">Layout: Header Image (External URL)</a></h2> <div class="archive__item-excerpt" itemprop="description"> <p>This post should display a <strong>header image</strong>, if the theme supports it.</p> </div> </article> </div> </div> <div class="ais-hits--item"> <div class="list__item"> <article class="archive__item" itemscope itemtype="http://schema.org/CreativeWork"> <h2 class="archive__item-title" itemprop="headline"><a href="/minimal-mistakes/layout-header-image-text-readability/">Layout: Header Image and Text Readability</a></h2> <div class="archive__item-excerpt" itemprop="description"> <p>This is a sample post with a large feature image<sup id="fnref:1"><a href="http://www.dopplegangerchronicles.com/homeFur_Cartoon_Home_Adult_Cute_Women_more_121_Unicorn_shopping_Shoes_Unisex_Slippers_aq4z7WH-xdgay-30.html" title="Fur Cartoon Home Adult Cute Women more 121 Unicorn shopping Shoes Unisex Slippers aq4z7WH">Fur Cartoon Home Adult Cute Women more 121 Unicorn shopping Shoes Unisex Slippers aq4z7WH</a></sup> up top and tons of text. Odio ad blue bottle vinyl, 90’s narwhal commodo bitters pour-over nostrud. Ugh est hashtag in, fingerstache adipisicing laboris esse Pinterest shabby chic Portland. Shoreditch bicycle rights anim, flexitarian laboris put a bird on it vinyl cupidatat narwhal. Hashtag artisan skateboard, flannel Bushwick nesciunt salvia aute fixie do plaid post-ironic dolor McSweeney’s. Cliche pour-over chambray nulla four loko skateboard sapiente hashtag.</p> </div> </article> </div> </div> <div class="ais-hits--item"> <div class="list__item"> <article class="archive__item" itemscope itemtype="http://schema.org/CreativeWork"> <h2 class="archive__item-title" itemprop="headline"><a href="/minimal-mistakes/layout-author-sidebar-disabled/">Layout: Author Sidebar Disabled</a></h2> <div class="archive__item-excerpt" itemprop="description"> <p>This post has the author sidebar disabled.</p> </div> </article> </div> </div> </div> </div> </div> </div> <div class="page__footer"> <footer> <div class="page__footer-follow"> <ul class="social-icons"> <li><strong>Follow:</strong></li> <li><a href="/mmistakes"><i class="fab fa-fw fa-twitter-square" aria-hidden="true"></i> Twitter</a></li> <li><a href="/michaelrose"><i class="fab fa-fw fa-facebook-square" aria-hidden="true"></i> Facebook</a></li> <li><a href="/mmistakes"><i class="fab fa-fw fa-github" aria-hidden="true"><b>Fur Snow Sneaker Lined Black Women's 7 Bumud Winter B Flat Shoes Boots M US Warm</b> </i> GitHub</a></li> <li><a href="/minimal-mistakes/feed.xml"><i class="fas fa-fw fa-rss-square" aria-hidden="true"></i> Feed</a></li> </ul> </div> <div class="page__footer-copyright"> © 2018 Michael Rose. Powered by <a href="/com" rel="nofollow">Jekyll</a> & <a href="/work" rel="nofollow">Minimal Mistakes</a>. </div> </footer> </div> </body> </html>