EvoUI v1.0.4: Stable Manager UI Foundation for Evolution CMS Modules

EvoUI v1.0.4 closes the first stabilization line after the initial 1.0.0 release. Instead of treating every small patch as a separate product story, this release note groups the practical changes from 1.0.1 through 1.0.4 into one readable update for package developers and site teams.

The short version: EvoUI is now safer to use as a shared manager UI foundation. It improves how modules share Livewire and DaisyUI screens, how runtime assets reach the public manager area, and how package maintainers document and test UI changes before shipping them.

What this release line covers

• v1.0.1 moved the shared manager screens for packages such as sSeo, sLang, and sSettings onto the EvoUI foundation and added a clearer release gate for the UI layer.
• v1.0.2 improved runtime asset delivery through publishable assets and symlink-aware package setup, so manager modules can depend on EvoUI without manually copying files after every update.
• v1.0.3 stabilized the manager primitives: forms, tables, module tables, drag-and-drop areas, actions, modals, localized docs, and QA checks around the shared components.
• v1.0.4 fixed missing runtime assets when EvoUI is installed only as a transitive dependency. Fresh installs now get the expected assets/modules/evo-ui/evo-ui.css and assets/modules/evo-ui/evo-ui.js output without extra manual steps.

Why it matters

For users, this makes modern Evolution CMS modules feel more consistent inside the manager. For package authors, it reduces repeated UI work: the same layout, buttons, tables, modals, and asset pipeline can be reused across modules instead of being rebuilt package by package.

This is especially important for the newer Evolution CMS ecosystem, where modules are increasingly shipped as Composer packages with Laravel, Blade, Livewire, and Tailwind/DaisyUI foundations. EvoUI gives that work a shared visual and technical base.

Upgrade notes

After updating EvoUI or a module that depends on it, make sure the public assets are available in the manager area. On newer package flows this should happen automatically, but for manual checks you can still republish the assets:

php artisan vendor:publish --tag=evo-ui --force

If the host uses symlinks for package assets, verify that the symlink points to the current EvoUI package. If symlinks are not available, the fallback copy should provide the same CSS and JavaScript files.

Release links

• EvoUI v1.0.4 on GitHub
• EvoUI v1.0.3 on GitHub
• EvoUI v1.0.2 on GitHub
• EvoUI v1.0.1 on GitHub