Storybook for Django is an experimental UI development environment for Django components. It allows you to implement, document, and test UI components in isolation from your Django views.
Server-side, this uses django-pattern-library to mock template context and template tags. Client-side, we use Storybook to create stories from our templates.
Let’s get you set up. There are two requirements:
- First, start by setting up django-pattern-library, v0.7.0 and up. Have a look at our demo settings.py as an example.
- Then, set up Storybook. We expect
storybook-djangoto work with any framework supported by Storybook, and provide built-in support for React (Vue in progress).
Next, install our package:
npm install --save-dev storybook-djangoAdd a middleware.js inside your Storybook configuration folder (.storybook by default):
const {
createDjangoAPIMiddleware,
} = require('storybook-django/src/middleware');
module.exports = createDjangoAPIMiddleware({
// Point this at your Django runserver instance, with the correct port number.
origin: 'http://localhost:8001',
apiPath: ['/pattern-library/'],
});This will forward pattern library API requests to Django. You may optionally add more API path patterns to apiPath to make other requests to your Django backend.
This is optional but highly recommended. To leverage Storybook’s live-reloading and documentation capabilities, we need to configure it to load our templates. Edit your Storybook main.js file to customise the webpackFinal option:
module.exports = {
webpackFinal: (config) => {
config.module.rules = config.module.rules.concat([
{
test: /\.html$/,
// Webpack 5:
type: 'asset/source',
// Webpack 4 (make sure to also install the raw-loader package):
// use: 'raw-loader',
},
]);
return config;
}Here is the most basic story for a Django template:
import { Pattern } from 'storybook-django/src/react';
export default {};
export const Base = () => (
<Pattern
template="patterns/components/streamfield/heading_block.html"
context={{ value: 'An important section' }}
/>
);Pattern uses a hard-coded endpoint of /pattern-library/api/v1/render-pattern by default. To change this, pass a different value. For example,
<Pattern endpoint="/storybook-patterns/api/v1/render-pattern" />If this is a necessity for your project, consider creating your own wrapper for the Pattern component rather than having to define the endpoint in all stories.
Our Pattern component has to be told which template to render, Alternatively, we can use Webpack’s __filename support to auto-generate the template path. First, configure Webpack:
config.node = {
__filename: true,
};Then, use the filename prop instead of template:
<Pattern filename={__filename} />This filename prop assumes the template is in the same folder as the template, with the same file name except for the extension (replaces .stories.(js|tsx) with .html).
And here is a more advanced examples, showcasing different Storybook features:
- Setting a custom title for the story.
- Loading Markdown files to use as documentation.
- Loading the component’s template to display alongside the docs, and for live-reloading.
- Setting up controls.
- Having multiple stories with different data.
import { Pattern } from 'storybook-django/src/react';
import docs from './quote_block.md';
import template from './quote_block.html';
export default {
title: 'Components / quote_block',
parameters: {
docs: {
source: { code: template },
extractComponentDescription: () => docs,
},
},
argTypes: {
quote: {
control: { type: 'text' },
description: 'Will be displayed first',
},
attribution: {
control: { type: 'text' },
description: 'Underneath the quote (optional)',
},
},
};
export const Base = (args) => (
<Pattern filename={__filename} context={{ value: args }} />
);
Base.args = {
quote: 'Someone believed in me once and now it’s time for me to do the same.',
attribution: 'Young person',
};
export const NoAttribution = Base.bind({});
NoAttribution.args = {
quote: Base.args.quote,
attribution: null,
};The point of using React is to be able to fully customise the context within which our Django components are displayed. Here is an example, with a simple SVG icon template:
const IconPattern = (props) => (
<Pattern
element="span"
template="patterns/components/icon/icon.html"
context={props}
/>
);
export const ReactDemoStory = () => (
<span>
<a href="https://www.example.com">
View our complete guide <IconPattern name="arrow" />
</a>
</span>
);We are working on Vue support. Please refer to Usage with Vue #7 in the meantime, and provide feedback.
storybook-django’s implementation is largely framework-agnostic, and should work equally as well with Storybook’s HTML and Web Components support.
You will need to directly import the imperative APIs:
import {
renderPattern,
simulateLoading,
insertHTMLWithScripts,
} from 'storybook-django';renderPatterncalls the django-pattern-library API rendering endpoint.simulateLoadingincludesinsertHTMLWithScripts, and fires aDOMContentLoadedevent.insertHTMLWithScriptsis like.innerHTML, but additionally executing any<script>tags.
There is nothing particular to change to make storybook-django work with TypeScript. Just make sure to configure TypeScript to understand .md and .html files if you use those features – here is a sample stories.d.ts file:
declare module '*.md';
declare module '*.html';Tag overrides are a feature of django-pattern-library. They’re very simple to use with storybook-django too. Here is an example:
import React from 'react';
import { Pattern, generateDocs } from 'storybook-django/src/react';
import template from './page_status_tag_new.html';
export default {};
const PublicTemplate = (args) => (
<Pattern
filename={__filename}
tags={{
test_page_is_public: {
'page as is_public': {
raw: false,
},
},
}}
context={{ page: args }}
/>
);
export const Public = PublicTemplate.bind({});
Public.args = {
live: true,
url: '#',
};This is the same API as that of django-pattern-library, but as JS objects rather than YAML.
storybook-django is still very experimental. Head over to Discussions to share information about more advanced usage.
storybook-django is compatible with Storyshots, with a few constraints due to rendering happening with Django via an API:
- We need a running Django server while the Storyshots test suite is running.
- Components render asynchronously, so we need to make sure to test the final rendering from Django, rather than an intermediary state.
- We need to use Jest’s
jsdomenvironment, and include a polyfill forwindow.fetchsuch aswhatwg-fetch.
Getting a Django server up and running is as simple as starting it in the background ahead of running the test suite. Here is a GitHub Actions example:
- run: source .venv/bin/activate && python manage.py runserver 0:8001 &
- run: npm run testTo check whether Django patterns have finished rendering, we use a data-state="loaded" attribute set by storybook-django when it first inserts the HTML into the DOM. Here is an example of automated accessibility tests with Axe, with @testing-library/react:
const { container, queryAllByTestId } = render(story.render());
const patterns = queryAllByTestId('storybook-django');
if (patterns.length > 0) {
await waitFor(
() => expect(patterns.map((p) => p.dataset.state)).toContain('loaded'),
{ timeout: 10000 },
);
}After checking the patterns are loaded, it’s as simple as expect(container).toMatchSnapshot();. See the full snapshot example.
With jest-axe, after checking the patterns are loaded,
const results = await axe(container, {
// See https://github.com/dequelabs/axe-core/blob/develop/doc/rule-descriptions.md for a list of rules.
// Try to only disable rules if strictly needed, alternatively also consider excluding stories from those tests
// with the `storyshots` parameter: https://github.com/storybookjs/storybook/tree/master/addons/storyshots/storyshots-core#disable.
rules: {
// Disabled because stories are expected to be rendered outside of landmarks for testing.
region: { enabled: false },
},
});
expect(results).toHaveNoViolations();See the full jest-axe example.
This is possible as well, with Storybook’s @storybook/addon-storyshots-puppeteer. View the full image snapshots example.
A few of the stories in our demo project use YAML to store a pattern’s mock context and tags. This is largely a demonstration of compatibility with how django-pattern-library works, and for most users defining context and tags with Storybook APIs is more suitable. There are a few cases where the YAML setup can help:
- There is currently no way to override context in other templates via API calls. YAML files make this possible.
- Similarly there is no way to override tags in other templates – again made possible with YAML files.
Since storybook-django relies on a Django backend, in this context the Storybook export can’t be hosted as a fully static site. We instead need to:
- Build a static export with
build-storybook - Configure a Django server to serve the static export
- Host the Django server
This repository’s demo site has an example of how to do this, serving the static files with Django’s django.views.static.serve.
django-pattern-library makes it possible to work with Django templates as UI components. It comes with its own rudimentary pattern library UI. storybook-django uses Storybook’s UI instead, and Storybook’s APIs to work on components, write tests, and documentation.
| Feature | django-pattern-library | storybook-django |
|---|---|---|
| UI framework support | Vanilla Django templates only | Vanilla templates and all frameworks Storybook supports |
| Dependencies | 1 PyPI package | 1 PyPI package, 1 npm package, all Storybook dependencies |
| Hosting | Django server or static site export | Django server only |
| Components documentation | Separate Markdown file | Storybook Docs addon with separate Markdown file, or Django templates comments extraction, or write in stories |
| Browser support | No restrictions | Modern browsers only |
| Live reload | No (bring your own) | Yes, if configured |
| View components at multiple breakpoints | Yes, with predefined breakpoints only | Yes, with viewport addon |
| Tweak template data in UI | No | Yes, Storybook controls |
| Component variations | No | Yes |
| Component status | No | Yes, with Docs addon |
| Components homepage | No (build your own) | No (build your own) |
| Pattern library theming | No | Yes |
| Customizing a component’s surroundings | No, create a new template for this | Yes |
| Automated snapshot tests | Basic support | Yes, with Storyshots |
| Automated accessibility tests | Basic support | Yes, with Storyshots or a11y addon |
| Automated visual regression tests | Basic support | Yes, with Storyshots or any other Storybook integration |
Compared to this project, @storybook/server only supports simple use cases.
See torchbox/django-pattern-library#103 – Storybook prototype of the pattern library for more context on this project, and to keep up with changes to it in relation with django-pattern-library.
Are Storybook’s capabilities appealing to you? Consider using storybook-django. If not, stick with django-pattern-library if you’re ok with its known limitations. It’s simpler to start with django-pattern-library and add Storybook later, than the other way around.
See anything you like in here? Anything missing? We welcome all support, whether on bug reports, feature requests, code, design, reviews, tests, documentation, and more. Please have a look at our contribution guidelines.
If you just want to set up the project on your own computer, the contribution guidelines also contain all of the setup commands.
View the full list of contributors. MIT licensed.
