future demo ideas: offline-first, data syncing, background tasks

I appreciated the recent blog post: [A Whole Website in a Single JavaScript File](https://deno.com/blog/a-whole-website-in-a-single-js-file).

I have some ideas for additional demos. Some of these might not be feasible yet but as Deno Deploy gets new features I hope they will become so. I think that being able to do these will really show how superior Deno Deploy is compared to other offerings.

1. A Whole Offline-First Installable Progressive Web App in a Single JavaScript File (I'm less concerned about a single file but creating an offline app that works on the edge when online but is usable offline too is greatly desired for any web apps these days)
2. Offline-First IndexedDB syncing (as s continuation of the previous idea, making it possible to store a web app's data for offline reads and writes that later when online syncs to the server; this would be especially awesome IMO if Deno Deploy supports IndexedDB and syncing between regions/instances and using that same syncing ability to sync an entire DB with clients or certain data sets based on users)
3. Scheduled/CRON jobs (I think this is already possible but things around lifecycle, what guarantees are in place to run a callback, versioning, etc. aren't clearly defined)