Public information
List the content-management system, media files and event pages you intend to publish. Include the resources used by search and application plugins.
Choose infrastructure for a campaign’s public website and event information, with clear publication controls and a plan for busy periods.
List the content-management system, media files and event pages you intend to publish. Include the resources used by search and application plugins.
Assign editor and administrator roles. Document who approves technical changes and how staff access is removed at the end of an assignment.
Estimate traffic around scheduled announcements and events. Prepare the application and its resource plan before those peaks.
Record ownership of the domain, server account and website content. Decide how the site will be archived, maintained or closed after the project.
Compare the content-management system’s CPU, RAM and database requirements with the published plans. Size media storage separately from application data. A dedicated server provides a physical-server option; a cloud plan should be assessed against its listed resource allocation and your expected traffic.
Use the server comparison to review the two server types, or explore country and city guides for location options.
Test menus, event pages, downloads and mobile layouts. Verify that unpublished material remains restricted to the appropriate editors.
Test representative demand and record who can respond to errors or capacity limits during an announcement.
Retain the website files, database backup and account ownership information needed for continued operation or an orderly archive.
The standard dedicated and cloud plans are presented as unmanaged. Assign responsibility for the operating system, applications, updates, monitoring and backups. Review server management responsibilities and use the deployment checklist to plan the move.
Compare the current configurations and prices, then review your product, location, options and final total in the cart.