Recensioni e dettagli del prodotto su Adobe Experience Manager

Scalability. It is pretty easy to add components and configure as needed. The HTML code editor makes it easy to import existing content your teams have already designed. Widgets are useful. Tree structure helps maintain several instances.

Tree structure lacks organization. Navigation takes longer than it should across interfaces. Online editor does not automatically synchronize with your IDE, so a lot of manual work to keep things sync'd.

Client WebSphere site migration to content management hub. Very straightforward in customization.

Very plug and play; easy to use once configured

Implementation has been difficult and costly.

Ability to put publishing in hands of content producers is very helpful. Removes need for large front-end dev team.

It was very organized and allowed for detailed tracking

Very time consuming to understand and get trained

Email A/B testing and tracking. Depending on audience subject line matters

I like the idea of content structure in the AEM, like inline editing and template features. I like the Idea of visual content management when users can add or remove some components.

It is cumbersome and has poor development documentation and support. The AEM uses a lot of obsolete and slow technologies like JCR, Sling. Also, I should mention that it is not Open Source.

The main problem that AEM solves is content management, and in my humble opinion, it is doing not so well in this task. But if you invest a decent amount of effort you will able to reach your goals

Provides a way to manage an online collection of PDF files that is visible to clients

The platform lacks intuitive organization, consistency and no alpha order of your documents

We are able to provide and manage a collection of PDF documents online

I like how easy it is to create collections in folders that are visually appealing. It is also very simple to upload assets.

I don't like how there is not a "back" button. If you enter search terms, click on an asset to get a closer look, and then go back, you will lose your search terms and results. I also do not how it does not display the number of results in a search.

We have temporarily solved the problem of where to put things.

I don't like anything about this, it's a frankenstein mix of acquired assets trying to be an enterprise product.

It's confusing and difficult to use, it feels dated by at least a decade if not more. Nearly any CMS will perform better than this.

It's being implemented as a replacement of another enterprise content management system. So far not benefitting at all from the installation.

AEM has a lot of flexibility and I guess the user facing side is ok.

On Premise AEM/CRXE Lite is ridiculously rigid and over engineered. If you make one change to a workflow, inevitably, three others break. No offense to programmers, but it's obvious progammers designed it. In no way intuitive. Stupid nested data structure. Adobe wants you to use their OOTB functionality and retrofit your needs to it. When they snub your enhancement requests, you have no choice but to do custom code. They like to randomly take away useful features, like Search & Promote, leaving you out in the cold and scrambling to find a solution on your own. Does not play nice with non-Adobe software. God forbid you try to integrate with Salesforce. Double whammy. Adobe's documentation is rarely helpful. Lots of 404 pages on Adobe Experience League. It's poorly organized and either gives you not enough information or too much uber technical Adobe jargon that means nothing. Much like Apple, Adobe wants total indoctrination from its clients. Thousands of paid consulting hours evaporate in a few weeks, and usually the results are "upgrade to (significantly more expensive) AEM CaaS, buy this add-on, buy this other add-on... If it sounds like I have an axe to grind, it's because I do.

It was well in place when I started at my company. I would dump it in a minute It's way too complicated, unintuitive, and the learning curve is huge. It causes more problems than solutions and there are much easier, less expensive platforms that would do the job.

Except that its only one jar and only takes a click to start your nightmare, Nothing good here.

Marketed as the best CMS and with many other huge claims, most of them are half truths if not flat lies. Marketed as OSGi, AEM in reality falls flat on key feature of OSGi, like ability of handling dependencies to the same library but with different versions. JCR is like filesystem but not truly a file system and this causes you lot of pain. TouchUI is said to be the future and but classicUI is what you will be using in reality, as TouchUI is not yet right there. Many features can only be used in theory like iParasys(designer's nightmare) for responsive design. Its an old system and hence has its not own legacy issues, as they have shied away from complete re-writing of the system. You pay a hefty price for license and will go through huge pain for implementing it. Maintenance is not easy as training staff is costly, it has a long learning curve and skilled consultants are again pricey and hard to find. To gain anything out of the power of this Monster you will probably need new Infrastructure and architecture which again can be costly. And the Marketing never stops, they try to sell you target and cloud services and other stuff.

This system might be good for intranet sites and govt sites which are fairly static, something like sharepoint or any old java based cms might be used for. But not a fit for many other USE CASES like eCommerce. Open source CMSs are free, as in free Cat. You still need to feed the free Cat . But AEM is pricey, as in a Pricey Elephant. And a Pricey Elephant takes lot more than a Cat.

As an web platform, AEM offers great flexibility for developers.

As a stand-alone brand portal, AEM lacks the out-of-the-box features included in most DAM systems such as robust metadata management, duplicate recognition, advanced search functions.

Stand-alone, password-protected DAM for marketing assets.