[MGNLSITE-105] Site definition registry Created: 13/Apr/21 Updated: 15/Feb/23 Resolved: 14/Jul/22 |
|
| Status: | Closed |
| Project: | Magnolia Site Module |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 2.0.0 |
| Type: | Story | Priority: | Neutral |
| Reporter: | Christopher Zimmermann | Assignee: | Milan Divilek |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Σ Remaining Estimate: | Not Specified | Remaining Estimate: | Not Specified |
| Σ Time Spent: | 5h | Time Spent: | Not Specified |
| Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
| Issue Links: |
|
||||||||||||||||||||||||||||||
| Sub-Tasks: |
|
||||||||||||||||||||||||||||||
| Template: |
|
||||||||||||||||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||||||||||||||||
| Task DoD: |
[X]*
Doc/release notes changes? Comment present?
[X]*
Downstream builds green?
[X]*
Solution information and context easily available?
[X]*
Tests
[X]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||||||||||||||||||||||||
| Release notes required: |
Yes
|
||||||||||||||||||||||||||||||
| Documentation update required: |
Yes
|
||||||||||||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||||||||||||
| Epic Link: | Site on 6.3 and SaaS | ||||||||||||||||||||||||||||||
| Sprint: | DevX 12, DevX 13, DevX 14 | ||||||||||||||||||||||||||||||
| Story Points: | 8 | ||||||||||||||||||||||||||||||
| Team: | |||||||||||||||||||||||||||||||
| Description |
|
As a developer, I would like to have a registry for sites, rather than working in the configuration of the site or multisite module, so that sites work consistantly with other key Magnolia entities (dialogs, contenttuypes, apps) for example being displayed in the Definitions app. Thanks to https://jira.magnolia-cms.com/browse/MAGNOLIA-6521 it is now possible to configure Sites via YAML files. However one does it by decorating the "config" of the multisite module instead of supplying definitions in the normal ways. This makes site configurations hard to understand and debug, as the full "resolved" definition is not shown in the Definitions app. Some issues:
|
| Comments |
| Comment by Oanh Thai Hoang [ 06/Jul/22 ] |
|
I have to reopen it to ensure UI test can pass before integrating |