A web app that helps students and small teams organize their projects and manage tasks in one place.
| Member | GitHub |
|---|---|
| Diego Artemio Garcia | @NomadicAlternative |
| Joshua Abinadi Cirilo | @joshuacirilo |
| Nelson Mandella Akpomah | @mandellasly1 |
| Taiye Gabriel Ade-Benson | add username |
Synchronous meeting: Wednesdays at 22:00 UTC.
| Layer | Technology |
|---|---|
| Framework | Next.js (App Router) |
| Language | TypeScript (strict mode) |
| Styling | Tailwind CSS |
| Linting and formatting | ESLint + Prettier |
| Deployment | Vercel |
git clone <repository-url>
cd taskflow
npm install
npm run devOpen http://localhost:3000.
| Command | What it does |
|---|---|
npm run dev |
Development server |
npm run build |
Production build |
npm run lint |
ESLint |
npm run format |
Formats the code with Prettier |
npm run format:check |
Checks formatting without changing files |
main is protected. Nobody pushes to it directly.
- Branch off
mainusingfeature/<short-description>, for examplefeature/user-auth. - Commit your work on that branch.
- Open a pull request into
main. - At least one other team member must review and approve it.
- Merge only after the review.
Keep pull requests small and focused on one thing. A pull request that does five things is a pull request nobody reviews properly.
- Formatting is handled by Prettier. The rules live in
.prettierrcand are shared by the whole team, so nobody argues about style in a review. Runnpm run formatbefore committing. - Correctness is handled by ESLint.
eslint-config-prettieris applied last so the linter does not report formatting issues. - Commits follow Conventional Commits:
feat:,fix:,docs:,chore:,refactor:. - TypeScript runs in strict mode and
anyis not allowed. Types are explicit on component props.
taskflow/
├── app/ Routes, layouts and API route handlers
├── components/ Reusable UI components
├── lib/ Types, data access and shared helpers
└── public/ Static assets
The project specification lives in specs/. Read it before starting a feature — it is the source of truth for what we are building and what is out of scope.
Beyond the weekly meeting, keep the team posted asynchronously in our Microsoft Teams channel: what you finished, what you are working on next, and anything blocking you.