Adobe Experience Manager (AEM)
Posts
Adobe Resources
- AEM 6.5 Developing User Guide
- AEM Gems Technical deep dives delivered by Adobe experts.
- AEM Releases and Updates
- AEM-Tech Slack Group To join, e-mail aemtech@argildx.com with your Slack e-mail address, name, title or job description.
- AEM Tutorials
- Content Fragments
- Creating your first Adobe Experience Manager Touch UI component
- Debug an AEM app using eclipse or Debug using VS Code
- Granite UI Foundation Server-side docs
- How to Build AEM Projects using Apache Maven
- Recent Documentation Updates
- Set up a Local AEM Development Environment
- Sling URL Decomposition - includes a tabular breakdown of a URI resource into resource path, selectors, extension and suffix.
Code Repositories
Configuration
- Configuring OSGi
- Disable Link Checker, Search for “CQ Link Checker Transformer” -> “Edit” -> Check “Disable Checking”
- OSGi Configuration Settings
- Run Modes
Security
By default, Adobe Experience Manager has pretty much everything enabled. When deploying to production, these items should be checked in addition to other precautions.
- Change administrative passwords
- CRX
- Apache Felix Console
- Disable WebDav
- Restrict access using the Dispatcher
- Check for cross-site scripting (XSS)
Classic UI
As of AEM 6.4, the Touch-Enabled UI is now the default at /aem/start. To get to the legacy Classic UI, use /welcome. Useful Classic UI tools include:
- /siteadmin this dashboard includes a search mechanism for use in the author environment. more info
Under The Hood
- Test Category Resolution:
/libs/granite/ui/content/dumplibs.html
Deploying Code to AEM
Methods for installing or deploying code from your local file system into an AEM server.
Sightly HTL Tips & Resources
Tips & Resources for using Sightly Hypertext Template Language (HTL) in Adobe Experience Manager (AEM). For more information, the HTML Template Language Specification is a comprehensive HTL resource.
Stubbing Data with AEM JavaScript Use-API
An Adobe Experience Manager (AEM) example of a new blank slate starter component with stub data. The JavaScript Use-API returns the data to the HTL template for development.
How to Start AEM in Debug Mode
How to start Adobe Experience Manager (AEM) in debug mode for applications running in a remote or local AEM server.
Import AEM Maven Project into Eclipse
These steps show how to import an AEM Maven Project into eclipse.
AEM JavaScript Use-API String Multi JSON
JSON content parsing, e.g., jcr:content Type string[] with JSON values.
Developer Tools for Eclipse
This page contains tips and resources for using Eclipse with Adobe Experience Manager (AEM). The first tip covers how to setup a simple Sling Content project and use it to transfer files between the local file system and AEM’s Java Content Repository (JCR).
AEM JavaScript Use-API
Tips and resources for using AEM’s Sightly / HTL JavaScript Use-API for writing server-side JavaScript. The AEM JavaScript Use-API ResourceUtils page contains examples for using ResourceUtils and functions.
AEM JavaScript Use-API ResourceUtils
ResourceUtils examples using an AEM Maven project and the We.Retail sample to show how to pass data from the HTL to server-side JavaScript, and use the /libs/wcm/foundation/components/utils/ResourceUtils.js to access properties from jcr:content.