Adobe Experience Manager (AEM) Developer Resources
default UI the Target Paths *
- Adobe AEM The Right Way
- Adobe Solution Partner Program - Product Request Page
- AEM Interview Questions
- AEM Releases and Updates
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
- Apache Felix Console
- Disable WebDav
- Restrict access using the Dispatcher
- Check for cross-site scripting (XSS)
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). Requirements Download and install Eclipse IDE for Java EE Developers (Eclipse Kepler or newer), eclipse.org/downloads/packages/release Install AEM Developer Tools For more information, helpx.