A brand new headless CMS built on core web standards, blazing fast with immense flexibility for both developers and editors.

Strife – Reinventing Content Management

https://strife.app/blog/the-story-behind-the-name

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”.

Cool, that you signed up. What stack are you working with at the moment?

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.

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?

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 :)

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. https://strife.app/blog/the-story-behind-the-name

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.

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.

Posts