feat: restore documentation examples

[stone-lyl]

website playground:

https://github.com/user-attachments/assets/d5c31f1e-3bc4-4e19-8793-7b10b413f24b

node server playground:

https://github.com/user-attachments/assets/577ad028-14a6-43c3-b346-47506e886127

vscode

https://github.com/user-attachments/assets/908508a1-049b-4088-a390-815faeca2e6f

Before	After
❌	✅

• fix: resolve node server could not auto restart
  • the previous nodemon couldn't auto-restart on Windows. I've switched to pm2 now.

Before	After
❌	✅

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
data-story-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 21, 2024 8:26am

[stone-lyl]

Possible updateDiagram bug?

This is not a bug. Since the socket server doesn't save the diagram, it doesn't implement the updateDiagram method.

Unfolding bug

I've resolved the issue, but I found another one : the eventManager is shared on the same page. When I run the Unfolded Main diagram demo, the Main diagram demo resets to its initial state. I'm not quite sure if this issue needs to be addressed right away.

[ajthinking]

Possible updateDiagram bug?

This is not a bug. Since the socket server doesn't save the diagram, it doesn't implement the updateDiagram method.

Unfolding bug

I've resolved the issue, but I found another one : the eventManager is shared on the same page. When I run the Unfolded Main diagram demo, the Main diagram demo resets to its initial state. I'm not quite sure if this issue needs to be addressed right away.

I see!

Yes lets "solve" this for now by only supporting one component per page 👍