thanks for sharing<p>I personally feel most graph patterns are just easier implemented using functions unless the graph has some other purpose like observability or even just visualization also those can always be added ;)<p>I prototyped a similar system at a hackerthon last year: <a href="https://github.com/Davidiusdadi/obsidian-node-canvas" rel="nofollow">https://github.com/Davidiusdadi/obsidian-node-canvas</a><p>Your docs would be more readable if you made the code blocks just wide enough so that the lines don't wrap.<p><a href="https://pocketflow.ai/" rel="nofollow">https://pocketflow.ai/</a> whitepaper link is 404ing btw.
I really like the idea and what you’re building here. That said, I’d argue the documentation website is the face of any open-source project. Reinventing the wheel rarely ends well — the current docs are hard to navigate and read.<p>Just use an off-the-shelf solution for docs, like Docusaurus, for example:<p><a href="https://github.com/facebook/docusaurus" rel="nofollow">https://github.com/facebook/docusaurus</a>