Caawi is a pioneering digital mentorship platform created by Somalis in Tech, designed to foster connections between mentors and mentees within the Somali tech community. It aims to support professional and personal development through meaningful interactions, making mentorship more accessible, intuitive, and culturally relevant for our community members worldwide.

• Personalised Mentorship: Matches mentors and mentees based on professional and personal development goals.
• Cultural Resonance: Tailored for the Somali community, ensuring relevance and understanding.
• Global Network: Offers access to a diverse, worldwide network of professionals and peers.

The platform is built with Next.js, Prisma, and Tailwind CSS, featuring robust authentication via Next Auth to ensure secure user connections.

• Node.js
• pnpm
• Docker (if setting up a local PostgreSQL database)
• Doppler CLI (for managing environment variables)

After executing doppler setup, your environment is set to the development configuration, which usually connects to a remote database. To run the application with a local database:

1. Adjust DATABASE_URL for Local Development: Manually change the DATABASE_URL in your Doppler configuration to point to your local database (e.g., postgres://postgres:password@localhost:5432/postgres).

2. Local Database Configuration (Optional): If you prefer using a local database and have updated your DATABASE_URL accordingly, use Docker to start your PostgreSQL database. Ensure Docker is installed, then run docker-compose up.

3. Database Migrations: Before applying migrations, confirm they are intended for your local setup to avoid affecting production data.

   pnpm migrate

4. Database Seeding: To seed the database with initial data:

   pnpm seed

5. Start the Application: Finally, launch the application:

   pnpm dev

• pnpm build: Builds the application for production.
• pnpm start: Runs the built application in production mode.
• pnpm lint: Enforces code quality.
• pnpm check-types: Ensures TypeScript correctness.

Our project adheres to a structured commit message format to ensure clarity and ease of tracking changes. This approach aids in maintaining a detailed and understandable history.

• Structure: Commits should begin with a type, optionally followed by a (scope), and a succinct subject:
  • type identifies the nature of the change (e.g., feat, fix, docs).
  • (scope) is optional and indicates the specific area affected.
  • subject offers a brief description of the changes.
• Details: The body should thoroughly explain the change, its motivation, and how it differs from previous behavior.
• Tracking: Include a JIRA task ID in the format CAAWI-XXX anywhere within the commit message for project tracking purposes.

feat(database): optimize query performance Enhances database efficiency by adding indexes to heavily queried columns, significantly cutting down response times. CAAWI-123

We welcome contributions! For guidelines on how to get involved, please consult our contributing guide.

For support, reach out to us at team@somalisintech.com or visit our website.