two-website model (showcase a vs studio b).

# SUB-006 — Two-website model

Story

Original idea was one internal site for the Sett UX team. After dictating thoughts in the car, Ishai realized there are actually two distinct surfaces with different audiences:

• Site A (Showcase, M4) — teammate-facing show-and-tell. Browse design system, prototypes, glossary, JTBD, milestones, digest. Comments via Giscus. Lives at TBD subdomain, @sett.ai SSO.
• Site B (Studio, M5) — Ishai-only personal hub. Subjects shelf, action board, activity log, errands queue, mobile inbox, observability graphs. Lives at TBD subdomain, ishairevach@sett.ai only.

Don't merge. Different audiences = different surfaces. Stack shared (Astro + MDX + design tokens), deploys separate.

Decisions made

• 2026-05-06. Two separate sites. M4 Showcase + M5 Studio. Both at sites// in workspace.
• 2026-05-06. Site A keeps prototype gallery (read-only show); Site B gets prototype hub (action-rich w/ cloud + local + Figma + push status).
• 2026-05-06. Site A gets Giscus comments (free, GitHub-backed).
• 2026-05-06. Site A audience = Sett team only. Site B audience = Ishai only.
• 2026-05-06. Stack: both Astro + MDX. Site B uses Bricolage variant (B handoff). Site A visual TBD when implemented (after MVP ships).
• 2026-05-06. Studio site name = "Studio" (Ishai is a designer, fits the brand). Considered: cockpit, command-center, bridge, atlas, helm, forge, atelier, desk, console, den, shelf.

Open threads

(none — resolved as architectural decision)

Raw refs

• vault/04-Concepts/personal-studio-site.md — full concept doc
• vault/08-Design-specs/sett-ux-showcase-site.md — Site A spec
• vault/00-Milestones.md — M4 + M5

Last activity

2026-05-06 14:55 — Resolved. Site B implementation in progress; Site A deferred until post-MVP.