One of the things I like about SitecoreAI is that you can build a fairly sophisticated page composition model using Page Designs, Partial Designs and Page Branches. But when you start combining all three, there are a few concepts that are easy to misunderstand. I recently worked through one such scenario where we were setting up Page Designs and Partial Designs and ran into questions around: Template to Design Mapping Page Design standard values Page Branch insert options Partial Design datasource locations local:/ versus page:/ Editing datasource content on individual pages Individually, each feature makes sense. The confusion starts when they are used together. The Page Design Structure Our intended structure was something like this: Page Template | v Page Design | +-- Header Partial Design | +-- Content Partial Design | | | +-- Hero Banner | +-- Footer Partial Design The id...
I recently spent some time troubleshooting SitecoreAI Page Branches, and what initially looked like one problem actually turned out to be two different things. The requirement was fairly straightforward: We wanted content authors to be able to create pages using Page Branches directly from Page Builder, without having to manually configure insert options on every page template. At the same time, we wanted the Page Branch to provide the required datasource structure for the components used by the page design. That led to two questions: Why are my Page Branches not appearing as insert options? Why aren't the datasource items being automatically created when a page is created from a Page Branch? The interesting part was that the answers were different. The Original Requirement We had Page Branches configured under: /sitecore/content/mysite/Shared/Presentation/Page Branches The idea was to configure a rule on the Page Branches folder so that a particular Pag...