Home

How it works:

These notes are really for me because I'm totally not going to remember how this fucking thing works a month from now. Essentially it works as follows:

When the site is running, a cascade of effects will be triggered when changes are made. This is their order:

• On the site, changes to the data model are being watched and will trigger createOutput().
• createOutput() will POST the data model and will rewrite instructions/build.json.
• Gulp is watching for changes in this file, and will rebuild output/template.html.
• After that happens, it will trigger fetchPreview().
• fetchPreview() will trigger the refreshIframe() in the html/iframe.html, updating the iFrame with the contents of rebuild/template.html

Backend

There is a NodeJS/Express server that handles serving the site and handling the upload. It works in tangent with Gulp to watch for changes to rebuild