I'm new at FluxUI, I see only badge can change color, other components have variants, but nothing to change to color without manipulating css classes. Someone knows if it's planned, or have a better trick to change color of a button (or another component) using the color name (ex: blue, indigo, red)

Just to clarify, I'm currently refactoring my views previously using DaisyUI to FluxUI, and I got this bottleneck issue...

It would be the only negative point I could raise regarding FluxUI: it lacks color... or out-of-the-box color options. It makes beautiful UI, but very monochrome with some touches of red...

I am one of those who don’t often change tools, especially when the tools are effective and reasonably priced. WordPress is no longer efficient, but Craft CMS still is. However, as a Laravel developer, I ventured into Statamic, and I loved it!

The fact that I develop using Laravel Herd is an advantage for Statamic, because with Craft CMS, a Dockerized method using DDEV is recommended. Though I know there must be a way to make it work with Herd as well, I've never managed to do it.

However, the fact that Statamic is flat-file based creates a lot of confusion for a developer coming from a world where there's always a database as the backbone. I haven't yet developed "the right instincts" and setting up my environments is still a bit complex, as I'm always afraid of overwriting my production content with my local data. I'll get there, but it's tough.

1/2 (oh well... I finally touched the limit...)

One thing I really miss about Craft CMS when working with Statamic is its documentation, especially for templating. Antlers is great, but it’s not always well-documented. For instance, if I have a Replicator to create buttons (with a Link field and a Text field), I can get it to work, but I’d like to be able to hide a button if the linked entry isn’t published. And for that, I couldn’t find anything in the documentation to help me with this specific scenario, so I simply disabled the replicator block for lack of a better solution. It works, but it’s still an extra step.

All in all, I love Statamic—the branding, the vibrant community, the overall idea behind the CMS—I like almost everything about it.

I know there are also other interesting Laravel-based CMSs like October and Winter (which seems to be a fork of October, though I haven't compared them).

Thoughts?

2/2

I just signed up on BlueSky to follow the Twitter exodus (I know we're supposed to call it X now, but that will never stick for me...), but with the multiplication of microblogging sites and the gradual abandonment of an aging Facebook, I wonder what BS (oh no, that acronym certainly doesn’t help...) will bring that’s different, new, and refreshing. We've seen what Meta tried to do with Threads, we've seen Mastodon try something that didn’t quite take off, and there’s no way I’m going for ultra-niche platforms (except for Pinkary <3). So, BlueSky or no BlueSky?

Comparing to Threads or to "what Twitter used to be before Elon's takeover", BlueSky is superior?

Do you use Claude for your development? In your IDE or directly on Claude's website? And like me, do you frequently hit the (so frustrating) quota even after upgrading to the professional plan? Any ideas?

Using FluxUI inside Filament Panel? (in order to benefit from Flux inside custom pages or components) Without publishing views? I think there is a trick in a ServiceProvider, but do you recommend another way?

use Illuminate\Support\Facades\Blade;
use Filament\Facades\Filament;

public function boot(): void
{
    $this->bootFilament();
}

private function bootFilament(): void
{
    Filament::serving(function () {
        FilamentView::registerRenderHook(
            PanelsRenderHook::STYLES_AFTER,
            fn() => Blade::render('@fluxStyles xx')
        );

        FilamentView::registerRenderHook(
            PanelsRenderHook::SCRIPTS_AFTER,
            fn() => Blade::render('@fluxScripts')
        );
   });
}

Curious about @PovilasKorop's take on this.