CrafterCMS Recensies & Productdetails

CrafterCMS is exceptionally versatile. It enables us to serve any content to any type of digital experience and integrate with any external system we need to.

We have not encountered any negatives or things that don't work well for us.

We're using CrafterCMS as a content and integration hub for our digital experiences. CrafterCMS makes integrating our timing, scoring and media with our web, mobile apps and digital signage simple and easy.

- Git Based platform <3 - Very friendly and active service support, development, and growing community - The platform is based on modern and reliable technologies

- Lack of deep testing in the development branch (from one version to another, some pieces might be missing in the development branch) - Documentation could be better, but they are doing a great job improving this point and providing CrafterCMS Courses through Crafter Academy

- We were able to successfully create and integrate into CrafterCMS our own React-based plugin using CrafterCMS APIs and a modern stack (using 4.0 dev branch) to leverage Git based file management - We were able to start a migration from NAS-based file management to a whole git-based file management flow in an easy way for stakeholders, thanks to CrafterCMS - We were able to adapt CrafterCMS backend and frontend to our needs very quickly, thanks to the documentation, support, and readability of the code

Crafter CMS offers several unique advantages for our company. For example, - Content Management, Crafter CMS offers easy-to-use WYSIWYG features that allow the content author to preview desktop and mobile content before publishing. - Content Distribution, Crafter CMS supports modern headless-cms capability, which allows the developer to build API(s) to distribute content through multi-tenant architecture. - Content Discovery, Crafter CMS provides GraphQL out of the box, which allows the developer to build advanced queries on top of a massive pool of content. - Content Version Control, we have complex needs to support CI/CD (Continue Integration and Deployment) for our multi-tier architecture between Content Authors and Developers. Crafter CMS offers version control, which allowed us to build automation and improves the overall code quality and time-to-market on content publishing. - Crafter Customer Support, Good software cannot be GREAT without superb customer support. The Crafter product team went beyond our needs as a software vendor. The core team members in Crafter software company had a long innovation history in the CMS industry. They experienced different paradigm shifts and created CMS solutions for different industries. They are passionate about CMS technologies and open to working with their customer to resolve challenges.

Crafter offers several advanced features with limited documentation support. It would be great to see an archive of how-to videos and examples so the Crafter community can take advantage of all the Crafter offerings.

We manage a global brand across 25 locales with 50 Million unique visitors (YTD 2020). The CMS system we used to manage and publish content cannot scale with the business grows. We need a modern CMS that provides security, scalability, and easy-to-use features so we can manage and distribute content across multiple web properties. Crafter CMS offers several benefits from a software development perspective. Crafter CMS has built-in API support that allows the developer to integrate internally sourced content onto Crafter in an automated fashion. Crafter CMS is AWS friendly and is extremely flexible to monitor, Lamdba functions, and integrations with other AWS features. Crafter CMS supports version control. We have complex needs to support CI/CD (Continue Integration and Deployment) for our multi-tier architecture between Content Authors and Developers. Crafter CMS offers version control, which allowed us to build automation and improves the overall code quality and time-to-market on content publishing. <We are in the process of CMS migration and more to come>

The ease of use and ability to tailor the platform to suit our needs. We are just at the beginning and our customers are delighted with what we've built. I can't wait to unlock the potential!

It does run a little slow over here in Australia. It was also disappointing there was no automated way to upload our content.

We have very complex needs to present a large volume of education and technical materials to our market. Crafter has made the usability so easy that each department in the business can own their own content, without having marketing or IT have to upload or manage everything.

We love the idea of the Git-based repository. The fact that code, content and configuration is in one place makes it very easy to synchronise dev, authoring and production systems. We can push our features forward from dev to production and pull production content back to work with real data on the development system. Testing features couldn’t be any easier than just switching branches. And while we deploy new features to production authors can work without interruption.

The market penetration of CrafterCMS isn't on the level it has to be.

It’s great to be able to use APIs for everything. We can in fact render markup, serve content and even use APIs for DevOps automation and processes. It makes Crafter highly flexible and gives us the possibility to manage, integrate and deliver content anywhere at any time. Furthermore, it gives us the freedom to work with any front end framework on top of Crafter’s headless content server. And finally we are pretty overwhelmed by Crafters responsive support. We use Slack to get in touch with them but there is a growing community in Google Groups and Stack Overflow as well.

Open Source. DevOps Friendly. Easy for authors. Create sites in a matter of minutes.

Since it's growing CMS framework it need sometimes to mature it's documentation.

Personalized Department Sites. Personal sites. Easy to integrate with any other platform since it has an amazing API's (mobile apps).

For many global footprint solutions I used the Crafter solution to power Marriott digital experiences. We found the software to be flexible enough to meet all of our customer touch points (mobile, desktop, kiosk, email, web, video) and the leadership team willing to jump in and develop solutions in partnership with us.

They are a small company that delivers on big solutions. At times it was hard to get leadership on board to use a smaller company even through they demonstrated (repeatedly) their solution and people were up for it.

I used the solution in many ways and to solve many problems. Probably the biggest benefit to me was the ease of which we could create digital experiences that were integrated with existing platforms (e.g. measurement, email, IAM). Speed to market was another huge benefit for us. We used a combination of SaaS and fully managed solutions with Crafter. Products we built were for users in the hundreds of thousands.

Easy to create templates, add/manage content and retrieve data as json/xml using rest calls.

bit difficult to modify the core package if incase we need to write custom methods to the core package.

We have automated the site content to get data from Crafter. Thus saving us time from Production move.

Crafter CMS has well architected modular design, which gives us great flexibility during our adoption. We chose headless approach to use contents as service. The flexible architecture make the integration with Crafter CMS easy to do. The preview feature give content authors the ability to view contents as how they will render in the final web site no matter what type of rendering engine you choose. Good product is only half of the story. We are particularly impressed by the superb support we get. You truly feel you can count on them as your partner. They listen to your need and work with you every step on the way to find the optimal solution.

not easy to integrate 3rd party UI controlls in the authoring tool.

Web Content Management so that web site can be updated without release.

Mainly it's architecture, developer friendliness and tech stack.

So resource intensity if you have a basic setup and a common use case was not provided out of the box but this was easily worked around.

We needed a multi-purpose CMS for blogs, content sections, content fragments, augmenting products with headless delivery.