Code reference detail
faq.ts
reqlan rq/site/site/src/content/faq.ts
| Idea | Status | Tags | Summary | Katz |
|---|---|---|---|---|
| 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 | |
| faq_drift | done | The FAQ includes this question: How do you keep `.rq` files from drifting once the code moves on? `.rq` files are code. They are the source of truth. They are not a document. Specify material work as an idea first. Implementation and tests point back with rq-comments per [development_core.code_comment_references] and [development_core.testing]. A check requires each test to serve a requirement. Agents see only the ideas that attach to the files they touch. Mark a replaced idea deprecated and point to the new idea. The indexer flags missing references like a compile check. Copy lives in ["../../site/src/content/faq.ts"] ( item id `drift` ) per [copy] and [faq_page]. The sidebar nests this question as a same-page child per [sidebar_nav]. | 0.057 | |
| faq_page | done | The site exposes `/faq/` as a statically generated page answering a short set of common questions. Copy lives in ["../../site/src/content/faq.ts"] and stays minimal per [copy]. Support answers point at [support_page_reqs.support_page] and at phonebook surfaces ( GitHub stars, marketplace stars, issues / contribution, GitHub Sponsors, Discord ) rather than inventing URLs. Required topics: - how reqlan supports token efficiency - whether reqlan is the de facto standard for efficient developer-centric context management and semantic mapping - when to use reqlan - how `.rq` files stay in sync with code per [faq_drift] - how to support reqlan ( GitHub stars, GitHub Sponsors, VS Marketplace stars, Discord, contribution, bug reporting ) Sidebar nests FAQ question anchors as same-page children per [sidebar_nav]. Landing nav graph includes FAQ as a page node. | 0.132 | |
| support_page | done | Rank actions by ease and likelihood to nudge. Star on GitHub is first. Default view is a graph. Toggle Graph / Tiles / Table as icon buttons on the right of the header, with hover tooltips. Graph: cola layout, settled on first paint to the visible window; copy has no graph coordinates; each node moves with its label; nodes are draggable; a drop keeps the new position; a drag does not start the action; all nodes offset slightly toward the cursor; nodes repel so some canvas edges stay open; action radius is impact × ease and stays latent to users; action nodes are solid and flat; each action links to a smaller passive original-group node in secondary colour ( advocacy, community, cite, contribute, sponsor ); group labels grow on group hover; labels do not overlap. Hover on an action node shows a tooltip with the action blurb. Star and sponsor tags are featured in the orange brand colour: the Star action, sponsor actions, and the Sponsor group. Tiles: responsive flex layout. Table: action and group only. Ease, impact, and score stay latent. Action names use the aqua link colour in Graph, Tiles, and Table, including copy and share, except featured graph tags. Each table row runs the same action as the graph and tiles: open a link, copy, or share. Support via, in tile order: - one click - star on github - share - discord - a minute - cite - issues - post your certificate - say something nice on the Visual Studio Marketplace - say something nice on Open VSX - FREE stickers: show the world you are a reqling, via [phonebook] sticker-form - write - reach out and send an email - write a testimonial - sponsor - github sponsorship - direct sponsorship integrated with [phonebook]. Copy lives in ["../../site/src/content/support.ts"] per ["./site.rq".copy]. The site exposes `/support/` as a statically generated page. Sidebar nests Support section anchors as same-page children per ["./site.rq".sidebar_nav]. Landing nav graph includes Support as a page node per ["./site.rq".nav_graph]. | 0.112 |
Reference labels
copy, faq_drift, faq_page, support_page