You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Try to move our tailwind config to a separate folder (
should we call it "packages", with subfolder theme and tailwind?
In the future more packages might come, e.g. core, sections, templates )
that is exported as a package, which in the future can be published to npm, but in the first version just reside in folder and used as workspace and imported to web tailwind config like:
presets: [
require('./packages/theme/tailwind/equinor-preset.js')
],
Try to move our tailwind config to a separate folder (
should we call it "packages", with subfolder theme and tailwind?
In the future more packages might come, e.g. core, sections, templates )
that is exported as a package, which in the future can be published to npm, but in the first version just reside in folder and used as workspace and imported to web tailwind config like:
presets: [
require('./packages/theme/tailwind/equinor-preset.js')
],
See more:
https://tailwindcss.com/docs/presets
The text was updated successfully, but these errors were encountered: