Butter CMS Reviews & Product Details - Page 7

It was pretty user friendly and easy to use. Review collected by and hosted on G2.com.

The UI/UX and admin functionality can be a bit smoother. Review collected by and hosted on G2.com.

ButterCMS's ability to allow us to design our own content type structures with ease, and conveniently adjust them as the project progressed was perfect for our project. That allowed us to easily follow an "agile-like" process with the different stake holders on the project by getting an idea prototyped, iterate on it, and then lock it in for production - without the tediousness of needing super-detailed specifications for each content widget or page. The available APIs were so easy to setup and use, which easily dropped into our development process and tooling. Review collected by and hosted on G2.com.

We really liked that ButterCMS doesn't attempt to get in the way with how we do the front-end/presentation layer, and intentionally stays in its lane by instead providing only a great API to build the UI with. It would be nice if they'd provide a simple way to inject some of our own custom CSS into the WYSIWYG editor within their admin console though, so that our content creators/writers/editors could get a more correct understanding of what the content will look like directly as they're editing it in the CMS. Review collected by and hosted on G2.com.

It was easy to use and provided the flexiblity we needed. Review collected by and hosted on G2.com.

I didn't find anything we didn't like about the solution. Review collected by and hosted on G2.com.

We found the pages and collections approach to be great once we got the hang of how to arrange pages for our needs. There are many options on structuring different page elements including repeating or flexible numbers of content items. Review collected by and hosted on G2.com.

The media library could have used more hierarchy and structure options. Browsing through dozens of images became cumbersome. Having a good naming scheme is critical to make use of searching and filtering features to access media items. Review collected by and hosted on G2.com.

Great user interface. Simple to use. Easy to navigate and create! Review collected by and hosted on G2.com.

Customer Support is not exactly meeting our needs. Review collected by and hosted on G2.com.

Component, Collection, Pages, Blogs.

In pages, the repeater field is very useful Review collected by and hosted on G2.com.

In Blogs, there is a feature to make use of nested blog post Review collected by and hosted on G2.com.

Great tool for creating and managing content for the company's website. We can build new pages and update the old ones in several clicks. The process reminds playing with blocks :) Review collected by and hosted on G2.com.

We want more tracking on our existing components' usage and on which pages they are already placed. However, this issue was addressed to the Butter team, who are trying to find a solution. Review collected by and hosted on G2.com.

Butter CMS is very easy to use the built-in API client make calling the API a breeze. As an architect, butter cms gives me more flexibility to use the cms as in ways that can not be used in a traditional CMS like WordPress. A good example is hybrid apps, we let parts of the website to be updated by butter (ie. button names, heading, wording for a page) this allows our business to do a change without any downtime to our clients. Also, Butter CMS allows us to build very reusable view components that can be added to the website without coding, just some very simple configuration on our end. Review collected by and hosted on G2.com.

*Not dislike or deal-breakers but my wish-list that I believe would take ButterCMS to the next level*

The write API if very lacking and not part of ButterCMS API Client, and documentation is not there yet(if you understand API shouldn't be a trouble for you). We were able to get things to work, but it was a lot of frustration at times.

Repeater needs to be able to have repeaters a list of lists of lists of objects.

If you think of Components as objects and Repeaters as List then you will understand why a user would want of list of objects or a list of lists.

These two above make it hard to create things like dynamic tables, or questionnaires. The references tool is too much clicking, especially for non-technical people.

a good example.

I want a repeater that has a component in it <- this is powerful, that can be used to make a table, or layouts, because now you have a List<T>, ICollection<T>. This is very important to a dev to make very dynamic content.

-Below are nice to have-

Needs a built-in Site Map component.

Needs a built-in Navigation component.

Needs SEO for pages, just like how the Blog works (it's very useful).

Write API for the ButterCMS Client.

Still Good Work. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

We can create various types of collections and also group it togather and creating pages, by default following seperation of concerns priniple Review collected by and hosted on G2.com.

RIght now as per my understanding, I am unable to create multiple environments Review collected by and hosted on G2.com.