Project Status

This project is currently in alpha status. It's not recommended to use it in production since the API is likely to change in the future. If you want to contribute and help to release 1.0.0, please look at the issues and roadmap.


Stasis is a simple and easy to use static site generator. It aims to provide production ready tools to create static website projects.

Stasis uses Handlebars templates to compile your Markdown source files into static HTML web pages. Scripts and styles are compiled using the powerful Parcel Bundler. It can handle sass, scss, ts and many more asset types and compiles them into pure javascript and CSS. You can read more about supported asset types at Parcel's documentation.

Getting started

To create a static site project you can clone or download the example project on Github.

Folder structure



  • src Main source folder for your project. Provide this folder as \<path> argument to the build, and serve CLI argument.
  • layouts Handlebars template layouts for your pages.
  • partials Handlebars partials that you can use in your layout files
  • helpers A folder with your custom handlebars helpers. The file name is the name of your helper that Stasis registers.
  • pages Your website content. Stasis respects the folder structure and automatically generate pretty URLs for each .md file.
  • static Place your static assets like images and fonts here.
  • assets Place all your scripts and stylesheets here. Those files are bundled using Parcel.
  • graphql Define your schema and root here. Read more in the Advanced Usage section.
  • stasis.config.json A simple configuration file for your project. Provide this file as -c argument to the build, and serve CLI argument.


    "sourcePath": "src",
    "publicPath": "dist",
    "assetsPath": "assets",
    "staticPath": "static",
    "graphQlPath": "graphql",
    "entryAssets": [


  • sourcePath Custom source path
  • publicPath The output directory of the compiled site
  • assetsPath Folder that holds your assets
  • staticPath Your static folder for fonts and images
  • entryAssets Patter to look for entry assets. Use **/* to compile everything inside the assets folder or provide a list of files.


You can choose to install Stasis globally with npm i -g stasis-generator.

Run the CLI with stasis-cli -h to see all available options.

Its recommended that you install Stasis locally in your project and use it via npm scripts.

npm i --save-dev stasis-generator

Basic usage example:

"build": "stasis-cli build -c stasis.config.json src",
"serve": "stasis-cli serve -c stasis.config.json src",

Advanced Usage


The compiler exposes various information:

  • body Raw html content
  • frontmatter Front Matter data
  • title The page title. Either frontmatter.title or the filename
  • slug A slug version of the title
  • excerpt An excerpt of your markdown content. (Everything above the first ---, frontmatter excluded)
  • query The result of a GraphQL query
  • isProduction Boolean flag
  • isDevelopment Boolean flag


Stasis lets you configure a GraphQL schema to query your pages. At this point it does not infer GraphQL types from your frontmatter content like Gatsby does. Its up to you to define your schema, queries and resolvers. To do this create an index.js file in your graphql directory and export an object with two functions. Both functions get an array of all your pages and the Stasis configuration:

module.exports = {
    createSchema: (pages, config) => {
        return `
    type Query {
        pageByIndex(index: Int!): Page
            pageByTitle(title: String!): Page
        pages: [Page]
  type Page {
        html: String
            frontmatter: Frontmatter
        excerpt: String
        relativePath: String
        active: Boolean
    type Frontmatter {
            title: String
            date: String
            layout: String
    } ,
    createRoot: (pages, config) => {
        return {
            pages: () => pages,
            pageByIndex: args => pages[args.index],
            pageByTitle: args => pages.find(p => p.frontmatter.title === args.title)
  • createSchema must return a string with a valid GraphQL schema.
  • createRoot must return an object with your GraphQL resolvers.

If you want to expose the result of a query to your layout, just specify a query field with a valid GraphQL query inside your page frontmatter:

title: front page
query: '{
    pages {
        frontmatter {
Some content...

You can use the result of that query inside your handlebars layouts:

        <li><a href="{{this.relativePath}}">{{this.frontmatter.title}}</a></li>

Use query results in Javascript client code.

In order to access your query results (or any other data) in your client side code, just attach it to the window object.

    window.pages = {{{ json }}}

Use live reload in development

The development server automatically starts a live reload server that you can use during development. The compiler exposes a isDevelopment variable to the layout that you can use to conditionally insert the client side live-reload script.

{{#if this.isDevelopment}}
    document.write('<script src="http://' + ( || 'localhost').split(':')[0] +
      ':35729/livereload.js?snipver=1"></' + 'script>')

Pretty URL

By default Stasis generates pretty urls. A file page called will be places at /example/index.html. If a file is called Stasis will just generate an index.html. You can choose to skip pretty url generation and tell Stasis to use the original filename by setting pretty_url in your pages Front Matter