Project Setup & Infrastructure Decisions
Based on Meeting 2 — Setup & Requirements Engineering
General Decisions
| Category | Decision |
|---|---|
| Application Name | LQ (chosen over Sphinx) |
| Repository | Gitea (created by Wilson) |
| Issue Tracking | Gitea Issues will be used to note bugs and track tasks. |
| Git Methodology | Lightweight GitFlow: feature → develop (via Pull Request) → main (stable releases only). |
| Code Review Preferences | Frontend help: Blessing & Safiyyah Backend help: Benjamin & Somnotho |
Git Access Note: We initially had issues committing. Wilson resolved this by adding everyone as collaborators with write access.
Navigation Structure (Navbar)
The following pages will be available in the main navigation:
- Dashboard – shows courses you’re currently learning and your progress.
- Browse courses – discover and filter available courses.
- Communities – conversation spaces for learners.
- My Profile – user profile and settings.
- Author Workspace – courses you are currently creating.
- Notifications – alerts and updates.
- Moderator Page – only shown for users with moderator permissions.
Setup Responsibilities
Who set up what during the foundation phase:
| Team Member | Setup Responsibility |
|---|---|
| Blessing | Frontend folder structure with React + Vite. |
| Somnotho (Somi) | Backend folder structure (microservices architecture), Docker, Zod, and database schema. |
| Nthabiseng | Added Docusaurus to the repo, set up Supabase Auth and Prisma. |
| Benjamin | Code quality tooling (ESLint, Prettier, Husky, lint-staged), and set up Express.js as the backend framework. |
| Wilson | Set up CI/CD pipeline. |
| Safiyyah | Set up testing tools — Vitest for the frontend and Supertest for the backend. |
This document serves as the single source of truth for our initial tech stack decisions and infrastructure ownership.