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
Nuxeo
Score 7.5 out of 10
N/A
The Hyland Nuxeo Platform is a cloud-native,
cloud-first, scalable solution which utilizes automation technologies to
improve efficiencies, increase accuracy, and provide its capabilities. With
it’s low-code technology, organizations can implement Hyland’s Nuxeo
Platform with customizable features that allow organizations to develop a creative workflow. Employees can then create,
tag, organize, and share dynamic content, including rich media and 3D digital
assets and their metadata to be used in…
So one of the primary focuses in the company has been SEO, and it does not seem well suited to SEO. For instance, how we set up the alt image tags. It's pretty tricky and there are multiple steps to do that. So I would like to see an Adobe Experience Manager that is more focused on out-of-the-box solutions for SEO, schema coding, alt image tags, and other sorts of SEO functionality to have that more built into the vanilla version of the product. Well suited? It's very good at scalability. And because we're managing such a large number of hotel properties, it works well for an enterprise.
Nuxeo works very well for us as a Digital Media Asset Management tool. I understand given its flexibility, it has also been used for managing insurance claims. It seems to be well suited for uses where some customization is required, yet there is a desire to leverage best practices, reusable code components.
It is able to support our incoming volume. We're one of the largest in what we do in the country, and we've not had any issues in terms of how it performs, or how it scales our customers coming in. It's a fairly stable platform. It is also a very intuitive platform in us being able to give our business users the ability to come make changes and request additions without going through a huge lift in getting those requests implemented. It has also been a very developer-friendly platform for my team to be able to develop, adapt, and build. We're also expanding on being able to use AEM both as a pure content management solution and also as a headless content solution. So that way we are trying to build a unified content platform that would allow us to create, publish, and manage content across channels from one place. So it's fairly intuitive that way. It's fairly scalable. Obviously, the modern tooling helps, but overall I think it's been a good experience.
I think some of the key things that can be done better is today we have more point solutions for different things like personalization. We have Adobe Target and for email marketing, we have Adobe Campaign Marketer and all that kind of stuff. But truly I have worked both as an implementation partner for Adobe as well as now I'm a client of Adobe. Being in both those shoes, I can say that we can do a lot better in terms of beefing up the capabilities of AEM, bringing personalization and search and content search experience closer together. It would definitely put Adobe Experience Manager in a different league if we can bring all those personalization capabilities together. I think initially the content management systems, the market was mostly meant to serve static sites. It never matured into that full-scale content personalization being married together. I think that's one area where if those integrations rather than being point solutions, if those capabilities can be made more native to AEM, I think it would definitely be a big sell for a lot of customers.
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.
From our learning curve until we got better. I'd say as we're moving forward and we're making more customizations and we're getting used to it, I'd say it's about a seven or an eight. But as more innovations and more information comes out from Adobe as they make more changes and they make improvements, I'd say they're getting probably about an eight right now.
Nuxeo provides a WebUI that they are always improving based on customer feedback. The interface is designed with flexibility in mind - this means that it must be customized to the business's use case before it can achieve its maximum usability.
The Nuxeo Studio interface provides developers and administrators the building blocks to achieve much of this customization - they just need to put the building blocks together in ways that best meet the end users' needs. The API and SDKs allow for more advanced customization.
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.
This is something that we have struggled with a bit. We push the boundaries of Nuxeo in this area, both with the number of assets and the size of assets. We have a lot of large, long videos, and we are continually tuning performance in this area.
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.
Nuxeo support is very willing to help whenever there is an issue. We have a weekly touchbase with someone from the Nuxeo team that we discuss any development issues with, and there is an open line of communication between our team and the Nuxeo team. They have been supporting us phenomenally, every step of the way.
I attended instructor-led trainings at a couple of points when I was first beginning to serve as project manager on Nuxeo projects. The first one that I attended was meant for business users and decision-makers. The second one was meant for system administrators. The first one provided a great introduction, through demos, of how Nuxeo could be adapted to very different business use cases. The second one, like many instructor-led trainings, was meant for users of a variety of skill levels, and so it could be a bit slow at times for students with a stronger technical background, but the instructor was able to include more advanced components as well.
Nuxeo University provides an ideal starting point for developers and system administrators who are new to the Nuxeo platform. So, in terms of online training for developers and administrators, the learning paths are definitely available. In terms of training for end users: keep in mind that Nuxeo is a foundation with building blocks - what you do with those building blocks is up to you and depends on your business's specific use cases. For this reason, end-user training is largely up to you because it will need to depend on how you've built and configured the system. That said, I've seen the companies that I've worked with configure the system based largely on end-user input, and so it has fit very closely with what those users wanted to do and how they wanted to do it. In cases where elements of the UI weren't fitting quite right with what users naturally wanted to do, based on their process flows, we've often found it easy enough to adapt the UI to the users, rather than using training to adapt the users to the UI.
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
The technical support team of the Nuxeo was always on the go to help us. Being an IT technician, I haven't faced any such issue, but the problem was that it took much longer than anticipated. Otherwise, we didn't need to get other implementation partners to help us in its implementation.
At Canadian Tire Financial, in the time I've been there, we've always used AEM, but in past places I've used WordPress, I've used Squarespace. Things that are more general user-friendly where you're like building your own blog or you're creating a small business website where it's basically just text, you're not intaking information or something like that. I think the customization options in AEM are huge. My experiences with WordPress were pretty straightforward. Again, it was like, I don't know, like college newspaper website or something like that where you're just like putting content up for people to look at. You're not necessarily taking in any other information. Maybe you might allow people to log in or something and save articles or something pretty straightforward, but then even then I remember that stuff taking me forever to do, to figure out and scroll through tons and tons and tons of documentation. It's just not fun. No one enjoys doing that and then even then you might not have the answer available to you. And that's so frustrating. Hey, it's super user-friendly, figuring out the content editor is pretty straightforward. You're not clicking around and being, "what the heck am I looking at?" Or you're not looking at a bazillion menus to be like, "maybe the thing I want is in here." I can't stand that. I want to be able to look at a page, see what I'm going to be getting in production, and then publish it. I don't want to look around in menus to figure out how to add something to a page.
It is built on open-source technologies. A very small footprint is required to run it. It can be run in a cloud and utilize the power of cloud services, unlike other competitors.
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.
This actually has been great for our websites. In the time that I've been with the company, we've seen at least the profitability of our websites because we are measuring that through analytics. We've seen it double since using it. We were using it when I first started with the company, but we've gotten better at how we're using it and really optimizing the use as well as the design. I think that that's made a huge difference. We've seen a huge jump in the performance of our websites with maintaining users and the e-commerce side of it.
