reqlanOverviewIdeasFilesCode filesClustersAttributesGraphPrint

Idea detail

showcase

site/reqs/showcase.rq:5

block done siteshowcasecontent

Summary

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.

Jump to outbound references

Jump to inbound references

Navigation

Source file

site/reqs/showcase.rq

 community 50

community cluster

showcase.rq

file cluster

site/reqs

folder cluster

status: done

status cluster

tag: content

tag cluster

tag: showcase

tag cluster

tag: site

tag cluster

 Printable page

Static print-friendly idea sheet.

Ancestor context

showcase_module

Showcases are standardised and typed in TS content objects. 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.