Built on Java EE standards, OU Campus runs on any major server (or can be hosted by OmniUpdate as SaaS) and publishes to any web server via FTP/SFTP. Plus, it supports all major operating systems, including Linux, Solaris, and Windows, and supports all major server-side languages, including PHP, .NET, ASP, ColdFusion, and JSP.
OU Campus provides a robust template structure using XML/XSL or XHTML, giving you standards-perfect pages every time. Templates can be nested and shared across multiple sites, providing flexibility and consistency across sites. Templates in OU Campus can use responsive and adaptive design to adapt to all screen sizes and devices, so your site visitors can have an enriched mobile user experience.
OU Campus is designed for high performance throughput following modern Model-View-Controller (MVC) design patterns. Prepared statements and stored procedures used throughout the design enable extraordinary end-user speed and responsiveness for the most commonly accessed functions. And AJAX is used to provide a responsive user interface and eliminate the time typically required to reload lists and commonly used data.
OU Campus' modular design handles hundreds of sites, thousands of users, and millions of pages. Its standards-based approach, combined with scalable architecture, allows for growth and change over the long haul.
The underlying platform of OU Campus is powered by XSLT 3.0, which gives developers a huge leap forward from a scripting-type language to a full-fledged functional programming language with typed variables and user-defined functions. The power is truly astounding, and it provides added functions, operators, and additional efficiencies that developers just don't get with other transformation languages.
OU Campus provides the high performance expected of an enterprise system through better engineering. Unlike other systems that rely on a proprietary database schema to store page content, OU Campus leverages the speed, efficiency, and openness of XML on the server's native file storage to provide a swift and robust experience.
Databases are great for storing large volumes of small blocks of data; however, there is typically a performance overhead when using a database to store large blocks of data. That is why OU Campus uses its database only where appropriate to store information that it needs to know about your content (e.g., permissions, tags, and other settings). Developers have the choice of using a MySQL, Microsoft SQL Server, SAP Sybase ASE, or PostgreSQL database. And it runs on a separate staging server, so content is published to the live web server on demand. This architecture ensures your website is never throttled by the web CMS application or process. Both static and dynamic pages can be published this way.
Built on open standards, OU Campus templates contain non-proprietary code that developers can fully control. And templates in the CMS use recognized standards, including HTML/CSS and XML/XSL, which means all major development platforms are supported. Plus, the system enforces industry standards including W3C, WAI, XML/XSL, RSS, Section 508, LDAP, Active Directory, and Single Sign-On via CAS or Shibboleth.
The CMS targets multiple server-side environments by publishing pages to HTML, HTML5, XHTML, PHP, ColdFusion, ASP, .NET, JSP, and more. It also supports the use of XSL:FO, a language for formatting XML documents that can be used, for example, to create PDF versions of XHTML pages when they are published.
A robust set of APIs allow developers to harness the power of OU Campus to remotely modify users, groups, and other record data, including creating new sites and subsites. And through the server-side Live Delivery Platform module, features like Forms, Surveys, and Polls can be added.
As users build content in OU Campus, proper supporting elements are automatically created, including navigation, breadcrumbs, sub-navigation, and any other needed "include" elements. The CMS enables any required taxonomy schema for search engine use, content repurposing, or automatic inclusion in select navigation. Automated and manual taxonomy metadata can be used. And because it is UTF-8 compliant, content can be added or edited in any single or double-byte language characters.