[Feature] add this repo graph type tree ---- better ui for the generated code graph

[vtempest]

https://grab.js.org/docs/code-graph

https://github.com/vtempest/GRAB-URL/tree/master/docs

A feature-rich documentation template built on Fumadocs with Next.js 16, offering interactive code analysis, dependency graphs, AI integrations, OpenAPI docs, and full-text search out of the box.

[RaghavChamadiya]

Cool project! Could you be more specific about what you'd like to see here? Are you suggesting we adopt a similar tree visualization for the dependency graph, or is this more about the overall docs template?

A mockup or screenshot of what you have in mind would help a lot.

[vtempest]

1. add the collapsible tree table -- it has auto type imports from the whole folder and updates live. this is a feature you completely lack. this uses ast for ts/py/jsx etc. make sure all commons work

2. add the mermaid style code graph (get it fixed) -- yours is too hard to read. believe me i tried every tool out there for k graphs they all suck at big data. look at this https://mindmap.qwksearch.com code: https://github.com/vtempest/mindmap

3. use fumadocs it's a bit better than docusaurus or mintlify.

4. use vitest-web ui and integrate it . also have the repowise generate additional unit tests on the fly and be able to run them

5. wrap as open-vsx for the new ide's and market discovery. i'm interested in working on this so ping me online https://www.linkedin.com/in/alex-js-dev

[RaghavChamadiya]

@
Thanks for taking the time to lay all five out, this is genuinely useful to push back on.

Quick pass on each:

1. The collapsible tree with live type imports is the most concrete gap. We have the dependency graph and per-file context but not that exact UX. Worth scoping as its own feature.

2. We do already render mermaid diagrams (tool_diagram.py on the server, MermaidDiagram component on the web side) but the readability complaint is fair, mermaid falls apart fast at real codebase scale. The deeper question is whether to invest in better mermaid layout heuristics or move to a different rendering path entirely. Going to look at what mindmap.qwksearch is doing under the hood.

3. Fumadocs is a reasonable suggestion but the web UI is already a fairly custom Next.js app rather than a docs framework, so swapping the substrate is a bigger lift than it sounds. Open to it if there is a clear win we cannot get incrementally.

4. The on-the-fly test generation idea is interesting and pretty distant from where we are today. Want to think on that one before committing to a direction.

5. open-vsx packaging is something we should do regardless. Tracking separately.

Going to ping you on LinkedIn. Easier to talk through which of these you actually want to pick up first without doing it via issue comments.
@