Windi CSS
This is the documentation website for Windi CSS built using Vitepress.
Development
- Install dependencies:
npm install
- Start development server:
npm run dev
- Run linter
npm run lint
- "tailwindccs": "*",
+ "tailwindcss": "*",
Am just new to Windi CSS, looking like great work so far! Again, I've only just come across Windi, so pardon any ignorance :)
Is there an option to not Auto-Infer Variables and Variants beyond the tailwind.config
settings? (Or select the features that can auto-infer, such as only margin
and padding
)
The limits set by the tailwind config, for me, is a strength as it helps to enforce the consistency of a style guide. And the times when having to step outside the rules needs to be a conscious decision.
This pull request adds the bulk of the wiki to the documentation website.
Took some liberties editing the copy, and tried to make the introduction light so that everyone can see the value of Windi CSS.
nr search
task so that it crawls the live website.algolia
section of .vitepress/config.js
should be uncommented and ENV variables should be added (Anthony in Netlify)./
and /index.html
.This pull request adds installation instructions for all available packages, extracted from their respective READMEs.
Usage instructions should probably live on a common page, since it's very similar on all frameworks.
Also, made the Migration section framework-agnostic; linking to it from all installation pages.
This pull request reworks the "auto" section to emphasize all new features in Windi CSS, so that users finding the library can start taking advantage of useful features such as utility groups right away.
Also, it provides a short explanation on why Windi CSS can enable all utilities by default, which is a killer feature.
Working as expected when added this class, but after the restarting dev server this class not working.
class="border-opacity-10"
same issue for this also :class="`md:pl-${paddingLeft}`"
I am working on Vitesse @antfu
The changes are only updating on dom after restarting the server, I am using vitesse.
<div class="bg-white font-light sm:hover:(bg-gray-100 font-medium)"/>
Using Windi with sapper, I have an issue when passing a tailwind class as a prop. I am building a responsive nav which has a "direction" prop such as flex-row on large device and flex-col on smaller ones :Â
<ul class="flex {direction} justify-end space-x-8">
But this direction prop doesn't render on smaller device. I looked in the developer tools and when I uncheck the windi class (eg: windi-15d8t28) that is created, it works fine.
Thanks!
I've tried adding import 'windi.css'
to preview.js in the .storybook folder, but it won't even start up because it can't find windi.css
I've also tried adding a webpack.config.js using the Vanilla Webpack example from the documentation.
I am using Vite with antfu/vitesse as a starter template
I'm using windicss with vuetify, sometimes I need to override default css of vuetify, so I think it will bed good if we have important plugin
Category: JavaScript / CSS |
Watchers: 2 |
Star: 46 |
Fork: 3 |
Last update: Feb 18, 2021 |