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.

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.

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?

This feels hand wavy, and while I like seeing the thinking, most people won’t care and simply won’t use your platform. Honest opinion: your brand is upstaging your product and domains are cheap.

Thought experiment: Would you use a dev platform called “Barf”? How about confidently recommending it to a client? I’d bet no, even if they had an insanely great post about how “bad API docs make us sick”.