11. Websites as public projections

Walk through the visual explanation →

Publishing is a boundary

A Profile, Production, Team or other eligible context may support public presentation. That does not make its private application records public. A Website is a configured projection of selected information, with publication as an explicit step.

Canonical identity and ownership remain in the application domain. Website configuration controls presentation. Publication decides which reviewed presentation becomes available through a public domain.

Why a projection

An unrelated website object that duplicates every identity field creates competing editing truth. Directly publishing private domain records creates an exposure problem. A projection can reuse authorized source information while limiting public output and retaining presentation-specific configuration.

The model still needs deliberate handling of updates. A change in canonical information and a public publication version need not mean the same thing. Draft configuration and issued public presentation should not be confused.

Different audiences

A production contact view serves participants under current policy. A public website serves anonymous visitors. Public presentation can have useful information without serializing private member context, operational obligations or internal source references.

The conceptual path is canonical context → public projection → website configuration → publication → Cloudflare → public domain. It explains responsibility without publishing provider credentials or private delivery endpoints.

The engineering site itself

This case study is operationally independent. It is built from public-safe authored content using Astro as a static compiler. It has no production API connection, account system or database. Moving it into a fresh repository should not require the Filmclusive Next.js build.

The engineering site’s separation makes the same projection principle concrete: public explanatory material is selected and authored for its audience rather than copied automatically from private implementation. Future tooling may assist candidate preparation, but it must not turn editorial review into automatic publication.