A long-lived project that still receives updates
A series of helpers for consistency among HashiCorp's middleman sites


~> 1.13
~> 11.3
~> 3.5


 Project Readme

HashiCorp Middleman Customizations

A wrapper around Middleman for HashiCorp's customizations.

Table of Contents

  • Installation
  • Usage
  • Customizations
  • Publishing a new Release
  • Contributing


Add this line to the Gemfile:

gem 'middleman-hashicorp', github: 'hashicorp/middleman-hashicorp'

And then run:

$ bundle


To generate a new site, follow the instructions in the Middleman docs. Then add the following line to your config.rb:

activate :hashicorp

If you are a HashiCorp employee and are deploying a HashiCorp middleman site, you will probably need to set some options. Here is an example from Packer:

activate :hashicorp do |h|
  h.name        = "packer"
  h.version     = "0.7.0"
  h.github_slug = "hashicorp/terraform"

  # Disable fetching release information - this is useful for non-product site
  # or local development.
  h.releases_enabled = false

  # Disable some extensions
  h.minify_javascript = false

Almost all other Middleman options may be removed from the config.rb. See a HashiCorp project for examples.

Now just run:

$ middleman server

and you are off running!


Default Options

  • Syntax highlighting (via middleman-syntax) is automatically enabled
  • Asset directories are organized like Rails:
    • assets/stylesheets
    • assets/javascripts
    • assets/images
    • assets/fonts
  • The Markdown engine is redcarpet (see the section below on Markdown customizations)
  • During development, live-reload is automatically enabled
  • During build, css, javascript and HTML are minified
  • During build, assets are hashed
  • During build, gzipped assets are also created

IE Compatibility

There are bundled things that make IE behave nicely. Include them like this:

<!--[if lt IE 9]>
  <%= javascript_include_tag "ie-compat" %>

Inline SVGs

Getting SVGs out of the asset pipeline and into the DOM can be hard, but not with the magic inline_svg helper!

<%= inline_svg "my-asset.svg" %>

It supports configuring the class, height, width, and viewbox.


Turbolinks highjack links on the same domain and use AJAX to dynamically update only the changed content. This is used by many popular sites, including GitHub. To enable turbolinks, include the javascript.

// assets/javascripts/application.js
//= require turbolinks

Mobile Sidebar

The mobile sidebar is displayed on mobile and small screens as a hamburger menu. It requires some additional markup and css for configuration. First, define the following variables in your scss:


Then include the scss scaffold:

@import 'hashicorp/sidebar';

Next, create some markup like this:

<div class="sidebar-overlay"></div>

<aside class="sidebar" role="navigation">
  <div class="sidebar-header">
    <img src="images/my-image.svg" alt="My Header" height="42">

  <ul class="nav sidebar-nav">
    <li><a href="/">Home</a></li>

  <!-- Optional -->
  <div class="divider"></div>

  <ul class="nav sidebar-nav">
    <li><a href="/">Other</li>

Finally include the required javascript:

//= require hashicorp/sidebar

Mega Nav

HashiCorp has a consistent mega-nav used across all project sites. This is insertable into any document using the following:

<%= mega_nav :terraform %>

Additionally, you must import the CSS and Javascript:

// assets/javascripts/application.js
//= require hashicorp/mega-nav
// assets/stylesheets/application.scss
@import 'hashicorp/mega-nav';


  • latest_version - get the version specified in config.rb as version, but replicated here for use in views.

    latest_version #=> "1.0.0"
  • system_icon - use vendored image assets for a system icon

    system_icon(:windows) #=> "<img src=\"/images/icons/....png\">"
  • pretty_os - get the human name of the given operating system

    pretty_os(:darwin) => "Mac OS X"
  • pretty_arch - get the arch out of an arch

    pretty_arch(:amd64) #=> "64-bit"


This extension extends the redcarpet markdown processor to add some additional features:

  • Autolinking of URLs
  • Fenced code blocks
  • Tables
  • TOC data
  • Strikethrough
  • Superscript

In addition to "standard markdown", the custom markdown parser supports the following:

Auto-linking Anchor Tags

Since the majority of HashiCorp's projects use the following syntax to define APIs, this extension automatically converts those to named anchor links:

* `api_method` - description


  <li><a name="api_method" /><a href="#api_method"></a> - description</li>

Auto-linking Header Tags

Header links will automatically generate linkable hrefs on hover. This can be used to easily link to sub-sections of a page. This requires the following SCSS.

// assets/stylesheets/application.scss
@import 'hashicorp/anchor-links';

Any special characters are converted to an underscore (_).

Recursive Markdown Rendering

By default, the Markdown spec does not call for rendering markdown recursively inside of HTML. With this extension, it is valid:

<div class="center">
  This will **be bold**!

Bootstrap Alerts

There are 4 custom markdown extensions that automatically create Twitter Bootstrap-style alerts:

  • => => success
  • -> => info
  • ~> => warning
  • !> => danger
-> Hey, you should know...
<div class="alert alert-info" role="alert">
  <p>Hey, you should know...</p>

Of course you can use Markdown inside the block:

!> This is a **really** advanced topic!
<div class="alert alert-danger" role="alert">
  <p>This is a <strong>really</strong> advanced topic!</p>


Twitter Bootstrap (3.x) is automatically bundled. Simply activate it it in your CSS and Javascript:

@import 'bootstrap-sprockets';
@import 'bootstrap';
//= require jquery
//= require bootstrap

Publishing a New Release

Just bump the version string and push a new tag to the repository and our CI will release the gem automatically. Do not try running any of the Makefile tasks yourself, the CI will run them for you.


  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create a new Pull Request