Butter CMS

What differentiates Butter CMS from other similar products?

The javascript library works great with NextJS. You can have a different team creating the content to be consumed by the we application. You get to have

What is your favorite aspect of this product?

Ease of use for content creation and the javascript library is very easy to use as well.

What do you dislike most about this product?

Nothing for now. I have been impressed with the product as it does all that we need from it as a company.

What recommendations would you give to someone considering this product?

It is a great product if you need to build a JAMStack application.

What differentiates Butter CMS from other similar products?

The degree of customization is a game-changer. It is easy to customize components and modules that give you a wide range of functionality, everything as simple as copy and image variations all the way up to special customized 3rd party integrations where other tools are leveraging Butter components for display.

What is your favorite aspect of this product?

I love the level of control this gives our marketers over the content on our site and app. Powering your website with CMS components significantly reduces the level of custom development required to manage content, and gives you the ability to exponentially increase the amount of testing and customization / personalization for your storefront.

What do you dislike most about this product?

The interface is very utilitarian, and can take some time to learn your way around the tool. It is not a WYSIWYG editor, so creating content requires quite a lot of draft publishing / previewing trial-and-error. It is also way too easy to accidentally publish your content to a production environment. The CTA to publish does not have any confirmation box, so if you click it - you're live, so beware of that button unless you're truly ready. It is also not possible to clone full pages, so if you want to create a new page and use an existing one as a starting point, you have to rebuild it from scratch.

What recommendations would you give to someone considering this product?

You should definitely consult with your web developers and make sure they are comfortable integrating with a CMS product. Integrating with a product like this should be viewed as a long-term commitment, not a one-time rollover. There will always be a need to maintain, troubleshoot, enhance, and expand the usage of the tool once it is implemented, so make sure you have the resources (i.e. a dedicated group of engineers) who will be available to support for the long-haul. Don't assume this is something you can buy, set up in a month or two, and then have marketers fully on their own.

What differentiates Butter CMS from other similar products?

What we like about ButterCms is that it isn't as invasive as other CMS's that we have used. There is a lot of flexibility to create assets that fit our needs.

What is your favorite aspect of this product?

It is intuitive to use, not made complicated by trying to do too much.

What do you dislike most about this product?

I dislike the implementation of the different environments. Without a simple self-serving way to push content from a staging environment to production, it means we just do everything in production and save drafts. I don't especially like that. It would be nice to be able to promote individual assets from one environment to another to keep production more clean and protected.

What recommendations would you give to someone considering this product?

I would recommend it.