Build step for building Init.ml editors

[disconcision]

Currently we have a somewhat brittle, laborious, and diff-intensive process of populating the initial editors by exporting the whole app state and inserting zipper serializations into the code. What I want instead is something like a folder in the codebase with a plain-text file for each doc slide, which, at compilation time, is turned into the Init.ml serialization. Or alternatively if the parser is fast enough we could just do this at run time. In any case whatever we build could reasonably be part of the git ignore so we no longer get those chonky commit diffs.

Complexities:

• Doc slides with additional text at the top (not sure how this is implemented)
• Projectors (would need to add textual syntax for them)

I think I have a simple-ish story for the latter at least.

[7h3kk1d]

Just curious for your thoughts. If we don't want to textify the projector state can we do a sexp-serialization and just have a better interface for downloading it from the app? I can't tell if you want the text version for updating the files in vs code or just for the git diffing.