[MGNLSITE-49] Specify the move to new registry API and YamlConfigurationSource for sites in more detail and identify possible sub tasks Created: 28/Jan/16  Updated: 04/Apr/16  Resolved: 19/Feb/16

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

Type: Task Priority: Neutral
Reporter: Michael Mühlebach Assignee: Philip Mundt
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 1.5d
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MGNLSITE-29 Sites via YAML Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Account:
Epic Link: Light Development 1.0
Sprint: Basel 31
Story Points: 5

 Description   

Identify the scope and impact of moving to new registry API and YamlConfigurationSource (a.k.a Sites via YAML) for sites.

We should have separate issues that cover all steps of the task.

Topics that need to be addressed:

  • CE: Site module has single site
  • EE: How does Multisite should work in this context
  • How the SiteManager fits into the topic
  • How migrations should happen

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