Avis sur Butter CMS et détails du produit

ButterCMS helps to save the time and effort of developers by removing the requirements of making deployments and allowing our marketing teams to make updates to our site quickly. The system has been well developed, making it seamless for developers to create components that non-technical staff can understand and translate into details for our site. The support team has quickly dealt with any issues that have arisen.

Signup was confusing when I accidentally signed up with my account instead of waiting for my company to invite me. The superb support team quickly rectified this!

It removes the requirement of developers to make changes to the site and therefore saving time and effort for developers. Allows marketing teams to make immediate changes to the site and rearrange it as they see fit.

Very responsive customer service. Butter CMS has made me feel like they value feedback and really want to help me succeed with their product. I asked a question, and they responded quickly, made some suggestions, and even arranged a Zoom meeting to discuss my needs in detail. They even decided to implement a feature that I requested, and kept communicating with me through the process. I've never experienced that from a company before. That service builds loyalty, because even if there's a bug or feature that doesn't exist, I have confidence that they will listen to me and try to help me find a solution.

The api is less complete than I was hoping for. (But that's getting better!)

I'm using it to store dynamic content for our app, so we can change lots of things w/o needing to do an app update. The UI is very simple and easy to coordinate with team members

Easy to use content management for blogging.

Photo placement feature. It's a little difficult to see how your photo fits into the posts.

Content management for storytelling and blogging for clients.

It was easy to use and understand, quick. I was thrilled with the website.

I had no issues using this website. Everything was ok.

I used it to do product review surveys for clients

Not provided

Not provided

Not provided

The best thing about Butter is that it's so easy to use. The layout is very simple and easy to navigate. If any problems come up, their team has incredibly fast response times. Nikki was super helpful and friendly.

I have yet to come across a downside with the platform. Any questions I've had were immediately answered on the chat.

Butter allows the company I work for to post blogs on our website. Our company blog is the driving force behind our marketing team. It's great that Butter allows our entire team to be on the same page as far as what is published and what is scheduled.

ButterCMS is easy to use for everything. We built our site on Jekyll, and then we use Butter to interface the editing for every single page. Regardless of the type of page, we can use Butter to interface with it, so our marketers can change the text. Home pages/blog pages/etc. anything. We can easily use the source code feature to write in add-ons such as calendly, or signup forms, so we can even build those kinds of pages easily.

Page limits! We hit the page limit a few times, and had to upgrade. Our strategies are really ambitious though - we're talking 10,000 pages or so. However, in butter's defense, they reached out to give us a special deal on mass-produced pages, and they reached out to offer that without us even asking. So good job guys!

The problem butter solves is it gives marketers the ability to edit webpages made of any design. So it's not only blog pages, but all pages. It also is a great blog editor.

Before ButterCMS we were using Wordpress with the ACF plugin to store data for our marketing website. And our dev team needed to spend a lot of time in WP to create pages, adjust fields and then pull the data through the APIs. What I really like about ButterCMS is that our marketing team managed to really quickly understand and learn ButterCMS and after first setup from the dev team, now they are able to create their own pages and collections without devs involved. Which really saves a lot of time for developer where they can focus on actual development and not content creation. The second part is their APIs which are really easy to understand and use. We were able to pull the data in a couple of minutes without any strange or unexpected results. Would really recommend this CMS to any team who want to quickly and efficiently develop their marketing websites. And their support is top notch!

These are not dislikes but more like "would be nice to have feature" (or wishlist for future development): - can't move content between environments - can't add an existing page to the page type - although you can have multiple workspaces, what I'm missing is pagination on the workspace (some workspace can have a lot of collections) - more content filtering options on the API calls - when updating component in the library, all page which is using that component should be updated (not just pages with the same type) - missing custom fields on the blog posts

We've migrated our marketing website from the Wordpress to ButterCMS as we've realised that by migrating we'll be resolving couple of things: - marketing team will be finally able to create content on their own - we won't need to run separate server to host our files (images, documents, videos) - we won't need to run separate CDN - all data will be in one place (previously some data was in Wordpress while other data was in our CRM)

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.

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.

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 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

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.

ButterCMS gives the flexibility to decouple from the traditional cms workflow. For me, this provides the ability for a more rapid development cycle and the ability to present multiple front-end designs using the same page data. Also, having the ability to integrate with any additional software is a breeze when using ButterCMS. You are no longer locked into a specific set of plugins/technologies or integrations that a more traditional CMS would provide. A very "Buttery" user experience that I look forward to using every time.

The ability to create reusable components within the ButterCMS GUI is great, but the ui/workflow for the process is a bit lackluster. There should be a menu item for a component builder. Each component could act as a master component. When a "master" component is updated, the user could be prompted to inflict the change on all implementations of the component or selectively change the implementations of them as needed.

Butter is allowing my company to decouple from the traditional cms workflow. This is allowing for unlimited integration possibilities without being dependant on the integrations allowed by other non-headless CMS options on the market. This is a powerful benefit because we now control what software we can integrate with.

It was so easy to start using and publishing blog posts. Took less than an hour!

The standard design isn't great, but they've got a robust github with css files for customization.

Wanted a blog on our website to drive engagement and inbound. They helped do that easily.

The intuitive WYSIWYG interface makes it easy for users to create and update the blogs whenever they need to.

Image management was a little tedious. We store some of our images on S3 buckets and when trying to upload an image from a link, it would save the image as an audio file instead of as an image. Also you are only allowed one feature image. Would be nice to have an option for something like a banner image as well as a hero image.

We used to have our own internally managed blog, which was nice, but it meant that we had to consistently manage and update all the codebase. This draws on developer resources that weren't always available and eventually the code became more brittle and harder to maintain. ButterCMS has allowed our marketing team to do their work without feeling frustrated trying to build content. This means they utilize their time better and developers aren't spending all their time maintaining the codebase.

The ease of use of the API in my blog has been seamless. The interface stays consistent so any between upgrades, and it's all restful. The CMS solution makes it very easy to live in the JAMstack world and manage my content from one place. For an example use case: if I wanted to setup content that defined how navigation looked, I just have to have the housing and design setup on the front-end and inject that data from their API. Simple! If I had to modify the content in any way, I can progressively enhance my content with ease pushing simply updates without much heavy lifting. Other benefits along the first example include the flexibility to define your content and collections freely for your needs. Lastly, the customer support is very responsive with quick resolution.

I like everything about Butter CMS so far. There was a hangup I had near the beginning of using the admin panel for creating collections and viewing the full list. I gave them a suggestion a while back on how to make this make more sense, and I see that they've improved on it so they do listen to the voice of the customer. The other thing I'd like to see better implemented is the response interface and accessing the inner content apart from the meta data.

The JAMstack is a growing entity, and this tool helps increase my development time by lifting logic I'd create in the front-end to the CMS.