Documentation
Part 1: Mental Models
Before you write code, you need a way to think about HTTP.
- What this is
Understanding Hectoday HTTP's purpose and philosophy
- How to read these docs
A guide to understanding Hectoday HTTP's documentation structure
- A mental model of HTTP
Understanding HTTP from first principles
Part 2: Core Concepts
The framework's primitives: handlers, facts, and guards.
- The web standard foundation
How Web Standards provide the primitives for HTTP servers
- Your first server
Building your first Hectoday HTTP server
- Describing Facts
Extracting request data without making decisions
- Validation without control flow
Using validation to describe data, not control requests
- Guards: making decisions explicit
Using guards to control request flow explicitly
Part 3: Composition
How the pieces fit together to build larger APIs.
- The request lifecycle (fully explicit)
Understanding the complete path of every request
- Hooks: the three extension points
Understanding onRequest, onResponse, and onError hooks
- Errors are responses
Handling failures explicitly without exceptions
- Composition over configuration
Building larger APIs from small, reusable pieces
Part 4: Real Concerns
Security, static files, and runtime differences.
- Security as a first-class concept
Designing secure APIs with explicit security controls
- Static files and assets
Serving static files explicitly without magic conventions
- Runtime independence
Running the same code across Deno, Bun, and Cloudflare Workers
Part 5: Reference
Testing, API reference, and philosophy.
- Reference
Complete API reference for Hectoday HTTP
- Philosophy (revisited)
Why Hectoday HTTP makes these design choices
Helpers
Copy-paste patterns for common tasks. Not built-in—customize for your needs.
- maxBodyBytes: limit request body size
Guard helper to limit request body size
- Zod validator: schema validation adapter
Validator adapter for using Zod schemas with Hectoday HTTP