The bad news, however, is the moment you are delinquent on your payments, your self-driving car is alerted and takes you immediately to the authorities and straps you in until you are removed - at which time it returns to the pool for those who are more deserving.
…just wait until until you find out what your music taste has already projected into the NCIS enhance-enhance AI technology to say about your personality, and deviations from what is acceptable in the social credit society.
A trend I’m seeing more of these days is “headless” CMS systems - basically, a CMS that edits a static site. Netlify CMS, Forestry, Ghost, and Contentful are some examples. Generally, the site content will be in a Git repository, and you’d have some hosting service that automatically deploys from Git (eg. Netlify, Github Pages, or something self-hosted).
You get the advantages of a static site (completely secure, very fast to load, can be deployed directly to CDN edge nodes as it’s just static content, etc) along with many of the advantages of a traditional CMS (non-technical users can edit the content). The production site just contains static content, and the CMS part can be completely isolated from the production site (eg. hosted on a different server, on a different domain if you want).
Storing the site in a Git repo gives you history for the entire site. If someone does obtain access to the CMS and pushes a bad update, just roll back to an earlier commit.
I’ve even seen some proof-of-concepts for using WordPress as a backend, but compiling the site into a static site using Gatsby. Gatsby’s plugin system lets you load data from anywhere, so it can just send API requests to WordPress when building the site.
