Discuss modularity of Kedro Viz

[astrojuanlu]

Hi @ravi-kumar-pilla, @astrojuanlu

This is amazing spike work @ravi-kumar-pilla —it has given us a lot to think about. I really appreciate the effort you’ve put into it

We need to evaluate maintainability, effort vs. impact, and alignment with future Kedro-Viz developments. Given that the second half of 2025 will focus on the Pipeline Editor, which will be a major architectural shift, I think we should take a step back and plan PS sessions to align on the best direction for Kedro-Viz.

Next Steps, can we do a PS session:

• Original problem - Kedro-Viz in Notebooks
  • Reviewing the user feedback we’ve received so far on the high fidelity prototypes
  • Understand what we can do to release an MVP soon
• UMD Bundling
  • What additional benefits would UMD bundling bring beyond notebook integration? cons to this?

and also another session on :-

• Broader Kedro-Viz Architecture
  • Flowchart Rendering as a separate Library
  • Separate the logic of Kedro project --> structure json pipeline in another package (Spin off pipeline inspection to separate package kedro#4363)
  • Pros/cons of the above two?
  • Would this help future-proof Kedro-Viz, especially for the Pipeline Editor?

Originally posted by @rashidakanchwala in #2256 (comment)