Contentful is a cloud based CMS solution that provides the ability to manage content across multiple platforms.The editing interface allows for managing content interactively and provides developers the ability to deliver the content with the programming language and template framework of their choice.
$489
Progress Sitefinity
Score 7.6 out of 10
N/A
Progress Sitefinity is a content management and customer analytics platform. It supports content management, tailored marketing, multi-channel management, and ecommerce sites.
Well suited for our needs of multiple images for auto auctions from a variety of sellers. Pointing them to one platform is easier than attempting to use a variety of platforms as we were doing before (email, slack, Dropbox and Google Drive would randomly be used by a variety of employees )
Progress Sitefinity remains a little heavyweight for sites that require basic text content, or a limited number of pages. However, its flexibility (including the range of different content types if supports) make it a good choice for any organization requiring advanced content management capabilities at an affordable price.
'Low-code structured content' (dynamic content types) is one of Sitefinity's most powerful features that allows you to structure content according to business needs, while at the same time dampening editorial freedom to ensure accessibility, meta enhancement, SEO and API consumption can be achieved.
Sitefinity's content provider model allows us to flexibly (by means of admin interface) easily aggregate or separate content sharing within a multi-site instance.
This proofs particularly powerful in emerging situations where there suddenly is a demand for content sharing across countries or regions.
Adaptability at its core.
While there's never a perfect fit for everything, it allows for easy code customization and extension being a .NET application at heart. Giving it a corporate edge over other custom solutions, whether it is on the development side or deployment side (on premise, IaaS or Azure DevOps Paas). And it has enabled us to put the system to use in its core feature - which is to manage content, where on other occasions we were able to take full advantage of its features such as A/B testing and personalization.
Contentful uses "references" to allow you to build very modular content. If I have a "slider" content type, I can create a "slide" content type which references a "button" content type, and so forth. This works well, but I occasionally wish there was a better solution for one-off content, like a settings page. Currently, this is done for creating an entire content type called "settings" with a single entry. Not a big deal, but not ideal, either.
There are a few quirks with GatsbyJS integration, etc, but these issues are being fixed and improved upon very quickly.
A minor gripe, but Contentful does not have a way to organize fields within an entry. Entries with many fields are somewhat tiresome to scroll through.
Diagram or illustrate more use cases for server setups, and managing of upgrades.
I'd like to see the ability to synchronize from one server to multiple others at once.
Implementation assistance as part of the purchase rather than farming out to 3rd party, although they did answer every question we asked in order to determine our best architecture setup.
Very big fan of this CMS, as it allows scalability, performance, and everything else. The support is great whenever we need it. As a marketer, the digital/marketing side of things is very easy to use and we've seen strong results from an SEO and marketing perspective. I can't speak to the developer/creative side too much, but in talking with these teams, they do recommend the tool as well.
Support can be pretty good, even though, depending on the level of licensing, it can take longer to hear back from their team. They do have a phone option, which works well. Overall, they are knowledgeable, and helpful when needed. At times, support is able to access the system directly and troubleshoot critical items when needed.
N/A - I was not part of the implementation team. We have had this internally for over 5 years. Based on my experience, ensure that you have documentation on the initial implementation and subsequent upgrades. I would also recommend to have all the documentation on how and why the system was implemented the way it was
In the past we've used WordPress to manage documentation content. WordPress was more flexible than Contentful but also prone to inconsistencies and we ended having a lot of hacks to accomplish various WordPress tricks. With Contentful there's less ambiguity so content producers are less likely to go astray. We also have our own in-house programmatic template solution for managing content, but this was a previous pain point when we needed to get the dev team to do a deploy for every content change.
It is hands down just easier for our customers to use. The interface and the page builder experience is much better than what we have used in the past and has many enterprise features even in the lower price-point
