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
Modern Campus CMS
Score 9.2 out of 10
N/A
Modern Campus CMS (formerly Omni Campus) is a CMS for institutions of higher education. It can be deployed as a cloud-based service or hosted locally. It is built in Java, uses open standards, and is extensible through APIs.
N/A
Pricing
Adobe Experience Manager
Modern Campus CMS
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Adobe Experience Manager
Modern Campus CMS
Free Trial
No
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
Required
Additional Details
—
—
More Pricing Information
Community Pulse
Adobe Experience Manager
Modern Campus CMS
Considered Both Products
Adobe Experience Manager
Verified User
Anonymous
Chose Adobe Experience Manager
End to end capabilities as well as integrations with upstream and downstream systems to make work flows, easier and faster time to market
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 …
Adobe Experience Manager is what I use most frequently. While the other tools I listed above are important, they are ultimately a secondary tool utilized on a need by need basis where as AEM is what we use daily for content creation, content updates, content optimization, etc.
AEM is comparable to Sitecore and less agile than Bynder, but Adobe products were already being used across the org and adding AEM allowed us to link it all together.
During the RFP process, we also evaluated Hannon Hill Cascade and Terminal Four. Both CMS systems had pros and cons, but overall, OU Campus was an easy choice. The features were better, non-technical users liked the simplicity of the interface, and the price was competitive.
We selected OU Campus after reviewing a number of CMS products and are extremely happy.
Verified User
Anonymous
Chose Modern Campus CMS
Before using OU Campus Content Management System we were using Adobe's DreamWeaver suite for creating and maintaining web pages. The core web development environment was cumbersome to set up. Non-tech people also had trouble understanding how the web works and how web pages are …
I don't know how OU Campus stacks against other products because I have been using OU Campus while I have been employed at my university.
Verified User
Anonymous
Chose Modern Campus CMS
MUCH easier to use than other CMS systems. Quite intuitive. Pleasant interface. Reduces anxiety for beggining users of cms system, and supports stronger users comfortable doing more.
I have evaluated Ektron, PHP Nuke, Drupal, Joomla!, typo3, Reason and SharePoint. OU Campus outshines all of these in the web CMS space. The OU Campus interface is more intuitive, more user-friendly, and the system itself is more flexible and scalable and capable in almost …
Features
Adobe Experience Manager
Modern Campus CMS
Security
Comparison of Security features of Product A and Product B
Adobe Experience Manager
8.4
Ratings
2% above category average
Modern Campus CMS
10.0
Ratings
21% above category average
Role-based user permissions
8.40 Ratings
10.00 Ratings
Platform & Infrastructure
Comparison of Platform & Infrastructure features of Product A and Product B
Adobe Experience Manager
8.0
Ratings
4% below category average
Modern Campus CMS
9.3
Ratings
20% above category average
API
7.80 Ratings
8.60 Ratings
Internationalization / multi-language
8.10 Ratings
10.00 Ratings
Web Content Creation
Comparison of Web Content Creation features of Product A and Product B
Adobe Experience Manager
7.5
Ratings
2% below category average
Modern Campus CMS
8.9
Ratings
14% above category average
WYSIWYG editor
7.40 Ratings
9.20 Ratings
Code quality / cleanliness
6.70 Ratings
9.20 Ratings
Admin section
7.00 Ratings
9.20 Ratings
Page templates
7.60 Ratings
9.60 Ratings
Library of website themes
7.30 Ratings
10.00 Ratings
Mobile optimization / responsive design
7.80 Ratings
8.80 Ratings
Publishing workflow
8.10 Ratings
9.20 Ratings
Form generator
7.60 Ratings
6.00 Ratings
Web Content Management
Comparison of Web Content Management features of Product A and Product B
Adobe Experience Manager
7.3
Ratings
1% above category average
Modern Campus CMS
8.8
Ratings
18% above category average
Content taxonomy
7.70 Ratings
9.20 Ratings
SEO support
7.10 Ratings
8.00 Ratings
Bulk management
7.20 Ratings
8.00 Ratings
Availability / breadth of extensions
7.50 Ratings
9.00 Ratings
Community / comment management
7.10 Ratings
9.60 Ratings
Best Alternatives
Adobe Experience Manager
Modern Campus CMS
Small Businesses
Bloomreach - The Agentic Platform for Personalization
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.
This website works well in an academic setting. It's easy to add pages as your site expands/grows. It's really easy to use and modify pages once you know what you're doing, but it can be a little tricky to get the hang of it at first. It is definitely useful to have in-person or virtual training before you dive in.
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.
Assets are easily managed and can be edited independently of the page they exist on.
Version history is handled well. Allows for a comment section to note what changes have been made.
Dependency tags are perfect for media that is used in several places. Upload a photo once, use it in multiple places, edit the photo or its description in one place.
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
OU Campus could use some improving on their upload changes as far as naming the document because when you are trying to upload the same document with minor revisions, OU Campus requires you to change the name of the document within OU Campus which creates multiple documents in the workfolder.
When naming documents to upload into OU Campus, it would be nice if we could name out documents the way we would instead of having to put an underscore to indicate a space in the document. Most users of OU Campus has not had proper training to know that you need to do 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.
I don't work at the college any longer, but I believe they will renew the license for the OU Campus Content Management System because of all the great benefits they have had since they initially deployed it. The system is very intuitive and easy to use. Department leads love it. The IT department also loves it because it saves them a lot of time and resources.
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
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.
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
Increased satisfaction with user experience. OU Campus has made it easier for us to address problems when they arise, making our website more efficient.
Role-based control. Our old CMS made it very easy for users to change fonts and colors on their sections, which was very detrimental to the overall brand. That's not a problem anymore.
Reduced training times. OU Campus is so easy to use, I've been able to cut training times down by half.