Archetype update 28: SPA editor


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:generate \
 -D archetypeGroupId=com.adobe.aem \
 -D archetypeArtifactId=aem-project-archetype \
 -D archetypeVersion=28 \
 -D appTitle="My Site" \
 -D appId="mysite" \
 -D groupId="com.mysite" \
 -D frontendModule="react" \
 -D enableSSR="y"


To provide more support / and insights I also released the following videos. I hope this will answer 90%+ of the questions I am usually getting.


Happy coding!

Reacties

Een reactie posten

Populaire posts van deze blog

AEM Spa editor - Error Page handling

Afbeelding
One of the questions we frequently got from customers was on how to handle 404 / 500 pages in the SPA editor. Unfortunately we could not give a good answer, and it required a lot of hacking to make it work. Thats why just now, we updated the spa page model manager to support handling 404 / 500 pages!  It works like this: Page Request is made and ACS AEM error handler catches it. Client tries to fetch a model JSON but get's a 404 error in return. Client now will take the error page root (given as meta property) and use the status code to make a new request.  Presuming the page exists, the authored error page model JSON is injected as requested path.  The error page is displayed. Result: Check out the repository providing a demo: https://github.com/niekraaijmakers/aem-spa-editor-errorpages-example happy coding!
Meer lezen

AEM SPA editor - FAQ

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
Meer lezen