Launch Checklist

Launch Checklist

Comprehensive checklist for launching LARC or LARC-based applications.

---

Timeline Overview

• 7 days before: Complete all "1 Week Before" tasks
• 3 days before: Complete all "3 Days Before" tasks
• 1 day before: Complete all "Day Before" tasks
• Launch day: Follow "Launch Day" timeline
• Post-launch: Monitor for 48 hours

---

1 Week Before Launch

Repository & Code

• All tests passing (261+ core tests)
• No critical or high-severity npm audit issues
• Latest versions published to npm:
  • @larcjs/core@2.0.0
  • @larcjs/core-lite@2.0.0
  • @larcjs/ui@2.0.0
• GitHub Actions workflows all green
• All TODO/FIXME comments resolved or documented

Documentation

• README.md up to date with latest features
• All docs/ files reviewed and current
• API documentation complete
• CONTRIBUTING.md, CODE_OF_CONDUCT.md, SECURITY.md in place
• CHANGELOG.md updated with latest release
• All links in documentation verified working
• TypeScript documentation complete

Examples & Demos

• Playground working and up-to-date
• All examples tested and working
• Mobile responsiveness verified
• Examples work in incognito mode (no cache dependencies)

---

3 Days Before Launch

Content Creation

• Demo video recorded (2-3 minutes)

  • Shows problem being solved
  • Shows solution
  • Shows wow moment
  • Shows playground

• FAQ prepared for common questions:

  • "How is this different from React/Vue?"
  • "What's the browser support?"
  • "Is it production-ready?"
  • "How does bundle size compare?"
  • "Can I use TypeScript?"
  • "What's the learning curve?"

Website & Infrastructure

• GitHub Pages deployed and current
• All CDN links working (test unpkg.com URLs)
• Site works on mobile devices
• Playground loads in <3 seconds
• SSL/HTTPS working correctly
• No broken images or assets

---

Day Before Launch

Final Testing (Critical!)

Test on multiple browsers:

• Chrome (desktop) - Latest version
• Firefox (desktop) - Latest version
• Safari (desktop) - Latest version
• Edge (desktop) - Latest version
• Chrome (mobile) - iOS
• Safari (mobile) - iOS
• Chrome (mobile) - Android

Test all key pages in incognito/private mode:

• Main README renders correctly on GitHub
• Playground loads and works
• Examples work
• Documentation site loads
• All links work (click every link!)

Test specific scenarios:

• Clone fresh repo and follow Quick Start
• Install from npm and verify it works
• TypeScript imports work correctly
• CDN imports work

Performance Check

• Playground loads in <3 seconds on 3G
• Core bundle size verified
• No console errors on any page
• No 404s in network tab

Team Coordination

• Team members available on launch day?
• Backup person assigned if primary unavailable
• Communication channel set up
• Response strategy discussed
• Roles assigned:
  • Technical questions responder
  • Community responder
  • Bug report triager

---

Launch Day

Pre-Launch

• Double-check all services are up:
  • GitHub.com accessible
  • GitHub Pages working
  • npm packages available
  • CDN links working
• Team members online and ready
• Notifications enabled for GitHub issues/discussions

Launch

• Post announcement
• Post follow-up comment with quick summary
• Save post URL
• Share on team communication channel
• Start monitoring

First Hour After Launch

• Monitor for questions
• Respond quickly to technical questions
• Be humble, helpful, and honest
• Note any repeated questions for FAQ
• Watch for bug reports

---

Post-Launch Monitoring

First 24 Hours

• Check for new issues every 2 hours
• Respond to all questions within 4 hours
• Triage any bug reports immediately
• Update FAQ if same question asked 3+ times
• Monitor for service issues

First 48 Hours

• Daily summary of feedback
• Prioritize and assign issues
• Plan fixes for any critical bugs
• Thank early contributors
• Update documentation if gaps found

First Week

• Publish post-launch blog post
• Add testimonials (if any)
• Release patch for any bugs found
• Update roadmap based on feedback
• Celebrate wins!

---

Emergency Procedures

If Site Goes Down

1. Check GitHub Status: https://githubstatus.com
2. Check CDN status (unpkg, jsdelivr)
3. Post update on social media
4. Switch to backup CDN if needed

If Critical Bug Found

1. Acknowledge the issue publicly
2. Assess severity and impact
3. If blocking: create hotfix branch
4. Test fix thoroughly
5. Publish patch release
6. Update users

If Overwhelmed with Questions

1. Prioritize: bugs > how-to > feature requests
2. Point to documentation first
3. Create FAQ entries for repeated questions
4. Ask community members to help

---

Success Metrics

Track these metrics after launch:

• GitHub stars in first 24 hours
• npm downloads in first week
• Issues opened (goal: constructive feedback)
• Documentation page views
• Playground usage
• Community questions answered

---

See Also

• Development-Workflow - Development guide
• Troubleshooting - Common issues
• FAQ - Frequently asked questions