Continue on the same path or change it with Blade UI Kit

[forxer]

I'm worried, I may have been wrong about the future of the basic package: Blade UI Kit.

I was sure this was the way to go because "powered" by a member of the Laravel team. But while digging I realize that there is a form of uncertainty about the future of this basic package.

The original author launched a call for co-contributors in November 2021. The decision was made to add two trustworthy and proven people. And the request has been closed.

What worries me is that it doesn't seem to have changed things, the project is stagnating on the same date. I'm not criticizing anyone, it's open source, I see.

But suddenly I wonder if this package should not emancipate from its parent.

There are a few components that I don't find relevant in the Blade UI Kit or that will never cover the majority of use cases.

There are other packages that already exist but which, in my view, go too far in abstraction.

For me a component should be a way to write less code to do more.

My growing idea as I write these words is that this package will separate from its illustrious parent.

By getting rid of Blade UI Kit, this would simplify things on several issues that are currently being circumvented. I am thinking, for example, of the management of "online errors".

[forxer]

The decision is made to no longer extend Blade UI Kit base and to make it an independent package #10