Meeting 1 – Internal Kickoff

Date: 25 July 2026
Time: (approx. 2 hours)
Platform: Whatsapp Group Call
Attendees: Whole team (Nthabiseng, Blessing, Somnotho, Benjamin, Wilson, Safiyyah)
Minutes taker: Benjamin

This document was reviewed and formatted with the assistance of AI.

---

Agenda

1. Rank project preferences.
2. Finalise tech stack and core architecture.
3. Decide on Git methodology.
4. Agree on tooling (code quality, UI design, deployment, documentation).
5. Outline backend folder structure.
6. Assign initial action items.

---

Key Decisions

Decision	Outcome
Project ranking	Finalised our top 5 preferences; Nthabiseng created a Trello board for tracking. Blessing volunteered to maintain Trello documentation.
Frontend framework	React + Vite (Blessing has experience and will set up the folder structure).
Backend framework	Express.js / Node.js (Benjamin will set this up).
Language	TypeScript (Somnotho convinced the team – static typing helps catch errors early).
Git methodology	GitHub Flow (short‑lived feature branches → PR into main → delete branch). [Later updated in Meeting 2]
Backend deployment	Render (decided).
Frontend deployment	Undecided – evaluating Vercel, Netlify, Cloudflare Pages (Somnotho has Vercel experience).
Containers	Docker – Somnotho will add it to ensure version compatibility.
Database	To be decided once we're assigned the project (e.g. Azure, Supabase, or similar).
Code quality	Under discussion – Husky + lint‑staged (Benjamin) vs AI agents (Somnotho). We will ask tutors for a recommendation.
UI design / wireframes	Debated: Figma (free tier limit: 3 files – workaround: use multiple pages per file) vs alternatives like Excalidraw, Penpot, or Whimsical. We will decide as a team.
Documentation	Docusaurus – Benjamin will set it up. Every feature must include a docs paragraph in the docs/ folder, deployed to GitHub Pages.
CI/CD	GitHub Actions – Wilson will set up the workflow file.
Testing	Whoever writes the code must write the test. (Tools to be decided later).
Development methodology	Scrum – we will mention this in our README.
Naming convention	camelCase (e.g. userService, not user_service).

---

Backend Folder Structure (Accepted)

For each user story, you will:

1. Create a TypeScript file in the models/ folder – this uses the connection pool from db.ts to write SQL queries.
2. Create a TypeScript file in the controllers/ folder – imports from the models file.
3. Create a TypeScript file in the routes/ folder – specifies endpoints and imports from the controllers file.
4. Register the route file in server.ts.

The frontend folder structure will follow React + Vite conventions (Blessing to define).

---

Action Items

Action	Owner	Status
Create & share Trello board	Nthabiseng	✅ Done
Join Trello board	Everyone	🔲 Pending
Join GitHub repository (Benjamin created it)	Everyone	🔲 Pending
Decide on frontend folder structure (React+Vite)	Blessing	🔲 Pending
Add this to‑do list to the Trello board	Blessing	🔲 Pending
Research and agree on a code quality tool	Everyone	🔲 Pending
Add Docker to the project	Somnotho	🔲 Pending
Decide on frontend deployment platform	Everyone	🔲 Pending
Decide on UI design tool (Figma vs alternative)	Everyone	🔲 Pending
Set up Docusaurus	Benjamin	🔲 Pending
Set up GitHub Actions workflow file	Wilson	🔲 Pending

---

Next meeting: Client Meeting on 4 August, followed by Internal Setup on 5 August.