Fleet hero sections concept

Home hero

Purpose: explain Fleet in one glance and route the reader.

Suggested copy:

Eyebrow: Forge Fleet
Title: Run governed container jobs from Studio, API, or automation.
Subtitle: Fleet is a small host-side HTTP service that accepts job requests, runs Docker workloads on the same machine, records logs in SQLite, and gives operators a dashboard for visibility and recovery.
Primary CTA: Start in 10 minutes
Secondary CTA: View API reference
Tertiary CTA: Operate a production host

Hero support chips:

Single-host runner
Bearer-aware API
SQLite job ledger
Docker argv jobs
/admin operator dashboard

Start hero

Title: Find the shortest path to a working Fleet setup.
Subtitle: Pick the path that matches your role: evaluator, local developer, Studio user, API integrator, or host operator.
CTA: Choose your path

Learn 101 hero

Title: Learn Fleet from zero to first job.
Subtitle: Understand the mental model, run Fleet locally, submit a job, and verify it in the admin dashboard.
CTA: Begin with What is Fleet?

Build 201 hero

Title: Build real integrations on Fleet.
Subtitle: Use the Jobs API, upload workspaces, build requirement templates, front Fleet with Caddy, and integrate clients.
CTA: Start with the Jobs API guide

Operate 301 hero

Title: Run Fleet safely on a host.
Subtitle: Secure the API, observe jobs and host health, back up SQLite data, handle incidents, and upgrade with rollback paths.
CTA: Open the production checklist

Reference hero

Title: Fleet contracts and lookup tables.
Subtitle: HTTP routes, OpenAPI, JSON Schemas, environment variables, and error models for clients and operators.
CTA: Open HTTP API reference

Examples hero

Title: Copy, run, verify.
Subtitle: Practical snippets for curl, Python, TypeScript, CI smoke tests, Studio integration, telemetry, Caddy, and workspace upload.
CTA: Pick an example