nice! i love the design system & overall UX! some thoughts/questions:
- i wonder if it would be more useful to be able to branch out from some previous message in a thread, vs being forced to branch out from the end of a thread. feels more natural to go back and branch out into some tangent/deep-dive.
- maybe there could be some autogen'd suggested branch-out topics/prompts?
- does the top-level chat composer input have context of other nodes on the canvas?
- is there a way to search across nodes?
- how do i delete a node?
- are there plans to try to unify this canvas experience with the primary duolingo-style course flow? if so, how?
react flow already supports connections, node dragging, zoom/pan and state support. I think D3 is better for custom data visualizations, but we’d need to build most editor behavior ourselves
nice! i love the design system & overall UX! some thoughts/questions:
- i wonder if it would be more useful to be able to branch out from some previous message in a thread, vs being forced to branch out from the end of a thread. feels more natural to go back and branch out into some tangent/deep-dive.
- maybe there could be some autogen'd suggested branch-out topics/prompts?
- does the top-level chat composer input have context of other nodes on the canvas?
- is there a way to search across nodes?
- how do i delete a node?
- are there plans to try to unify this canvas experience with the primary duolingo-style course flow? if so, how?
would you mind sharing why react flow over d3?
react flow already supports connections, node dragging, zoom/pan and state support. I think D3 is better for custom data visualizations, but we’d need to build most editor behavior ourselves
this is how my brain works!