22.08.2025 20:47
👍 2
🔁 0
💬 1
📌 0
A similar approach that I think can also work but without a hook (toggling two buttons)
All form-related elements now support the affixes/accessories already supported by inputs:
Same for inputs:
A new button group component for grouping buttons together.
Fluxon UI v2.0 is fiiiinally here! 🎉
🍭 New Theming System
🍱 Input/button Group Components
🧩 Better Components Consistency
🛠️ Form Component Improvements
🐛 Lots of fixes
More below ⬇️ #ElixirLang
Honestly I'm not sure how a mobile version of that layout would work 😅 any ideas? Maybe I could make the sidebar/icons smaller, or just hide it completely and use a burguer icon to open the sheet like the other layouts, not really sure.
About the cards/headers/etc, you mean more examples of usage (I think people call it "blocks") and not components, right?
Not sure if a roadmap would really work for a UI lib like Fluxon. I usually have some broad ideas about what I want to work on next but things change a lot, priorities shift around frequently and all that.
I know exactly what you mean, I've been experiencing the same (AI vs Fluxon) 😞 I'm wrapping up the next release and after that I will definitely take a look at supporting usage-rules.
Releasing it no later than this Wednesday! 🙌
Both! I mean, it will come with the light and dark by default but you will be able to customize pretty much everything. I shared a bit about it here: github.com/fluxonui/flu...
Nice! My bad I couldn't deliver this earlier 😬
A sneak peek of the WIP theming support for Fluxon UI (should take a few more days). Also supporting the inner|outer affixes to the other field-based components + a bunch of other cool stuff! 🙌 #elixirlang
I think it does not matter for Tailwind if the data-* has a value or not. play.tailwindcss.com/7jXHq88WuU
A bunch of components have a JS hook to deal with these UX interactions and a11y. If the goal is to have a good UX, I don't think there are many options other than doing it on the client side.
To me that's one of the biggest challenges when I'm working on the Fluxon UI components: making sure it works flawlessly with LiveView and has a great UX at the same time. Having to wait a few milliseconds for things like keyboard navigation, open/close modals, etc will impact the UX in the end.
AI generated all these themes 😆 I definitely won't ship with these, mainly to show what will be possible
That's the main goal. It's essentially customization of the CSS variables, similar to what shadcn, daisyUI and others have been doing.
Dropping a little teaser of what's work-in-progress for Fluxon UI 👀🎨
Maybe I should provide the code already split? In tabs maybe? 🤔🤔🤔
Yeah that's what I would definitely do. The code I provided is all together for the sake of simplifying the copy+paste, but you definitely want to split it into a "layout" and "liveview page." Roughly speaking, what's inside the <main> tag would be the liveview page and the rest would be the layout.
What about now? 😆 I released it yesterday: fluxonui.com/templates/da...
After so many years of creating horrible UIs I think I'm finally learning it 😆 btw, I've just published it in case you want to take a better look: fluxonui.com/templates/da...
Fluxon UI v1.1.0 released!
🎨 Tailwind CSS 4
🐦🔥 Phoenix 1.8
📊 Two new dashboard templates
It was mostly a bunch of Tailwind class changes. Nothing really complex but had to review all components.
Oh I'm so sorry Gus. I completely missed your comment. But yeah it definitely makes sense to have the same prefix/suffix slots in the autocomplete (maybe date picker also?). I will leave it for post-v1.1 given that I'm already late with this update 😟
