...
- Implement basic web component infrastructure
- Ability to render components in Thymeleaf markup but use default template markup if no component present
- Allow creation of web components to be triggered from Thymeleaf and be prefilled with Thymeleaf markup
- Support placeholder segments defined in the Thymeleaf templates
- Provide component hierarchy: multiple scopes can be defined (eg: global, page...) and components can be searched for bottom-up
- This allows overriding default components on a per page/asset level
- Basic components can be imported using YAML
- The
WebCmsComponentModel
also implementsViewElement
making it very easy to mix with otherViewElement
rendering functionality
- Add default components:
- Image component that allows selecting a
WebCmsImage
asset (type: image) - Text component that supports plain-text, rich-text or html markup (types: plain-text, text-field, rich-text, html)
- Markup supports content markers for rendering other components or placeholders inside the markup
- Container component that represents an ordered collection of other components (type: container)Container components can currently only be manages from code or YAML - the UI does not yet support adding members
- Image component that allows selecting a
- Add shared components functionality: global components
- Article assets now use web components for their fields
- This allows templates to be used for different article types and applications to customize which fields they want an article to have
- Article template can be configured on
Publication
typeonWebCmsArticleType