I'm unsure if you're being facetious so I'll take your comment at face value.
Government isn't a static thing - especially one that is elected by the people (for the people). Sooner or later members within said government will also consider retirement. So even if you can elect a government that disagrees with #1, you won't be able to hold it for too long.
Thanks for the explanation Sven. I got confused due to the terminology. I've usually seen similar projects referred to as static site generators. I sincerely wish you luck with the project.
There is one recommendation I'd like to make however. In the README, it might be nice to display some sample configuration and/or possibly a diagram explaining how all the pieces fit together. I'm most interested in learning how to get started with Webiny and what are the various cloud things I'll need to configure to get an operating system.
The official site looks great. However, I'm a little confused by this product. I'm having a tough time figuring out how content is managed by this system. The github page mentions that this is a serverless CMS. How does that work?
When you describe this as a CMS, I compare it to systems like Wordpress or Drupal. I realize you're selling this as a developer-friendly CMS. But seems like this is a developer-only CMS. How would a non-developer use this system to manage content?
Government isn't a static thing - especially one that is elected by the people (for the people). Sooner or later members within said government will also consider retirement. So even if you can elect a government that disagrees with #1, you won't be able to hold it for too long.