Butter CMS Reviews & Product Details

I like the interface. It's very clear and intuitive. Everything is described in the documentation. Also the API is very simple to use. Using Butter as a CMS we were able to create rich blog (with categories, tags, multi-language), but also we built a documentation for our application with menu, which is generated directly from the CMS. Using this app you have great opportunities to built something awesome! And they have integration with a Filestack. It means that you can optimize your images very easily! Also ButterCMS has a great support team. They are always willing to help. I really appreciate it. And they react very quickly when there is some issue on their side (very rarely).

ButterCMS have great search engine, but it works only for blog posts. It would be good to have this rich search functionality also for pages.

We created a multi-language blog, documentation and other dynamic pages, which can be modified in the butterCMS without developers help. It's great solution when you want to update your data on the website and you are not a software engineer.

I like the easy to use page design functionality. It is super intuitive and works great. Additionally, when a certain aspect of the preview functionality wasn't working correctly with out setup (and this had to do with an issue that was specific to our existing website), Butter CMS Made a code change to fix our problem in UNDER 3 DAYS. This just shows their incredible customer service and willingness to do whatever it takes to meet your needs.

The only qualm I have about this software is the inability to push content from stage->production. Although, this can be overcome by simply creating a draft of your page on production, and waiting to publish it, it would be ideal to be able to work on stage, then push any content to prod. (You can push schema from stage to prod, but not page content)

We're solving the problems we were facing by using an outdated inefficient CMS, we have realized improved user experience from our customers, as well as an easier to manage CMS.

ButterCMS design is straight forward, easy to implement with fast API calls. Our admin people picked it almost immediately for day-to-day content changes via the online UI. They love see results immediately without IT support. The ButterCMS support team is excellent, fast and responsive.

The online UI could use some polishing including an option of a more detailed view of the various components such as a collection lists.

Off-loading content maintenance to our users is a real time saver for the developers.

- Easy to manage - Customer service was really helpful

- Nothing, I wouldn't say that there was something wrong along the way

- Content is easy to add and manage, useful tag management - I had a problem wit tags but it was solved quickly

The platform is very easy to use. We built our entire SaaS off of there API. In the few times I wasn’t able to figure something out, there support guided me through the entire process.

Not much to be said here. I wish they had some stronger filters on their API. I hope these are coming soon.

I wanted to create a SaaS with no backend. Using their CMS API I was able to create an entire SaaS with not a single line of backend code or infrastructure.

Easy to set up and use in development that after integrating it to our app, the marketing can handle content management even without the help of devs which helps improve efficiency in our workflows.

API documentation can be improved. It shouldn't be a problem if you know what you are doing but it can be frustrating at times, especially for less-experienced devs.

The marketing team can now add or update dynamic content without the help of devs which used to take away development resources.

Before Butter, we were locked into a self-hosted solution that commanded regular updates, plugin management, and a learning curve for any new joiners within our team reading documentation to get up to speed. We have just completed a website redesign project with ButterCMS as its backbone, one major plus we noticed from the get-go is the fact collections make it really easy to share data across the content platform. Our website is based on a component architecture and that was easily replicated in Butter using the component library, this was further advanced by re-using collections and for us, this has meant colors, image sizes, and other re-usable elements can be shared so our content editors can create pages quickly. From a technical point of view, we were able to get up and running in a matter of minutes using the API documentation and the ButterClient, after finding our feet using collections we were able to build a scalable architecture based on a React app. Since our website is built around component design, we now have a bunch of styled-components that allow any new pages to be quickly built up and deployed in minutes. This is mirrored in ButterCMS and therefore allows our content editors to build pages, send us the link and within minutes the page is created and live.

One of the biggest issues we're facing right now is the speed of the backend dashboard, this may be due to the number of collections we're running in order to create re-use of content across the platform. With that said the time-savings we get from architecting our content in this way far outway the degradation in the admin. It would be nice to see an easier way to manage collections to help page load times increase when managing content on the platform. Our second biggest gripe could be again down to how we've architected our solution, but since our components are mirrored both in code and the Butter component library it has meant when content editors build pages they are utilizing the drag and drop interface for the type builder. This process has two issues: - The first being that once a component is created, it cannot be updated, you are required to first add the component to a new/existing page, remove it from the component library, add your new field and then save it as a new component. It would be great if components could be edited which leads to our next issue (which is also true of page type configurations as well). - Secondly, if you edit a component that has been used on a page to add/remove a field this is then not reflected across all components where this instance is used. It would be great if the component schema could be shared across the board and those instances were used listed on the update to confirm where the changes will take effect.

The main issues we solved using butter was to migrate away from the old age problem or developing our own in-house CMS or absorbing the cost of licensing, running, and training our team on a platform that changed regularly. With Butter we're able to use our own architecture, coding standards and share content across multiple platforms from a single source.

I don't know where to start... I like it all! If I have to choose, I like the components in the Pages the most. I like how I can re-use page components. Second, I like how versatile the Collections are.

I may want to see more columns on my Collections view.

So many problems. We have quite a big Frontend system with upto 5 platforms running on the same API. ButterCMS helps us to minimize our platforms from 5 to 3. We want to have fewer platforms to manage all our content, and ButterCMS fulfils that need.

While I did not create the layout, I liked the ease of customization and data entry.

We ran into a few bugs throughout the process that delayed development.

We used Butter CMS to input content for our app build.

Butter CMS was extremely easy to integrate into our Node.js application and the docs made everything clear. The interface/UI was easy to use and packed with enough features to act as an excellent blogging platform. Post/Page data was always lightning fast to load. The support was always friendly and helpful.

The pricing tiers may not match all use cases.

Setting up a CMS was too much overhead for our lightweight application. Butter CMS made adding an SEO optimized block to your site extremely easy.