Brad Meehan provides the reasoning for his suggestion to use categories in component names. Adobe AEM the Right Way: USABILITY TIP: USE CATEGORIES TO PREFIX COMPONENT NAMES – PART 2
About The Author
Deke departed Southern Alabama as a young man, leaving the humidity and fire ants behind. The fire ants are catching up with him. He works for Adobe. Despite that, his opinions expressed on this site are his own and should never, ever, be attributed or blamed on Adobe. Ask him what he thinks of chiggars sometime. Home Page | GitHub | Adobe Blog | Twitter | LinkedIn
You may also like
AEM Symbiots
The sub-set of the English language that is AEM-based jargon uses the word, integration, in...More
0Working Workflows: Customizing
Axis41 created a nice overview in the customization of workflows within Adobe Experience Manager. Adobe Experience...More
0Using ACS Commons
Adobe Consulting Services finds itself creating reusable solutions for common tasks. They decided to share...More
0Change Not from Author to Publish
Adobe Experience Manager has the ability to install base functionality and bundles on first run...More
0Use JSTL Within Adobe Experience Manager JSP
New, detailed, tutorial from Adobe CQ Help: Adobe CQ Help | Creating Adobe Experience Manager Components that...More
0The Apache Sling JCR Installer as a Design Pattern
There are more than one way to install a bundle to Apache Sling and Adobe...More
2Example: Read RunModes in Sightly
Gabriel Walt provides an example of reading run modes from within Sightly. Run modes...More
0Dispatcher and AEM Image Renditions
Adobe Experience Manager, when an image is first loaded, creates multiple versions of the image...More
0