---
sourceDocument: Xanadu ServiceNow AI Platform user interface
sourceDocumentLink: https://www.servicenow.com/docs/r/xanadu/platform-user-interface

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu ServiceNow AI Platform user interface

ft:clusterId :

    - platux

bundleId :

    - platux

workflow :

    - Platform


---

# Content Management System

# Content Management System {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

The Content Management System (CMS) is a ServiceNow application that enables users to
create a custom interface for the ServiceNow platform and ServiceNow
applications.  
Important:  
Use Service Portal for new development instead of CMS. Service Portal is an alternative to CMS with a refined user experience, and is active by default in the base system. For more information, see [Service Portal](https://www.servicenow.com/docs/aDoIZlOcBXAck1dFMDKg9w "Service Portal allows you to build a mobile-friendly self-service portal experience for your employees or customers. Service Portal is a ServiceNow AI Platform feature that is active by default and interacts with parts of the platform so users can access platform features through portals.") and [Content Management and Service Portal](https://www.servicenow.com/docs/7dv8o2Jyl0fzvb_pqSGyBA "Service Portal is a compelling alternative to the Content Management System (CMS) with a refined user experience. It does not duplicate CMS or platform UI functionality. Users who have sophisticated experiences delivered through CMS may need to invest time into transitioning to Service Portal, especially if the CMS implementation includes complex and customized Service Catalog forms.").

A CMS typically requires a systems administrator or a web developer to set up and add features.
Non-technical users can use the CMS application as a tool for website maintenance. You also want
to consider the timing of the addition of content management, and the maturity level of ServiceNow data. For more information, see
[CMS
Planning](https://www.servicenow.com/docs/ogbpWpDx2oNGIK~G3T~kog "Before building a website in the CMS, it is important to have a good understanding of what to build and who the audience is.").  
Following are several CMS project ideas:

* Design a company-wide service catalog that offers a collection of services.
* Present a customized UI for a knowledge base.
* Create customized login pages, search pages, views of lists, tables, charts, or graphs.
* Design a complete website.
* Integrate ServiceNow with other company applications.
* Build a tailored self-service portal for end users that is in compliance with a corporate style guide.
{#c_ContentManagementSystem__ul_dhr_rxm_44}

## Example CMS sites

There are two common interface approaches within the ServiceNow community:  
* An image and text-based interface similar to Amazon.com
* A search-based interface similar to Google
{#c_ContentManagementSystem__ul_drw_gzm_44}

Both approaches have been used successfully. The approach you select depends on the needs of
the people using the data and how easy it is to train them. While the two design philosophies
are different, both approaches share the common goal of UI simplicity.
* **[Content Management design](https://www.servicenow.com/docs/ogbpWpDx2oNGIK~G3T~kog)**   
  Before building a website in the CMS, it is important to have a good understanding of what to build and who the audience is.
* **[Domain separation and the Content Management System](https://www.servicenow.com/docs/2OwInKXyBHRIbFN~IqcB_g)**   
  Domain separation is supported in the Content Management System. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.
* **[Configure Content Management sites](https://www.servicenow.com/docs/NNEiFAjIphR9X~6IKI85lw)**   
  Planning a CMS site involves obtaining resources, communicating with others about design, and gathering content.
* **[Content Management integration points](https://www.servicenow.com/docs/vPsgEcj5FuZ5dHBdzU1d0w)**   
  Integration points use content blocks in CMS to link different applications together using static and dynamic methods.
* **[Content Management testing](https://www.servicenow.com/docs/X0Jfm2_gjD8p8b4Gdbfprw)**   
  Test your site to ensure that all pages display correctly, links go to the specified address, and images are not broken. It is important to test the site as you build it. Do not wait until just before launch to begin testing.
* **[Global search in Content Management](https://www.servicenow.com/docs/np7wHyQIWNbRIa5kDgRYHQ)**   
  When you add global search to a CMS site, two different search result blocks can display, depending on the user role: global or no global.
* **[CMS translation](https://www.servicenow.com/docs/2YKXMAtO1xiHOErbhkGgoA#c_CMSTranslation)**   
  You can translate CMS sites by activating internationalization plugins and manually translating custom interface strings.