Files
supabase/apps/www/data
2043400335 chore(www): update Declarative Schemas feature entry for pg-delta (#51588)
## Problem

Declarative schemas now runs on `pg-delta`. The Declarative Schemas
entry on the features page still describes the old diff flow: it points
readers to `supabase db diff`, says migrations come from the current
database state, and tells readers to use `supabase db dump` to start
from an existing project.

## Solution

Updates the `declarative-schemas` entry in `apps/www/data/features.tsx`:

- Adds a paragraph after the intro saying the feature now runs on
`pg-delta`, that it is in alpha, and how to opt in.
- Updates key benefit 5 to list grants, partitions, publications, and
domains, and extension-managed objects.
- Replaces the `supabase db diff` integration bullet with `supabase db
schema declarative sync`.
- Updates the intro bullet and three FAQ answers to match the current
docs: how migrations are generated, whether readers write their own
migration files, and how to start from an existing project (`supabase db
schema declarative generate --linked`, with `supabase db dump` kept for
the legacy engine).

The entry's status stays `PRODUCT_STAGES.GA`. The feature is GA and only
the new engine is alpha, and the new paragraph says so.

This should merge with or after the launch blog post (#51571), so the
page doesn't get ahead of the announcement.

## Preview links

| Site | Live | Preview | Search for |
| ---- | ---- | ------- | ---------- |
| WWW |
[/features/declarative-schemas](https://supabase.com/features/declarative-schemas)
| Vercel bot comment on this PR, `/features/declarative-schemas` | `now
runs on` |

## Review instructions

1. Open the live and preview links side by side.
2. Check that the new paragraph appears after the intro and renders its
inline code.
3. Check that key benefit 5 and the CLI integration bullet use the new
text.
4. Check the three updated FAQ answers: how declarative schemas differ
from migrations, whether you write your own migration files, and using
declarative schemas with an existing project.
5. Confirm the status badge still reads General Availability.

## Checklist

Check all before review:

- [ ] I have read
[CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md)
- [ ] If I wrote a new docs topic or edited an existing topic, I used
the `/write-the-docs` or `/edit-the-docs` skill, which applies the docs
[style
guide](https://github.com/supabase/supabase/tree/master/apps/docs/style-guide)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Wendie Cheung <wendie.cheung@supabase.io>
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-authored-by: Wen Bo Xie <wenbox323@gmail.com>
2026-10-14 07:02:22 +11:00
..
2022-10-14 17:12:44 +08:00
2026-07-03 15:00:43 +10:00
2023-12-12 16:41:16 +01:00
2026-07-03 15:00:43 +10:00
2022-10-13 10:42:36 +08:00
2026-06-26 15:47:52 +02:00
2026-10-02 16:14:13 +02:00
2026-07-03 15:00:43 +10:00
2022-12-05 23:52:44 -05:00
2026-09-11 12:17:49 +08:00
2024-12-05 15:05:47 +00:00
2024-12-04 21:42:23 +08:00