Encouraging the adoption of a standard API model.
-
Okay, let's kick this one off with my idea for all CMS systems to adopt!
The biggest reason that content management systems are often compromised isn't just because of badly written plugins and themes. It's simply because the idea that you can log into your website to manage the website, it fundamentally a flawed design. It makes the website much more attractive as a target.
Many people don't seem to realize WordPress can operate headless and there's even a phone app that works to interact with your sites using the API. Other content management systems could adopt this idea. Imagine a world where you pick your CMS backend and use whatever front-end you want. We need a standard API for this.
So, that's what I want to propose.
-
I think I’ve spotted similar concept: https://strapi.io/
I think it is a great tool and while personally I love Go it won’t reach the popularity of JS or PHP. And adoption is a key here.
API-first approach is great and reflects the modern approach. However, this requires more careful decisions and actually may lead to building 2 products: API platform and client platform, to make sure bootstrap and customization is fast.
Obviously there must be a default implementation to make it possible fast-forward setup.I think CSS is relatively easy with CSS-framework.
OpenAPI might provide a convenient way to generate client-agnostic network layer.The components are tricky: I’m not a huge fan of React but this seems to be the most popular option. From another perspective there are framework-agnostic solutions like Astro.build, that actually misses a reliable API data source.
These solutions, however increases total complexity of the entire solution, but might provide more flexible solutions. Also high performance might be easier to achieve while splitting the client/data source roles.