As a page administrator I can export one content page template as a well defined open format

• Type: Story
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: Master
• Component/s: Page Templates
• Labels:
  • fc_19_12
  • fc_20_01
  • fc_20_02
  • fc_20_03
  • fc_20_04
• Epic Link: automate-fragment-page-creation
• Sprint: S01E04 - Turtles Swamp, S01E05 - Flowers Rebellion, S01E06 - Trip to Canada

The goal of this story is to allow page administrators to export an existing fragments-based page into an Open Format. In particular, as a first step this Story will focus on exporting one page template from the Page Templates Administration. The idea is that the exported page definition can be imported later as it is or with modifications. Since a page template may contain a number of variations of content and configuration, to keep the scope of this story limited, only the following data will be exported:

• Fragments added to the page
• The layouts of columns added to the page and the fragments inside its columns
• Inline content introduced within fragment editable elements
• The configuration of all the fragments of the page
• The look & feel configuration of the page

The format of the page template should be standardized and a schema should be provided (i.e. in OpenAPI or JSON Schema) so that any modifications can be validated by the user. 

Since the ultimate goal is to export a fragments-based page definition, any information that is specific for the page template should be kept separate (potentially in a different file) from the page definition itself (which is common for other page template types or even content pages).

Known limitations

The following information will not be exported for now (support will be added in subsequent stories):

• Widget Configuration (Portlet Preferences)
• Widget Permissions
• Mappings of editables to existing content
• Fragment HTML, CSS, JavaScript & Resources: Only a reference to the name of the fragment will be exported. 

Technical notes

• The export should be done into a JSON file, or a ZIP which contains a main JSON file together with secondary files.

Test Scenarios

Test Scenarios	Test Strategy	Kind of test	Is it covered by FrontEnd ? (JS-Unit)	Is it covered by BackEnd ? (unit or integration)
Cannot export a content page template when it doesn't have published version	Smoke	Manual	No	ExportLayoutPageTemplateEntriesMVCResourceCommandTest.testGetFileSingleLayoutPageTemplateDraft
Can export a content page template in approved status	Smoke	Manual	No	ExportLayoutPageTemplateEntriesMVCResourceCommandTest.testGetFile
Can export a content page template in draft status when it has published version and only the published version is exported	Sanity	Manual	No	TBD
Can export multiple selected content page templates in approved status	Smoke	Manual	No	ExportLayoutPageTemplateEntriesMVCResourceCommandTest.testGetFileMultipleLayoutPageTemplatesSingleCollection
Can not export multiple selected content page templates when one of them doesn't have published version	Sanity	Manual	No	No
Can not export multiple selected page templates if one of them is widget page template	Sanity	Manual	No	No
When export a content page template, the reference of widgets should also be exported.	Smoke	Manual	No	TBD
When export a content page template, the reference of theme should also be exported.	Smoke	Manual	No	Yes, testToPageDefinitionRoot
When export a content page template, the layout elements and nested elements should also be exported.	Sanity	Manual	No	Yes, testToPageDefinitionRoot, testToPageDefinitionRow, testToPageDefinitionSection
When export a content page template, the changes for inline content of fragments should also be exported.	Sanity	Manual	No	Yes, testToPageDefinitionFragmentFieldBackgroundImage, testToPageDefinitionFragmentFieldBackgroundImageTitle, testToPageDefinitionFragmentFieldHTML, testToPageDefinitionFragmentFieldImage, testToPageDefinitionFragmentFieldImageTitle, testToPageDefinitionFragmentFieldLink, testToPageDefinitionFragmentFieldText
When export a content page template, the changes for configuration settings of fragments should also be exported.	Sanity	Manual	No	Yes, testToPageDefinitionFragmentConfig
When export a content page template, the changes for Theme of it should also be exported	Sanity	Manual	TBD	TBD
When export a content page template based on custom master, the reference of custom master should also be exported.	Sanity	Manual	No	No
When export a content page template, the changes for Look and Feel Settings of it should also be exported	Sanity	Manual	No	No