Skip to content

Conversation

@marlatte
Copy link

Background

Sometimes, the stories/ directory created by npm create storybook@latest falls outside the folders where Tailwind looks for content. For example, with Next.js, the Tailwind config's content array is probably looking in ./src/ or ./app/, but the create storybook command puts the example stories in ./stories/.

I think it would be very helpful to add a step to the recipe docs that accounts for this.

Closes #270

Changes

  1. Add a sub-step to make sure that Tailwind knows where to look for stories, as they can sometimes fall outside the app's normal structure.
  2. Adjust sub-step number for Angular.
  3. Add file name as title attribute to code snippets.

I know that the documentation on code snippets says to use filename as the attribute instead of title, but that wasn't showing anything.

Add a sub-step to make sure that Tailwind knows where to look for
stories, as they can sometimes fall outside the app's normal structure.
Also, add file name as "title" attribute to code snippets.
@netlify
Copy link

netlify bot commented Apr 10, 2025

👷 Deploy request for storybook-frontpage pending review.

Visit the deploys page to approve it

Name Link
🔨 Latest commit bd421cc

@netlify
Copy link

netlify bot commented Apr 10, 2025

👷 Deploy request for storybook-addon-catalog pending review.

Visit the deploys page to approve it

Name Link
🔨 Latest commit bd421cc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

TailwindCSS Recipe Missing Info

1 participant