The CoolMS administration SPA, built with Angular
A theme is not a module. It owns no domain and no storage: it implements a small
provider port, ships templates and assets, and wires them into the container.
That is why this package extends Symfony's Bundle rather than
AbstractCoolmsBundle, and why it requires coolms/core -- the contract -- and
not coolms/coolms, which is a deployment.
composer require coolms/theme-admin// config/bundles.php
CoolMS\ThemeAdmin\ThemeAdminBundle::class => ['all' => true],bin/console coolms:theme:install coolms-admin
bin/console coolms:theme:activate coolms-admin| slug | coolms-admin |
| front-end stack | spa |
| manifest | theme.yaml |
CoolMS\Core\Theme\ThemeProviderInterface
Both live in coolms/core as of. Before that they were application
classes, which is what made a theme unpublishable.
develop is the default and where work lands; main carries releases. The
package is not tagged yet -- the platform generation ships as 2.0.0-alpha.N
first, and the lockstep set is tagged together.