Web application
Managed Link Site
A small site with a proper publishing workflow.
SYSTEM ARCHITECTURETHE PROJECT
A server-rendered link website with a private administration interface and managed content.
A lightweight public page and a private editing surface share a simple content model. Pages Functions render the public view from KV data, while authenticated updates pass through the administration boundary. The result is a focused managed website rather than a manual list of hard-coded links.
- Server-rendered public content
- Private administration interface
- KV-backed data and authenticated updates
Independent managed website project.
UNDER THE SURFACE
How it fits together.
The public route renders stored content. The administration route uses a separate authenticated path to validate and persist edits.
Swipe or scroll the diagram to inspect it. The components are also listed below.
- 01Public request
Browser page visit
- 02Pages Function
Server-rendered view
- 03KV content
Stored links and metadata
- 04Admin interface
Content editing
- 05Authentication
HMAC-signed session
- 06Update route
Validated content writes
START WITH ONE EMAIL
Need something
like this?
Tell us what you would use it for. The four lines on the right are enough to start.
There is no form to fill in and nothing to sign up for.
WHAT TO PUT IN IT
- The taskWhat is done by hand today, and how often.
- The toolsWhere the data lives: files, sheets, apps.
- The resultWhat a good outcome looks like for you.
- The timingWhen you need it.
The button opens your email app with the four questions already in the message. Examples: how to write a software brief.