Project Structure

ShockStack is a monorepo with shared tooling and clearly separated responsibilities.

Top-Level Areas

  • frontend: web app, routes, components, and content
  • backend: optional API and supporting services
  • packages/tokens: design token source and generated artifacts
  • docker: container setup for local/full-stack workflows
  • docs: architecture and usage documentation
  • .github: CI/CD workflow automation

Workspace Model

Workspaces allow each package to keep its own dependencies while sharing repository-wide tooling for:

  • linting
  • formatting
  • testing
  • type checks
  • release automation

Build Orchestration

Build tasks are orchestrated so shared prerequisites run first (for example, token generation before frontend builds).
This preserves deterministic builds while keeping package boundaries independent.

Optional Backend

The backend is additive. You can run frontend-only workflows or enable the API stack when needed.

Practical Navigation Tip

When exploring the repo, start from intent:

  1. UI/content concern -> frontend
  2. domain/API concern -> backend
  3. visual system concern -> packages/tokens
  4. delivery/runtime concern -> docker and .github