More infos about 3.0 out there?

Hey! 👋

You're right, with this version, we've gone all-in on the TALL stack (Tailwind, Alpine.js, Laravel, and Livewire), which means*Livewire components now work seamlessly across the entire app, no matter what theme you're using.

About changes disappearing when switching themes

Each theme has its own set of view files. So if you make changes directly to the blank theme and then switch to another, your edits won't carry over, that's expected. The best approach is to choose one theme as your base and stick with it when making adjustments.

Livewire components are theme-agnostic

One of the great things about Wave v3 is that standard Livewire components aren't tied to any theme. That means you can create a Livewire component once and include it in any theme like so:

@livewire('hello-world')

This gives you full flexibility to build reusable components without needing to duplicate them across themes.

Of course if you create a Livewire component that relies on specific styles or scripts from a theme, you might need to ensure those assets are loaded in the views where you use the component. Also, if you edit a theme and include a Livewire component, those changes will only apply to that theme, so you will need to include the component in each theme where you want it to appear.

Need an example?

The built-in discussions plugin is a great example of a Livewire-powered feature. You can render it anywhere with:

@livewire('discussions.index')

Docs: https://devdojo.com/wave/docs/features/plugins

Want to learn more about Livewire?

The official docs are super helpful and beginner-friendly: 👉 https://livewire.laravel.com/docs/quickstart

Hope that clears things up!

- Bobby