How ani03sha/aem-tutorials works
Project type and purpose
• This is a multi-module, full-stack AEM (Adobe Experience Manager) tutorial application.
• Purpose: Demonstrate AEM concepts (OSGi services, Sling models, servlets, workflows, clientlibs, templates) alongside a React-based front end.
File structure
• Top-level modules (in Maven aggregator “all/pom.xml”):
• core — Java OSGi bundle (backend services, Sling models, servlets, event handlers, schedulers, workflows)
• ui.apps & ui.apps.structure — JCR-root packages defining AEM components, clientlibs (HTL, CSS, JS), dialogs, templates, configurations
• ui.content — JCR content packages (policies, templates, site content, experience fragments, DAM assets, workflows definitions)
• ui.frontend — React SPA (App.js, components, utilities) built and packaged as a clientlib or deployed separately
• “all” is the aggregator POM, orchestrating build order and package assembly for AEM deployment.
README for additional insights
• It’s a tutorial series compatible with AEM 6.3–6.5 covering OSGi, Sling, HTL, workflows, schedulers, eventing, etc.
Main components and interactions
a. AEM Author/Publish Instance
• OSGi Container: runs the “core” bundle
• JCR Repository: stores everything under /apps and /conf from ui.apps & ui.content
• Sling Engine: resolves requests via Sling models and servlets
b. Java OSGi “core” Bundle
• Services (CardService, EmailService, etc.)
• Sling Models (CardImpl, UserImpl)
• Servlets (FetchTODOServlet, SearchServlet, etc.)
• Event Handlers & Schedulers
• Workflow Participants & Processes
c. JCR Packages
• ui.apps — component definitions, HTL templates, dialogs, clientlibs for styling and client-side behavior
• ui.content — content policies, templates, sample content, experience fragments, DAM assets
d. React Front End (ui.frontend)
• Independent SPA that fetches data via Sling servlet endpoints
• Packaged as AEM clientlib or served externally and proxied to AEM APIs
Architectural patterns & design principles
• OSGi modularity: one bundle (“core”) with clear service interfaces and implementations
• MVC/MVVM in Sling: Models (Sling Models) → Views (HTL) → Controllers (Servlets & Services)
• Content-first: separation of content (ui.content) vs. presentation (ui.apps)
• Headless/client-side: React front-end consuming Sling JSON endpoints (servlets)
• Maven multi-module: isolates build artifacts, packages, and dependencies