Make the repo more hosting platform agnostic

[glypse]

I'm finding it very opinionated that this template is Cloudflare-targeted. I understand it is the stack Motion Core uses, but I think this has the potential to be a popular template in the Svelte community, so defaulting it to something like GitHub pages would make sense to me, especially given that very little of the logic is server-side.

I do understand this would remove certain functionalities though, such as the llms.txt endpoint and such.

Or is there any way we could architect it so that the whole repo contains multiple target platforms and use only parts of the code depending on the end user config?

[66HEX]

This would require a major refactor, but we could split out the modules/packages responsible for specific features (llms.txt/satori/raw docs, etc.), with each feature supporting different modes (workers/node/static). Take Satori with resvg, for example - in the case of CF workers, it requires a small hacky patch; when deploying to a VPS, this patch can be bypassed; in the case of a static build, each image would need to be generated during the build