title: "Websites" description: "Cloudflare Pages projects, domains, deployment" type: development queries: ["how to deploy website", "what sites exist"] <<<<<<< HEAD updated: "2026-04-21" ======= updated: "2026-04-20"

356c6c8 (docs(infra): document dashe-email-worker + naming convention)

Websites & Cloudflare Pages¶

Most websites are deployed via Cloudflare Pages (npx wrangler pages deploy <dir> --project-name=<name>); some domains are served by standalone Cloudflare Workers instead — see Standalone Cloudflare Workers below.

Rig docs single source of truth: topology, auto-deploy, linking, and rollout for all rig documentation is maintained at https://docs.rig.dashecorp.com/docs-architecture/. Read that before editing rig doc plumbing — the section below is just the Cloudflare-level summary.

Cloudflare Pages Projects¶

Project	Custom Domain	Purpose	Source Repo	Last Modified
dashecorp	dashecorp.com, www.dashecorp.com	Dashecorp main site — app pages, blog, per-app landing pages	Stig-Johnny/dashecorp (`website/`)	Active
invotek-no	invotek.no, www.invotek.no	Invotek AS company website	Stig-Johnny/invotek-no-2023	Active
nutri-e	www.nutrieapp.com	Nutri-E app website	—	Active
cuti-e	cuti-e.com	Cuti-E platform marketing site	—	Active
cutie-admin-dashboard	app.cuti-e.com	Cuti-E admin dashboard (customer conversations, analytics)	—	Active
cutie-super-admin	cutie-super-admin.pages.dev	Cuti-E super admin panel	—	Active
scout	scout.dashecorp.com	Scout tool	—	Active
invotek-docs	invotek-docs.pages.dev	Internal documentation site	—	Active
infra-registry	infra-registry.pages.dev	This infrastructure registry	Manual deploy from `/tmp/infra-deploy/`	Active
<<<<<<< HEAD
rig-docs	docs.rig.dashecorp.com (backend: rig-docs.pages.dev)	Rig MkDocs aggregator — pulls each rig repo's `docs/` hourly + on dispatch. Hosts `/brain/`, `/docs-architecture/`, `/components/<repo>/`.	dashecorp/rig-gitops (`docs-site/`, build-docs.sh)	Active
rig-research	research.rig.dashecorp.com (backend: rig-research.pages.dev)	Astro Starlight — BRAIN.md, `/brain/`, `/map/`, research, proposals, user-stories, whitepapers	dashecorp/rig-docs	Active
=======
rig-docs	rig-docs.pages.dev, rig.dashecorp.com/docs	Rig architecture / onboarding / runbooks (Astro, BRAIN + facts)	dashecorp/rig-docs	Active
rig-research	rig-research.pages.dev, rig.dashecorp.com/research	Rig experiments, papers, notes	dashecorp/rig-research	Active
conductor-e-docs	conductor-e-docs.pages.dev, rig.dashecorp.com/conductor-e	Conductor-E orchestrator docs	dashecorp/rig-conductor	Active
mac-executor-docs	mac-executor-docs.pages.dev, rig.dashecorp.com/ibuild-e	iBuild-E agent docs	(legacy name, tracking rename)	Active
>>>>>>> 356c6c8 (docs(infra): document dashe-email-worker + naming convention)
dashecorp-docs	dashecorp-docs.pages.dev	Dashecorp internal docs	dashecorp/dashecorp-docs	Active
run-the-docs	run-the-docs.pages.dev	Run the Docs YouTube production	Stig-Johnny/run-the-docs	Active
ai-accountant	ai-accountant-yl9.pages.dev	AI accountant experiment	—	Active
atl-docs	atl-docs.pages.dev	ATL-E docs (legacy — agent retired)	Stig-Johnny/atl-agent (`docs/`)	Stale
gran-canaria-plan	gran-canaria-plan.pages.dev	Travel planning (personal)	—	Active

<<<<<<< HEAD

Unified rig domain (post-consolidation 2026-04-21)¶

Canonical URLs — always link these, never the *.pages.dev backends:

URL	Role
`rig.dashecorp.com/`	Landing page (Worker-rendered, managed in `dashecorp/infra` → `cloudflare/dashecorp.com/workers/rig-router.js`)
`rig.dashecorp.com/docs/*`	301 → `docs.rig.dashecorp.com/*` (legacy compat)
`docs.rig.dashecorp.com/`	MkDocs aggregator — engineering reference. Hosts `/brain/`, `/docs-architecture/`, `/components/<repo>/`, `/whitepaper/`, `/architecture/`, `/guides/`
`research.rig.dashecorp.com/`	Astro Starlight. Hosts `/brain/`, `/BRAIN.md`, `/map/`, `/research/`, `/proposals/`, `/user-stories/`, `/whitepapers/`

Retired 2026-04-21: conductor-e-docs.pages.dev, mac-executor-docs.pages.dev — their content now lives under docs.rig.dashecorp.com/components/rig-conductor/ and docs.rig.dashecorp.com/components/rig-agent-runtime/.

Plumbing, topology, and rollout log: https://docs.rig.dashecorp.com/docs-architecture/.¶

Unified rig domain¶

rig.dashecorp.com is fronted by the rig-router Cloudflare Worker (managed in dashecorp/infra → cloudflare/dashecorp.com/rig-router.tf). Path prefixes route to existing Pages projects so each source repo keeps its own deploy-on-merge workflow:

Path	Backend
`/`	Worker-rendered landing
`/docs/*`	`rig-docs.pages.dev`
`/research/*`	`rig-research.pages.dev`
`/conductor-e/*`	`conductor-e-docs.pages.dev`
`/ibuild-e/*`	`mac-executor-docs.pages.dev`

/brain is deferred — tracked as a follow-up to dashecorp/infra#92.

356c6c8 (docs(infra): document dashe-email-worker + naming convention)

Dashecorp Website Structure¶

The dashecorp.com site serves as the hub for all apps. Structure in Stig-Johnny/dashecorp/website/:

website/
├── index.html          — Main landing page
├── codi-e/             — Codi-E page
├── count-e/            — Count-E app page
├── drink-e/            — Drink-E app page
├── fast-e/             — Fast-E app page
├── heart-e/            — Heart-E app page
├── reward-e/           — Reward-E (Star Rewards) app page
├── llms.txt            — AI-readable app list
├── sitemap.xml         — SEO sitemap
├── feed.xml            — RSS feed
└── images/             — Shared assets

Domain → Pages Mapping¶

Domain	CF Pages Project	CF Workers on same domain
dashecorp.com	dashecorp	—
invotek.no	invotek-no	invotek-account-deletion, invotek-privacy-policy, grafana tunnel
nutrie.app	— (Workers only)	nutrie-dsld, nutrie-openai, nutrie-apple-webhook, nutrie-stats-rss
nutrieapp.com	nutri-e	—
cutiefeedback.com	— (Workers only)	cutie-worker, cutie-worker-sandbox
cuti-e.com	cuti-e (marketing), cutie-admin-dashboard (app subdomain)	—
scout.dashecorp.com	scout	—

Private/Personal Sites¶

Site	Repo	Description
Stig-Johnny CV	Stig-Johnny/cv	CV/resume (English + Norwegian)
private-sites	Stig-Johnny/private-sites	Contains: moving-planner

Standalone Cloudflare Workers (non-Pages)¶

Worker	Source Repo	Purpose
email-inbox	dashecorp/dashe-email-worker	Cloudflare Email Routing → D1 ingest for agent inboxes (`agents+*@dashecorp.com`). Deploy on merge via wrangler.
<<<<<<< HEAD
rig-router	dashecorp/infra (Tofu-managed)	`rig.dashecorp.com/` landing page + 301 of `/docs/*` to `docs.rig.dashecorp.com`. Subdomain traffic (`docs.rig` / `research.rig`) bypasses the Worker and goes straight to Pages.
=======
rig-router	dashecorp/infra (Tofu-managed)	Path-prefix proxy on `rig.dashecorp.com` to rig-docs/research/conductor-e/ibuild-e Pages projects.
>>>>>>> 356c6c8 (docs(infra): document dashe-email-worker + naming convention)

Both are managed through git/CI — do not deploy manually from a laptop.

Naming convention¶

rig-* — engineering rig repos (agents, orchestration, memory)
dashe-* — shared dashecorp platform (new: dashe-email-worker; planned: dashe-docs renamed from dashecorp-docs)
Product names (nutri-e, cuti-e, star-rewards, ...) — one per app
Unprefixed — only for genuinely cross-cutting repos. infra is the canonical example (IaC for both rig and dashe).

Rollout tracked in dashecorp/infra#99.

Deployment¶

All Cloudflare Pages projects use manual deploy (no git integration):

# Deploy a project
npx wrangler pages deploy <directory> --project-name=<name> --branch=main

# Example: deploy dashecorp website
npx wrangler pages deploy repos/dashecorp/website --project-name=dashecorp --branch=main

# Example: deploy infra registry
npx wrangler pages deploy /tmp/infra-deploy --project-name=infra-registry --branch=main