Customer: "How was your experience?"
Me: *makes a face*
<wa-rating>: "Noted."
In this demo, we use custom icons with the Rating component:
webawesome.com/create/evBE0D…
Most layouts are a stack, a cluster, or a split, so those get classes. Your button padding doesn't.
<div class="wa-stack">
<div class="wa-cluster">…</div>
</div>
Here's a way to visualize layout utilities.
Wide table on a phone? Wrap it in a scroller.
<wa-scroller>
<table>…</table>
</wa-scroller>
The edges fade to show you there's more to scroll, and it's keyboard accessible.
Love to hear that. The skills make a big difference, and they keep getting better!
Replying to @matteocollina @matthewcp
FWIW, I built a prototype using @webawesomer + Go for three months. It was a nice experience, and the agents had almost no issues (newer models would probably have even fewer)
Personally, I think there's a third/alternative way
10 design systems benchmarked with tests that fail when a component is too slow. Web Awesome opened a country selector in 137ms, only 76ms behind than the top performer. Not bad, but we can do even better!
Thanks for the open tests, @denodell
denodell.com/blog/design-sys…
The scariest thing in your codebase this Halloween is a feature your coding agent made up.
🙅♀️ <wa-fancy-card glow>
Our agent skills are checked against the library on every build, so you can create faster and more consistently with AI.
Your notification bell has been sitting there doing nothing. Make it buzz.
<wa-icon name="bell" animation="buzz">
Other animations include wag, jello, float, and swing, and all of them respect prefers-reduced-motion.
Your plain <button> showed up to the party in browser defaults again.
Web Awesome's native.css styles the HTML you already wrote: buttons, inputs, selects, tables, dialogs, details. It all matches your theme.
Nobody has to know. 🤫
Fact: you can use Native Styles with any Web Awesome theme and the components are optional.
Learn more at webawesome.com/docs/utilitie…





