Code reference detail
faq.module.css
site/src/views/faq.module.css
| Idea | Status | Tags | Summary | Katz |
|---|---|---|---|---|
| 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 | |
| site | the / site folder contains a static Next. js App Router landing page for reqlan. should align with [brand] Copy modules: [copy] Document head: [meta_tags] | 0.040 |
Reference labels
"../../site/src/views/faq.module.css", ../../site/src/views/faq.module.css