
Powered by Pre
One governed source. Many useful forms.
Flying Over Time’s website is built as a document-native institutional surface: content lives in governed records and is projected into responsive pages, print-ready documents, machine-readable data, and—later—private operating views.
Architecture
Supabase stores the records. Pre defines how they become trustworthy surfaces.
Pages, revisions, routes, redirects, events, programs, forms, relationships, content metadata, rights, and publication state are held in Supabase. Trusted Flying Over Time and Pre code validates those records and turns them into semantic server-rendered pages. Stored content cannot inject arbitrary React, JavaScript, HTML, or design classes.
The same approved revision can produce a responsive web page, a clean print layout, a JSON document, and a readable source projection without maintaining four separate copies.
Institutional boundary
Technology support does not transfer organizational ownership.
What this enables
A website that behaves like an institutional record—not a stack of disposable pages.
Versioned publication
Every published page can identify its approved revision, source digest, status, and update time.
Responsive and printable
Each page is designed to read well on a phone, desktop, printed sheet, or generated document.
Machine-readable
The same trusted document can be retrieved as structured JSON or readable text for reuse and accessibility.
Portable content
Content is not trapped in the Git repository or coupled to a single page component, CMS, model provider, or storage vendor.
Protected operations
Public pages, editorial drafts, raw legacy snapshots, youth data, rights files, donor records, and board materials can remain distinct permissioned views.