Butter CMS Reviews & Product Details

It was pretty user friendly and easy to use.

The UI/UX and admin functionality can be a bit smoother.

They are helping us host and support blogs on our website.

In my opinion, one of the best things about Butter CMS is their customer support. They are always super responsive and willing to work through issues with us, whether they are solvable in the moment or whether a new feature request needs to be added to their roadmap. Our account manager is communicating with us regularly on any needs, questions, or concerns, and has been willing to set a meeting whenever we've needed a more thorough discussion. Another great thing about Butter is the user interface and experience. We migrated to Butter from a legacy CMS system, and our users have really enjoyed it. Training is much simpler and easier due to their interface, which has cut down on our onboarding time required to get new users up and running. Last but not least, Butter is continually evolving and improving their product. There have been a lot of features and improvements done over the last 1-2 years while we've been using it, some of which include: speed improvements to their interface, media library feature additions, improvements to schema building and creation, more granular access controls, write API improvements regarding setting reference fields, read API specificy improvements on queries, the list goes on. It is awesome to be using a product that is constantly evolving due to their ability to listen to customers and take action on any feedback.

There haven't been too many downsides using Butter over the last 1-2 years, but here are a few things that could have been better: 1. For a global business model like ours, we saw Page duplication as a bug versus a feature. For example, with a presence in 75 different markets globally, we have a variety of products available in different markets. When a product Page type is created, it is duplicated to every other locale. In some instances, this can be a great feature (pages that apply to every market). However, with products specifically, this caused a lot of unnecessary duplication in the system and has made it difficult to navigate product directories. We have partially solved this with an organizational change in our site structure within Butter, and continue to improve on this solution to this issue. 2. The Blog content type doesn't currently support localization, but we are working with Butter to get this feature on their roadmap. 3. Content migration between sites wasn't available when we first partnered with Butter. We developed our own utility tool to accomplish this for global websites. Since that time, Butter has made large leaps in this area and offers some migration capabilities, and we hope to see more down the road. 4. Granular access control was something we have struggled with, and our situation might be more unique with multiple sites, countries, and locales as a large global business. Butter has been working on this and we are excited for the future in regards to this issue. 5. One of the issues we faced initially was the ability to use the Write API to set reference fields. This made it particularly difficult with some aspects of our business internally as a development team. However, Butter has made improvements on this since then, but that is something that was difficult to manage around initially.

Butter CMS has taken the heavy lifting of managing a CMS system, data, and interface and has done a great job providing this functionality as a service or headless CMS. Previously we built and maintained our own CMS system, and it absorbed a lot of resources and time from our development teams. Also, it was difficult to push out new features and upgrades as often as they were requested. Working with Butter has been fantastic in that they have provided a great product and are continually working to improve it.

There are many great features of butter, but from a developer's perspective; their documentation is very thorough. They have guides for most all tech stacks, and querying the ButterAPI is seamless.

One thing that i disliked, is that you cant reference specific Blog Posts at the collection level. This made it slightly difficult to allow customization for content editors to choose specific blog posts for a section.

ButterCMS is solving the problem of monolithic website builds. This is where the code and content arent decoupled, and as a developer that is a much more confusing environment. By creating an intuitive headless platform, ButterCMS makes developers' lives easier as well as provides better website performance.

Butter CMS has helped speed up our web workflow tremendously! The program allows our marketing team to make quick image and copy edits to keep our site fresh and up-to-date.

One improvement that I think would be helpful for me is if the tool could crop and resize images to the needed specs.

Butter CMS lets our IT team focus on larger web projects that will improve our site as a whole.

The best feature I like is page type (page schema), where you can easily create and manage multiple pages through a single schema.

Only thing I disklike the most is you can upload single image at a time

Butter CMS help us to solve our SEO problem by combining two subdomains (info site and main application)

• ButterCMS is a flexible headless CMS, which allows the front end to be completely decoupled from the backend datastore o Its not WordPress! lol • Content response times are superfast, this should translate into improved scalability (our site is still in the development phase so we have not tested for that yet) • Page types are a nice feature as you are able to model the page content and can be as rigid or as flexible with the content by using predefined fields and components (rigid) and with the use of the component picker, you can introduce some flexibility by allowing the authors to add predefined components to the page • I have used the write API, and this is a very nice feature for importing content. o That said as mentioned before the documentation is a bit lacking and the write API is not integrated into the SDK. I extended some of the SDK classes to make my own write SDK • Chat support is great, Nikki and the others are super helpful and quick to respond • The team is super open to feedback on product suggestions • Overall, it’s a good product, it works, its easy to work with once you wrap your head around the idea of a headless CMS, so far in our implementation of Butter there really hasn’t been anything that I haven’t been able to do

• The inability to move content between environments is probably the biggest limitation. • Building navigation bars using collections is a bit cumbersome if you have a large number of menu options. • Including the write API in the SDK (as mentioned above) would be nice, but I was able to work around it • The interface is very spacious, that said on very long page there is a LOT of scrolling to get to the content section and not every content item is collapsible.

The primary problem being solved is we want a decoupled CMS that can support multiple brand sites under a single parent umbrella therefore: • Improving consistency between brands and Markets (we operate in 60+ countries) • Reduce or eliminate the reliance on the internally developed CMS • Reduce support issues and maintenance cost relating to the internally developed CMS • Consolidate multiple web properties into a single site • Consolidate and replace all instances of WordPresss The project is still in development, so the benefits have not yet been realized.

ButterCMS has a very easy set up and a good documentation.

Would be good to have an ability to POST

Easy access to information from a client's side. Instead of using CMS that require PHP, this one was very convenient for use in React. I wish it had an ability to send information back (POST, PUT etc), but I guess Butter CMS is still growing. Good luck with your service!

Butter CMS is known for its simplicity and ease of use. Ease of Integration Ease of Implementation Intuitive Interface Content Modeling Developer-Friendly Content API Rich Text Editing Scalability Good Customer Support

The system does not facilitate or accommodate incremental changes. The migration of blog content is not supported within the current system. The system does not support JSON file types.

Minimize reliance on developers. Ease of Content Management Reduced Development Time Flexibility in Content Modeling Developer Empowerment

Great user interface. Simple to use. Easy to navigate and create!

Customer Support is not exactly meeting our needs.

A simple API is all that is needed - we love that!

We can create various types of collections and also group it togather and creating pages, by default following seperation of concerns priniple

RIght now as per my understanding, I am unable to create multiple environments

It is able to solve the problem of content management

I like that it makes it easy to create a website and use it to create a blog and online store. Butter CMS is a flexible platform for creating and managing a website. It uses an API-based approach that makes it easy to integrate it with any framework or programming language. This makes it a great tool for creating a blog and online store, as well as managing any type of content.

Butter CMS does not have all the advanced features and is expensive

The advantages are that you do not need any special knowledge to use this program. CMS is a content management system (CMS) designed to be easy to use for people without special technical knowledge. This means that you don't need to be a developer or have great programming experience to use Butter CMS. Some of the other benefits of using Butter CMS are that it can be easy to install, customized to suit your specific needs, and help you organize and manage your site's content more easily.

I love how easy it was to add ButterCMS into my existing Rails application without a hassle. The trial period is perfect for testing the waters. The support is exceptional.

Being such a small non-profit and only using Butter's capabilities for a small subset of our business. I wish there were cheaper options. Even a discounted product adds up. I wish there was an option for snippets rather than full pages.

We have certain pages on our website that will be updated by other-than-IT personnel. Butter makes it easy for them to add content.

I like that my dev team is comfortable working with it and found it relatively easy to implement. As a user it is simple enough to use and did not require much learning curve.

Overall I'm happy with it. One issue that I did find that is inconsisent in content management within Butter, and not sure if it is our execution or an issue with consistency within the platform, is related to the support for HTML elements. In most page types that we have created we can use Distribution List tags (i.e., <dl>, <dd>, and <dt>), however if we use those tags when creating a blog post, those tags get rewritten as divs, and consequently losing their utility. I imagine there the issue is not isolated to Description List elements, but I haven't tested every HTML element yet. Ultimately, I'd just like consistency.

We run a large headless site, and Butter has allowed us to easily manage it. It isn't too prescriptive in how it handles different use cases which has allowed our dev team to create solutions for deployment, etc. that solve our specific use cases.

It was easy to use and provided the flexiblity we needed.

I didn't find anything we didn't like about the solution.

It gave us the ability to update photos and text on our mobile app.

The ease of use and javascript library is great.

None for now. It is a great tool for building nextJs e-commerce websites.

We use it for dynamically updating page title and description without needing to re-deploy the website(mostly SEO)

Very user-friendly platform for non-technical people to add, edit, and manage content with minimal training/experience. This was my first time using a CMS and I found it relatively straightforward.

While this may be just because I was a user of the platform (i.e., not the one who implemented it), there was some confusion about pages vs. posts vs. other content, but that was ultimately sorted out.

As a non-technical person, it allowed us to do things like update our user manuals and other website help-text without having to do a full deployment on our site.

As a developer, I like the most how easy to understand their API documentation is. Also, the fact it can be implemented in several languages makes it even more helpful. Finally, in case you need it, Customer Support will readily be there to help you, and they have different code examples that can walk you through the implementation process.

There is nothing I can think of now. If anything, I have not much experience in the UI for writing blog posts so it might seem foreign to me when trying to figure out how to structure blog posts, for example.

We use ButterCMS as a tool for non-tech people to write blog posts. Before, the dev team would have to be in charge of adding the blog posts made by the marketing site to the project, which takes time. Now they can upload it themselves, thanks to their UI, and it will be fetched automatically.

Flexible CMS with a lot of features, like Text, Images, Collections, Components that can be reused across pages and of course a great support, that answers your questions very fast.

There are still can be more features like repeater of components inside other component.

It allows to reduce implementation time for new pages, allows to chage content quickly. Provides Blog Posts, Pages features, different Environments support.

I've developed in nearly every legacy CMS from Umbraco to Wordpress and drupal to e-comm specific CMS's like Shopify and Magento... but once you go headless, it is so hard to go back. Before Butter I even dipped my toe in the water with Contentful and other legacy CMS that claim to have headless capability (looking at your Drupal) but I eventually settled on Butter. Butter has one of the cleanest and easy-to-use API's on the market and a good balance between price and functionality, without the bloat of the past (headless drupal). Butter also has SDK's available for a whole host of languages making it even quicker to get to market. While Contentful does have more features at the present time, but it has the cost to come with it. While Butter does cater to larger companies, they are also more accessible in terms of price points than several of their competitors (Contentful included). Update and Improvements are also coming on at a good steady pace.

- It would be nice to have some additional "pages" vs price points across all their plans... contentful offers 25k "objects" even on their free tier. - A plug-in or Marketplace of add-ins would be nice to extend the capability of the CMS on the backend. E.g. SEO plugins, writing assistants, DAM's or Dropbox for asset upload etc. - Would be nice to have proxied DNS for CDN locations for images/assets etc, to improve the appearance and make it easier to re-wrap Butter into API's of our product.

- easy separation of concerns between content, code, and design/templates. - marketer and developer-friendly.

The seamless Ruby on Rails integration with code samples.

I wish the lowest plan was maybe a little cheaper...

The backend CMS part of it is super robust like Wordpress, with the ability to completely customize your front-end.