Skip to content

ADR-0008: Astro for the public sites

  • Status: Accepted
  • Date: 2026-11-12

Some pages are opened by people without an account, mostly on a phone: the landing page, the careers page and job pages of each company, the application form, and the pages reached by a link (scheduling, signing, unsubscribe, candidate area). They must load fast, be readable by search engines where that matters and ship little JavaScript.

Which stack serves the public pages?

  • Little or no JavaScript on a page that is mostly text.
  • A job page must stop being served the moment the job is unpublished.
  • The same design tokens as the product.
  • No business logic outside the API.
  1. Astro: static output for the landing site, server rendering for the careers site.
  2. Routes of the React single page app (ADR-0007). Obvious alternative, listed for comparison.
  3. A React framework with server rendering for all front ends. Common market alternative, listed for comparison.

Chosen option: 1.

  • apps/landing is a static site. It uses no React: its pages are HTML with the CSS classes of packages/ui and small scripts.
  • apps/careers runs with output: 'server' and the Node adapter in standalone mode. Every page is rendered on request, so an unpublished job answers 404 at once. React is loaded only on pages that have interaction. The site reads only the public routes of the API, through the generated client.
  • apps/docs is this documentation, see ADR-0020.
  • Good, because a public page ships only the script it needs.
  • Good, because the careers site holds no data of its own: unpublishing a job or revoking a link takes effect on the next request.
  • Bad, because the careers site is one more server process to run, next to the API and the worker.
  • Bad, because the components of packages/ui are React components. The landing site reuses their CSS classes, not the components, so a change of markup in a component is not picked up there automatically.