Skip to main content

Posts Tagged ‘spa’

deliver the Headless side of the AEM experience with SPA

Headful or Headless AEM? Why not both with Hybrid? – Part 2

Previously I presented a common situation where an engineering team might push for Headless AEM and covered why, in my opinion, a Hybrid solution is a better approach.  I discussed how Content Fragments, Experience Fragments, and Sling Model Exporters are used in combination to deliver the Headless side of the AEM experience.  In case you […]

A case for headless AEM or hybrid?

Headful or Headless AEM? Why Not Both with Hybrid?

It’s not uncommon when facing a new problem, to fall back on a tried-and-true solution.  Then, suddenly remember why the team moved off of that solution in the first place.  Recently, I’ve seen this trend with engineering teams and a desire for multichannel content. A Common Case for Headless Content on AEM Let’s set the […]

Approach Overview: Compiling and Authoring React Applications in AEM

The Adobe Experience Manager (AEM) platform allows for a great level of customizability – there can be endless unique implementations. This level of customization will continue to increase given Adobe’s frequent updates in integrations and emerging technologies. With the surge in single-page application (SPA) designs, JavaScript frameworks like React, Angular, and Handlebars are now some […]

Mixing MPA and SPA: worst of both worlds

When the web was young, it was simple, it was stateless. It was originally envisioned by its creators as a set of hypertext documents linked together. Then, somebody added a forms tag and the era of web applications has begun. Nowadays, web applications could be as complex as needed. Pretty much any kind of application could be […]