ADR-0008: Astro for the public sites
- Status: Accepted
- Date: 2026-11-12
Context and problem statement
Section titled “Context and problem statement”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?
Decision drivers
Section titled “Decision drivers”- 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.
Considered options
Section titled “Considered options”- Astro: static output for the landing site, server rendering for the careers site.
- Routes of the React single page app (ADR-0007). Obvious alternative, listed for comparison.
- A React framework with server rendering for all front ends. Common market alternative, listed for comparison.
Decision outcome
Section titled “Decision outcome”Chosen option: 1.
apps/landingis a static site. It uses no React: its pages are HTML with the CSS classes ofpackages/uiand small scripts.apps/careersruns withoutput: '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/docsis this documentation, see ADR-0020.
Consequences
Section titled “Consequences”- 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/uiare 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.
More information
Section titled “More information”apps/landing/astro.config.tsandapps/careers/astro.config.ts: the two configurations.apps/careers/src/pages: the public pages per company.- Building blocks and Deployment view.
- Concept pages: Design system, Internationalization, API contract.
- User guide: Careers and campaign pages, What applicants see.