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.

View full review »

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.

View full review »

I enjoy using Adobe Experience Manager and recommend it to large and enterprise level organizations.

Overall, I would rate it at eight out of ten.

View full review »

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.

View full review »

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.

View full review »

Before using it, you should have some hands-on experience. Someone should show you a two-day demo of what a developer actually does, how exactly do we use it? 

If you understand how to use it, then it can be beneficial for development as well. Understanding how to use it allows to explain to clients the use cases where Experience Manager is effective.

It is easy to learn. You don't need to be an advanced Java developer. With basic Java knowledge and about 15 days to a month of AEM training, including a week or two of hands-on experience, you should be good to go.

Overall, I would rate the solution an eight out of ten, especially considering AEM as a Cloud Service. The best part is the seamless integration with other products. Everything is connected.  

In my current company, we just started using Adobe Target, and the integration with Experience Manager is very smooth. This, combined with how easy it is to manage digital marketing and publish content, is why I give it that rating. Development happens once, but maintenance is ongoing, and AEM makes maintenance simple.

View full review »

Have a good relationship with budgeting and your various in-house IT divisions; have them understand the needs of digital marketing.

View full review »

Full knowledge with its technical stack.

View full review »

CQ is expensive but the worth money. If you are looking for a free or cheap equivalent use Magnolia CMS. Very similar in the general design idea.

View full review »

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. 

View full review »

Start small and plan your first set of objectives clearly, leaving all the “nice-to- haves” for a later phase.

Starting this way will help companies get a sample of the benefits, and get familiar with the tool in general.

After the first phase, they may find things that they thought they wanted are not really required or can be achieved in a better, more efficient way in the AEM world.

Another useful piece of advice is to avoid trying to re-create your current solution using AEM, and rather, try to look for new and different ways to achieve the same results that take advantage of AEM’s features.

View full review »

The product was originally developed by a company called Day Software that was taken over, and then further developed by Adobe, changing its name from CQ5 to Adobe Experience Manager (AEM). Currently, the latest version is AEM 6.3.

When using other Adobe Marketing Cloud products with AEM, I would advise keeping short-term goals instead of going straight ahead to build something massive/complex. Furthermore, selecting an experienced and competitive consulting partner for the development goes a long way.

View full review »

The way it's stored is different from the legacy system, where we used an RDBMS-based solution.

Here, we have a file-based system and all information is saved on nodes. Also, keep in mind David's principle.

View full review »

If you're looking for a .NET based CMS, do yourself a favor and go with an open source CMS. If your company is afraid of open source products, there are much better, less expensive proprietary .NET content management systems out there. View full review »