Sideby / HandbookWEBSITE IMPLEMENTATION · V1.0OpenAPI ↓
THE SIDEBY WEBSITE

Follow the request.

A static public site and two server-side operations. Cloudflare Pages is the deployment platform.

One entry. Two paths.

ENTRYBrowser
GET /…Cloudflare Pages

HTML · CSS · JavaScript
SVG · Fonts · OpenAPI

Static response
POST /api/…Pages Functions

Validate → execute
→ confirm or reject

D1 database

Astro renders the public pages at build time. The browser receives complete HTML. JavaScript adds theme controls, purposeful scroll motion and form handling.

Each layer has a job.

The browser
Shows content, reads the theme preference, animates the concept, validates form fields and displays server-confirmed outcomes. It has no database credentials.
The static build
Produces the pages, assets, sitemap and OpenAPI contract. The output directory is dist/. No framework server renders the pages at request time.
Pages Functions
Routes in functions/api/ handle signup and removal. Shared code in functions/_lib/http.ts checks methods, origins, formats and body size.
D1
The DB binding supplies a dedicated database. Prepared statements persist signups, count validated attempts and remove registrations.

public/_routes.json limits Functions invocation to /api/*. Static security headers are defined in public/_headers; the API attaches its own response headers.

Where this system stops.

There is no purchase connector, reward engine, financial account, custody service, wallet, blockchain integration or partner API in this repository. Financial terminology describes the concept, not implemented settlement behavior.

Cloudflare Pages hosts both the static output and its Pages Functions bundle. This project does not deploy a standalone Worker application.

Follow a signup through storage →
REAL CODE. DOCUMENTED BOUNDARIES.Back to the handbook ↑