At Airtable, we make it possible for anyone—not just developers—to create the tools they need in order to do the work that matters to them. You don’t need to know any code to build a CMS that works exactly how your team wants.
If you’re also running a static site and wondering how best to go about collecting form submissions without a backend, then I’d highly recommend using Zapier, everytime. There is however one exception, and the reason I made the switch. And that reason is Netlify.
Tools like Hugo, Jekyll, and Gatsby have made building static sites a popular and practical choice for developers. One major disadvantage these tools have, however, is the need to regenerate and redeploy their files every time there is new content to publish. Automating this process will go a long way toward making your static site feel like a dynamic CMS. /