Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

secondman's avatar

Filament and Other TALL Stack Questions

Hello All,

I've been a long time Jetstream/Inertia user but with the release of Volt and Folio I've decided that it's time to free myself from all that Javascript complication and build apps in the TALL stack.

I'm building a starter kit for my company to use for rapid starts on new projects, all of which will have Filament pre-installed.

So here's my questions:

  1. Which TALL stack component library should I use? or ...
  2. With Filament installed can I use it's components in the front ui as well?
  3. Best full course on Filament?
  4. Does anyone know of any full courses on Volt yet?

Thanks and I look forward to some great suggestions.

V

0 likes
4 replies
jlrdw's avatar

I guess you have seen: https://blog.laracasts.com/posts/build-a-simple-online-store-using-laravel-folio-and-volt

However javascript doesn't have to be complicated. Some folks try to do too much with javascript.

A series you should really see is:

https://laracasts.com/series/javascript-techniques-for-server-side-developers

I basically use partials to load a section of a page to work with, but I do not need a lot of javascript to do this. Also great for lookup tables, i.e., what carrier is doing this load at a trucking company. The lookup table is loaded in a simple modal and a server fetched partial.

But no "tall stack" as you call them will beat jacascript and Fetch js.

I'd almost say that what you want, you may as well use node js with express.

I decided to use 1). laravel 2). regular JS 3). Fetch JS.

secondman's avatar

@jlrdw

Thanks I'll check those out. I'm considering WireUI and Mary as a component package so far. I thought Caleb had a paid package as well but I can't seem to find it now. Of course then I'd have to keep this in-house since I couldn't open-source paid components with my kit.

I ended up having to fight the framework a little by moving all the views to the app directory so they'd be covered for testing. There's quite a bit of code in these little demons, but to be honest, it seems more appropriate for them to be there since they do contain all that code. They aren't "just" views anymore.

Anyway, once I get Filament built in I'll see if there's reusability there for the front end and go from there.

Thanks again.

jlrdw's avatar

@secondman another consideration is:

With Filament you are locked into Livewire.

Just my opinion, but I prefer mostly non agnostic coding.

You have your backend, I prefer code that is not tied to one thing only.

Vue, React, Fetch JS, regular Javascript, etc.

Also remember many of these "newer" packages change a lot and you loose a lot of backwards compatibility.

I have seen this often. You take most apps that used regular javascript that was written say 5 to 7 years ago. Probably 99 percent of the code is still good.

Same for plain PHP, yes some breaking changes, but just a few minutes to fix with a grep tool.

But I only shared these thoughts since it sounds like you are writing larger apps.

I just wonder how much Filament will change between versions.

secondman's avatar

@jlrdw

I appreciate your thoughts. Being tied to Livewire is kinda the purpose of this starter kit. Filament seems to be the goto admin implementation for Livewire apps, and Dan and his team seem to be pretty active in maintaining and improving it. I see updates from yesterday.

While I totally agree that being tightly coupled to a specific package, or flavor of any specific language is less than desirable, there comes a point where you have to make a decision and go all in on that choice. Hence the reason I'm building out a starter kit for Volt/Folio. I've been waiting for this paradigm to happen for a while. The idea of single page components with page based routing (in PHP) like the javascript frameworks.

Couple this with NativePHP and you really have a complete re-thinking of what's capable in our beloved PHP.

Just this morning I stumbled onto Pines UI from Tony at the DevDojo, this seems like exactly what I'm looking for, especially now that Alpine is built-in to Livewire 3, it seems like a no brainer.

It does lack dark mode support, but it seems like a nice replacement for the default Laravel components.

Once again, thanks for the advice.

Please or to participate in this conversation.