Finding out what components my page is using

There are a few ways to do this. One way is to go into the felix console: http://localhost:4502/system/console/bundles, and go under main, and click on the "Sling Resource Resolver" link. Enter the url you want to know more about and press enter. It will give you a list of possible pages it is using. Open up crx/de or the Eclipse plug-in and find the page, and find where the page or template is located.


A quicker way is to add ?debug=layout to the end of the url of the page in question. It will display where every component on your page is located.

AEM Blogs in the Community worth reading - Work in Progress

I seem to continually go to these blogs for some reason...

Blog for How to in Adobe CQ or WEM by Yogesh Upadhyay
http://www.wemblog.com/

Jorg Hoh - Tips and tricks for CQ5 and Adobe AEM, trying to avoid BS
http://cqdump.wordpress.com/

AEM Operations
http://cq-ops.tumblr.com/

AEM 5.6 - Quick Reference
http://activecq.com/system/assets/46/original/quick-reference.html

AEM 6 - Asset Improvement Capabilities

Dynamic video

• Preview and annotate videos (Notes at certain parts of videos)
• Set video profiles for auto-encoding
• Insight into viewer drop-off reporting to improve video content
• Smart, responsive video players that automatically resize based on page break points
• Video deliver in the cloud. Device optimized streaming on demand
• Video Publishing. Easily add videos to web properties using sites components, URL or embed code
• Social Video: Grow reach by publishing to YouTube and Social Sharing (Facebook, Twitter, Linked-in, etc…)

Dynamic media

• Sizes, Formats, resolutions without knowing the device or browser. Creates multiple renditions based on one asset.
• Dynamic Image Rendition 
• Swap out colors dynamically
• Create media sets for 360 degree views. Think of looking at a car from all angles.

Metadata, search, workflow, and share

• Bulk Metadata Operations
• Smart Collections - Think saved searches that update automatically
• Easy Metadata Schema definitions with ability to set fields as required / visible
• Search paths, mime types, last modified, file size, orientation, style, video height, video width, publish status, approval status. Much easier to add custom tags.
• Saved Searches and share with other teams

Task and Workflow Management

• Photoshoot-to-site workflow
• PIM Integration (Product Information Management)
• Organize Teams
• Track tasks and Deadlines
• Pre-configured workflows
• Review and Approval
• Dashboards and team assignments

Admin & Security

• Reports
• Added
• Downloaded
• Modified
• Expired License
• Published 
• Custom

Creative Cloud integration

Significant Engine Improvements

• TarPM and MongoDB as preferred repositories
• Reads and Writes Improvements
• Many Performance improvements

Using Automated Tests for Sling Based Applications

Testing Sling based Applications:
http://sling.apache.org/documentation/tutorials-how-tos/testing-sling-based-applications.html

Automated UI Testing
http://www.seleniumhq.org/

AEM Dev Tools for eclipse released TODAY

Just released today. The new AEM Dev Tools for Eclipse:

http://docs.adobe.com/content/docs/en/dev-tools/aem-eclipse.html

Need the stand-alone files if you work disconnnected?, you can get the contents here:
http://eclipse.adobe.com/aem/dev-tools/com.adobe.granite.ide.p2update-1.0.0.zip

Use this link to learn how to use it:
https://sling.apache.org/documentation/development/ide-tooling.html

The main features of this Eclipse plugin are:

• Seamless integration with AEM instances through Eclipse Server Connector.
• Synchronization for both content and OSGI bundles.
• Debugging support with code hot-swaping capability.
• Simple bootstrap of AEM projects via a specific Project Creation Wizard.
• Easy JCR properties editing.

Here are a few screenshots of the plug-in in action. It's a great tool that will get you away from using CRXDE Lite and finally optimizes your development workflow. You will still need to configure your filter.xml to set what syncs to your server.

Configuring the server, publishing changes

Adding Nodes

Local changes automatically published

Setting Properties

Migrating Assets Approach

I'm working on a project that requires a significant asset migration from a legacy system. I've used this approach for a few different migrations from legacy systems, and it has not failed me yet. As much as I would like to use a connector or some other easy route out of a lot of code, I didn't have a choice because the legacy software was ancient or the customer didn't want to keep both systems up.

So, the approach was to:

1. If this is a mass asset migration, turn off the workflow, "DAM Update Asset" and any other custom workflows that might interfere and cause noise.
2. If you have a slave, turn it off to eliminate another variable. When you turn the slave on, it will sync.
3. Ensure your aem instance is patched.
4. Go into the legacy system, zip up each package of content with an associated metadata xml file
5. Curl it over from the legacy system to AEM to a place under /content/dam/migrate/
6. Excluded a directory from the DAM Update Asset workflow so it wouldn't create renditions of content I was about to migrate. (see my post about regular expressions)
7. Create a workflow launcher that listens for zip files being created in that directory
8. Execute a custom workflow model
1. Created a custom workflow step that saves the path. This was needed because the payload gets destroyed in the next step.
2. Executes the DAM unarchiver workflow to extract the contents, destroys the zip
3. Execute a custom workflow step to process the data
1. Use the path stored in step 1, use JAXB to read the data from the XML file
2. Create the asset/page/etc... and add the custom data fields as needed

I've used other variations in my workflow model to DRM documents using the LiveCycle connector, executing other processes, and sending emails.

If you migrated a ton of assets, you can put the assets back into the "DAM Update Asset" workflow by using the script here:
http://www.wemblog.com/2012/09/how-to-put-dam-asset-back-to-workflow.html

AEM 6 Reference materials

AEM 6 Documentation
http://docs.adobe.com/docs/en/aem/6-0.html

What's new in AEM 6?
http://cq-ops.tumblr.com/post/86504895994/whats-new-in-aem-6-0

Gems on Adobe Experience Manager - Many recorded in depth videos
http://dev.day.com/gems

AEM 6.0 and Admin Sessions
https://cqdump.wordpress.com/2014/06/23/aem-6-0-admin-sessions/

What is Sightly? (Preferred HTML templating system in AEM 6. No more JSP's!)
http://docs.adobe.com/content/docs/en/aem/6-0/develop/sightly.html

AEM 6 Hotfixes
http://helpx.adobe.com/experience-manager/kb/aem6-available-hotfixes.html

RELEASED TODAY (July 28th, 2014) - The AEM Sightly Brackets Extension:

https://github.com/Adobe-Marketing-Cloud/aem-sightly-brackets-extension

Adobe Consulting Services AEM Commons
http://adobe-consulting-services.github.io/acs-aem-commons/