Deployment & Go-Live Checklist

Pre-Deployment Checklist

Complete these steps before deploying to production or handing over to the client.

• Environment variables set for production (NEXT_PUBLIC_HANDOVER_API_URL, NEXT_PUBLIC_HANDOVER_API_KEY)
• Using ho_live_* API key (not ho_test_*)
• All branding variables configured (site name, support email)
• Test content created and displaying correctly
• At least one image uploaded and rendering
• Admin login tested with correct credentials
• Lock state tested (toggle lock in dashboard, verify site shows lock screen)
• Password reset flow tested
• Rate limiting tested (5 failed logins = 30min lockout)
• Build passes without errors (npm run build)

Bootstrap Admin Account

Before handing over, create the owner admin account for the client. This is a one-time setup that gives them full control.

// Client visits: https://clientsite.com/admin/login
// First-time setup form appears
// Enter:
// - Client password (from project creation)
// - Desired username (e.g., "admin")
// - Secure password (10+ chars, upper, lower, number)

// Save credentials securely for client

Content Migration

If migrating from an existing CMS, import content before launch to avoid downtime.

• Export content from old CMS
• Use updateText() to bulk import via script
• Upload all images via admin interface
• Verify all pages render with new content
• Keep old CMS as backup until confirmed working

Testing Scenarios

Test these scenarios before marking the project as complete.

• Edit text content and see live update
• Upload image and verify it appears
• Delete image and confirm removed
• Create second admin user (editor role)
• Test editor permissions (can't create users)
• Reset password and confirm all sessions revoked
• Toggle project lock and verify admin shows lock screen
• Test on mobile devices (admin interface is responsive)

Deployment Platforms

Handover works with any Next.js deployment platform. Follow platform-specific steps for environment variables.

# Vercel
vercel --prod

# Netlify
netlify deploy --prod

# Custom server (Node.js)
npm run build
npm run start

Post-Launch Support

After handover, monitor these areas and provide client training.

• Train client on admin interface (10-15 min walkthrough)
• Provide documentation link
• Set up monitoring/alerts for errors
• Schedule 1-week follow-up call
• Document storage usage (show in dashboard)
• Share upgrade process if nearing limits

Rollback Plan

If issues arise post-launch, have a rollback strategy ready.

• Keep previous deployment active initially
• Use feature flags to toggle Handover on/off
• Export content regularly as backup
• Document rollback steps for team