I have copied this Page from Andreas Sefzigs Homepage.

This is a Homepage Page.
The content is published.
It has the title "Tech Stack".
The summary is "The Markdown-first system that lets humans and Agents author, compile, and serve this Homepage.".

The canonical Web URL is `https://homepage.sefzig-net.workers.dev/docs/stack`.
The Markdown URL is `https://homepage.sefzig-net.workers.dev/source/pages/docs/stack/Content.md`.
The Prompt URL is `https://homepage.sefzig-net.workers.dev/source/pages/docs/stack/Prompt.md`.

The Markdown:
"""
# Tech Stack

_This Homepage is an application for Humans and Agents._

We author only readable Markdown sources. A local compiler turns those into typed artifacts for a React Router application, while Cloudflare delivers the result.

> One source for one application and multiple representations.

Internal and external Agents are provided with the content and custom instructions for every page.

## Markdown is the source [v]

_All content lives as Markdown files in a filesystem._

All content lives as Markdown files in a local filesystem.

![Markdown(full)](md.webp)

Markdown (with Frontmatter) is authored in `Content.md` and sanitized as `Markdown.md` for external systems. `Prompt.md` provides Agents with custom directions.

> The content is portable and readable for both Humans and Agents.

Read more: [Markdown](https://homepage.sefzig-net.workers.dev/docs/markdown), [Prompts](https://homepage.sefzig-net.workers.dev/docs/prompts).

## One source, multiple uses [v]

_The source is converted for various audiences._

The source is converted for various audiences.

![Loop(full)](loop.webp)

The generator validates and reshapes authored source into runtime data, public source views, Agent-readable Prompts, and the registries the Homepage uses to assemble itself.

> Once assembled, React Router handles the presentation.

## A compiler does the work [v]

_A local compiler generates the distributions._

A local compiler generates the distributions.

![Node.js(full)](node.webp)

A Node.js Backend reads authored content and App distributions, validates frontmatter and Markdown, resolves Prompt templates, and emits importable TypeScript artifacts for the Frontend.

It turns authored structure into the registries the runtime needs: routes, navigation, and the content.

> With local generation, the deployed runtime is simple.

## React is the interface [v]

_React renders the Homepage from generated data._

React renders the Homepage from the generated data.

![React(full)](react.webp)

The same runtime can present Pages, Posts, Presentations, Media, Preferences, and integrated Apps through shared UI primitives and route modules.

> React Router turnsthe pages into an application.

![React Router(full)](router.webp)

React Router supplies the application shell and route model. The Homepage uses ordinary path URLs, nested presentation routes, server-backed behavior, and an SSR-capable runtime.

## Vite is the driving force [v]

_The build layer turns the data into an application._

The build layer turns the data into an application.

![Vite(full)](vite.webp)

Generated data and frontend code become the application. Vite connects local development, generated content, and the React Router build.

> Changes are visible immediately on localhost.

![TypeScript(full)](ts.webp)

TypeScript makes the generated contract visible to the Frontend. Authored Markdown remains pleasant to edit while the runtime receives structured, validated modules.

## Cloudflare delivers the app [v]

_The finished application runs close to its audience._

The finished application runs close to its audience.

![Cloudflare(full)](cf.webp)

The production Frontend runs as a Cloudflare Worker with its client assets delivered alongside it. Cloudflare R2 and CDN delivery extend the same model to managed media, including adaptive HLS video generated locally.

> I love Cloudflare for it's simple effectivenss.

The deployment target is part of the architecture: local generation produces the artifacts that the deployed runtime serves.

## Customizable agent interface [v]

_The Homepage explains itself to agents._

The Homepage explains itself to agents.

![Agents(full)](ai.webp)

A generated `Prompt.md` combines a reusable template with its related `Content.md`. It gives an Agent the metadata and partly customized instructions in a predictable format.

> This makes the Homepage inspectable and teachable.

[Read how Prompts are generated](https://homepage.sefzig-net.workers.dev/docs/prompts)
"""