---
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 design

# Content Management design {#ariaid-title1}

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

Before building a website in the CMS, it is important to have a good understanding of
what to build and who the audience is.

A high volume of content can heavily influence the look and feel of the site and the site
hierarchy. When deciding the content, design for ease of maintenance for the people who take care
of the system. This level of planning can be time-consuming, but is important.

Review website design prerequisites to help you set expectations, scope deliverables, and
define reasonable time lines. Consider both the planning and execution of site design, to
understand how sites are built, and to provide a working overview of the CMS.

Timing is important when considering the addition of content management. Successful deployments
of the content management system usually take place after phase 1 processes (for example,
Incident, Problem, Change, Catalog, and Knowledge) are in place. This is especially true if the
team has limited website design experience. Waiting until phase 2 of deployment gives
administrators time to work in ServiceNow
and to understand how the organization uses the system and what business needs it meets.

Also consider the maturity level of data in the ServiceNow system. Depending on the ITIL
processes used, content management is only useful and effective once the data within ServiceNow is established. Ensure that
hierarchies, tasks, and workflows are well-defined. For example, before creating a catalog
interface, confirm that the service catalog has been in place for some time, has been used, and
contains data. The same is true for a knowledge management interface, particularly when high
ratings or view counts define article placement on the page.
* **[Content organization](https://www.servicenow.com/docs/oaQ6P4QhaxPN4DobRlZNBw)**   
  Before you begin to build the CMS website, list all the content that you want to include and take the time to organize it.
* **[Team member identification](https://www.servicenow.com/docs/EzWwqRXD7UyUOJvButHzmw)**   
  Identify the team members who assist you with website design, branding, and development.
* **[Data preparation](https://www.servicenow.com/docs/kgqzdhzdt96q7eqr02YheA)**   
  It is important that there is enough data in the ServiceNow instance before you begin to build the CMS website.
* **[Corporate style guide](https://www.servicenow.com/docs/h2MML5jiP6Q4t2WHpNwc8g)**   
  When you build a CMS website, you design the look and feel based on guidelines in the corporate style guide.
* **[Prototypes and rapid web design](https://www.servicenow.com/docs/d_UqI24kVASejMYgRLApow)**   
  Many user interface designers use prototypes and rapid web design techniques to visualize the final product before it is developed.
* **[Content Management navigation](https://www.servicenow.com/docs/PJiFrcoWMQqbGvgG_5anMQ)**   
  After you design the hierarchical structure of the site, begin planning site navigation.
* **[System content management](https://www.servicenow.com/docs/ie9H4084BTcQM~J6WJ1ekg)**   
  Most of the content in a CMS site is managed in different locations throughout the system.

**Related concepts**   

* [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.")
* [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.")  
**Related tasks**   

* [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.")