schema definition (open to revision)

[ucey-star]

Description

I have designed the initial database schema for the ID8 platform. This schema includes tables for Users, User_Profile, Projects, Project_Engagement, Comments, and Project_Attachments, each serving distinct functionalities to handle user accounts, project creation, feedback, and engagement metrics within the platform. The schema is structured to ensure data integrity, maintainability, and scalability, considering anticipated user interactions and platform needs.

Type of Change

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] Tests (adding or updating tests)
• [x] Documentation update

Testing Instructions

Since this change is a documentation update, no direct testing of code or functionality is required. However, the following steps can help verify the schema’s comprehensiveness and accuracy:

• Review for Completeness: Read through the schema file to ensure that all required tables, fields, and relationships are included, as per the platform’s requirements.
• Cross-check with Frontend Requirements: Ensure that the fields and tables align with the anticipated frontend needs, especially for user profiles, projects, and engagement tracking.
• Check for Consistency: Ensure naming conventions and data types are consistent across the schema for maintainability.

Screenshots (if applicable)

No screenshots needed as this is a documentation file.

[lewiskyron]

I will be closing this for now. No need to merge this as I have seen you have already created the tables on supabase. Nice work!