Content structure and hierarchy

Hey guys, in this video we’re going to cover how site pages are stored within AEM for your organization. As a content author, you need to organize your content pages within AEM by creating and naming your pages. Having a well organized website structure makes it easy for other AEM users with an author instance to quickly browse the content, as well as helps external site visitors discover content when the content is pushed live. From the AEM homepage, let’s navigate to AEM Sites console. AEM Sites console maps to the /content part in your AEM author instance. All site pages for your organization would be created underneath the /content part. In this video we assume you already have a site created by your administrator and you have been granted access to author content.

If you do not see your site or if it feels like you can not perform some of the operations, please reach out to your AEM Site administrator. We have a sample site created for this video and let’s open it. Let’s open the WKND site folder. The structure of a website can be thought of as a tree structure that holds your content pages. When creating a page, there are two key fields: title and name. The title is displayed to the user in the console and shown at the top of the page content when editing. This field is required. The name is used to generate the URL for your final page. User input for this field is optional. If not specified, the name is automatically generated by AEM from the title. Our sample reference company WKND is a multinational organization and has a separate website for each country or region. If your organization requires a separate website for each region, it is recommended to use a language master site and an individual website page structure for each locale, as displayed here. AEM supports multi-site management capabilities and that’s not a topic for discussion. We’re going to check the United States WKND site locale, and let’s open the page and select the English language page. Within the WKND site we can see various categories. Let’s open the adventure category page and then select the Ski Touring adventure. Under the Ski Touring page, you do not see any other page. Let’s do a recap of how we reached here using the rail selector content tree option. WKND site at the top shows the site root page with the content part at /content/wknd. Then we have one language master and several other site root pages for each locale. Selecting the United States part added the /us to our content part. Navigating to the English language node added the /en to our content part, and finally we got the ski touring adventure part.

Navigating back to the parent folder structure is quick and easy with the help of folder navigation drop down. I hope this video helps you to get an understanding of how site pages are stored in an AEM author instance. -