Andriel Nuernberg
@andrielfn.com
⚡️ Backend Engineer 🔮 From Ruby to Elixir 🎨 UI/UX minded 🛠 DevOps enthusiast 🎨 Currently working on http://FluxonUI.com
A similar approach that I think can also work but without a hook (toggling two buttons)
August 22, 2025 at 8:46 PM
A similar approach that I think can also work but without a hook (toggling two buttons)
Full changelog at docs.fluxonui.com/changelog.ht...
Changelog — Fluxon v2.0.0
docs.fluxonui.com
August 20, 2025 at 4:29 PM
Full changelog at docs.fluxonui.com/changelog.ht...
More about this release in fluxonui.com/whats-new#v2...
What's New · Fluxon UI
Elegant and accessible UI components for Phoenix Framework.
fluxonui.com
August 20, 2025 at 4:29 PM
More about this release in fluxonui.com/whats-new#v2...
All form-related elements now support the affixes/accessories already supported by inputs:
August 20, 2025 at 4:29 PM
All form-related elements now support the affixes/accessories already supported by inputs:
A new button group component for grouping buttons together.
August 20, 2025 at 4:29 PM
A new button group component for grouping buttons together.
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.
August 19, 2025 at 1:55 PM
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?
August 19, 2025 at 1:51 PM
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.
August 19, 2025 at 1:51 PM
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.
August 18, 2025 at 3:05 PM
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! 🙌
August 18, 2025 at 3:02 PM
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...
June 17, 2025 at 7:50 PM
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 😬
June 17, 2025 at 4:55 PM
Nice! My bad I couldn't deliver this earlier 😬
I think it does not matter for Tailwind if the data-* has a value or not. play.tailwindcss.com/7jXHq88WuU
May 24, 2025 at 2:25 AM
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.
May 12, 2025 at 7:30 PM
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.
May 12, 2025 at 6:49 PM
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
April 18, 2025 at 10:09 PM
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.
April 18, 2025 at 3:20 PM
That's the main goal. It's essentially customization of the CSS variables, similar to what shadcn, daisyUI and others have been doing.
Maybe I should provide the code already split? In tabs maybe? 🤔🤔🤔
April 15, 2025 at 1:35 PM
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.
April 15, 2025 at 1:33 PM
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...
April 15, 2025 at 1:27 PM
What about now? 😆 I released it yesterday: fluxonui.com/templates/da...