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

From source to site.

Run the complete Pages runtime locally, verify the website, then publish the build to the existing Pages project.

Start with an isolated database.

Local development
# Node 24; project root
npm ci
npm run build
npm run db:local
npm run preview
# Open http://localhost:8791

Node 24 is the documented runtime. npm run dev starts Astro for visual development; it does not provide the Pages Functions API. Use the built site with Wrangler Pages dev to exercise forms and D1.

db:local applies the schema to the local D1 emulator. It does not modify production. Rebuild after source changes before running the Pages preview.

Check the actual behavior.

Validation
npm run check
npm test
# For a system Chromium browser:
PLAYWRIGHT_EXECUTABLE_PATH=/path/to/chromium npm test

The type check covers Astro pages and Pages Functions. Playwright starts the local runtime and tests persistence, duplicates, removal, rejected requests, failure states, mobile layouts, theme persistence, motion preferences and no-JavaScript content.

Test setup applies local migrations and clears only local temporary rate counters. Do not point destructive test fixtures at the production database.

After editing bindings, regenerate worker-configuration.d.ts with npx wrangler types. Do not hand-edit generated runtime types.

Publish through Cloudflare Pages.

Production release
# Authenticate with the intended Cloudflare account first.
npx wrangler whoami
npm run db:remote
npm run deploy

wrangler.jsonc defines the Pages project, dist/ output, runtime compatibility date and dedicated DB binding. The production branch is main.

The release command builds the static pages and uploads their assets plus functions/ with Wrangler Pages deploy. Run it from this project root. Database migrations and site deployment are separate operations.

SITE_URL can override canonical metadata at build time. Preview deployments must use an isolated D1 binding if they write test data. A Pages preview URL alone does not make its database isolated.

Find the right file.

src/content/brand.ts
Shared financial vocabulary, product description and FAQ answers.
src/pages/
Homepage, editorial pages, legal notices and documentation.
src/components/Artwork.astro
The original loop, cut, Part, return and collection drawings.
src/styles/
Base identity, homepage scenes, editorial layouts and handbook design.
src/scripts/
Themes, navigation, forms, scroll composition and copy controls.
functions/ + migrations/
API handlers, shared request checks and D1 schema.
public/brand/
Exported identity assets, font licenses and downloadable brand kit.
REAL CODE. DOCUMENTED BOUNDARIES.Back to the handbook ↑