feat(admin): add discovery pages database migration

[DigitalDaDie]

What & Why

What: Add database migration for discovery pages management feature
Why: Enable administrators to dynamically create and manage custom discovery pages with flexible routing

Fixes #300

Pre-PR Checklist

Run these:

• pnpm type-check
• pnpm format:check
• pnpm lint
• pnpm build
• pnpm i18n:check (if applicable)

Type

• 🐛 Bug fix
• ✨ Feature
• 💥 Breaking change
• 📚 Docs
• ♻️ Refactor
• ⚡ Performance

Changes

Database Schema

Created discovery_pages table with:

• id: UUID primary key
• title: Page title
• route: Unique route path (validated format: /[a-z0-9\-/]+)
• description: Page description
• icon_name: Lucide icon name for UI display
• content: JSONB for flexible content structure
• is_active: Boolean for activation control
• display_order: Integer for ordering pages
• timestamps: created_at, updated_at (auto-managed)
• audit: created_by, updated_by (user tracking)

Security (RLS Policies)

• SELECT: All authenticated users can view active pages; admins can view all
• INSERT/UPDATE/DELETE: Only admins can manage pages

Performance

Added indexes on:

• route (unique constraint + index)
• is_active (filtering active pages)
• display_order (ordering)
• created_at DESC (chronological queries)

Automation

• Auto-update updated_at timestamp trigger

Migration File

supabase/migrations/20251018000000_create_discovery_pages_table.sql

[gemini-code-assist]

Summary of Changes

Hello @DigitalDaDie, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a new database migration to establish the foundational data structures for a "discovery pages management" feature. This feature will empower administrators to dynamically create, configure, and manage custom content pages with flexible routing, enhancing the application's ability to present curated information. The migration meticulously defines the discovery_pages table, implements robust security through Row Level Security, optimizes for performance with strategic indexing, and includes automation for data integrity.

Highlights

• New Database Table: A new discovery_pages table has been added to the database schema, designed to store information for dynamically managed discovery pages, including fields for title, route, content (JSONB), and activation status.
• Row Level Security (RLS): Robust RLS policies have been implemented, allowing authenticated users to view active discovery pages, while restricting all CUD (Create, Update, Delete) operations and viewing of inactive pages exclusively to administrators.
• Performance Optimization: Performance enhancements include the addition of indexes on route, is_active, display_order, and created_at columns to optimize common query patterns.
• Automatic Timestamp Updates: An automatic updated_at timestamp trigger has been set up to ensure records accurately reflect their last modification time.
• Route Validation: A valid_route constraint was added to enforce a specific format for page routes, ensuring they start with '/' and contain only lowercase alphanumeric characters and hyphens.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces a well-structured database migration for the new discovery_pages feature. The table schema is comprehensive, and the use of RLS policies for security is excellent. I've identified a couple of areas for improvement, primarily related to database indexing, to enhance performance and clarity. Overall, this is a solid contribution.

[vercel]

@DigitalDaDie is attempting to deploy a commit to the zhang's projects Team on Vercel.

A member of the Team first needs to authorize it.