Content Management design 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 organizationBefore 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 identificationIdentify the team members who assist you with website design, branding, and development.Data preparationIt is important that there is enough data in the ServiceNow instance before you begin to build the CMS website.Corporate style guideWhen you build a CMS website, you design the look and feel based on guidelines in the corporate style guide.Prototypes and rapid web designMany user interface designers use prototypes and rapid web design techniques to visualize the final product before it is developed.Content Management navigationAfter you design the hierarchical structure of the site, begin planning site navigation.System content managementMost of the content in a CMS site is managed in different locations throughout the system.Related TasksActivate the Content Management SystemConfigure Content Management sitesRelated ConceptsDomain separation in the Content Management SystemContent Management integration pointsContent Management testingGlobal search in Content ManagementCMS translation
Content Management design 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 organizationBefore 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 identificationIdentify the team members who assist you with website design, branding, and development.Data preparationIt is important that there is enough data in the ServiceNow instance before you begin to build the CMS website.Corporate style guideWhen you build a CMS website, you design the look and feel based on guidelines in the corporate style guide.Prototypes and rapid web designMany user interface designers use prototypes and rapid web design techniques to visualize the final product before it is developed.Content Management navigationAfter you design the hierarchical structure of the site, begin planning site navigation.System content managementMost of the content in a CMS site is managed in different locations throughout the system.Related TasksActivate the Content Management SystemConfigure Content Management sitesRelated ConceptsDomain separation in the Content Management SystemContent Management integration pointsContent Management testingGlobal search in Content ManagementCMS translation
