exercise outline

[ghost]

i'd like to brainstorm a little bit on what the structure of the exercises could look like. so far we have

1. setting up create-choo-app
2. understanding the basic structure by implementing a line of code in an event listener

i'd like to do stuff such as:

• choo-devtools
• routing
• prebuilt events
• understanding choo's building blocks
• maybe even browserify stuff? could be doable using bankai

[ghost]

/cc @yoshuawuyts @substack (since i believe you expressed interest in this)

[yoshuawuyts]

Was thinking it might perhaps be fun to follow the reference guide's bits first:

• views (link)
• stores (link)
• routing (wip, pr)
• components (tbi)

And then work onto higher level concepts such as:

• debugging (choo-devtools, choo-hooks)
• networking (choo-websocket, choo-sse)
• threads (webworkify, Atomics)
• forms (native form validation is underrated / underused, autofill, credential-management)
• analytics (microanalytics, choo-hooks, fair-analytics — we should perhaps create a choo-analytics module, lol)
• accessibility (aria-live-regions)
• offline data (nanoidb, choo-service-worker)
• speech api (choo-tts, choo-stt)

Not all are equally accessible, is my guess — but some of these can be lots of fun & useful!