Skip to content

Work Plan: Devonside Labs Marketing Site Repository

Objective

Scaffold a new implementation repository, devonside-labs-site, to hold a light static marketing front end for the Devonside Labs brand: a homepage plus a listing of any products that have cleared to-market status, each linking out to its third-party point of sale (e.g. Etsy for schedule-c-workbook). No backend, no checkout — purely a marketing/discovery surface, per the Founder's request.

Scope

  • Scaffold C:\Users\Stuart\repos\devonside-labs-site via scripts/create_implementation_repository.py (slug digital-products, per ADR-0014), as a second implementation repository for the Digital Products / Devonside Labs venture — distinct role from the existing devonside-labs repo, mirroring the precedent already established for Shelfery (shelfery app repo + shelfery-site marketing repo, both listed in portfolio/repository-registry.json).
  • Fill in README.md, docs/ai/product-vision.md, and docs/ai/architecture.md with known context (purpose, no-backend static approach, link-out-to-marketplace model).
  • Register the new repository in portfolio/repository-registry.json with status: planned (path only, no URL yet) until it is actually created and pushed to GitHub, following the same record shape as the shelfery-site entry (custom role, owning_venture field).
  • git init and an initial local commit in the new repository.

Out of scope

  • Creating the GitHub remote and pushing — a shared-state, hard-to-reverse action left for explicit confirmation in-session before being carried out.
  • Choosing which specific products appear on the site beyond schedule-c-workbook (the only product with a real marketplace link today) — future products get added as they clear to-market status.
  • Visual identity / brand assets for Devonside Labs — not yet finalized per ventures/digital-products/venture.json; the site scaffold will use placeholder styling, not invented brand assets.
  • Any change to the existing devonside-labs (app/generator) implementation repository.

Applicable authority

  • Root AGENTS.md; ventures/digital-products/AGENTS.md.
  • ADR-0014 — venture implementation repositories are the default pattern; this is a second, distinct-role repository for the same venture (marketing site vs. product-generation code), consistent with the shelfery/shelfery-site precedent already recorded in portfolio/repository-registry.json, not "one repository per product" (which ADR-0014 disallows).

Files expected to change

devonshire-digital (this repo): - work/active/2026-07-20-devonside-labs-site.md (this file) - portfolio/repository-registry.json (new planned entry for devonside-labs-site)

New repository (devonside-labs-site, separate git history): - Initial scaffold from templates/implementation-repository/, with README.md, docs/ai/product-vision.md, docs/ai/architecture.md filled in.

Assumptions

  • Stack: static site generator (Astro + Tailwind, matching shelfery-site's approach) is a reasonable default for a "light marketing front end" with no backend — flagged as an assumption in the new repo's docs, not locked in as irreversible; easy to swap before any real code is written.
  • The site starts with a single product link (schedule-c-workbook → Etsy, once that listing exists) and an "more products coming soon" placeholder, since no Etsy listing exists yet per the venture's product records.

Risks

  • Creating a second implementation repository per venture is a pattern precedent, not yet an ADR-documented rule — shelfery-site established it in practice but no ADR generalizes it. If this becomes a recurring pattern, it may warrant its own ADR; noted here rather than silently assumed as settled policy.

Validation plan

  • python scripts/check.py and python -m unittest discover tests in this repository after the registry update.

Progress checklist

  • [x] Work plan written.
  • [x] Repository scaffolded locally.
  • [x] README.md / docs/ai/product-vision.md / docs/ai/architecture.md filled in.
  • [x] Registry updated (planned status); venture.json known_implementation_repositories updated to match.
  • [x] git init + initial commit in new repository.
  • [x] scripts/check.py + tests run in governance repo — both passed.
  • [x] Confirmed with Founder: create the GitHub remote and push now; keep Astro + Tailwind; deploy target is Cloudflare Pages (per Founder's explicit instruction).
  • [x] GitHub repository created and pushed; registry/venture.json updated to active with the real URL.
  • [x] Re-ran scripts/check.py + tests after final registry update — both passed.

Decisions required (human)

  • Confirm before the GitHub remote is created and pushed (out of scope for this pass unless explicitly authorized).
  • Confirm the assumed stack (Astro + Tailwind, static) or specify a different one.

Handoff notes

Local scaffold only as of this plan; nothing pushed to GitHub. See work log below for status at handoff.

Work log

  • 2026-07-20: Wrote this plan; proceeding to scaffold.
  • 2026-07-20: Scaffolded devonside-labs-site locally via scripts/create_implementation_repository.py (slug digital-products); filled in README/product-vision/architecture; git-initialized with one commit. Registered in portfolio/repository-registry.json (planned, no URL) and updated ventures/digital-products/venture.json. scripts/check.py and the test suite both passed. GitHub remote/push left for explicit confirmation.
  • 2026-07-20: Founder confirmed: push now, keep Astro + Tailwind, deploy to Cloudflare Pages. Noted Cloudflare Pages as deployment target in the new repo's docs; created and pushed https://github.com/Devonshire-Digital/devonside-labs-site (private) via gh repo create --push. Updated portfolio/repository-registry.json and ventures/digital-products/venture.json to active with the real URL. Re-ran scripts/check.py and the test suite — both passed. Archiving this plan; task complete.

Report an issue about this page