I was wondering if Elements makes any assumptions about the site backend? For instance, is Elements assuming (or requiring) a LAMP stack (Apache + PHP), or is it simply geared towards entirely static sites at this time?
For instance, will it possible to add custom functions for sites deployed via Cloudflare Pages? Also, being able to add Cloudflare redirects, along with error pages and headers within a site would be helpful. These would simply need to be passed-through on build.
Worst case I could always keep these in a separate workspace and merge them when I deploy, but being able to have them (or at least the bits that don’t require version control) in an Elements site (editable through a 3rd party editor; ie: Nova or Code) could be helpful.
You can deploy a static HTML site now with RapidWeaver Classic on something like Cloudflare pages if you know how, so I think you’ll be able to do the same with RapidWeaver Elements. They’re pretty backend agnostic.
We’ve got some interesting ideas regarding some built-in solutions that we are discussing. Amazon’s infrastructure has been tossed around as a serverless solution, however I lean towards Cloudflare’s infrastructure because they have more security and optimization features that can integrate with their serverless stuff (workers, pages, D1 Database, etc.). Plus I think their dashboard is easier to navigate. Maybe a couple options could be good.
Thanks @dang, yes that generally answers my question.
Having used AWS for years (and LAMP before that), I find that not only is Cloudflare MUCH easier to use, but its generous free tier is often more than enough for many projects.
Very glad to hear you’re leaning towards Cloudflare as I think it would pair nicely with Elements (especially DNS, CDN, Pages, Images, Stream, R2, D1, Workers, etc). Add a decent little tutorial/guide to getting set-up with Cloudflare, and Elements becomes a very cost-effective, easy and fun (judging by what I’ve seen so far) way of creating and deploying modern websites.
