Web Build Notes

Implemented behaviours

The website rests on underlying build, delivery, metadata, and interaction behaviours that keep it predictable.

• Built as static files rather than served from a live application backend.
• Uses browser and deployment rules for predictable loading.
• Reuses unchanged application files safely on repeat visits.
• Gives each major route page identity and social preview information.
• Publishes a sitemap so public routes are declared in one place.
• Exposes selected public content through a machine-readable route.
• Respects reduced-motion preferences during longer visual transitions.
• Supports keyboard operation, Escape close, and focus return in floating action controls.
• Confirms when copy actions succeed.
• Handles older or redirected page anchors without leaving the visitor at a dead position.

Portrait transition and navigation state

The portrait transition is visual entry behaviour. It is not application loading. Control availability is handled separately from the fade sequence.

• Visual fade state and page readiness are handled separately.
• Controls are released before the portrait fade has fully completed.
• Reduced-motion handling skips the long fade path.
• Cleanup removes transition state after the intro is no longer needed.

Interaction controls

Button-triggered action lists need clear close and focus behaviour. Clipboard actions need visible and accessible feedback.

• Floating actions behave like simple action lists rather than complex menu widgets.
• Escape closes the action list.
• Focus returns to the control that opened it.
• Copy actions report success after writing to the clipboard.
• Copy feedback clears after a short delay.
• Resume collapse controls appear only when there is something relevant to collapse.

Public structure

The website exposes public structure through route metadata, a manual sitemap, and a bounded canonical JSON endpoint. These surfaces describe selected public content outside the visible page layout.

• Routes declare public identity for browsers and link previews.
• The sitemap lists intentionally exposed public routes.
• /canonical.json gives machines a structured version of selected public content.
• The machine-readable content is limited to public claims and signals.
• It is not a private model of the website or its development process.

Static delivery

The public website is built as static output. Delivery behaviour is defined through generated HTML, static assets, and deployment headers.

• Generated files can be served without a dynamic application backend.
• Deployment headers define browser-facing delivery rules.
• Security policy is present in the generated HTML.
• Long-lived caching is limited to hashed application files.
• Public pages do not require a dynamic application server to render.

Closing

The practical constraint is consistency. Visual effects, interaction state, public data, and delivery rules must keep their proper limits.

• Visual effects must not decide when the page is usable.
• Controls must show their state.
• Machine-readable data must stay limited to public content.
• Delivery behaviour must be explicit.