Migration of Content and Content Types between content tenants
The standard way of developing a site indicates you work on a DEV or TEST environment at first and then, once everything is ready, you push the site to PROD.
As it is now, doing this migration of content between tenants is hard. We need to use the command line interface, and even doing so last time we had so many difficulties we went out in production with our DEV environment.
-
Guest
- Apr 30 2020
- Future consideration
|
How will this idea be used?
The idea is to have a publishing process that instead of making content public in the Akamai CDN, it publishes to another tenant. Being able to move from a simple content piece or content type to being able to move a complete site structure and all of its associated components. |
|
| What is your industry? | Banking |
| What is the idea priority? | Urgent |
Related ideas
I think we would rather aim for have a sites model whereby the content does not need to be moved between 2 tenants, through support of drafts/approvals/fine grained access control etc.
You would create you site as drafts for dev/test and then simply publish them in order to move them to the prod site.
Attachments Open full size
Nice, this will be very helpful to our ecosystem and clients.
Attachments Open full size