How to use this academy
Purpose: Explain the page conventions, the learning paths, and the expectations for sessions vs labs vs reference material.
Who this page is for
| Audience | Why it matters to you |
|---|---|
| All new joiners | Sets expectations for how content is structured and consumed |
| Mentors/buddies | Explains how to pair sessions with labs when coaching |
Page conventions
Every page in the academy follows the same shape, so you always know where to look:
| Section | What you will find there |
|---|---|
| Purpose statement | One sentence: why this page exists |
| Audience | Who the page is for and why it matters to them |
| Content | Tables-first explanations, ASCII diagrams, worked examples |
| Quick navigation | Previous/next within the section, section home, academy home |
| Related pages | Curated cross-links, not exhaustive ones |
Sessions vs labs vs reference
- Sessions teach concepts. Read them like a chapter — 30–45 minutes each, no keyboard required.
- Labs are paired 1:1 with sessions and are hands-on. Do the lab within a day or two of its session.
- Reference pages are not meant to be read linearly. Search or browse when you need them.
The running example
All examples model the same fictional page: the PHI gold-tier hospital cover plan page — a product page with a hero banner, a benefits table, premium information, disclaimers, and a call-to-action. It is rich enough to exercise components, templates, fragments, caching and workflows, and entirely made up.
Suggested cadence
| Week | Focus |
|---|---|
| 1 | Start Here pages, Sessions 1–2 + labs |
| 2 | Sessions 3–5 + labs |
| 3 | Sessions 6–7 + labs, browse Developer Reference as needed |
| 4 | Sessions 8–9 + labs, Security & Governance overview |
| Ongoing | Reference, Enterprise Engineering, Troubleshooting as your tickets demand |