What needs to be checked when Switching content in Prod | Community
Skip to main content
A
amanagarwal
Level 3
January 4, 2017
Solved

What needs to be checked when Switching content in Prod

  • January 4, 2017
  • 4 replies
  • 2633 views

Hi,

We have a Business requirement, where, we are recreating all the components using a different approach in Phase 2 of a Project. Now the Business needs to have the existing site in Prod before the Phase 2 is launched. For this, we would be copying all the existing components under re-writing code in it. Once the new components are created, The Authors would start creating new pages using the new components. Once the Content is created, we have to switch the Live site from Old content to new Content path.

So my query here is, what all things we have to take care, or pre-determine before doing this switch. We could think of the following:

  • Check Analytics pointings
  • SSO pointings
  • Config related changes
  • URL shortening update to new URL

Are there any other things we need to take care, if anyone has worked on such a condition in the past. Thanks

-Aman

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Runal_Trivedi

what changes in terms of content between your project1 content and project2 content.

if the page hierarchy and or page name changes, then this will affect your final URL structure, which mean you will lose all your SEO value when you move from project1 to project2, unless you decide to maintain additional rewrites at webserver level or in project1 content that will end up doing a redirect to corresponding page on project2.

Along with the bullets that you already mentioned. Some other things you should consider is:

  • vanity URLs
  • permissions
  • cloud products configurations

But out of curiosity, did you try exploring Launches feature of AEM? it allows you to maintain separate hierarchy/copy of main content and when you are ready, you can merge all the updates from the copy tree into main tree and publish.

- Runal

4 replies

smacdonald2008
smacdonald2008
Level 10
January 4, 2017

Switching Content to prod?

Sounds like you are referring to publishing content from Author to Publish - pushing it live. See: 

https://docs.adobe.com/docs/en/cq/5-6-1/wcm/page_publish.html

A
amanagarwalAuthor
Level 3
January 4, 2017

smacdonald2008 wrote...

Switching Content to prod?

Sounds like you are referring to publishing content from Author to Publish - pushing it live. See: 

https://docs.adobe.com/docs/en/cq/5-6-1/wcm/page_publish.html

 

No, we mean, suppose the live site is pointing to "content/sites/project1" in prod-publish instance and want to switch to "content/sites/project2" in prod-publish, once this project2 content is created in prod-author and pushed to prod-publish. Thanks..

Runal_Trivedi
Runal_TrivediAccepted solution
Level 6
January 5, 2017

what changes in terms of content between your project1 content and project2 content.

if the page hierarchy and or page name changes, then this will affect your final URL structure, which mean you will lose all your SEO value when you move from project1 to project2, unless you decide to maintain additional rewrites at webserver level or in project1 content that will end up doing a redirect to corresponding page on project2.

Along with the bullets that you already mentioned. Some other things you should consider is:

  • vanity URLs
  • permissions
  • cloud products configurations

But out of curiosity, did you try exploring Launches feature of AEM? it allows you to maintain separate hierarchy/copy of main content and when you are ready, you can merge all the updates from the copy tree into main tree and publish.

- Runal

    A
    amanagarwalAuthor
    Level 3
    January 6, 2017

    Runal.Trivedi wrote...

    what changes in terms of content between your project1 content and project2 content.

    if the page hierarchy and or page name changes, then this will affect your final URL structure, which mean you will lose all your SEO value when you move from project1 to project2, unless you decide to maintain additional rewrites at webserver level or in project1 content that will end up doing a redirect to corresponding page on project2.

    Along with the bullets that you already mentioned. Some other things you should consider is:

    • vanity URLs
    • permissions
    • cloud products configurations

    But out of curiosity, did you try exploring Launches feature of AEM? it allows you to maintain separate hierarchy/copy of main content and when you are ready, you can merge all the updates from the copy tree into main tree and publish.

    - Runal

     

    Thanks for the reply and putting down additional points.

    Also, Launches feature looks to be what I was looking for, will explore it more. Thanks. 

    Terms & ConditionsAccessibility statement

    Loading footer...