A team of three or four developers is needed for the solution's deployment and maintenance. Users must set up a team with all the professionals they need to use the product and create their website. Overall, I rate Adobe Experience Manager an eight out of ten.
I use the solution’s online version licenses. Adobe Experience Manager is deployed on-cloud in our organization. People could use Adobe Experience Manager if pricing is not a challenge for them. Before using Adobe Experience Manager, people can start with free tools like Inkscape, Pencil, or Sketch. Overall, I rate Adobe Experience Manager an eight out of ten.
Because of the improvement needed with the client-side framework and because page loading takes time, I rate Adobe Experience Manager at seven out of ten.
Adobe Experience Manager requires maintenance, but the client side takes care of it. Even during the deployment, the client joined the call, and any needed improvements will be made from the client side, for example, migrating from one server to another. Hence, the maintenance of Adobe Experience Manager is the client's responsibility. My company has one project on Adobe Experience Manager, with a team of forty people working on different parts. My advice to anyone planning to implement Adobe Experience Manager is that it has a broad scope in terms of usage, so I recommend that you learn about the solution before implementing it, especially if you have a lot of clients for it. My company has a partnership with Adobe. I'd rate Adobe Experience Manager as ten out of ten.
Chief Technology Architect at a tech services company with 1,001-5,000 employees
Real User
2020-08-04T07:26:12Z
Aug 4, 2020
Adobe is a more expensive solution than, say, Liferay. But we don't like the portal approach in Liferay, it's quite old. We've worked on our portal CMS since 2010, so it's been over 10 years. In Liferay, the core is still based on portal frameworks which is a disadvantage because we know that to develop something with that model is quite expensive. In general, our employees are more familiar with Adobe and have more confidence using that solution. I would rate this solution an eight out of 10.
Adobe Communique 5 (Adobe CQ5), currently manifested as Adobe Experience Manager (AEM), is a web-based content management system which is developed to help businesses in offering high-end digital experience to their customers.
A team of three or four developers is needed for the solution's deployment and maintenance. Users must set up a team with all the professionals they need to use the product and create their website. Overall, I rate Adobe Experience Manager an eight out of ten.
I use the solution’s online version licenses. Adobe Experience Manager is deployed on-cloud in our organization. People could use Adobe Experience Manager if pricing is not a challenge for them. Before using Adobe Experience Manager, people can start with free tools like Inkscape, Pencil, or Sketch. Overall, I rate Adobe Experience Manager an eight out of ten.
Because of the improvement needed with the client-side framework and because page loading takes time, I rate Adobe Experience Manager at seven out of ten.
Adobe Experience Manager requires maintenance, but the client side takes care of it. Even during the deployment, the client joined the call, and any needed improvements will be made from the client side, for example, migrating from one server to another. Hence, the maintenance of Adobe Experience Manager is the client's responsibility. My company has one project on Adobe Experience Manager, with a team of forty people working on different parts. My advice to anyone planning to implement Adobe Experience Manager is that it has a broad scope in terms of usage, so I recommend that you learn about the solution before implementing it, especially if you have a lot of clients for it. My company has a partnership with Adobe. I'd rate Adobe Experience Manager as ten out of ten.
Adobe is a more expensive solution than, say, Liferay. But we don't like the portal approach in Liferay, it's quite old. We've worked on our portal CMS since 2010, so it's been over 10 years. In Liferay, the core is still based on portal frameworks which is a disadvantage because we know that to develop something with that model is quite expensive. In general, our employees are more familiar with Adobe and have more confidence using that solution. I would rate this solution an eight out of 10.