Am I right to say if I don't use any client side frameworks like React, Vue, etc I should just stick to pattern-library? about storybook-django HOT 3 CLOSED

FYI I’ll be working on a new version of the docs shortly. So far this has been very experimental, so spending the time writing docs didn’t feel appropriate. Now the package almost has a stable API.

For the question at hand,

• django-pattern-library handles the rendering of Django templates with arbitrary context and tag overrides. It also provides a rudimentary UI and workflows to test templates as UI components.
• storybook-django makes it possible to test Django templates in Storybook. It relies on django-pattern-library for templates rendering only, everything else is done with Storybook APIs.
• django-components solves a different problem to the above two – which is helping you structure and reuse Django templates as components.

from storybook-django.

I'd also appreciate clarification on the distinction between these two projects, and when to use one vs the other

Would also be curious to hear about how both compare to https://github.com/EmilStenstrom/django-components -- would it make sense to use either this or pattern-library to document components designed to be used with django-components?

from storybook-django.

Looking for ward @thibaudcolas

from storybook-django.