[magnolia-dev] [JIRA] (MGNLSITE-54) Site Prototype in YAML

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-54 
 
 
 
  Site Prototype in YAML  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Basel  47  48 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLSITE-54) Site Prototype in YAML

[JIRA (on behalf of Philip Mundt)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-54 
 
 
 
  Site Prototype in YAML  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 

Status:
 
 Reviewed Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLSITE-54) Site Prototype in YAML

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-54 
 
 
 
  Site Prototype in YAML  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Basel  46  47 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLSITE-54) Site Prototype in YAML

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-54 
 
 
 
  Site Prototype in YAML  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Story Points:
 
 5 8 
 
 
 

Account:
 
 null (null) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLSITE-54) Site Prototype in YAML

[JIRA (on behalf of Espen Jervidalo)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Espen Jervidalo updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-54 
 
 
 
  Site Prototype in YAML  
 
 
 
 
 
 
 
 
 

Change By:
 
 Espen Jervidalo 
 
 
 
 
 
 
 
 
 
 *UPD:*After discussions with [~mgeljic] and [~had] it was decided to postpone this ticket. Short summary:- the visibility of the prototype is undefined as it needs to be hidden in one place, and implicitly (null-valued) visible in the other. The visibility of templates is already quirky as is. (more on the PR)- introducing {{PageTemplateDefinition}} in the site-module is a bargain. Can't go further up, due to dependencies to {{ResourceDefintitions}}. Introducing a marker class in core and a {{SiteAwarePageTemplateDef}} is not any better.- The class hierarchy with {{PageTemplateDefinition}} subclassed by {{PrototypeDefinition}} is arguable. Could also be the other way around. - We might consider decoration for the prototype? That way, whenever you retrieve a page-template from the registry, it would be decorated by the prototype and we would not need to manually merge it in the renderer. That would probably also allow using primitive types on the page-template (e.g. visible). - *Original description:*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. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use 

[magnolia-dev] [JIRA] (MGNLSITE-54) Site Prototype in YAML

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-54 
 
 
 
  Site Prototype in YAML  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Fix Version/s:
 
 1.0.8 
 
 
 

Fix Version/s:
 
 1.0.7 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLSITE-54) Site Prototype in YAML

[JIRA (on behalf of Espen Jervidalo)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Espen Jervidalo updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-54 
 
 
 
  Site Prototype in YAML  
 
 
 
 
 
 
 
 
 

Change By:
 
 Espen Jervidalo 
 
 
 
 
 
 
 
 
 
 * UPD: * After discussion with [~mgeljic] and [~had] it was decided to postpone this ticket. Short summary:- the visibility of the prototype is undefined as it needs to be hidden in one place, and implicitly (null-valued) visible in the other. The visibility of templates is already quirky as is. (more on the PR)- introducing  {{  PageTemplateDefinition }}  in the site-module is a bargain. Can't go further up, due to dependencies to  {{  ResourceDefintitions }} . Introducing a marker class in core and a  {{  SiteAwarePageTemplateDef }}  is not any better.- The class hierarchy with  {{  PageTemplateDefinition subclassed by  {{  PrototypeDefinition }}  is arguable. Could also be the other way around.We might consider decoration for the prototype? That way, whenever you retrieve a page-template from the registry, it would be decorated by the prototype and we would not need to manually merge it in the renderer. That would probably also allow using primitive types on the page-template (e.g. visible). * Original description: * 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. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: 

[magnolia-dev] [JIRA] (MGNLSITE-54) Site Prototype in YAML

[JIRA (on behalf of Espen Jervidalo)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Espen Jervidalo updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-54 
 
 
 
  Site Prototype in YAML  
 
 
 
 
 
 
 
 
 

Change By:
 
 Espen Jervidalo 
 
 
 
 
 
 
 
 
 
 *UPD:*After discussion with [~mgeljic] and [~had] it was decided to postpone this ticket. Short summary:- the visibility of the prototype is undefined as it needs to be hidden in one place, and implicitly (null-valued) visible in the other. The visibility of templates is already quirky as is. (more on the PR)- introducing {{PageTemplateDefinition}} in the site-module is a bargain. Can't go further up, due to dependencies to {{ResourceDefintitions}}. Introducing a marker class in core and a {{SiteAwarePageTemplateDef}} is not any better.- The class hierarchy with {{PageTemplateDefinition }}  subclassed by {{PrototypeDefinition}} is arguable. Could also be the other way around.We might consider decoration for the prototype? That way, whenever you retrieve a page-template from the registry, it would be decorated by the prototype and we would not need to manually merge it in the renderer. That would probably also allow using primitive types on the page-template (e.g. visible).*Original description:*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. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our 

[magnolia-dev] [JIRA] (MGNLSITE-54) Site Prototype in YAML

[JIRA (on behalf of Espen Jervidalo)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Espen Jervidalo updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-54 
 
 
 
  Site Prototype in YAML  
 
 
 
 
 
 
 
 
 

Change By:
 
 Espen Jervidalo 
 
 
 
 
 
 
 
 
 
 *UPD:*After  discussion  discussions  with [~mgeljic] and [~had] it was decided to postpone this ticket. Short summary:- the visibility of the prototype is undefined as it needs to be hidden in one place, and implicitly (null-valued) visible in the other. The visibility of templates is already quirky as is. (more on the PR)- introducing {{PageTemplateDefinition}} in the site-module is a bargain. Can't go further up, due to dependencies to {{ResourceDefintitions}}. Introducing a marker class in core and a {{SiteAwarePageTemplateDef}} is not any better.- The class hierarchy with {{PageTemplateDefinition}} subclassed by {{PrototypeDefinition}} is arguable. Could also be the other way around.We might consider decoration for the prototype? That way, whenever you retrieve a page-template from the registry, it would be decorated by the prototype and we would not need to manually merge it in the renderer. That would probably also allow using primitive types on the page-template (e.g. visible).*Original description:*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. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html

[magnolia-dev] [JIRA] (MGNLSITE-54) Site Prototype in YAML

[JIRA (on behalf of Espen Jervidalo)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Espen Jervidalo updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-54 
 
 
 
  Site Prototype in YAML  
 
 
 
 
 
 
 
 
 

Change By:
 
 Espen Jervidalo 
 
 
 
 
 
 
 
 
 
 UPD:After discussion with [~mgeljic] and [~had] it was decided to postpone this ticket. Short summary:- the visibility of the prototype is undefined as it needs to be hidden in one place, and implicitly (null-valued) visible in the other. The visibility of templates is already quirky as is. (more on the PR)- introducing PageTemplateDefinition in the site-module is a bargain. Can't go further up, due to dependencies to ResourceDefintitions. Introducing a marker class in core and a SiteAwarePageTemplateDef is not any better.- The class hierarchy with PageTemplateDefinition subclassed by PrototypeDefinition is arguable. Could also be the other way around.We might consider decoration for the prototype? That way, whenever you retrieve a page-template from the registry, it would be decorated by the prototype and we would not need to manually merge it in the renderer. That would probably also allow using primitive types on the page-template (e.g. visible).Original description: 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. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: 

[magnolia-dev] [JIRA] (MGNLSITE-54) Site Prototype in YAML

[JIRA (on behalf of Antti Hietala)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antti Hietala updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-54 
 
 
 
  Site Prototype in YAML  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antti Hietala 
 
 
 

Documentation update required:
 
 Yes 
 
 
 

Release notes required:
 
 Yes 
 
 
 

Account:
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLSITE-54) Site Prototype in YAML

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-54 
 
 
 
  Site Prototype in YAML  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Basel  45  46 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLSITE-54) Site Prototype in YAML

[JIRA (on behalf of Philip Mundt)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-54 
 
 
 
  Site Prototype in YAML  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 

Fix Version/s:
 
 1.0.7 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLSITE-54) Site Prototype in YAML

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-54 
 
 
 
  Site Prototype in YAML  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Assignee:
 
 Philip Mundt 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLSITE-54) Site Prototype in YAML

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-54 
 
 
 
  Site Prototype in YAML  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Story Points:
 
 5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLSITE-54) Site Prototype in YAML

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-54 
 
 
 
  Site Prototype in YAML  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Basel 45 
 
 
 

Account:
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLSITE-54) Site Prototype in YAML

[JIRA (on behalf of Jan Haderka)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jan Haderka updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-54 
 
 
 
  Site Prototype in YAML  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jan Haderka 
 
 
 

Labels:
 
 estimate-pm-ld-5.5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLSITE-54) Site Prototype in YAML

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Zimmermann updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-54 
 
 
 
  Site Prototype in YAML  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christopher Zimmermann 
 
 
 

Account:
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLSITE-54) Site Prototype in YAML

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Zimmermann created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-54 
 
 
 
  Site Prototype in YAML  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Story 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 23/Feb/16 4:36 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Christopher Zimmermann 
 
 
 
 
 
 
 
 
 
 
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. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)