Adobe Experience Manager vs. Extensis Portfolio

I'll answer the second one because I mean, the first one I don't have an issue with. The second scenario is we oftentimes have the need to spin off very small campaign style sites or sites that generate leads but are unbranded and that sort of thing. So that's hard to do in AEM because you have to then create another organization within AEM to do that. And we're talking about sites that are maybe five to 10 pages in size. So we've been investigating Edge, but then that's a different workflow, so we'd have to train people on that. So it would be nice if there was something within the AEM structure that could allow you to do something very similar to Edge, where you make some small micro sites that are not necessarily branded, that you could still host within the platform and not have to retrain everybody on a completely different platform.

Incentivized

Extensis Portfolio is perfect for organizing photos as long as everything is keyworded correctly. If it is not part of a group's workflow to add a description or keywords to your photos, then you'd be dumping your photos into a pool with no way to search for them. Extensis Portfolio is best utilized when you give it the ability to help you search (by keywords yourself).

Incentivized

• It allows us to scale so that we can make a change on a global footer. And it applies to all of the different property websites. It allows us to set up components and compartmentalize things in a way. The big thing is that it's scalable. And then it also ties into Adobe Analytics and other Adobe products. So we are a complete Adobe shop. Every Adobe product that we can use, we use. I don't think we do it for marketing so much, but for doing target testing and analytics, data scientists are using the same product and so it all speaks.

Incentivized

• Watch folders: Extensis allows for multiple watch folders to be commissioned on a variety of network connected data shares--NAS, direct connect external HDs, etc.. We have our workflow such that each photographer can upload their job into their own folder, and Portfolio automatically injests the image assets.
• Metadata injecting: a key component of our archiving needs are met with Portfolio's fully- customizatable and automatic metadata injection. This allows us to set standard fields across all the assets, while also allowing for custom variations in categories, keywords, and tags. Absolutely key to our workflow.
• Integration with Adobe CC is seamless through the built-in connector.
• Finally, the support team is OUTSTANDING! We absolutely LOVE our support engineer. We are a small org compared to the rest of his portfolio, but he always puts in the extra effort and takes the time to allow us to feel like we are totally supported.

Incentivized

• easier way to make universal changes for multiple websites at a time (ie pushing out a new experience fragment to all as opposed to having to individually add to each site)
• easier way to get site images to look and be sized exactly as I want directly from the site page editor

Incentivized

• Learning curve. It can be very intimidating and difficult to learn for people who are not experienced with similar software.
• Ease of adding new users. It's currently a long process to bring anyone new onto the platform. We have to go through our DAM manager and only they have the ability to add or remove people.
• Thumbnail previews sometimes blank. Sometimes the thumbnails for photos don't load or need to be refreshed manually, which can be frustrating when needing to search through multiple folders and photos.

Incentivized

We had and still have a fantastic experience using Adobe CQ. Lots of flexibility, great integration with other Adobe products we already use and a powerful technology make it a great fit for our corporate environment. Also as the community grows, it makes it easier to network with other developers and users to get new ideas on how to continue to get the best out of the software.

Sure there are a few quirks in the interface, but once you learn them, building and editing pages is fast and efficient. Once you have the content and the planned design decided (how the pages will look and which components you will use), page builds and publishing are quick. I was able to build a 10-page specialized site with cards built using the list component in an afternoon

Incentivized

Being part of Adobe Suite means you are already notified when the tool has any outages. However, I have never faced unplanned outages. Whenever you face any issue with the site, it is clearly stated if there were any planned outages and how quickly you will be back to normal. So, I will say that even the outages are planned and managed in a great way like their other services.

Incentivized

With respect to performance, Adobe experience manager is one of the best in the CMS space. We didn't observe frequent slowness on platform, however the systems which are accessing experience manager should be of good specifications without which slowness would be observed. Adobe experience manager works well in integration with other solutions, unless the destination application is designed to trigger frequent calls to AEM.

Incentivized

Adobe Experience Manager, in all its capacity, is a great alternative to any other CMS you are using. It helps in rapid development and makes life easier for maintaining the website for multi-language sites. Technical know-how is eliminated at content authoring. Better documentation in terms of live examples with videos would be appreciated.

Incentivized

Because our organization tends to run software on older equipment, finding someone to support our particular configuration was a challenge. Additionally, trying to explain to someone In tech support about our issues was difficult because a lot of the issues were quirks within the software that had to be seen to be understood.

Incentivized

Depending on your individual needs, It is really quite simple to create an authoring experience for a website that looks really good. I have been part of many implementations and many teams and have seen many projects that were super successful and others that were not implemented well. AEM has room for a lot of flexibility in the implementation process compared to other CMS like SharePoint

SSO is one fits all, so we don't have to have a separate SSO for each application of Adobe The integration with Analytics works perfectly and bring directly value really quickly Target remains more complicated to set up, but can also bring a lot of value once integrated with the rest of the Adobe platform The fact that the solution is Cloud services is also a big advantage for maintenance

Incentivized

We have been with Extensis for many years-- so the comparisons are outdated at this point. Companies like WebDAM, Adobe's Lightroom, mediavalet, and others, just don't have the robust catalogue management Portfolio does. There is a solidness and assurance of functionality we experience when using Portfolio-- nothing clunky or web-cloud shaky

Incentivized

• Makes it easy to reuse components across multiple pages and site, which reduces the overhead needed to create all the individual components.
• Improves business process agility by allowing users to easily create entirely new pages or content by using existing templates
• Increases conversion rates across our sites by enabling a more consistent experience for users

Incentivized

• Allows quick and easy image and asset searches.
• Has been an invaluable tool for our organization by freeing up database employees to tackle other tasks.

Incentivized