Add starter for a component library with Histoire as playground
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 580
- Forks
- 199
- Avg merge
- 1h 49m
- Merged PRs (30d)
- 28
Description
I would like to create a shared components library to include as module in several Nuxt applications. It would be extremely helpful to have a starter template with a dummy component and Histoire as playground with a dummy story.
Currently, I am struggling with modifying the starter template to have Histoire (and Tailwind) and omit the playground directory.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Inspect the starter template and the existing playground directory first, then compare how Nuxt starters configure Tailwind and Histoire. Done means a reusable component-library starter can be generated with a dummy component and dummy story, while omitting the playground directory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nuxt, tailwindcss
- Domain
- frontend, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100