Tracks

Canonical list of disciplines/tracks used across roles/, roadmaps/, career-paths/, and evaluation-criteria/. The Slug column is the filename (without extension) used in each of those folders — e.g. the frontend slug corresponds to roles/frontend.md, roadmaps/frontend.md, career-paths/frontend.md, and evaluation-criteria/frontend.md.

Track	Slug	Description
Frontend	frontend	Client-side/UI development across the team’s CMS platforms.
Backend	backend	Server-side/platform development: content modeling, APIs, integrations.
DevOps	devops	CI/CD, infrastructure and delivery pipelines per platform.
QA	qa	Test strategy, automation and quality assurance per platform.

For frontend, backend, devops and qa, roadmaps/ and career-paths/ now exist for all four tracks. Only evaluation-criteria/ is still pending; its index page notes this. See reference/career-levels.md for the seniority ladder shared by every track’s career-paths/<slug>.md.

Specialization by CMS

A track’s common core (mission, responsibilities, baseline requirements) lives once in its roles/<slug>.md — not a separate file per CMS. Where a CMS materially changes the tools or practice for a track (e.g. AEM Traditional Frontend uses HTL/AEM Core Components, Optimizely Cloud Frontend uses React/Next.js on Optimizely Graph), every track-based role doc carries a ### By CMS subsection under Requirements, listing what’s specific to each of the team’s four CMS platforms — see technologies/ for the full stack behind each one. That subsection is never omitted, and it never skips a CMS silently: if a given CMS needs nothing beyond the common core, the doc says so explicitly rather than leaving it out.

Adding a track

1. Add a row to the table above with the track’s name, slug, and a one-line description.
2. Create roles/<slug>.md, roadmaps/<slug>.md, career-paths/<slug>.md, and evaluation-criteria/<slug>.md from the templates in _templates/ in the repository root (not part of this site).