Comment by volted

These are interesting options! Thanks for sharing your feedback. Dealing with an existing stack is an interesting problem. But frankly, to think of setting up an SSG and then plug it into a Cloud CMS frontend in my view sounds complicated. But I see the appeal for existing projects.

I think the question to figure out is: What would be a way to keep PRSS simple for the average person, but powerful enough for Devs? Currently the approach is to have the preset build system (to reduce third party dependencies and bugs), but provide the ability for devs to fork themes locally and use them in PRSS (this is supported).

Ideally folks should only need to download PRSS, and have the Wizard to automatically setup Git and the GitHub CLI, and then PRSS would take care of the rest. But as I hear of folks use cases, it brings some good perspective. I will definitely think about these further! Thanks!