Butter CMS Reviews & Product Details

As an engineering leader, I'm most concerned about the technical effort required to implement tools. Butter was dead-simple - set it up, grab the API key, and call their endpoints when needed.

The only tricky thing was a minor issue; we wanted to be able to filter/search all of our posts/content or grab all of the headers so we could display a "home page" for our blog, but they didn't have that ability at the time. It might have been implemented since, but it was performant enough to load all of our content simultaneously.

If you're looking for a simple, lightweight, cost-effective CRM for a small-medium size business, Butter is it. We tried a few others and they were either way too heavy/complicated or didn't have basic features.

The UI is quite intuitive, clear, and neat. Customer support is beneficial and friendly. APIs such as 'write' and 'image' are helpful. The preview feature is pretty cool. There was a solution for every feature we wanted to implement.

Butter CMS is alright in every way. Having a root preview URL without slugs is something that can be nice.

Easy content management with control of meta description and SEO. Managing icons from one source. Having a preview of the data before actually integrating it.

As a developer, working with a headless CMS has been great. I haven't had any issues with performance or reliability, and customer service has been incredibly helpful.

There are a few additional features that would be nice, but in my experience with a few other CMS options, Butter isn't behind the times at all.

We have multiple places on our site that require somewhat frequent content changes. These would be a pain in the butt for me, as a developer, to maintain. With Butter, I was able to set up those pages so that my non-tech team can be in complete control of the content.

As a developer, I used butter as a CMS to integrate with a Ruby/Jekyll stack. The documentation was easy enough to follow and the content comes in an easy to manipulate format. This made it great to fully customise the pages I was working on. It made it a lot easier to create new style of pages with great content. As a content creator, Butter is great and super easy to use to create website pages, blog posts and also update pre-existing content. The non-technical people I worked with found it a breeze to learn and use.

I think I would have liked more documentation into how to integrate at the beginning. There was a little bit to figure out. When I would research, I would find many blog articles from Butter explaining about "being able" to do these things, but not so much as to "how".

Definitely getting non technical people, able to create content on the website, without having to use confusing applications or even dive into the code itself. The Auto-updates from an API driven solution is also a plus.

Easy to use. Nice UI. Lots of features. Ability to create reusable components.

Moving content and schemas between staging and production has to be done manually.

We are using it as our content and cdn for assets for our production application. It makes it very easy to make updates to our websites.

- Easy to set up. - Very flexible and customizable. - Customer service reply quickly and will accommodate most of the customer's specific needs.

It would be great to add in feature to move content between environments.

We don't have to deploy to production for simple copy changes, but we can just easily change them from butterCMS without any hassle.

Configuration of Butter is pretty simple and straightforward. We are able to use it to essentially maintain multiple versions of our app by customizing content for specific clients. As a Product Manager, it saves a lot of time for my engineers as I can go in and update/change items myself instead of relying on them to alter hardcoded copy.

We primarily use the Collection function, and there are a couple things that are just a bit annoying about it. Nothing that we can't work around, but: 1. Because we have a lot of content in some of our collections, it sometimes takes a while for them to all load and I have to refresh a few times. 2. You can't open items in a new tab. If you want to view multiple items at the same time for editing or to compare configurations, you have to use "inspect" to get the URLs to open items in a new tab. 3. There's no export option for items.

Dynamic content in our app, language localization, reducing reliance on engineers for content changes.

Butter CMS allows me to make content pages quickly and easily while being flexible and powerful enough to allow for the needs of my company. On the rare occasion I have an issue, the team at Butter CMS was very quick to help me find a resolution - even going far as to troubleshoot an issue on my end.

A few more options with blog posts in the API would be great the editor for the raw html/text could be a little nicer but these are very minor complaints.

Essentially, ButterCMS allows for our online sales platform to rapidly make pages for all of our products. The well documented API makes it extremely easy to update our content dynamically and customize it to fit our needs.

The detailed documentation that gets any project up and running within no time is the best aspect of butter. Also the content updates in seconds right after you hit publish, so that you don't need to wait for your project to build.

Butter is best for managing content for blogs & static informative website. It will be good to have dynamic data feature which updates in butter itself based on user inputs.

The biggest benefit is that you don't need to spend days setting up a database, spending the rxtra dimes on it as well as spending extra time on content creation. Butter manages all your data and lets you create content on the fly. It adds value to startups & medium sized business as they might not always have enough staff & budget to do all that.

Agile support, able to meet the ongoing requirements of our business.

Seems to be a little underdeveloped as a product, but I'm sure they will improve.

Permissioned access and streamlining efficiency to remove workload off of developers.

Easy to install for the engineers and easy to use for the marketing team. Once the gem was installed, I was able to start transferring old blog posts to this new CMS. The pages looked way better since the css matched the site and page views have increased more than 5 fold.

More friendly UI for typing posts and configuring the page. Commonly used templates would be awesome. While these are nice to haves, the team has been very responsive with requests.

Our old blog was buried on the bottom of our site and linked to Tumblr. Needless to say, we weren't getting the traffic we were looking for and didn't show up in search for key terms around our business. We installed the Butter gem and within a few days saw immediate results as more page views started to roll in. As we continued to add posts, we suggested features to the Butter team and were pleasantly surprised when they responded quickly with product updates integrating our requests. Now that blogging is easier with this gem, we have produced more content, increased page views, and converted more leads to sales.

Easy to navigate and intuitive interface.

No real downsides based on our current needs.

Allows our marketing team to edit content on our website without involving the engineering team.

It's very easy to use and to create customized pages and even incorporate on-page technical SEO into them. It's also very flexible and, so far, has been able to fulfill all of the features I've asked for.

We've been using Butter for about 8 months now and I haven't found anything we haven't been able to do.

Making the marketing team much more self-sufficient, not having to rely on IT for every little (and not-so-little) change we need to make to the website. It saves a lot of time and resources, which result in saving money.

Currently doing sales and marketing and I have to say changing a few contents here and there helped my day today. The option to customize a few areas is key, that key has helped us during the tenure we had with it.

We haven't faced any real issues. The odd bug but nothing like a good ole refresh fixes that. We did have one issue but realized we haven't turned off our computer for almost 4 days. So we just restarted it and everything was fine.

WeIt helped our sales and marketing solve complex content while keeping the content up to date. It helped us keep the retention #s with areas to concentrate growth.

God, I love butter! It was a straightforward enough system to write blog content on: i could integrate other media, carry out basic formatting etc. Wow! it was simple to view all the content I had written too!

Nothing. It was fantastic! Though I haven't use it a lot; I probably need to use it a bit more to find anything that really bugged me. I don't know what I'm doing tbh.

I only use it to write blog content. So it helped me add that to our website. I'm so grateful! There were quite a few issues between butter and our website showing things properly, but that's a fault on our end! How silly!

The simple user interface makes it easy to manage content.

Looking at the preview link if a blog post can sometimes be a hassle.

I don't have any experience as a dev, but I can easily make changes to certain parts of the website.

It's a perfectly fine product that will save you headaches.

There's not a ton about Butter that I dislike.

Landing pages, testimonials, faqs, etc.

Once we got things set up, which is relatively easy, you can publish posts through a GUI directly to your domain without having to make a pull request.

- The UI is relatively simple, but could use polish in places.

- our blog is now in a subdirectory instead of a subdomain - the above can be accomplished while allowing non-technical people to publish content - don't have to mix application/product code updates with content updates. - built in SEO features

Ease of use and ability to localize for other markets

Searching collections is difficult sometimes. Having to manually copy content to other locales one at a time.

I appreciate how closely they work with the dev team to find ways to manage content better.

The documentation is great and it is easy to implement and use. Also, their customer service is quick to respond and gives in-depth answers.

Copying data between locales and environments has been an issue and lead to us creating our own migration tools. It would be great if they had more robust tools to accomplish that. Also working with locales can be messy. When creating a resource for a locale that resource automatically gets created for all locales. This means that if some resources are meant for 1 locale then they get duplicated for all and so you end up paying for unused resources.

For us it solved the problem of translating content for many different locales. Since the UI is easy to use then it has been easy for us to implement new pages and get those pages translated.