Code reference detail
index.ts
reqlan rq/site/site/src/content/showcases/index.ts
| Idea | Status | Tags | Summary | Katz |
|---|---|---|---|---|
| showcase | done | site, showcase, content | Every showcase demonstrates a mechanism, not a metaphor. Domain problem, the. rq that binds it, the real artifact in another language it binds to, and the thing the tooling hands back. Content is authored in TS objects per [showcase_module], not generated from this file at runtime. This file is the source of truth for intent, ordering, and editorial rules. | 0.040 |
| showcase_module | done | Showcases are standardised and typed in TS content objects. Types live in ["../../site/src/content/showcases/types.ts"]. Each showcase is its own file under ["../../site/src/content/showcases"]. ["../../site/src/content/showcases/index.ts"] composes them in [showcase_set] order. Each showcase file carries rq: comment references to its showcase idea and to the product ideas it demonstrates. Short version ( list card ): id, title, summary, tags, mechanism badge. Long version ( detail page ): full blocks array including payoff. Exist as a list page and as a full page per slug. Routes: `/showcase/` and `/showcase/[slug]/` — static export. Block kinds needed beyond today's code | features union: callout — the one-sentence point of the page exchange — query + response, terminal-styled diagnostic — editor-style error with quick-fixes diagram — visually distinct from code; never language- " rq " caption / mechanism fields on the showcase object Copy stays minimal and show-don ' t-tell, aligned with site copy rules. | 0.057 | |
| showcase_set | Ideaset (showcase_set) | 0.053 |
Reference labels
showcase, showcase_module, showcase_set