4 out of 5.0, Reviewed Dec 6, 2016
The project was about migrating from Version 6.1 to 6.2. At the beginning everything seemed to be ease, but some customized featured were difficult to migrate. The product maturity was not as expected, as well.
5 out of 5.0, Reviewed Dec 1, 2016
Overall the experience with AEM has been fantastic. Quick support and online resources.
3 out of 5.0, Reviewed Nov 30, 2016
The product got us up and running quickly and provided good basic functionality to simplify and streamline work. Unfortunately, the product was too simple for our content management needs and we needed to significantly customize. This lead to future upgrade issues that held us back from upgrading for a few years due to cost of rework.
Again, understand the complexity of your basic content workflow to see if the product aligns. If it does not, you will either need to change your workflow and the requirements or customize this product. Customization of the product might be sub-optimal.
I would make sure that we had a better understanding of the complexity of content management needed to understand whether the product aligned well enough.
Deployment of this solution was overly complex. It should not be this complicated and fragile from a deployment standpoint.
3 out of 5.0, Reviewed Nov 23, 2016
stay vanilla - configruation not codiing
enterprise solution good support
was more influential to see the value in staying vanilla - configruation not codiing
stay vanilla - configruation not codiing
5 out of 5.0, Reviewed Nov 21, 2016
Adobe Experience Manager is a web-based client-server system for building, managing and deploying commercial websites and related services. It combines a number of infrastructure-level and application-level functions into a single integrated package. At the infrastructure level AEM provides the following: Web Application Server: AEM can be deployed in standalone mode (it includes an intergated Jetty web server) or as a web application within a third-party application server (WebLogic, WebSphere, etc). Web Application Framework: AEM incorporates the Sling Web Application Framework that simplifies the writing of RESTful, content-oriented web applications. Content Repository: AEM includes a Java Content Repository (JCR), a type of hierarchical database designed specifically for unstructured and semi-structured data. The repository stores not only the user-facing content but also all code, templates and internal data used by the application.
support is not so good
easy of documentation
4 out of 5.0, Reviewed Sep 22, 2016
Great product. Ease to configure. Smooth deployment.
Minimize the templates and components across business divisions. This will speed the implementation process.
Ease of use. The ability for business users to create websites without IT intervention. Easy to maintain and support. State of the art functionality and features.
Support has been responsive to our issues.
4 out of 5.0, Reviewed Aug 17, 2016
Excellent experience with vendor and product, with relatively few late-breaking surprises.
The cloud model is definitely the way to go for WCM, but they are not all created equal. The Adobe Managed Service option for AEM is a great way to go.
Open source stack with open API integration.
We have very few regrets, but it would have helped to fully understand all of the options for deployment topology earlier in the process, in order to communicate them more effectively with stakeholders.
Response from the vendor has been very good.
4 out of 5.0, Reviewed Jul 11, 2016
AEM has enabled our content creators to work with little to no IT involvement. Turn-around time for new content has been reduced significantly.
Dig through the marketing hype and carefully consider your use cases when evaluating AEM.
The platform is flexible once you learn the underlying technologies. Configuring and adding on to the core platform in a supported way is relatively simple for experienced developers.
Allowing for and assisting with early proofs of concept would help the entire organization get on board. Over exaggerated sales hype is easily seen through and people dismiss the underlying value in the platform.
We would more closely control early site development rather than outsourcing nearly all of the work. The costs were higher than expected due in part to the external vendor treating our sites the same way as other sites they've done, then having to rework later.
5 out of 5.0, Reviewed Jun 21, 2016
Adobe treated us as a true partner and they were extremely flexible and agile with the implementation. Additionally, our internal team focused on execution and they were able to complete tasks without defect and keep the business engaged throughout.
Be agile and realistic. 80/20 rule.
Out of the box mobility.
The customizations and the lack of support for them.
A little more clarity up front with the managed service and their ability to support the customizations done throughout the project.
We would put a little more focus on the editors and how many each agency should have. We are already seeing some sprawl with agencies requesting multiple editors which is making it a challenge to keep the content pristine.
4 out of 5.0, Reviewed Jun 16, 2016
Mature product. Still catching up with modern SPA based digital offerings.
Explore how your applications will have to change/evolve to adopt AEM.
More sample interactions with frameworks/libraries being used by the industry.
More through POCs on our tech stack working with AEM.