Hosting Strategy
Primary URL Structure
All specifications are published under a single canonical authority:
https://jellylabs.ai/spec/<name>/v<major>
Examples
| Protocol | Version | URL |
|---|---|---|
| DIDP | v1 | https://jellylabs.ai/spec/didp/v1 |
| PPP | v1 | https://jellylabs.ai/spec/ppp/v1 |
| DIDP | v2 (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
| Platform | Pros | Cons |
|---|---|---|
| Cloudflare Pages | Free, fast CDN, easy DNS | Limited build minutes on free tier |
| Vercel | Great DX, automatic previews | May have cold starts |
| Netlify | Good form handling | Similar to Vercel |
| GitHub Pages | Free, simple | Limited features |
Recommended: Cloudflare Pages
- DNS already managed via Cloudflare
- Native integration with Workers for redirects
- Global CDN with excellent performance
- 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