Separate design from operations
The implementation preserves an existing visual design while adding a content and hosting layer.
The contribution is implementation and tooling; visual-design authorship remains distinct.
W.07 / SITE & CONTENT OPERATIONS
XOT Studio
Keep the design. Give its operator control.
Why this
was worth building.
A site should remain useful to the person operating it after the implementation work is done.
An existing site needed a self-hosted foundation and a practical way to edit content and handle incoming messages.
The underlying
logic.
Preserve the existing design, map editable content into a visual administration flow, and connect form submissions to an inbox.
01Existing design
02Content mapping
03Visual editor
04Operator control
The decisions
inside it.
What you
can inspect.
A Next.js implementation with a visual editor, contact inbox and self-hosted assets, as documented in the repository.
Inspect the implementation ↗
The original visual design is not claimed as my authorship. This case focuses on the implementation documented in the source.
Have a related
problem?
Tell me what you want to make possible, where the difficulty is, and what a useful result would look like.