Core Learning Journey — overview
Purpose: Map the nine sessions and their paired labs, with prerequisites and what you can do after each one.
Who this page is for
| Audience | Why it matters to you |
|---|---|
| All new joiners | This is the spine of the academy — do it in order |
| Mentors | Use the "you can now" column to check progress |
The journey at a glance
Each session is a 30–45 minute read; each lab is 1–2 hours hands-on against your local instance from Environment setup. Everything builds one artefact: the fictional PHI gold-tier hospital cover plan page.
| # | Session | Paired lab | After it, you can… |
|---|---|---|---|
| 1 | Platform overview & architecture | Explore the consoles | Navigate author, CRXDE, OSGi console |
| 2 | JCR & content modelling basics | Model the plan page content | Design a content tree for a real page |
| 3 | Sling & resource resolution | Resolution experiments | Predict which script renders any URL |
| 4 | Components, dialogs & HTL | Build the plan-card component | Ship an authorable component |
| 5 | Sling Models | Model the benefits table | Back components with clean Java models |
| 6 | Templates, policies & pages | Build the plan page template | Create governed page structures |
| 7 | Client libraries & frontend workflow | Style the plan page | Ship CSS/JS the AEM way |
| 8 | Dispatcher, caching & delivery | Cache rules for plan pages | Reason about caching and invalidation |
| 9 | Workflows, launches & content ops | Approval workflow for plan updates | Support real authoring operations |
What is deliberately NOT here
Capacity planning, Oak clustering, cold standby, and edge-compute patterns are electives in Enterprise Engineering. You do not need them to be productive, and mixing them into the core journey is how onboarding drowns.