Content Management testing
-
- UpdatedJan 30, 2025
- 1 minute read
- Yokohama
- Content Management System
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.
Also, test templates as you create them so any issues are resolved before creating other content based on the templates. Recruit as many people as possible to help you test.
Here are some general site testing guidelines:
- Test on the browsers and platforms your site visitors use
- Test on various monitors (for example, LCD and CRT)
- View pages using different screen resolutions
- View pages using different color settings
- Test all navigation and links
- Test items that can be downloaded (for example, PDF files)
- Test the search functionality
- Test site security
- If necessary, test for accessibility (for guidelines, see the W3C Website Accessibility Initiative)
Related Content
- 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.
- Domain separation and the Content Management System
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
Planning a CMS site involves obtaining resources, communicating with others about design, and gathering content.
- Content Management integration points
Integration points use content blocks in CMS to link different applications together using static and dynamic methods.
- Global search in Content Management
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
You can translate CMS sites by activating internationalization plugins and manually translating custom interface strings.