Inspired Digital Experiences for Manufacturing & Automotive
Whether you’re just beginning your digital transformation journey or are well on your way, we invite you to explore our partnership with Adobe and our diverse capabilities in manufacturing and automotive.
“As Maine goes, so goes the nation” is a phrase that at one time was in wide currency in United States politics. The phrase described Maine’s reputation as a bellwether state for presidential elections. As an Adobe Experience Manager (AEM) developer, it is not what proceeds from the Pine Tree State that concerns me, it is what is developed in Switzerland.
Component Development has changes a lot within the past few releases of AEM. We went from Classic UI to Touch UI. From JSP scriptlets to HTL. AEM 6.2 added the Template Editor. Given those changes, I was curious what new features AEM 6.3 would have in store. Adobe announced their “Core Components” would be open sourced. These components include:
Page authoring components:
- Page component
- Breadcrumb component
- Title component
- Text component
- Image component
- List component
- Sharing component
- Form container
- Form text field
- Form options field
- Form hidden field
- Form button
What does this mean to me or to you? I think it means a lot. In fact, Adobe releasing the AEM core components under an open source license gives me a lot of hope.
First of all, the code is beautiful. I remember learning AEM over three years ago. At that time, my background had been in J2EE, and I was an early convert to Tag Libraries. Needless to say, I was shocked to discover the foundation AEM components were still developed using scriptlets! The code was ugly and quite difficult to follow. I felt sorry for young developers learning how to build components from this confusing web of embedded Java code. The years have been good to AEM. Take a look at the new Image Component via Github. Clean HTML with HTL markup. HTL is used in all of these components.
With code this clean coming out of Adobe, we can expect new components based upon this code to be cleaner than anything created referencing the earlier foundation components. No longer will you cringe when you open another’s code. If the budding AEM developer has cut his teeth with clean code, there is a good chance the resultant code will also be clean. My mind reels with the possibilities.
Let me take this scenario a step further. What if a developer takes Adobe’s lead and begin to offer his custom component open source? There are too few open source options for AEM components compared to other technologies, like Eclipse/IntelliJ Plugins, JSR 168 and JSR 286 compliant Portlets, and WordPress Plugins.
This leads me to my next consideration… About a year ago I was looking at the stylesheet of AEM’s responsive grid. The code was quite similar to Bootstrap’s responsive grid. This made me wonder why Adobe didn’t just use Bootstrap’s grid. It would make the development of templates based on Bootstrap so much easier. I concluded it was possible Adobe didn’t want to tether itself to Bootstrap. I’m sure there was a licensing consideration involved. I was concerned over AEM’s future. How could Adobe promote AEM as a tool to easily create websites and not provide components based on popular libraries?