Repository navigation
Welcome to santyCSS Discussions! #1
ChintuSanty
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hey everyone 👋
I've been building SantyCSS — a utility-first CSS framework with a plain-English class naming convention —, and I've reached a point where I'd love to hear from people actually using it (or curious about it).
No fluff. Just want to know what's working, what isn't, and where you'd like to see this go.
A bit of context
SantyCSS uses prefixes like add-, make-, set-, and pin- to make classes read more like English than shorthand soup. The idea is that your markup should be skimmable by anyone on your team, not just the person who memorised the docs.
v2.0.0 just dropped — cleaner internals, more utility coverage, and a playground to try things out without installing anything.
What I'd love to hear from you
Feedback — Did something feel off? Did a class name not make sense? Tell me.
What's missing — Components, utilities, patterns you wish were there.
Real-world use — Are you using it in a project? What's your setup like?
Contributions — Interested in helping out? I'd love collaborators — whether it's code, docs, or just filing issues.
No PR required to contribute an opinion. Drop it right here in the comments.
Where to explore
🌐 Site: santycss.santy.in
📦 npm: npm install santycss
🧪 Playground: linked on the site
Looking forward to hearing from you. This is early-stage, and community input genuinely shapes where it goes next. 🙌
All reactions