116d41a284
* feat: add changelog feature and update site navigation - Introduced a new Changelog page with pagination and detailed entry views. - Added components for displaying changelog entries, pagination, and entry details. - Updated site navigation to include a link to the new Changelog page. - Enhanced localization for changelog-related texts in marketing.json. * refactor: enhance Changelog page layout and entry display - Increased the number of changelog entries displayed per page from 2 to 20 for better visibility. - Improved the layout of the Changelog page by adjusting the container styles and removing unnecessary divs. - Updated the ChangelogEntry component to enhance the visual presentation of entries, including a new date badge with an icon. - Refined the CSS styles for Markdoc headings to improve typography and spacing. * refactor: enhance Changelog page functionality and layout - Increased the number of changelog entries displayed per page from 20 to 50 for improved user experience. - Updated ChangelogEntry component to make the highlight prop optional and refined the layout for better visual clarity. - Adjusted styles in ChangelogHeader and ChangelogPagination components for a more cohesive design. - Removed unnecessary order fields from changelog markdown files to streamline content management. * feat: enhance Changelog entry navigation and data loading - Refactored ChangelogEntry page to load previous and next entries for improved navigation. - Introduced ChangelogNavigation component to facilitate navigation between changelog entries. - Updated ChangelogDetail component to display navigation links and entry details. - Enhanced data fetching logic to retrieve all changelog entries alongside the current entry. - Added localization keys for navigation text in marketing.json. * Update package dependencies and enhance documentation layout - Upgraded various packages including @turbo/gen and turbo to version 2.6.0, and react-hook-form to version 7.66.0. - Updated lucide-react to version 0.552.0 across multiple packages. - Refactored documentation layout components for improved styling and structure. - Removed deprecated loading components and adjusted navigation elements for better user experience. - Added placeholder notes in changelog entries for clarity.
44 lines
1.4 KiB
Plaintext
44 lines
1.4 KiB
Plaintext
---
|
|
title: "Database Overview"
|
|
description: "Understanding the database schema and table structure in your application."
|
|
publishedAt: 2024-04-11
|
|
order: 0
|
|
status: "published"
|
|
---
|
|
|
|
> **Note:** This is mock/placeholder content for demonstration purposes.
|
|
|
|
The database schema is designed with a multi-tenant architecture that supports both personal and team accounts.
|
|
|
|
## Core Tables
|
|
|
|
### Users Table
|
|
The `users` table stores user authentication data and is managed by Supabase Auth:
|
|
- `id` - Unique user identifier
|
|
- `email` - User's email address
|
|
- `created_at` - Account creation timestamp
|
|
|
|
### Accounts Table
|
|
The `accounts` table represents both personal and team accounts:
|
|
- `id` - Unique account identifier
|
|
- `name` - Account display name
|
|
- `slug` - URL-friendly identifier
|
|
- `is_personal_account` - Boolean flag for personal vs team accounts
|
|
|
|
### Projects Table
|
|
Store your application's project data:
|
|
- `id` - Unique project identifier
|
|
- `account_id` - Foreign key to accounts table
|
|
- `name` - Project name
|
|
- `description` - Project description
|
|
- `created_at` - Creation timestamp
|
|
|
|
## Relationships
|
|
|
|
All data in the application is tied to accounts through foreign key relationships. This ensures proper data isolation and access control through Row Level Security (RLS).
|
|
|
|
## Next Steps
|
|
|
|
- Learn about [migrations](/docs/database/migrations)
|
|
- Understand [RLS policies](/docs/database/row-level-security)
|