Details
-
Epic
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
None
-
None
-
To Do
Description
Intro/Context:
We recently worked on the possibility to design a site using customization of page templates, stylebook, and configurations with no code. In continuation to this work and the objective to be able to distribute and share solutions across sites we need to go one step further and allow developers to also export pages in a format that allows to use an external tool and modifying them before importing them again.
With this we will be in a position to provide a way to create microsites prototypes that can be shared. We might include the ability to Import/Export:
* Stylebooks
* Master Templates
* Fragments
* Pages
* Content
* Menus
* Collections
One difficulty to tackle is to manage exporting a page and keep the relation to all the contents that relate to the page in a way that if imported again those relations are not lost.
Functions:
* Support exporting a hierarchy pages of a site and import them into a different site or installation
** Export/Import page definition
** References to existing content shouldn't be internal
* Get a consistent user experience when it comes to :
** importing/exporting group of pages
** page templates / and fragments
** Style Book as a ZIP.
* CLI toolkit:
** The exported pages will need to be visible/editable using CLI fragment toolkit
** Ability to import/export pages using CLI toolkit
Attachments
Issue Links
- duplicates
-
LPS-121500 As a Site Admin I would like to export the content of a site so that I can import them into a different site or installation (4)
-
- Open
-
- fixes
-
LPS-119197 The fragment instance on the page is not updated after import.
-
- Reviewed
-
- relates
-
LPS-122311 As a Page Creators I want to export/import a page in a well structured format so that it can be updated using appropriate tool (4)
-
- Open
-