The Acquia Digital Experience Platform is an "Open DXP" with its two core pillars being content and data. Built on top of one of the largest open-source content management systems, Drupal, it aims to provide the flexibility and interoperability a modern organization needs. With its customer data platform, it allows organizations to understand who their customers are and deliver personalized experiences. Acquia's DXP offers variety of other tools including digital asset management,…
N/A
GraphCMS
Score 8.0 out of 10
N/A
GraphCMS, from the German company of the same name, is a headless CMS designed to enable developers to build content APIs, while giving content editors the tools they need to manage their content. The hosted content APIs can then be consumed by websites, apps or any other platform or partner. The founders describe their product as content microservice, as it fits in any tool chain dealing with content.
Acquia Cloud is well suited for organizations and teams without the ability to support their own hosting, such as on AWS, Digital Ocean, etc. If a team has the ability (and desire) to manage it themselves, I'm not sure I would recommend it. However, if your team needs reliable, hands-off Drupal hosting, I would definitely recommend Acquia Cloud. Once a deployment pipeline is configured, it's very nearly set-and-forget as far as server configuration is concerned
I would recommend GraphCMS to anyone who is also using Gatsby to build their website. If not, I would recommend them to consider GraphCMS but also consider other options. GraphCMS is a tool in which you are responsible to make the most out of it, but sometimes this requires more time and knowledge than a normal engineer may be able to handle. But with more time and attention, the reward of off-lifting content creation from the developers is a huge time saver in the long run.
the support portal can be hit and miss. sometimes there are very helpful people who get back to you in a timely manner, but more often there's a lot of lag time for the ticket to get picked up and in between responses, which can also be less than helpful.
it seems like the different departments within acquia (support, management, build teams) don't communicate with each other.
because features are so dense and granular, sometimes the workflow or how they are connected can be really complex to access.
GraphCMS is very expensive at the enterprise level.
GraphCMS requires deep knowledge of the system and requires lots of time to be efficient with it (especially around creating specific data patterns/relationships).
Multiple times a day, the system will give us errors when attempting to save something but the errors are unclear as to what went wrong (can be irritating).
We're moving away from Drupal as a platform. Drupal 8 and 9 were simply too overburdened and difficult to maintain compared to other offerings. PHP seems like a dying language so we are currently in the process of migrating all of our Drupal 7 functionality and custom modules to a Python/Django/Wagtail platform. This doesn't mean Acquia isn't a great service, they are professional and top-knotch, but the only way we'd say with them is if I didn't complete the migration.
They are absolutely fabulous and have never dropped the ball in 8 years of us being on the platform. If it wasn't for Drupal 8/9 being unrealistically complicated compared to other offerings like Django/Wagtail we'd be still with Acquia and Drupal.
We use AWS (a variety of services inside AWS) to host our less than mission-critical sites. These are great options for sites that are relatively simple, technically, and/or that can tolerate occasional problems. However, Acquia Digital Experience Platform does provide a level of concierge service that I have appreciated when it comes to running a highly available web application.
We picked GraphCMS since it used Graph API and easily integrated it into our Gatsby website. It was also cheap (free) and easy to test out the product, making it easier to prove to our company we should pay for the product in the long run. Lastly, it seems to have a bunch of support from other developers which makes us confident will be around for a while (and we won't need to replace it anytime soon). Note: I also looked at Directus and DatoCMS but these were not options within TrustRadius
Since the beginning of the website rebuild project, our agency gathered our needs and expectations. We also shared several technical or SEO specifications, and they have been able to fully adapt the software to our needs, in order to create a custom interface that we can easy use on a daily-basis.
It's done a really nice job of allowing us to focus on business-specific needs as opposed to infrastructure/security issues. The platform is rock solid from a support and security standpoint.
The ability to add automation and levels of personalization without having to break the bank has been a big boost to clients.
Unfortunately, our adoption of Site Studio was short-lived due to some inherent restrictions that limited the level of customization we were able to do.
