Immediate Action Plan - What to Focus On First

Superseded: This document predates all locked platform decisions and is retained only as a historical record. It must NOT be used as implementation guidance. The decisions below have all been resolved:

• Auth is Clerk (Apple/Google social login — ADR 0003). Not Azure AD B2C / Entra.
• Database is PostgreSQL on Azure DB for PostgreSQL Flexible Server (ADR 0024). Not Azure SQL.
• Compute is Azure Container Apps (containerised Node.js) (ADR 0024). Not Azure Functions.
• SMS is Twilio (ADR 0013). Not unspecified.
• Package manager is pnpm + Turborepo (ADR 0001). Not npm.
• Project management is Azure DevOps Boards, not GitHub Issues/Projects.

For current guidance see pmo/platform-strategy.md, docs/internal/architecture/system-architecture.md, and the ADRs in docs/internal/adr/.

Phase 1 Priority Order (Next 4 Weeks)

Week 1: Foundation Setup

🏗️ Repository Structure ✅ DONE

• ✅ Created proper folder organization
• ✅ Added documentation and planning files
• ✅ Set up GitHub templates

💰 Cost Optimization Setup 🔥 HIGH PRIORITY

1. Apply for Microsoft Nonprofits Program

   • Visit: https://nonprofit.microsoft.com/
   • Required: 501(c)(3) documentation
   • Benefit: Up to $3,500/year Azure credits
   • Processing time: 2-3 weeks

2. Set up Azure Subscription

   • Create Azure account
   • Apply nonprofit credits when approved
   • Set up billing alerts

Week 2: Identity & Authentication

🔐 Azure AD B2C Setup 🔥 HIGH PRIORITY

1. Create Azure AD B2C tenant
2. Configure social identity providers (Google, Microsoft)
3. Set up custom user flows with invitation codes
4. Design approval workflow

📊 Database Setup

1. Create Azure SQL Database (Basic tier)
2. Run schema creation scripts
3. Set up connection strings
4. Configure managed identity access

Week 3: Development Environment

⚙️ Local Development Setup

1. Initialize React frontend project
2. Set up Azure Functions backend
3. Configure local authentication
4. Create basic API endpoints

🚀 Deployment Pipeline

1. Set up Azure Static Web Apps
2. Configure GitHub Actions
3. Set up staging environment
4. Test deployment pipeline

Week 4: MVP Features

📅 Basic Calendar Implementation

1. Create event management API
2. Build basic calendar UI
3. Implement RBAC permissions
4. Add user registration flow

📢 Priority Communication System Setup 🚨 HIGH PRIORITY

1. Set up SMS service (Twilio)
2. Configure email service (SendGrid)
3. Build message approval workflow
4. Create member communication preferences

🎯 Phase 2 Priorities (Weeks 5-8)

Communication System - Essential for community coordination Pony Express Network - High demand feature for inter-community support

🛠️ Tools You'll Need to Install

Development Tools

# Install Node.js 18+
winget install OpenJS.NodeJS

# Install Azure CLI
winget install Microsoft.AzureCLI

# Install Azure Functions Core Tools
npm install -g azure-functions-core-tools@4 --unsafe-perm true

# Install VS Code extensions
code --install-extension ms-vscode.vscode-typescript-next
code --install-extension ms-vscode.azurecli
code --install-extension ms-azuretools.vscode-azurefunctions

📋 Key Decisions Needed This Week

1. Microsoft Nonprofits Application

Decision: Apply immediately to get Azure credits Action: Gather 501(c)(3) documentation and submit application

2. Frontend Framework Choice

Recommendation: React + TypeScript + Chakra UI Why:

• Excellent VS Code/Copilot support
• Great Azure Static Web Apps integration
• Clean, accessible UI components
• Strong community support

3. Authentication Strategy

Recommendation: Azure AD B2C with custom flows Why:

• Built-in social login
• Custom approval workflows
• Scales with your community
• Integrated with Azure ecosystem

4. Database Tier

Recommendation: Start with Azure SQL Basic tier (~$5/month) Why:

• Easy scaling as community grows
• Familiar SQL Server tools
• Good VS Code integration
• Can upgrade seamlessly

🎯 Success Metrics for Week 1

• [ ] Microsoft Nonprofits application submitted
• [ ] Azure subscription created
• [ ] Basic project structure in place
• [ ] Team alignment on technology choices
• [ ] Development environment requirements documented

🚨 Potential Roadblocks & Solutions

Roadblock: Microsoft Nonprofits Approval Delay

Solution: Start with Azure free tier, migrate credits when approved

Roadblock: Complex Authentication Requirements

Solution: Start with simple email/password, add social login later

Roadblock: Database Design Complexity

Solution: Implement core tables first, add advanced features iteratively

📞 Next Steps After Week 1

1. Week 2: Focus on authentication and user management
2. Week 3: Build core calendar functionality
3. Week 4: Implement RBAC and approval workflows
4. Month 2: Admin portal and advanced features

💡 Quick Wins to Build Momentum

1. Set up live staging environment - Shows real progress
2. Create sample user accounts - Makes testing easier
3. Build simple event listing - Core functionality visible
4. Add basic email notifications - Professional touch

---

Remember: Start simple, iterate quickly, and leverage Azure's free tiers to minimize costs while building.

Next Immediate Action: Apply for Microsoft Nonprofits Program today! 🚀

Would you like me to help you with any of these specific steps, such as setting up the React frontend or creating the Azure Function APIs?