Adobe CQ content author and jr developer
July 24, 2014

Adobe CQ content author and jr developer

Anonymous | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User

Software Version


Overall Satisfaction with Adobe CQ

We used Adobe CQ for a client who wanted to migrate away from their old CMS. It was a global site with more than 15 countries and 20 different languages. Adobe CQ allowed us to roll out different regions and languages of the site very quick and easy saving time and money which all business love.
  • Very easy to use and understand. Adobe CQ already has many components and a developer can build off these components or develop new ones.
  • Authoring content is a breeze. After a developer has completed a component all an author has to do is click and drag the component onto the page and start putting their content in.
  • Publishing content so the customers can see the content be done with a click of the button.
  • CRXDE is not a very good platform
  • If CQ had better out of the box multilingual support
  • The out of the box components are not customizable enough so we ended up having to override them
  • Environment kept crashing because it is such a memory hog
  • Increased employee efficiency - Once the components were created the content authors could knock out a ton of pages in one day.
  • Customer changes were easier to fix.
After using Hybris I would love to go back to Adobe CQ. Although we didn't use CQ for an e-commerce it is a lot easier to use and understand compared to Hybris. Adobe CQ has better documentation to figure out how to use it than Hybris does and CQ also has a better UI.
Adobe CQ has training classes that you can be in or watch to get a better understanding. They have some of the best customer support so if you run into any problems you can just contact them put a ticket in and they will fix it or work with you to fix the problem or issue you are running into.
Adobe CQ is a CMS for a large site. I would not recommend this for smaller sites since there is so much Adobe CQ can do that the small site will never use. Key questions can include: How big is the site you are building for the customer? Is this a global site? How comfortable are you with Java since CQ is Java based.