Docs
Systhema Design (opens in new tab)
Unreleased

Going-live checklist

Verify content, infrastructure, forms and accessibility before opening a client site to visitors.

On this page

Complete this against the deployed production site. Keep evidence and unresolved items with the release record. A local build is only one check.

Project and releaseLink to this section

  • Record the deployed revision and installed Systhema version.
  • Run pnpm sync, the project's type check, lint and formatting check.
  • Run pnpm build with the production build environment.
  • Run systhema doctor and resolve failures or record reviewed exceptions.
  • Review upgrade notes and any schema or data migrations in this release.
  • Confirm staging and production point at separate intended databases.

Hosting and recoveryLink to this section

  • Set NEXT_PUBLIC_SERVER_URL to the production origin.
  • Set APP_ENVIRONMENT=production on production and staging on staging.
  • Configure real PAYLOAD_SECRET and SYSTHEMA_API_SECRET values.
  • Keep registry and service credentials private.
  • Confirm the runtime can connect to its database.
  • Use SYSTHEMA_PRERENDER=off if the builder cannot reach the database.
  • Verify media persists across restarts and redeploys.
  • Back up the database and media; test a restore to an isolated environment.
  • Record the owner of domain, hosting, certificates and renewals.

Content and navigationLink to this section

  • Publish the approved pages in each intended locale.
  • Set the homepage and verify / while signed out.
  • Review Header and Footer links, including logo and enquiry actions.
  • Check nested page paths and intended redirect destinations.
  • Confirm unknown URLs return the expected not-found response.
  • Remove starter branding, sample copy and placeholder assets.
  • Confirm image alternatives describe informative images.
  • Publish privacy and cookie information appropriate to the site's integrations.

Forms and accountsLink to this section

  • Submit every public form while signed out.
  • Confirm the submission exists in Admin.
  • Confirm notification email reaches its intended recipient.
  • Test validation errors, captcha failure and success messages.
  • Check captcha configuration for the production hostname.
  • Test password reset on the public Admin origin.
  • Review each client's role and publishing permissions.

SEO and analyticsLink to this section

  • Review rendered titles, descriptions, canonical URLs and share images.
  • Verify /robots.txt and /sitemap.xml on the production hostname.
  • Confirm staging remains excluded from indexing as intended.
  • Verify locale-specific canonical and sitemap entries.
  • Test tracking before consent, after acceptance and after withdrawal.
  • Confirm analytics uses the correct property and period.

Accessibility and visual QALink to this section

  • Complete navigation and form submission using a keyboard.
  • Verify visible focus and the skip link to main-content.
  • Test mobile-menu opening, closing and Escape behavior.
  • Inspect small, medium and large layouts with long real content.
  • Check supported themes for contrast and readable controls.
  • Check reduced-motion behavior.
  • Verify unsaved live preview and published edits becoming visible.

After approval, complete the client-handover checklist. Deployment details are in Launch and Deploying.