Shared Technology Stack
Overview
Section titled “Overview”Tools and practices common across all DXP solutions, regardless of CMS choice.
Stack by layer
Section titled “Stack by layer”| Layer | Technology / Tool | Notes |
|---|---|---|
| Version control | GitHub | Default; used unless the project/client mandates another platform |
| Testing & QA | Playwright | Standard E2E framework across all solutions |
| Testing & QA | Lighthouse CI | Performance budget/regression checks |
| Testing & QA | axe | Accessibility auditing |
| Design | Figma | Design-to-development handoff |
| APIs & integration | REST / GraphQL | Common integration protocols |
| APIs & integration | Postman | API exploration/testing |
| CI/CD & tooling | GitHub Actions | Default when the CMS/platform doesn’t impose its own pipeline (see per-CMS files) |
| Observability | New Relic / Datadog | Application monitoring |
| CDN | Cloudflare / Fastly / Akamai | Edge delivery for headless/decoupled frontends |
These are the tools used regardless of which CMS a project is built on.
Per-CMS files repeat a shared tool only when its role or weight differs
for that solution (e.g. why Lighthouse CI matters more for EDS) — read
this file alongside the relevant per-CMS file
(aem-traditional.md,
aem-eds.md, optimizely-cloud.md,
contentful.md) for a project’s full stack.