Idea detail
faq_page
reqlan rq/site/site.rq:361
block
done
Summary
The site exposes `/faq/` as a statically generated page answering a short set of common questions.
Copy lives in faq.ts and stays minimal per copy. Support answers point at 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.
Navigation
Attributes
Ancestor context
No ancestor chain recorded.
Outbound references
Inbound references
| Kind | Idea | Path | Snippet |
|---|---|---|---|
| references | routes | reqlan rq/site/site.rq | faq_page |
| references | components | reqlan rq/site/site.rq | faq_page |
| references | sidebar_nav | reqlan rq/site/site.rq | faq_page |
| references | faq_drift | reqlan rq/site/site.rq | faq_page |
| references | copy | reqlan rq/site/site.rq | faq_page |
Unresolved references
| Kind | Idea | Path | Snippet |
|---|---|---|---|
| None | |||
Local graph
Initialising graph…