Hosting Strategy

Primary URL Structure

All specifications are published under a single canonical authority:

https://jellylabs.ai/spec/<name>/v<major>

Examples

ProtocolVersionURL
DIDPv1https://jellylabs.ai/spec/didp/v1
PPPv1https://jellylabs.ai/spec/ppp/v1
DIDPv2 (future)https://jellylabs.ai/spec/didp/v2

Optional Mirror

A dedicated subdomain can mirror the specs:

https://specs.jellylabs.ai/<name>/v<major>

Implementation

Using Cloudflare Page Rules or Workers:

specs.jellylabs.ai/* → jellylabs.ai/spec/*

Benefits

  • Dedicated subdomain for indexing and clarity
  • Supports future separation without changing canonical URLs
  • Enables specs-focused SSL certificate if needed

Current Architecture

Single Site (Current)

jellylabs.ai/
├── /spec/          # Normative specifications (immutable per version)
│   ├── /didp/v1
│   └── /ppp/v1
└── /docs/          # Explanatory content (can evolve)
    ├── /methodology
    ├── /workflow-contract
    └── ...

Future Split (At Maturity)

When trigger conditions are met, split into:

specs.jellylabs.ai/     # Canonical specifications
docs.jellylabs.ai/      # Explanatory documentation

See Specs vs Docs for trigger conditions.

Deployment

Static Site Generation

  • Built with Astro
  • Output: Static HTML/CSS/JS
  • No server-side rendering required

Hosting Platform Options

PlatformProsCons
Cloudflare PagesFree, fast CDN, easy DNSLimited build minutes on free tier
VercelGreat DX, automatic previewsMay have cold starts
NetlifyGood form handlingSimilar to Vercel
GitHub PagesFree, simpleLimited features
  1. DNS already managed via Cloudflare
  2. Native integration with Workers for redirects
  3. Global CDN with excellent performance
  4. Free tier sufficient for spec hosting

Rationale

Single Canonical Authority

  • Avoids confusion about authoritative source
  • Simplifies linking and citation
  • Clear governance model

Mirror Support

  • Enables alternative access patterns
  • Supports future architectural changes
  • No impact on canonical URLs

Static Generation

  • Maximum reliability (no server dependencies)
  • Excellent cacheability
  • Version-controlled deployments