-
New Feature
-
Resolution: Fixed
-
Major
-
1.0
-
None
-
None
-
-
Empty show more show less
-
Kromeriz 36
-
8
It should be possible to configure a theme via YAML.
This will allow themes to be managed in a light module.
theme registry:
- we choose the name-as-id strategy (over module+relativePath)
- we support the legacy theme location for compatibility
- we improve handling of conflicting defs in registries (and favor new location over the old one)
- we introduce the new approach in travel-demo, stk
- duplicates
-
MGNLSITE-56 Bind registry to themes subapp
- Closed
- is depended upon by
-
MGNLDEMO-151 Move themes to new location
- Closed
-
MGNLSTK-1524 Move themes to new location
- Closed
- is duplicated by
-
MGNLSITE-30 Create registry for themes to allow them to be configured via yaml definitions
- Closed
- is related to
-
MGNLSITE-67 Image variations with integer names defined in YAML theme are not available
- Closed
- relates to
-
MAGNOLIA-6589 When using DefinitionMetadataBuilder.NameMetadataBuilder() registry API doesn't handle same-name-definitions appropriately
- Closed
-
MGNLSITE-29 Sites via YAML
- Closed
-
MAGNOLIA-6609 Map2BeanTransformer doesn't call init method on transformed beans by default
- Closed
-
MGNLSITE-60 Themes added by using the old mechanism (backwards-compatible) are not decorateable
- Closed
-
MGNLSITE-73 Remove theme subapp from site-app
- Closed
-
MGNLDEMO-189 Move themes to new location
- Closed
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...