You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Great idea, thank you @hrstoyanov 🙏 This is adjacent to a couple of open threads: #504 (import existing ADR docs) and #346 (a memory.md). The graph today is code structure first, so correlating prose docs with code is a larger feature.
The realistic first step is lighter than full doc indexing: extract headings and the code symbols a doc references (fenced code identifiers, inline code spans, explicit links) and create "documents" edges to existing graph nodes, rather than semantically embedding the prose. Which formats matter most to you, in priority order (Markdown and MDX, AsciiDoc, HTML)? That'll help us scope a first cut!
Thanks for clarifying that you convert scraped HTML documentation to Markdown, and for your patience while this waited in triage. That gives useful context for the format question above.
We’re keeping Issues focused on actionable defects. Please open a Discussion with this request and a link back here, so documentation indexing and links between headings, referenced symbols, and the code graph can be explored together.
I’m closing this issue as an administrative redirect to that discussion venue. Feature acceptance, prioritization, and implementation timing remain undecided.
Activity
DeusData commentedon Jun 18, 2026
Great idea, thank you @hrstoyanov 🙏 This is adjacent to a couple of open threads: #504 (import existing ADR docs) and #346 (a
memory.md). The graph today is code structure first, so correlating prose docs with code is a larger feature.The realistic first step is lighter than full doc indexing: extract headings and the code symbols a doc references (fenced code identifiers, inline
codespans, explicit links) and create "documents" edges to existing graph nodes, rather than semantically embedding the prose. Which formats matter most to you, in priority order (Markdown and MDX, AsciiDoc, HTML)? That'll help us scope a first cut!hrstoyanov commentedon Jun 18, 2026
I have a web scraper tool that downloads documentation (html) and converts it to markdown.
You may want to take a look at QMD - it does very well with the docs, not so much with figuring out code and graphs
Ideally I want one tool that does it all
hrstoyanov commentedon Jun 18, 2026
Btw I love the "single fast executable" approach. Too much models and python slop out there
DeusData commentedon Oct 2, 2026
Thanks for clarifying that you convert scraped HTML documentation to Markdown, and for your patience while this waited in triage. That gives useful context for the format question above.
We’re keeping Issues focused on actionable defects. Please open a Discussion with this request and a link back here, so documentation indexing and links between headings, referenced symbols, and the code graph can be explored together.
I’m closing this issue as an administrative redirect to that discussion venue. Feature acceptance, prioritization, and implementation timing remain undecided.