Briefing

Phase 0 Deployment Checklist

Source: docs/briefings/phase0-checklist.md · Back to index · Beta hub

Phase 0 Deployment Checklist

Digest of apps/stps/deploy_n_v2/v2/claude/step_0.md so the team can deploy the preview quickly.

Scope

  • Goal: Ship a working preview (teacher/student review) with access control.
  • Keep: Signals, Resources, Collections/Weeks, Sessions (basic), Discussions, Timeline, Calendar, Dashboard.
  • Hide/remove: Workflow/Pipeline, Materials Manager, Todos, Ideas, any AI features (for now).

Steps

  1. Navigation cleanup

    • Hide unfinished routes.
    • Add a FeatureGate component so blocked URLs show “not available” even if someone navigates manually.
  2. Temporary auth guard

    • Simple password prompt in _app.tsx (Phase 0 only).
    • Use sessionStorage to avoid repeated prompts; replace with Supabase Auth + middleware in Phase 1.
  3. Environment variables (.env.production)

    NEXT_PUBLIC_APP_NAME="STPS Learning Platform"
    NEXT_PUBLIC_USE_CONVEX=true
    NEXT_PUBLIC_USE_SUPABASE=true
    NEXT_PUBLIC_ACCESS_PASSWORD="stps2024"   # change for actual deploy
    SUPABASE_URL=""
    SUPABASE_ANON_KEY=""
    CONVEX_URL=""
    
  4. Build scripts (apps/stps/package.json)

    {
      "scripts": {
        "dev": "next dev",
        "build": "next build",
        "start": "next start",
        "export": "next export"
      }
    }
    
  5. Vercel deployment

    • Use Next.js next build / next start.
    • Configure env vars in Vercel dashboard.
    • Keep current router (no Pages/App Router refactor during Phase 0).

Use this checklist when you’re ready to flip on the preview; Phase 1 work (feature flags, universal blocks, session enhancements) lives in claude-overview.md.