AEM - FrontendHub

One of the questions that arise when starting a new AEM project, is what kind of front-end approach to choose. In Adobe we have internal guidance with a document of 15+ pages, and obviously I won't put that here because it's going to bore you out. Instead, I want to distill it down to a few considerations. Customer First Remember, the first priority is the customers needs, and that often includes not spending too much money and effort, on the short and long term. This might sound basic, but what I often saw in my consulting days, is that very passionate (Front-End) agencies push for the latest and greatest front-end tech.  Why?  Because it's cool.  We like working with it.  Everybody else we know is doing it  It's a few milliseconds faster in rendering. Now while these above are understandable, and I admire passion for the job, these reasons should be the lowest priority. Instead think this, I choose this front-end approach because: It fits the goals of my customer It&#

Answering the most commonly asked questions about the SPA editor Today I am going to answer some FAQ that I get a lot from customers, that are not addressed in the latest post / archetype updates. Disclaimer: As the solution gets updated frequently, these answers might become outdated. Are Content Fragments supported? As of today just recently, for react yes, for angular not yet. (PR is pending) Check the PR for react here and for Angular here to see how it's used. Note: this is for the spa editor only because it depends on the component-mapping. Are Experience Fragments supported? As of today just recently, yes. They require you to overload a resource type from the spa-core project, and to provide 3 HTL files. No more Java hacking required. This is baked into the latest AEM archetype release now, so you don't need to worry about it if you use this as a base. Otherwise, you can generate a project and see how it's done there with minimal code. I hate Java! How do I avoid

At Adobe, we just released some updates to the AEM archetype. This includes some important updates for the react / angular frontend-module: Experience Fragment support provided OOTB (demo provided) Code splitting / lazy loading demo provided Navigation Component with routing provided in Header XF Server Side Rendering bootstrap provided  Express + IO runtime for React Express for Angular  These were topics that caused our customers that were implementing the solution to spend a lot of time on setting up. And most of them required this. Personally I got bombarded with questions on how to tackle this. Then the customers would implement these solutions on their private repositories. Now with these changes, our customers won't need to ask these questions; they will be armed with a working solution from the start without any effort.  That's why I am really excited that this release is shipped successfully! You can start out with this maven command to get going: mvn -B archetype:gene