farskid / xstate.tips

Tips and tricks of using xstate for UI Development
https://xstate.tips
18 stars 0 forks source link

Epic: Tip Page #20

Closed farskid closed 3 years ago

farskid commented 4 years ago

Plans for the tip page:

Each tip should:

Demos

Each demo will have to have at least a demo.html and demo.js. The JS file can be a single bundle of demo's framework of choice if needs be. This JS file will also contain some boilerplate code for tip page and demo frame communication.

Demo files should live under /static/[demo-name]/ directory.

Demo and Tip communication bridge

The bridge is a global variable defined on the tip page window. This variable will contain the frame's interpreter info so that we could extract current state and context to be shown as debug values on the tip page.

Tip compilation process

Tip page layout

image

farskid commented 4 years ago

@jamestthompson3 Let's keep this issue as the master and split off subtasks into separate issues.

github-actions[bot] commented 4 years ago

This issue is marked as stale due to inactivity.