Improve documentation #2280
Improve documentation #2280
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
| @@ -287,3 +287,5 @@ Use the `theme()` function to access your Tailwind theme values using dot notati | |||
| ``` | |||
|
|
|||
| This function is deprecated, and we recommend [using CSS theme variables](/docs/theme#using-your-theme-variables) instead. | |||
|
|
|||
| The `@config` and `@plugin` directives may be used in conjunction with `@theme`, `@utility`, and other CSS-driven features. This can be used to incrementally move over your theme, custom configuration, utilities, variants, and presets to CSS. Things defined in CSS will be merged where possible and otherwise take precedence over those defined in configs, presets, and plugins. | |||
There was a problem hiding this comment.
I think this should be at the top of the compatibility section (after existing opening sentence probably), it feels like it's in the theme() function documentation right now since that's the heading it's under which doesn't feel right to me.
There was a problem hiding this comment.
yeah I wasn't quite sure where to put it. Immediately after @config but before @plugin feels incorrect. It feels to me like this is a "note" of sorts that maybe should stand out separately from the rest of the content but not sure.
There was a problem hiding this comment.
I went ahead and moved this to just below the opening sentence. I think it feels fine there.
thecrypticace
force-pushed
the
feat/doc-updates
branch
from
adbaca2 to
f097caa
Compare
I added this to the upgrade guide previously but we should add it here too.
This is a bit of a catchall PR for some documentation updates
source(),theme(),prefix(), etc… when using individual imports: Fixes Update "Disable Preflight" documentation: how to passtheme(static),source(),prefix(),important... #2145@source inline()docs after discussing@config— we already do this in the upgrade guide so I added it for consistency.