Just for fun, here’s some output from a brainstorming session on team names.
- Wrapper’s Delight
- The Reflectionists
- Mighty Polymorphin Rangers
- The Uncastables
- Frequently Extended
- The Illegal Modifiers
- Low Overriders
- Dazed and Dequeued
AEM provides a great WYSIWYG interface to drag and drop a discrete set of components onto a page. This interface, however, does not account for components that need to be added to a page dynamically. This post will discuss how to add sets of components to a page programatically based on custom logic.
When building sites with AEM, a practical distinction is made between authors and developers. An author’s role is to create content. A developer’s role is to add functionality. When developers build functionality into sets of components, authors can add, arrange, and configure these components with content directly onto user-facing site pages.
Note: topic is unrelated to AEM and based on another Adobe technology, LiveCycle.
Adobe provides much documentation on LiveCycle ES4 component creation. Unfortunately, that documentation is a site-copy from the ES2.5 instructions and, as of the time of this post’s publication, has not been updated to account for ES4 changes. Therefore, much of it is obsolete and many links and downloads are no longer functional. In this post, I’ll try to bridge the gap between the outdated documentation and the necessary changes required to create and deploy custom components on ES4.
Problem: CRXDE opens and displays most folders, but doesn’t show the content folder.
Problem: CRXDE opens, but doesn’t respond when trying to connect. There are no error messages and the development window won’t appear.
CQ Client Libararies (clientlibs) contain two configuration options that every developer should be aware of: minify and debug.
A strength of Sling is the automatic and expected way that resources are structured and exposed in a logical, ordered manner. For example, AEM, by configuration allows page access through the /content/ directory. A typical page URL would be access with a browser visit to /content/projectname/pagename/subpagename.html. The minimal effort in maintaining this structure has its benefits, but changing that structure to fulfill business needs can be troublesome. Thankfully, AEM provides a number of tools and techniques to do so. This text will explore some of those options.
Problem: A single video asset is provided for a page, but that page should support multiple browsers and formats
Solution: AEM’s DAM can create alternate renditions automatically. It just needs some configuration
Problem: The popular css library Foundation causes conflicts with some of the author mode dialog widgets.