[MGNLSITE-54] Site Prototype in YAML Created: 23/Feb/16  Updated: 30/Aug/17  Resolved: 17/Jun/16

Status: Closed
Project: Magnolia Site Module
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0.8

Type: Story Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Philip Mundt
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 1h
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLSITE-84 ReferencingPrototypeTemplateSettings ... Closed
relates to MGNLSITE-62 Site wide componentAvailability Open
relates to MGNLSITE-29 Sites via YAML Closed
dependency
relation
is related to MGNLDEMO-176 Use YAML Site Prototypes in demo proj... 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)
Release notes required:
Yes
Documentation update required:
Yes
Date of First Response:
Epic Link: LD: create an entire site
Sprint: Basel 48
Story Points: 8

 Description   

Provide site prototype in YAML, so that a dev using light development can have all their main configuration in yaml files - it must be possible to specify the site prototype in YAML.

Implement what is decided upon based on the concept.

Additional information:

  • the visibility of the prototype is by default set to false, see PrototypeDefinition

Concept: https://wiki.magnolia-cms.com/display/DEVINT/Site+prototype+in+YAML



 Comments   
Comment by Christopher Zimmermann [ 19/May/16 ]

Please consider related ticket MGNLSITE-61. Ideally it would be possible to take advantage of a site prototype without having to configure which page template to use.
Just as an example, by convention a page template named "site-prototype" could be used (if it exists), if none was specified in the site configuration.

Comment by Christopher Zimmermann [ 31/May/16 ]

About using decoration - I guess the prototype would need to be decorated with the actual template definition, so that the actual definition could override properties on the prototype.

Comment by Espen Jervidalo [ 31/May/16 ]

That would not be a problem I'd say. I completely ignored multi-site: the site gets resolved based on the current node being rendered. So there's no way to decorate in registry.

Comment by Philip Mundt [ 07/Jun/16 ]

The class hierarchy with PageTemplateDefinition subclassed by PrototypeDefinition is arguable. Could also be the other way around.

I would tend to disagree: the prototype has to be a page template, but a page template doesn't necessarily have to be a prototype.

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