Code reference detail
example.ts
reqlan rq/site/site/src/content/example.ts
| Idea | Status | Tags | Summary | Katz |
|---|---|---|---|---|
| accurate_rq_snippets_must_parse | done | Every site snippet that demonstrates accurate reqlan must parse against the Langium grammar. In scope: language- " rq " blocks ( landing syntax pairs, the example slice, the hero snippet, showcase `.rq` blocks ). Out of scope: ts / md / py snippets that only show `rq:` comment links. Invalid-on-purpose samples must not be labelled language- " rq ". Enforced by tests plus the content parse gate in ["../../site/scripts/validate-showcase-rq.mts"]. Showcases are a subset per [every_rq_block_must_parse] / [phase_1_parse_gate]. | 0.090 | |
| copy | done | Marketing copy lives in typed TS modules under ["../../site/src/content"], composed by ["../../site/src/content/site.ts"]. Shared types: ["../../site/src/content/types.ts"]. Copy stays decoupled from layout / styling. Copy should be really super minimal and concise if at all. ( show don't tell ) Copy should be user facing; not simply a description of the feature requirements. Production code doesn't have latent dev notes in visible components. Landing modules: [hero_section], [elevator_pitch_section], [featured_in_section], [motivation_section], [syntax_section], [example_section], [roadmap_section], [nav_graph], [faq_page], [sidebar_nav], [links], [footer], [sticky_cta_node], [quiz_sticker_tab]. | 0.336 | |
| example_section | done | Landing `#example`: one worked graph slice ( imports, file anchors, wildcards, status, tags, tests ). Copy lives in ["../../site/src/content/example.ts"] per [copy]. The slice must parse as accurate reqlan per [accurate_rq_snippets_must_parse]. | 0.091 |
Reference labels
accurate_rq_snippets_must_parse, copy, example_section