I thought of something similar, making the backend an application, and then have the site be static, publish would be an upload.
It would remove a number of concerns from the web server environment.
Changes could be synced similar to how git manages it and data could be stored locally or in some sort of shared database only access able from the client network.
But I always come back to a web app being better, a hybrid of the two might make sense in certain usecases.
I thought of something similar, making the backend an application, and then have the site be static, publish would be an upload.
It would remove a number of concerns from the web server environment.
Changes could be synced similar to how git manages it and data could be stored locally or in some sort of shared database only access able from the client network.
But I always come back to a web app being better, a hybrid of the two might make sense in certain usecases.
The smart thing about this setup would be CMS independence.
If you want to use another you would just have to accept that you cannot use it to edit the old pages.