Images are needed for many Components. But to use them, they need to be uploaded and handled in the right Way. Pages can be added, moved, cloned, or deleted. Learn how to handle a Page correctly. A Copy from Pages can be taken to provide a Page in different Languages. It is not recommanded to use every Component everywhere. Learn what can be used where. Get to know the Component Policies. There is only one Template available for Pages. This is structured in different Areas. Protect Pages with Login. Experience Fragments are used for a Lot of Components, like Web Navigation, Third Level Navigation, Footer, Modal, Google Maps, and some more, as well as for full Content Parts. A Sitemap is an XML Page that stores the Pages and their Connections to make it easier for Search Engines, like Google, to crawl through the Site. AEM provides three different Views for Sites. They can be used for the Pages, Experience Fragments, and Images. The Build Information Component is used to show Build Version Information, so that I can easily see relevant Version Details. Filter Pages or Experience Fragments using Tags. Beside having a Homepage Configuration, also Context Aware Configuration (CAC) is possible, using multiple Configuration Pages. Error Page are shown when an Error occurs using a Website. For Example if a User wants to navigate to a Page that does not exist. This should only be maintained by Tracking Experts!
Tracking Options are available for a Lot of Components. Those Options allow to add Tracking-IDs as well as Journey-IDs to the Components. Images are needed for many Components. With WebP Image Optimization is possible. Schema.org is a collaborative Initiative between major Search Engines like Google, Bing, Yahoo, and Yandex. In AEM it can be used for Accordion and Video. Welcome to our Guide on enhancing Website Accessibility!
Explore the essential Steps and Strategies to make a Website inclusive for all Users.