Skip to main content

Frontend

Source of truth for frontend development of the orchestration cluster components (Admin, Operate and Tasklist) hosted in webapp/client.

Who this is for​

Anyone working on the orchestration cluster frontend components.

What you'll find here​

  • Getting started — clone, prerequisites, run backend + frontend locally.
  • Project outline — packages and apps inside webapp/client and what each owns.
  • Orchestration cluster webapp — deeper intro to the unified app: tech stack, layout, scripts, dev-server proxy, testing.
  • Camunda API Zod schemas — installation, usage, and publishing for the @camunda/camunda-api-zod-schemas package.
  • Data loading — TanStack Query + Zod schema patterns.
  • Forms — form library choice and shared form-agnostic patterns.
  • Development process — pre-flight checklist plus playbooks for new pages, extending pages, and large features.
  • Testing — unit (Vitest browser), integration (Playwright + MSW), a11y, and visual regression.
  • Using AI — guidelines for AI-assisted frontend work.
  • Code reviews — what we look for.
  • ADRs — recorded architecture decisions.
  • Code style — formatting and naming conventions.
  • Legacy components — pointers to components still living outside webapp/client.

Status​

No component lives in webapp/client yet — we're currently laying the foundations. The legacy components still ship from identity/client, tasklist/client, operate/client, and optimize/client.

For the latest status, check the unification epic (camunda/camunda#51305) or the Slack channel #prj-pdp-3456-frontend-application-unification.

Get in touch​

  • Slack: #team-core-features-frontend — day-to-day questions and discussion.
  • Bi-weekly team sync — ask in the Slack channel for the invite.