Client Meeting 1 β 4 August 2026
Date: 4 August 2026
Time: 1:30 PM β 2:15 PM
Platform: In-Person MSL 005
Attendees: Whole team + Client
Minutes taker: Benjamin
Agendaβ
- Present the proposed tech stack and architecture.
- Walk through the initial project flow and development plan.
- Gather client feedback and suggestions.
- Confirm the regular meeting schedule.
Key Presentationsβ
- Tech Stack: React+Vite (frontend), Express/Node.js (backend), TypeScript, Docker, Render (backend hosting), Docusaurus (docs), GitHub Actions (CI/CD). Database TBD (Supabase/Azure).
- Development Workflow: GitHub Flow (shortβlived branches β PR β main) β Note: this was later refined in our internal meeting on the 5th.
- Scrum Cadence: We proposed biβweekly internal standups + a weekly client sync.
Client Feedback & Suggestionsβ
- The client approved the proposed tech stack, noting that TypeScript and Docker are good choices for a teamβbased project.
- Suggestion: Prioritise the learner experience early β the Browse and Dashboard pages should feel smooth and responsive.
- Suggestion: For the reputation system, consider tying it to quality rather than just volume (e.g. accepted corrections should count more than many rejected suggestions). This aligns with our design thinking.
- Confirmation: The client is happy with the Wednesday 1:30 PM timeslot for weekly syncs.
Decisions Madeβ
- Regular client meetings will take place every Wednesday at 1:30 PM.
- We will share a Figma prototype (or wireframes) with the client before the next meeting for early feedback.
Action Itemsβ
| Action | Owner | Deadline |
|---|---|---|
| Share first UI wireframes/mockups | Team (design lead) | Before next client meeting |
| Finalise database selection (Supabase/Azure) | Team | End of Week 1 |
| Update project plan with client feedback | Nthabiseng | 6 August |
Meeting concluded. Next internal sync: 5 August.