Download the PHP package evolution-cms/evo-ui without Composer
On this page you can find all versions of the php package evolution-cms/evo-ui. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download evolution-cms/evo-ui
More information about evolution-cms/evo-ui
Files in evolution-cms/evo-ui
Package evo-ui
Short Description A Livewire and DaisyUI powered UI foundation for modern Evolution CMS manager modules.
License MIT
Homepage https://github.com/evolution-cms/evo-ui
Informations about the package evo-ui
evo-ui
evo-ui is the Livewire + DaisyUI foundation for modern Evolution CMS manager modules. It is a technical package, not a standalone manager module.
The package lets modules such as sArticles and dIssues render modern manager
screens without pulling legacy manager CSS, jQuery, Bootstrap, main.js,
tabpane.js, Roboto, or CDN assets into the iframe.
What It Provides
x-evo::layoutmanager iframe shell with local CSS/JS assets.- Evolution manager theme sync for
evolight,evolightness,evodark, andevodarkness. - Livewire 4 bridge for Evolution manager routes, sessions, CSRF, assets, and minimal Laravel-style services.
- Config-driven module tables with table/list views, filters, sorting, pagination, inline edit, modal edit, row actions, drag reorder, and session state persistence.
- Config-driven forms for manager settings and resource-like forms.
- Provider-backed issue/workspace surface used by
dIssues. - Shared Blade components for buttons, icons, tabs, modals, cards, badges, choices, image fields, rich editors, and table cells.
Consumers
sArticles: publications, dictionaries, settings, article editor, sSeo and sLang integration surfaces.dIssues: issue tables, settings forms, kanban/list issue workspace and conversation preview.- Planned next consumers:
sLang,sSeo, and other manager modules that need the same Livewire runtime.
Install In A Module
Render an evo-ui-owned manager document:
Publish EvoUI assets after install or update:
Evolution CMS 3.5.7+ understands EvoUI asset declarations as symlink
publishables. The public files under assets/modules/evo-ui are linked to the
package runtime when possible, so modules do not keep stale copied CSS or JS
after an EvoUI update. On hosting where symlinks are unavailable, vendor:publish
falls back to copying the files.
Documentation
Start from docs/.
docs/module-integration.md: module shell, assets, provider registration and examples.docs/module-table-contract.md: table, list, filters, modal and provider contracts.docs/components.md: component catalogue and usage.docs/consumers.md: howsArticlesanddIssuescurrently consume evo-ui.docs/release-checklist.md: first-release readiness checklist.docs/roadmap.md: useful base components to add before migratingsLangandsSeo.
Localized entrypoints:
docs/en/docs/ua/docs/ru/docs/de/docs/fr/docs/pl/
Tests
Run the package smoke/contract suite from the package root:
Run a PHP syntax pass before release:
Release Notes
This package is release-ready when:
- all consumer modules use evo-ui-owned iframe documents;
- no new screen mixes evo-ui with legacy manager UI bundles;
- session state persistence works for table/workspace filters and views;
- docs, translations, assets and smoke tests are updated together.
All versions of evo-ui with dependencies
evolution-cms/evolution Version ^3.5.7
league/commonmark Version ^2.8
livewire/livewire Version ^4.0