Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

A StoryBlok / Nuxt starterkit

Demo in use:

This code HEAVILY borrows from two different repositories:

Improvements in functionality to those base versions

  • Update of all libraries.
  • Static site generation with payload
  • Use of a vuex store

Changes to those versions

  • Moving away from SASS and Bootstrap towards Tailwind and PostCSS
  • Yarn as the command interface

Getting Started

Set up a demo site on Storyblok

First we are setting up a site that uses the base bootstrap demo version). But don't worry; we will add our own soon.

  1. Go to
  2. Choose Create new space
  3. Choose Play with a demo
  4. Wait for the demo to be created
  5. Get the preview key
    • Settings -> API Keys -> Preview Key
  6. Add a preview url
    • Settings -> General -> Preview Urls
    • Add http://localhost:3000

Download or copy or clone the code to your own computer

If you're reading this, then I'm guessing you know how to do this. Otherwise, learn how to git or just use the zip download.

Set the storyblok token in the nuxt.config.js

Change the STORYBLOK_TOKEN in the nuxt.config.js, or set it using an environment variable.

// NOTE: The Storyblok token should NOT be commited to code as a general rule. 
// Using an environment variable is a good choice
// e.g. const token = process.env.STORYBLOK_TOKEN
  process.env.STORYBLOK_TOKEN || "fRhLxFwXxMQSuteNdL1Lrwtt";

Building for development

Building for dev will let you see the site on your own computer! You will also be able to edit and change things through the storyblok interface.

# install dependencies
$ yarn install 

# serve with hot reload at localhost:3000
$ yarn dev

The static production ready version of the site is able to be run locally.

# to build, export and then serve up the built files on http://localhost:3000
$ yarn static

# or to just build and export
$ yarn generate

# or to run each command individually 
$ yarn build --static
$ yarn export
$ yarn serve

There are some issues in making the static version "non-static" in edit mode via Storyblok. These are being worked on where found.

Editing content

This is the part where it all comes together.

  1. Start the site locally http://localhost:3000 using either:
    • yarn dev - SPA (Single Page Application) in dev mode; auto updates on code changes.
    • yarn static- Serves statically generated HTML; emulates production.
  2. Go to
  3. Go to the demo space you have created.
  4. Content -> Home
  5. Change the Preview url to the localhost option using the navigation dropdown

It should be working! If not, let me know and I'll try to help.

Deploying to Netlify

Deploying to Netlify is super easy. Set up a webhook to keep the generated files up to date with latest content.

  1. Create a site
  2. Connect your repo
  3. Set the build commands
    • Build Command: yarn generate
    • Folder: dist
  4. Add the Storyblok PREVIEW key as an environment variable
    • Don't use the public key unless you want it to be a non-editing site.
  5. Deploy Site and verify deployment
  6. Create a build webhook on Netlify Build & Deploy -> Add build hook -> master
  7. Copy build webhook url to Storyblok General -> Webhooks -> Story Published & Unpublished

Possible deployment strategies

Single site

If you want one site for both editing and delivery

  • yarn generate
  • Use the preview key

Downsides to this is that your preview key is exposed. It may or may not be a concern to you.

Separate Edit and Delivery sites

  • Delivery site
    • yarn generate
    • Use the PUBLISHED key
  • Editing site
    • yarn build --spa
    • yarn export
    • Use the PREVIEW key

No static generation means everything is loaded dynamically, and should be up-to date. Another benefit is that the preview key is not exposed.


How to use this kit for your own project

  1. Get it running using the instructions above
  2. Delete all the Storyblok pages from the demo site.
  3. Delete all components EXCEPT Global and Page:
    • from Storyblok
    • from the Components folder.
    • from the /plugins/components.js
  4. Modify Global and Page components to the data structure you need
    • Global: Keep the header and footer sections
  5. Add pages
    • Global of type Global
    • Home of type Page
  6. Remove all custom styles from assets/css/tailwind.css

If you leave this repo as a git secondary remote, you will be able to pull in changes when they are made here.


Tailwind usually purges all unused css classes within it's library on production build. Dynamic classes must be whitelisted in the tailwind.config.js for this project or they will be purged by PostCSS


A starterkit using Nuxt.js and Storyblok based on demo content






No releases published


No packages published