Initialize Companion for bt-web-v2

[voctory]

Notes

Completes Workstream E: bt-web-v2 Companion Migration

• Imported the Companion structure from bt-web-v1 and add BluePrint 2025 as the event
• On the production environment, block non-admins from accessing non-Companion pages and redirect to Companion at /companion
• Revert .env flag name change of REACT_APP_STAGE back to NEXT_PUBLIC_REACT_APP_STAGE
  • seems like we're doing client-side fetching which is why we need to expose the .env variable. Ideally, all fetchBackend requests should be running on Next.js server-side, might address this in another PR

Future Work

• Before merging to main: we'll need to create the blueprint;2025 event on Production
• Future refactoring: remove all 'fetch' calls and replace with fetchBackend
• Remove dependency on /registrations API
• Implement UI/UX from MMD Figma

Testing

Manual testing on local with npm run dev, localhost:3000/companion

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
biztech-v2	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 16, 2024 7:21am

[voctory]

Adding Workstream C for review @liuisaac @AllanT102