For years, I've worked with CMS platforms that trap both developers and clients. One of the core missions of strife.app is to break free from these constraints. Here's a demo showcasing how Strife is utilized as a CMS for a web built with Astro and hosted on @github Pages.
Thread
Really interesting, just signed up for the waitlist. The name is not ideal if I ever have to sell a client on it, but project looks interesting and I’m looking forward to testing it.
We get this question quite often and I understand your concern. We see it a bit differently and I hope that this blog post explains it well. strife.app/blog/the-story…
Strife – Reinventing Content Management
A brand new headless CMS built on core web standards, blazing fast with immense flexibility for both developers and editors.
strife.app
I understand and I appreciate your honest feedback. Though I think your example is somewhat far fetched. A better example would be to compare Strife and Discord. They have more in common than Strife and Barf I think :)
Slack as another example. But you said yourself, you get this feedback enough from folks that you felt the need to write an explanation. Why not remove a point of friction early, while you still can?
Cool, that you signed up. What stack are you working with at the moment?