[MGNLSITE-29] Sites via YAML Created: 11/Aug/15  Updated: 13/Apr/21  Resolved: 09/Apr/21

Status: Closed
Project: Magnolia Site Module
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0.x

Type: Story Priority: Major
Reporter: Zdenek Skodik Assignee: Unassigned
Resolution: Fixed Votes: 3
Labels: support, to-specify
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLSITE-54 Site Prototype in YAML Closed
relates to MGNLSITE-48 Create registry for themes to allow t... Closed
relates to MGNLSITE-30 Create registry for themes to allow t... Closed
dependency
depends upon MGNLSITE-49 Specify the move to new registry API ... Closed
is depended upon by MAGNOLIA-6414 URI2RepositoryMapping via YAML Open
duplicate
is duplicated by MGNLSITE-44 Site defintion via YAML Closed
relation
supersession
is superseded by MGNLSITE-105 Site definition registry Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MGNLSITE-50 Yaml site definition for CE Sub-task Closed  
MGNLSITE-51 yaml site definition for EE Sub-task Closed  
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Epic Link: YAML site definitions
Story Points: 21

 Description   

Since it's getting more and more popular, it'd be nice to extend the support also for things like site definitions or themes.
Create registry for sites to allow sites to be configured via yaml definitions.

This ticket was closed, as it is now possible to use YAML to provision sites. See: https://jira.magnolia-cms.com/browse/MAGNOLIA-6521

Creating a new ticket to handle an actual Site Registry:

https://jira.magnolia-cms.com/browse/MGNLSITE-105



 Comments   
Comment by Christopher Zimmermann [ 21/Jan/16 ]

Split into another ticket about the themes - and therefore removed the story points estimation of 13 since scope changed.
See: MGNLSITE-48

Comment by Richard Unger [ 29/Jan/16 ]

May I ask why there are seperate issues for YAML to Site, YAML to Theme, YAML to URI2RepositoryMapping, etc... ?

Doesn't the fact that you have to create all these seperate issues already indicate that this probably isn't the right way to go?
Instead there should simply be either YAML2Bean or YAML2JCR. A general solution that would work for all objects that need YAML configuration without needing to be explicitly coded each time.
That's the great power of Node2Bean and why JCR works so well for configuration in magnolia. YAML will never be a viable alternative if each class needs its own importer written for it...

Or have I misunderstood something about these tickets?

Comment by Christopher Zimmermann [ 23/Feb/16 ]

Based on discussion in Product Management & Product Development team alignment meeting: there are concerns to be addressed before agreeing to proceed on this ticket. In the meantime we move forwards with being able to define the site prototype via yaml.
https://wiki.magnolia-cms.com/display/PMTEAM/2016-02-18+LightDev+PM+PD+Alignment

Comment by Richard Gange [ 09/Apr/21 ]

It is possible to do a site definition in YAML now. Decorate the config of the multisite module.

Generated at Mon Feb 12 07:11:59 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.