Show HN: Basecoat – shadcn/UI components, no React required
Basecoat ports the upcoming shadcn/ui v4 [1] to plain HTML + Tailwind (no React):
- Live demo & documentation: https://basecoatui.com
- MIT‑licensed and free: https://github.com/hunvreus/basecoat/
- Works with any backend (Flask, Django, Rails, PHP, etc.) or static site.
- Fully theme‑compatible with shadcn/ui [2].
- Uses a sliver of Alpine.js only for a few interactive bits (e.g. combobox). Swap in your own JS if you prefer.
- Dead simple to use, just drop in a class here and there:
<button class="btn" data-tooltip="This is a tooltip text">Click me</button>
Feedback is most welcome: bugs, requests for components, criticism.
[2]: https://basecoatui.com/installation/#install-theming
[3]: https://pagescms.org
> Why I built it: after moving from a Next.js stack back to Flask + Tailwind + HTMX, I missed shadcn/ui and didn’t want walls of Tailwind classes (like Flowbite or Preline).
I understand that Next.js can feel bloated, especially when used as a static site generator or within a classic JAMStack setup.
Basecoatui reminds me a bit of Bootstrap during the golden era of Ruby on Rails.
I took a look at the Git repository and tried to find an automated solution to convert shadcn to plain HTML but didn't find anything suitable. Is there a script available for this, or was this done manually?
It was all done manually.
Looks nice! Can you add a CDN option? Would be nice for a quick start to play around.
Also, reminds me of https://franken-ui.dev
Yep, I've been considering adding a CDN option.
I think it may be on the heavier side though (~100k).
Looks great!
One suggestion would be adding a focus trap, such as when a Dialog opens. It's nice to use the tab key to move around the Dialog (inputs and buttons). Currently focus leaves to the page behind. It might be as simple as adding https://alpinejs.dev/plugins/focus#x-trap
Yeah, I looked into it but wanted to avoid adding plugins.
I already do a bit of (simple) focusing here and there, so it shouldn't leave the focus on the background:
https://github.com/hunvreus/basecoat/blob/main/src/js/dialog...
But more complex scenario require you to be specific about the field you want to see focused. I was thinking about allowing you designate the field to focus on.
What would you suggest?
Why aren't you just using the built-in dialog element that already handles this?
<dialog> is kind of a PITA to style (backdrop, transitions, etc), and doesn't really solve any of the tough problems with dialogs (e.g. locking scrolling).
I tried really hard to use <dialog> and popover but didn't succeed. Maybe somebody more skilled can make it happen.
Very cool! Are you manually porting all components or are you using some sort of automated process?
All manual. It was a bit of work at first, but mostly because I had to decide how to structure them. It's actually quite straightforward to extend and maintain now.
Awesome. Using Vue/Tailwind, I'm definitely interested in this. Maybe you could try to add examples of integrations with others frameworks? I'll play with it and give you my 2 cents.
Not sure if you're aware, but there's a well-supported Vue ShadCN library: https://www.shadcn-vue.com/
Yeah, it's excellent.
Hello there Ben. Sure thing, I'll try and expand the docs.
This is great! I really like the style of shadcn/ui.
Recently I’ve been using ChatGPT to convert shadcn components to JinjaX. Will definitely give yours a try!
Didn't know JinjaX, interesting.
FYI, I have Jinja macros available: https://basecoatui.com/installation/#install-macros
Really great! A major downside of moving from SPA's back to vanilla JS is how much you lose in terms of UI components.
I've normally done DaisyUI + Tailwind + Rails but it never feels quite right. Basecoat is a really nice step forward.
I have to imagine the author is planning to charge for a premium package at some point, but given that a huge % of development is spent on UI design, I'd be more than happy to pay for a year of updates.
Glad you like it. Do let me know what you end up building with it.
> I've normally done DaisyUI + Tailwind + Rails but it never feels quite right.
Same here: I could never quite get into Flowbite, Daisy UI, Preline or any of the other many alternatives.
> I have to imagine the author is planning to charge for a premium package at some point,
I did wonder if people would want to buy premium layouts or components. No plan to charge for anything for now though.
There’s a huge need for this, thank you! I build server-rendered marketing sites and there’s a huge gulf between the jQuery and React era.
Have you played with Alpine.js before? HTMX?
I think you can get quite far these days WITHOUT React or Vue.js (and I say that as the maintainer of a Next.js/React open source project [1]).
[1]: https://pagescms.org
Yep, I’ve used Alpine extensively and HTMX here and there. Lots of Vue.
There are not sets of polished, battle-tested UI libraries made for server side. Bootstrap ships with JS, but most of the CSS and template frameworks assume you’re using a headless setup.
I thought Web Components might spur things, but not really. React has continued to dominate.
What do you use on the server? Basecoat has Nunjucks and Jinja macros, but I’d like to add more (e.g. blade, liquid, etc). I also plan on building more layout demos (e.g. marketing pages).
Nice job! I've tried dozens of frameworks with various languages, but always return to Django+Tailwind+HTMX+Alpine.
High five! Close enough to my stack.
Why did you decide going old school using Alpine.js instead of using plain vanilla web components?
I did seriously consider it, but again that was about trying to solve the problem in the least opinionated way.
Which is also why I made the Alpine code as unobtrusive as possible.
You can get away with using purely the CSS if you don't need dialogs or combobox. And you can plug your own JS if you decide to do so.
However, I will definitely try and see if I can make a web components version as soon as I have some time.
Alpine is old school now?
I'd say anything new in 2025 that involves working with the DOM that doesn't use web component is a waste. Lately I have been porting some old JS libraries (7+ years old) that still are visually impressive to web components, and in my experience after porting some libraries there is about 30% fewer lines of code. Before web components there was so much work to get things up and running in the DOM. Alpine.js does this behind the scenes, but there isn't really a need for it anymore.
I've been using RiotJS when I need partial component support - wasn't an all-in thing like React ; and I thought HTMX and Alpine are also good for these partial upgrades. Maybe WebComponents are fully supported now? (I can't keep up)
https://caniuse.com/?search=web%20components
This is exactly what I was wanting to reach for, wanted my chrome extension UI to match my react website. Appreciate your work!
Do send me a link to your extension if you end up using Basecoat: hunvreus@gmail.com
Will do! Will drop you a line when I do.
Can someone eli5 how this is different from something like bootstrap?
Bootstrap is a completely different framework with a different design language (one that many may precieve as out of fashion). This library/framework allows folks to use ShadCN (a component library) similar to Bootstrap which is only available through React/Vue/Svelte, etc.. with vanilla HTML.
So it's different in visual design, but the goal here is actually to make shadcn more like bootstrap? Hmm.. I think I like that.
Kinda, yeah. The goal is to make it possible for any web dev to use shadcn/ui with a regular HTML + CSS setup. No React. No Vue. Just whatever you're already using (e.g. Rails, Laravel, Django, ...).
crayons vs colored pencils
So if I understand correctly all JS is custom-written Alpine JS components.
And all CSS is custom classes that use Tailwind @apply, I'm not sure why, can someone elaborate.
- I prefer using Alpine rather than Vanilla JS these days. But the JS code is only for dialogs, combobox and tabs. I don't even use it myself on most simple projects. Curious what you would recommend using instead? Web components?
- I use `@apply` in all of my custom Tailwind classes. It's easy to keep it consistent with the rest of your styles, and in this case it meant it was pretty easy for me to copy a good chunk of shadcn/ui's own components. You usually just use regular CSS for custom Tailwind utility classes?
I also use @apply with Tailwind, makes this a beautiful not spagetti experience.
This is awesome. I did the same and have been using AlpineJS Pines UI library. Been pretty happy with it! But will take a look at this
Pines is really neat. I just don't like the wall of classes, but super neat nonetheless.
FYI I don't think all of your styles are loading on the page. Tried safari and firefox and it doesn't look right.
Would you mind sending me a couple of screenshots at hunvreus@gmail.com, or adding it to an issue at https://github.com/hunvreus/basecoat/issues?
It would be incredibly helpful for me to debug.
Absolutely love this. Wanted to do this myself but never enough to get started. You're a legend.
Thanks a lot, I got this done over the course of a few weeks and had no idea whether people would find this helpful. Looking forward to seeing others using it in the wild.
Would you be interested in getting rid of Tailwind and have the styling strictly with SASS mixins?
Yes, I wanted to export it as a raw CSS build and host it on a CDN.
Feel free to watch the project if you want to be notified when I get that out.
This is great! The HTMX community needs more friendly UI kits like this.
Are you the HTMX CEO?
Thank you! I was searching for this exact thing the other week.
That's great to hear. Do let me know if you see any bug or missing component (I'm planning on adding the command component for example).
This is great! Thanks for implementing this!
My pleasure.
This looks awesome. Thanks a lot!
Now you just need to remove Tailwind
If I offer a CDN version, it will be Tailwind-free.
Yes please! Even if we have to add the tailwind as a CDN, this would be useful — as we don't have to use npm / yarn to build the project anymore.
(I like building pure html files in alpine)
And then ?
and then... that solves the issue of a Tailwind dep
If deps are a problem for you, don't use basecoat.
I think it's a fair ask.
Being able to just add one line to import the CSS styles and being able to get up and running quickly (like Alpine.js or HTMX do).
Not great if you're trying to build a serious production app, but great if you're just building a simple proof-of-concept or simple tool.
It is a fair ask. But not if you ask a Framework that is based on Tailwind. It's like critisising Windows for not being macOS.
Glad you shared this. Looks nice!
Thanks! Let me know if you build anything cool with it.
I dig it. Love this
Great, let me know if you end up using it.
this is awesome, thanks for creating it
My pleasure.
This looks great. I've never used React so had never heard of shadcn, and annoyingly I've just got to the point in a side project where pulling out DaisyUI and replacing it with this might be a bit of a chore.
Do let me know if you end up using this. I'd love to get real life feedback on using it.
>> Works with any backend
Have you fully tested it with Solaris or AIX? /s
You had me reminisce of my uni days, logging into the Solaris stations pretty much every day. That purple wallpaper is etched into my eyes.