It's just a static site. Only the CMS is "dynamic" (though it itself is just a 10 line HTML page with a bunch of client side JS that talks to firebase).
Saves to that CMS, which is hosted statically, then send a build notification to our node based build servers, which then regenerate new static html files (from template you deployed to us) and send them to the proper place. Indexing and SEO are then just as they are for any other static site.
In local development, this is done through simple watch commands in Grunt, similar to what you'd see in something like Jekyll.
Yes, we think there's probably a separate product there as well. I'd always wanted to do something like the formbuilder but was usually trapped in more traditional dbs. Always got hung up on how you'd handle data migrations and the like. Moving to Firebase and working with essentially a string database in JSON really opened that side up. The only bummer is that we basically have to do lots of clean-up anytime there is relational data (which we allow through the system).
The CMS designer is the interesting part to your design, the static site part is easily handled through something like Varnish. Do you have further plans for extending the CMS designer?
Saves to that CMS, which is hosted statically, then send a build notification to our node based build servers, which then regenerate new static html files (from template you deployed to us) and send them to the proper place. Indexing and SEO are then just as they are for any other static site.
In local development, this is done through simple watch commands in Grunt, similar to what you'd see in something like Jekyll.