Adobe Experience Manager is a combined web content management system and digital asset management system. The combined applications of Adobe Experience Manager Sites and Adobe Experience Manager Assets is offered by the vendor as an end-to-end solution for managing and delivering marketing content.
N/A
Chrome DevTools
Score 9.6 out of 10
N/A
Chrome DevTools is a set of authoring, debugging, and profiling tools built into Google Chrome.
N/A
Crownpeak Digital Accessibility and Quality
Score 7.4 out of 10
N/A
Crownpeak Digital Accessibility and Quality is a digital governance and web content management and monitoring solution designed to support excellent customer experience across all digital touchpoints, supporting web accessibility needs, error catching, SEO best practices, brand compliance, and analytics with benchmarking. Crownpeak Digital Accessibility and Quality can be integrated into an existing CMS.
AEM isn't really like Chrome DevTools but offers some ability to crop images once you see how the content would look on a particular device. So I would say AEM compliments this tool, rather than be considered as a replacement or competitor.
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.
Chrome DevTools are great for troubleshooting bugs, broken elements on pages, styling issues, responsiveness, identifying performance issues, third-party connections for data privacy, reviewing cookies and local storage, screenshots in different dimensions. Chrome DevTools are for technical users, so you do need to have a decent understanding of some basics like HTML and CSS to get started using them.
If you have a fully customized cms and have people working on the site with html and css knowledge this is the best tool ever, all specifics can be checked. Using ab tests and optimization services we identify best practices of the website and everywhere the best practices aren't implemented we find using the custom checkpoints. Aspects that cannot be automated via a quick IT solution is turned into a checkpoint and that's great!
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.
There are some glitches in permissions inheritance that require us to toggle a save on permissions in groups that inherit from a group that was recently updated.
Large packages require stopping the workflow launcher OSGi components or many workflows will slow down the server.
Locked pages are hard to find unless I use /siteadmin... I often hear that the CQ tools will go away, but if we lose that, some small things might be harder to do, like finding locked pages.
As one delves into DevTools, one encounters a gradually steeper learning curve. You can do a lot very quickly, but to fully utilize DevTools takes time as one explores what it can do.
With many new updates, tools and items are moved, and a comfortable workflow becomes a frustrating search. This often happens when following only slightly outdated tutorials on a given feature, even in Google's own documentation.
The experimental flags, settings, and options are scattered about and a little clunky to configure when one has to make changes in multiple places.
It would be helpful if the Issues page under Website showed the WCAG level for each issue (A, AA, AAA). You currently have to look up the guideline to find the level.
There is no indicator that a page is currently being scanned. During a website scan, some of the reports are blank or missing information. Having a notification on the main page showing which websites are being scanned would be helpful.
Some ADA compliance items are left off, such as keyboard navigation, tabbing, etc.
It doesn't view the websites on mobile devices or if using a screen reader. Some pages or formatting changes depending on resolution. The DQM, from what I have seen, doesn't account for that.
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.
Adobe Experience Manager overall is fairly easy to use and caters to a wide range of users when it comes to their technical abilities. It has the flexibility to enable UI/UX designers to pop in and easily design new content with drop in components. It also has sufficient capabilities for those who are more technically inclined and want to dig more into custom code or solutions
While Chrome DevTools are very powerful, it's not the easiest thing to use, as there are so many different tools built in. It takes some exploring to discover all the options possible within DevTools, but with a little exploring, the DevTools become a very powerful asset. Accessing the basic HTML and CSS inspection is very easy though, and that's the most common usage for the DevTools.
I had a small learning curve in order to become fluent with the platform as it doesn't work like the other automated accessibility tools that I've used. However, once I was up to speed, I like it better than any of the other tools and find the data more useful, digestible, and relevant.
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.
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.
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.
I'm not entirely sure what to rate the support for DevTools, because I don't have any experience dealing with official customer support for DevTools. I would guess the primary support for DevTools would be in a Chrome forum. Typically if I have a question or issue, I am able to find an answer from doing a quick Google search. It's pretty widely used, so it's not difficult to find answers.
DQM support teams are responsive and knowledgeable, and will spend time working directly with client and agency teams to ensure the best outcomes are achieved. I can't fault the level of input and engagement from Crownpeak support teams across the board.
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
I find them pretty much the same, they have the same tools except Firefox doesn't provide the lighthouse functionality. I do prefer firefox's dark theme and colour palette. But I use Chrome Dev tools because of the Light house functionality that analyzes the page load and scores the website on desktop and mobile experience.
One of the most similar solutions to Crownpeak is the Yext tool because it has a good set of functions that can be managed from content to customer experiences, it is fascinating to be able to track all user interactions through users, in the same way as in Crownpeak that allows all users to create digital experiences.
Instead of being directly involved in the tool purchase, I am involved in analysis or what we can use to maximize the tool. Small organizations may find it expensive. However, if the team or organization focuses more on your ROI or the features you will get, then it will definitely be worth it. Pricing is based on a number of factors, including team size or the use of the tool. The user can select the pricing option that best fits their needs based on the number of form submissions they make or the number of pages they wish to publish on their global/multisite sites.
The professional services team within adobe is one of the best in terms of technical and solutioning knowledge. However, considering the billing charges of adobe professional services team, it is always recommended to involve them during platform initial setup or when a complex solution is to be built with platform customizations.
too soon to tell on increased conversion rates based on external marketing factors in play but having increased visibility into customer engagement trends will most likely lead to improvement of our conversion rates.
There have been productivity gains from the perspective of actually migrating all of our externally managed sites to the same in-house Adobe Experience Manager platform and then being able to utilize those universal components.
When driving Customer Care, it was great to be able to add the Autofix tool to the web estate - a quick-win that really drives the accessibility agenda.
Building reports off the back of DQM gives senior stakeholders an understanding of the importance of usability and accessibility.
The gamification of league tables highlights to stakeholders the areas that need focus and budget in order to improve.
