http is where the portfolio becomes a working system: routing, auth/session transport, Datastar endpoints, SSE fanout, Maud views, and the live operational surface.
- router and middleware composition
- page handlers, Datastar partial handlers, and EventSource endpoints
- session-aware stream routing and event helpers
- page, partial, and component rendering surfaces
- trace surfaces that feed the operational UI
/for the portfolio landing page/labfor the operational demo surface/eventsfor the EventSource stream/demo/chat/*and/partials/*for the interactive support surfaces behind the demos
If you want to evaluate this crate quickly, start with /lab and the EventSource-backed surfaces. http is where transport behavior becomes inspectable.
- src/router/routes.rs for public route shape
- src/state.rs for HTTP-owned runtime state
- src/trace_log.rs for live vs diagnostic tracing behavior
- src/views/page.rs for the site shell
- src/views/partials/README.md for the reusable component vs demo-composition split
It keeps transport, rendering, and realtime delivery close together while still treating app and domain as the source of business truth. It is also where the repo proves that interactive pages can be assembled from reusable typed components instead of growing as route-local template sprawl.