thanks Avinash! The content here actually isn't common for the most part. The components and structure are the same across pages but for 90% of them, the content in those components would differ one each of the 100 pages. I would like the ability to edit the content in one location.

Hello all! We would like to create a whole page and then move it to the existing place and URL in our sites structure at the same live site. In other words, we would like to change out an existing live site with one we have built in a different AEM location.  Is there an existing workflow around thi...

Hi there,  I'm wondering if I can leverage MSM to create a single-source workflow of 100+ pages with different content but based on the same structure. Is this doable with MSM and non-localized content? 1. In other words, I'd like to have one parent page with a structural blueprint but be able to dr...

hello again Esteban! I had one other question about nested launches. When I created a nested launch (B or C in the above example), the nested launch I create- is that a branch of a launch? Or of the source page? Basically, if my page edits on launch C are underway, and I create launch B, do the edit...

Thank you Hema! Last clarifying question: "Stage can be used by content authors to test any new features, preview changes before they move to actual Production site if needed" Is there any downside to following this logic but authoring in prod first? In other words, authoring content in prod, pushin...

Thank you, Hemalatha! This is what I'm thinking to propose at my organization (author and review in prod then publish live.) One follow up question- what do people use stage environment for (if at all) in those cases?

Hi all,  We are using AEM cloud version 6.5 and author in stage, publish and then package pages, assets and other elements individually, package all of these and push them to the AEM prod environment.  I'm just curious, for others using cloud, do you author in stage? Directly in prod? Do you use pac...

Hi all! I'm hoping to be able to set up a launch branch (A) say, from July 1s that gets promoted live (C) on July 30th. I'd like to start another branch (B) on July 15th from the same origin page, but then promote the changes from branch B to branch C, for a final live version of the origin page fro...