A flat file compiler that powers our prototyping template. Create pages with consistent layouts and reusable partials with ease.

If you've ever created a static site, maybe you had five pages that all shared the same header and footer. You create your first page, and then copy and paste the common elements to the next page. But now if you need to make a change to the header, the change has to be made across multiple files.

Panini is a flat file compiler that uses the concepts of templates, pages, and partials—powered by the Handlebars templating language—to streamline the process of creating static prototypes.

Our prototyping template uses Panini, along with a host of other tools for processing Sass, JavaScript, and images, to make creating static prototypes easy. It's already been configured to utilize all of the features below, but if you want to learn the specifics of how to configure the library, head over to the Panini GitHub page.

Basics: Templates & Pages

A template is a common layout that every page in your design shares. It's possible to have multiple templates, but generally you'll only need one, and a page can only use one template. In the prototyping template, the default layout is found under src/layouts/default.html.

Here's what a basic template might look like:

    <title>Definitely a Website!</title>
    <header class="header"><!-- ... --></header>
    {{> body}}
    <footer class="footer"><!-- ... --></footer>

In the middle of the HTML is a bit of Handlebars code: {{> body}}. This is where the pages you write are injected when Panini runs, giving you a series of complete HTML files at the end.

The pages make up the guts of your layouts. These files will just have the middle section of the design, since the layout already covers the top and bottom. The prototyping template includes one blank page to get you started, under src/pages/index.html.

A basic page might look like this:

<h1>Page Title</h1>
<p>Lorem ipsum dolor sit amet, consectetur adipisicing elit. Praesentium ducimus eligendi, reiciendis corporis quam facere quaerat qui, aspernatur molestiae velit, vero ea quisquam laborum corrupti repudiandae totam, at aliquam esse.</p>

Note that there's no <html> or <body> tags, and no header or footer. This code will be injected into the {{> body}} declaration when Panini assembles your pages.

In the prototyping template, these finished files are compiled into a standalone folder called dist (short for "distribution"), which also includes your processed CSS, JavaScript, and images. This folder can easily be uploaded to any web server, or Notable's Hosted Prototypes service.


Partials are a feature of Handlebars which allow you to inject HTML anywhere in a page or layout. They're really useful when you need to repeat certain chunks of code throughout your pages, or to keep individual files from getting too cluttered with HTML.

Here's an example of a layout file that divides its key sections into partials:

    <title>Definitely STILL a Website!</title>
    {{> header}}
    {{> navigation}}
    {{> body}}
    {{> footer}}

The {{> }} syntax tells Handlebars to look for an HTML file with that name, and inject it at that place. In this example, we have files called header.html, navigation.html, and footer.html. In the prototyping template, these files all exist within src/partials.

Page Variables

Pages have a few built-in variables, which can be used within the page template itself, or within a layout or partial being used in tandem with the page.


Prints the name of the current page, without its original file extension. In the below example, if the page is index.html, {{page}} will become index.

<p>You are here: {{page}}</p>


Use {{root}} before a file path to make sure it works no matter what folder the current page is in.

For example, a path to an external CSS file will need to be different if the current page is at the root level of your site, or in a sub-folder.

Here's how you'd use it with a <link> tag:

<link rel="stylesheet" href="{{root}}assets/css/app.css">

If the page is index.html, the path will look like this:

<link rel="stylesheet" href="assets/css/app.css">

If the page is folder/page.html, the path will look like this:

<link rel="stylesheet" href="../assets/css/app.css">

The ../ is added only on pages in a sub-folder, so the CSS can still be properly loaded.


Helpers are special functions that manipulate content on the page. In addition to Handlebars's built-in helpers, Panini includes a few custom helpers and you can add your own.


Displays the HTML inside the helper if the two values are equal.

{{#ifequal foo bar}}
  <p>foo and bar are equal</p>
  <p>foo and bar are not equal</p>  


Displays the HTML inside the helper only on specific pages. In the below example, the HTML inside the helper will only show up on the index.html page.

{{#ifpage 'index'}}
  <p>This is definitely the Index page.</p>

You can also check for multiple pages. If any name in the list matches the current page, the HTML will appear.

{{#ifpage 'index' 'about'}}
  <p>This is definitely either the Index or About page.</p>


The opposite of #ifpage, #unlesspage will only display the HTML inside of it if the current page is not in the parameters.

{{#unlesspage 'index'}}
  <p>This is definitely <em>not</em> the Index page.</p>


Repeats the content inside of it n number of times. Use this to easily print lots of duplicate HTML in a prototype.

  {{#repeat 5}}
  <li>Five hundred ninety-nine US dollars</li>


Converts Markdown into HTML.

# Heading 1
Lorem ipsum [dolor sit amet](, consectetur adipisicing elit. Nam dolor, perferendis. Mollitia aut dolorum, est amet libero eos ad facere pariatur, ullam dolorem similique fugit, debitis impedit, eligendi officiis dolores.

Custom Helpers

If you don't see the right helper, you can write your own. Add a javascript file to 'src/helpers', add helpers: 'src/helpers' to the Panini process in your gulpfile.babel.js, restart npm, then call it in your templates.

// Example file src/helpers/bold.js
module.exports = function(options) {
  // options.fn(this) = Handelbars content between {{#bold}} HERE {{/bold}}
  var bolder = '<strong>' + options.fn(this) + '</strong>';
  return bolder;
// Example  gulpfile.babel.js
function pages() {
  return gulp.src('src/pages/**/*.html')
      root: 'src/pages',
      layouts: 'src/layouts',
      partials: 'src/partials',
      helpers: 'src/helpers'

Then in your projects call your custom {{#bold}} helper


Custom Data

Custom data can be added to your pages. This data can then be inserted into your HTML through Handlebars. There are two ways to add data to a project.

To add variables to a specific page only, add it at the top of the page's HTML as a Front Matter block. Let's say the below content is inside src/pages/index.html.

title: Page Title
description: Lorem ipsum.

<!-- The rest of your HTML is down here. -->

Now, you can insert the values of these variables into the index.html page, or the default.html layout. To insert a variable, wrap the name of the variable in double curly braces, like so:

<h1>{{ title }}</h1>

Variables can also be added globally by creating an external JSON or YML file, and adding it to the src/data folder in your project. Let's create a file called breakfast.yml:

- eggs
- bacon
- toast

Panini will load in the contents of this YML file as a variable called {{ breakfast }}. Because it's an array, we can loop through it using Handlebars's {{#each}} helper:

<ul class="breakfast-items">
  {{#each breakfast}}
    <li>{{ this }}</li>

This code will print three <li>s, one for each item in the file.