> For the complete documentation index, see [llms.txt](https://hossams-organization-1.gitbook.io/edulink/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hossams-organization-1.gitbook.io/edulink/chapter-2-data-source-and-tools-and-technologies-we-used.md).

# Chapter 2: Data Source and Tools & Technologies We Used

### Data Source <a href="#data-source" id="data-source"></a>

#### **Data Sources Used in EduLink**

1. **Cloud Firestore**
   * Used as the primary NoSQL database to store structured data such as:
     * Users (students and professors)
     * Courses
     * Assignments
     * Q\&A forum posts
     * Messages (chat)
   * Supports real-time data sync across devices.
2. **Supabase Storage**
   * Used to store and retrieve large files such as:
     * PDFs
     * Video lectures
     * Images (e.g., profile pictures or course materials)
3. **Local Storage (SharedPreferences)**&#x20;
   * Used for temporary or cached data like:
     * Theme preferences (Dark/Light mode)
     * User login status/session
     * Recent activities or local app settings

***

### Technologies Used <a href="#technologies-used" id="technologies-used"></a>

The following tools and technologies were utilized throughout this project:

* VS Code:
  * used as our main code editor for building and debugging the app efficiently
* Figma:
  * used to design the user interface and prototype the app layout before development
* GitHub:
  * used to collaborate as a team, manage version control, and store our project code
* Firebase:
  * handled user authentication, real-time database,  and push notifications
* Supabase:
  * for cloud storage , flexible database management and real-time syncing features
* Trello:
  * helped us manage tasks, track progress, and organize our workflow as a team
* Canva:
  * Used during pre - development and to design simple visuals like the logo, mockups, and some presentation graphics during the early stages

<br>