ObliviOS Developer portal Project site

Home / Decisions / ADR-252

Start the real build of oblivios.org (gates W-2 to W-8 for that site) before the mockups of oblivios.dev exist.

Accepted, recorded 17 November 2026.

Decision
ADR-252
Date
2026-11-17
Status
AcceptedAccepted (owner, 2026-11-17: after the mockups were accepted and the work was recorded, the owner asked for the hand-over to build oblivios.org for real). Started on 2026-11-17, not finished (ADR-253).
Mentions
ADR-251, ADR-253
Mentioned by
ADR-253, ADR-268

1Decision

Start the real build of oblivios.org (gates W-2 to W-8 for that site) before the mockups of oblivios.dev exist. W-1 is met for oblivios.org by ADR-251 and stays open for oblivios.dev, which is built only after its own mockups are accepted. The build follows the mockup sources in docs/design/oblivios-org-2026-11-17/: Astro with static output, the application of oblivios.org in site/, the privacy rules of section 5.4 of the public launch design, and the open points of ADR-251 asked of the owner before any of them is written into a page.

2Why and evidence

The mockups of oblivios.org are accepted and the owner wants the site; the design of oblivios.dev is separate and the build of oblivios.org does not need it. The shared package of the spec (tokens, logo, prints, layout) is built once and used by both sites later. Rejected: waiting for the mockups of oblivios.dev (the site the owner asked for is oblivios.org).

3Consequences

site/ appears in this repository and is copied into oblivios-docs by tools/docs/build-public-docs.py, extended for it (W-8); the SBOM extension (W-7) is part of the build. The open points of ADR-251 stay open and are asked, not decided.

4Review when

The owner wants oblivios.dev first; the shared package turns out to need the oblivios.dev design; a gate of the spec cannot be met for one site alone.

Read from docs/governance/decision-log.md, entry ADR-252.