Adobe Experience Manager 6.5 - Build Websites and Components

Explore CRXDE Lite, web console, and package manager for development and administration in Adobe Experience Manager 6.5. Manage OSGi bundles, configurations, and content packages, and access package share.

Compare mutable and immutable content packages in Adobe Experience Manager 6.5, noting code is persisted in repository and deployed via Cloud Manager, with mutable content including service users and templates.

Understand the content package structure: separate code and content in a single experience manager package, with immutable apps and libs and mutable areas like content and conf.

Upload, validate, and install the Am guides weekend package in Adobe Experience Manager 6.5, creating the weekend UI apps and weekend UI content packages, then verify the site in English.

Create and build immutable and mutable content packages in the package manager, add filters for root paths, build and verify, then share your packages with external groups.

Explore the AEM UI features, including the navigation, search bar, and links to marketing cloud resources, tools, and authoring sections for sites, assets, and forms.

Explore the WKND reference site built with AEM to learn project setup, core components, editable templates, client libraries, and component development, including localized structure, content fragments, and SDL.

Build a fresh page in AEM Sites by selecting the landing page template and naming it 'demo page,' then edit to add text and image components and preview the result.

Explore Adobe Experience Manager 6.5 assets, including files, collections, templates, catalogs, and jobs, in assets console. Share, annotate, resize, tag, and organize assets in folders.

Create a private demo asset folder under the English directory, then upload two assets by using create files, monitor processing, and refresh the browser to confirm they appear.

Learn to add metadata to assets in Adobe Experience Manager 6.5, including title, description, language, tags, and advanced fields like creator and copyright.

Begin hands-on Adobe Experience Manager work in Eclipse, covering Maven pom.xml, archetypes, Uber jar, and key plugins, and understand the UI apps, UI content, core, dispatcher, and front-end modules.

Learn to create an AEM project with Maven by verifying Maven and Java 1.8 JDK, updating the Adobe Public profile in settings.xml, and running the archetype generator.

Install the AEM project using mvn -P auto-install-single-package to deploy UI apps, UI content, and core components on the author instance, and verify with the learning site in English.

OSGi, open services gateway initiative, introduces a modular bundle architecture where bundles (jar files) expose and import services via a dynamic service registry, with lifecycle, security, and execution environment support.

Use maven profiles auto install single package and auto install package to build and deploy UI apps, UI content, and rendering code as an OSGi bundle to AEM; validate active status via the system console.

Learn to sync local development changes to Adobe Experience Manager using the am sync extension in Visual Studio, including configuring host, port, and credentials and validating updates in AEM.

Navigate the JCR repository's hierarchy of nodes and properties, learn node types and namespaces, and review the essential folder structure like apps, conf, and content.

Learn to build an AEM 6.5 website by creating a basic JCR project structure, adding a code component with code.html, and rendering it with a content node.

Create a training folder with components and structure subfolders, save changes, and review the folder properties like jcr primary type during this lab.

Create a cq:component in the content folder, add jcr:title with value 'Quote' and component group 'weekend.content', then create code.html and paste start code.html contents, then save.

Create and display content in Adobe Experience Manager 6.5 by adding a code component to a content node and rendering it with the sling resource type.

learn to configure and reuse a cq dialog from core wcm components, attach it to a code component, and render dialog properties with sdl templates and a runtime expression.

Explore how Apache Sling resolves a request by mapping a URL to a JCR node and selecting the appropriate rendering script, using content-centric processing and resource type hints.

discover how to implement inheritance in Adobe Experience Manager by setting Sling resource super type to inherit properties from the core title component, expanding form fields and speeding up development.

Enhance the quote component by creating and reusing local script files such as orange dot html, and include them via local and data-sly include, inheriting from the title component.

HDL, the HTML template language, replaces JSP in AEM and powers component development with sightly, using an expression language and data-sly attributes to render server-side HTML.

Practice HTL in a lab by using global objects, including the request object API, resource object, and resource resolver, to display the request path, resource type, and current page details.

Discover how HTL attributes render dynamic content in AEM by using data-sly attributes like data-slice-set and data-sly-test to display code, titles, and JCR content and title from root CQ pages.

Explore templates and components in Adobe Experience Manager, including static and editable templates, core and proxy components, and role-based access for authors and developers, enabling scalable page authoring.

Create a proxy page component in Adobe Experience Manager by adding a node under apps/training/components/structure and setting the sling resource super type to apps/core/wcm/components/page/v2/page.

Examine context aware configuration to manage site region specific settings within a content resource hierarchy, using sling config ref roots and a site-to-region-to-tenant lookup with apps and libs fallback.

Create a context aware configuration using the configuration browser, adjust the w e train property to w e dot train, then use the folder to create an editable template.

Learn how editable templates in Adobe Experience Manager 6.5 define page structure, initial content, layout, and content policies, and how to create, edit, enable, and publish HTML5 page templates.

Copy the HTML5 page template type into the training folder, update JCR content to training components, remove the root node, and test by creating the train empty page template.

Create and publish an editable development template in Adobe Experience Manager by selecting an empty page, naming it content page, adding content fragment, experience fragment, and layout container.

Explore how content components, templates, proxy components, core components, and sling models interrelate to render a site from editable templates and associated policies.

Create a content route and build the site structure by adding nodes, selecting queue page types, and applying the sling resource type training components structure and page.

Create a site structure for we train by adding content fragments and layout containers, then build English pages and subpages like about us and experiences, using lower case with hyphens.

Understand client side libraries in adobe experience manager: store css and javascript in repository to avoid duplicates. Organize site and component libraries and load them via html templates or jsp.

Add content to a web page in Adobe Experience Manager 6.5 by dragging a content fragment from assets, configuring its description, and applying We Train package client libraries to components.

Create a base client-side library in Adobe Experience Manager by configuring the client libs base folder, adding properties (categories, embed type, proxy type), and creating css.txt and js.txt files.

Learn to install and attach client libraries to an AEM page component by uploading a training package and validating with page source.

Perform a lab exercise to apply weekend design changes by updating the custom header lips HTML and custom footer lips HTML in the training component, then test the published page.