Files
supabase/apps/docs/data/content-listings/database.data.ts
T
74c116de74 docs: add Multigres Public Alpha documentation — MERGE ON SEP 14, 2026 (#49020)
## I have read the CONTRIBUTING.md file.

YES

## What kind of change does this PR introduce?

This PR adds Public Alpha documentation for Multigres, Supabase's
multi-node Postgres high-availability integration. It introduces an
overview guide, a compatibility stub, Database sidebar navigation, a
Features table row, and a "What you get" card grid. ContentListings
items can now omit `href` so those cards are not forced to be links.

Linear: MUL-452.

~~🚨 **DO NOT MERGE UNTIL THE PUBLIC ALPHA GOES LIVE** 🚨~~ [@jhydra12
OK'ed merging, FYI]


## What is the current behavior?

- Linear item: Documentation for Multigres
- Production has no Multigres guides.
`https://supabase.com/docs/guides/database/multigres` and
`https://supabase.com/docs/guides/database/multigres/compatibility`
return 404
- The Database sidebar has no Multigres section
- The Features status table does not list Multigres
- ContentListings items required a link (`href` was mandatory)

## What is the new behavior?

- Overview guide at `/docs/guides/database/multigres` covering alpha
status, eligibility, enablement, and what is not included
- Compatibility stub at `/docs/guides/database/multigres/compatibility`
- Database sidebar: Multigres → Overview, Compatibility (after OrioleDB)
- Features table: Database / Multigres / `public alpha`
- "What you get" renders as three non-link ContentListings cards
- `href` is optional on ContentListings items; markdown export renders
unlinked entries when it is omitted

## Additional context

- Worktree:
~/GitHub/supabase/supabase-worktrees/nikrichers/mul-452-documentation-for-multigres-ready
- Branch commits: Initial Multigres docs draft; Edits (cards, copy, MDX
comments); merge master; spelling allow-list for Multigres, Vitess, and
sharding

- Verification:

| Check                                   | Result          |
| --------------------------------------- | --------------- |
| Preview overview                        | 200             |
| Preview compatibility                   | 200             |
| Production overview                     | 404 (expected)  |
| Production compatibility                | 404 (expected)  |
| `supa-mdx-lint` on changed MDX          | pass            |
| `vitest` `lib/content-listings.test.ts` | pass (21 tests) |

### Proof: Multigres docs pages render, including non-link What you get
cards

**Verified:** production 404 · Vercel docs preview 200

#### Overview [(PR
preview)](https://docs-git-nikrichers-mul-452-documentation-for-m-6f8a59-supabase.vercel.app/docs/guides/database/multigres)

<img width="1388" height="2272" alt="image"
src="https://github.com/user-attachments/assets/2780f728-07c0-4320-9826-8f6e68df21e6"
/>

#### Compatibility [(PR
preview)](https://docs-git-nikrichers-mul-452-documentation-for-m-6f8a59-supabase.vercel.app/docs/guides/database/multigres/compatibility)

<img width="1388" height="852" alt="image"
src="https://github.com/user-attachments/assets/1f8f7181-5b7d-4d01-b376-a2eac923626b"
/>

### Test plan

- [ ] [Production
overview](https://supabase.com/docs/guides/database/multigres) (404) vs
[preview
overview](https://docs-git-nikrichers-mul-452-documentation-for-m-6f8a59-supabase.vercel.app/docs/guides/database/multigres)
- [ ] [Production
compatibility](https://supabase.com/docs/guides/database/multigres/compatibility)
(404) vs [preview
compatibility](https://docs-git-nikrichers-mul-452-documentation-for-m-6f8a59-supabase.vercel.app/docs/guides/database/multigres/compatibility)
- [ ] Database sidebar shows Multigres → Overview and Compatibility
after OrioleDB
- [ ] Overview shows Public Alpha caution, three What you get cards (not
links), eligibility, and one-way-migration caution
- [ ] Compatibility page is a placeholder that links back to the
overview
- [ ] Features table lists Database / Multigres / `public alpha`
- [ ] `supa-mdx-lint` on
`apps/docs/content/guides/database/multigres.mdx`,
`apps/docs/content/guides/database/multigres/compatibility.mdx`, and
`apps/docs/content/guides/getting-started/features.mdx`


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **New Features**
* Added Multigres documentation covering availability, setup,
compatibility, limitations, migration behavior, and external resources.
  * Added Multigres to database navigation and feature-status listings.
* Added an overview of Multigres benefits, including automatic failover,
unchanged connection strings, and consensus-backed write durability.

* **Improvements**
* Content listings now support informational items without links across
layouts.
* Improved listing rendering and click tracking for linked and
non-linked items.

* **Documentation**
* Added spelling support for Multigres, Vitess, and sharding
terminology.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: Nik Richers <nik@validmind.ai>
Co-authored-by: Cursor Agent <cursoragent@cursor.com>
2026-09-15 09:48:39 +10:00

121 lines
4.2 KiB
TypeScript

import type { ContentListingGroup } from '~/lib/content-listings.schema'
export const databaseGetStarted: ContentListingGroup = {
id: 'database-get-started',
heading: 'Get started',
description: "If you're new to the database section, these are the pages to read first:",
type: 'grid',
columns: 2,
items: [
{
title: 'Connect to your database',
href: '/guides/database/connecting-to-postgres',
description:
'Connection strings, the Supavisor connection pooler, and when to use direct, transaction, or session mode.',
},
{
title: 'Tables and data',
href: '/guides/database/tables',
description: 'Create tables and relationships, and edit rows from the Dashboard.',
},
{
title: 'Import data',
href: '/guides/database/import-data',
description: 'Load existing data from CSV files, `pg_dump`, or another Postgres database.',
},
{
title: 'Secure your data',
href: '/guides/database/secure-data',
description:
'Row Level Security (RLS) is how Supabase makes the database safe to query directly from the client. Read this before exposing any table to your app.',
},
{
title: 'Extensions',
href: '/guides/database/extensions',
description:
'Add Postgres extensions from the Dashboard, including `pgvector` for embeddings, `PostGIS` for geospatial data, and `pg_cron` for scheduled jobs.',
},
{
title: 'Run SQL commands',
href: 'https://supabase.com/dashboard/project/_/sql',
description: "Use the Dashboard's SQL Editor for ad-hoc queries and saved snippets.",
},
],
}
export const databaseNextSteps: ContentListingGroup = {
id: 'database-next-steps',
heading: 'Next steps',
description:
"Once you've covered the basics, these guides help with other use cases and features:",
type: 'grid',
items: [
{
title: 'Database functions',
href: '/guides/database/functions',
description: 'Run logic inside the database in response to inserts, updates, or deletes.',
},
{
title: 'Triggers',
href: '/guides/database/postgres/triggers',
description: 'Run logic inside the database in response to inserts, updates, or deletes.',
},
{
title: 'Database webhooks',
href: '/guides/database/webhooks',
description: 'Send row changes to an external HTTP endpoint.',
},
{
title: 'Replication and read replicas',
href: '/guides/database/replication',
description: 'Stream changes to other systems or read from a geographically closer replica.',
},
{
title: 'Backups',
href: '/guides/platform/backups',
description:
'Daily backups on every project, with point-in-time recovery on paid plans. Backups cover the database itself; objects stored through the Storage API are not included.',
},
{
title: 'Query performance and optimization',
href: '/guides/database/query-optimization',
description: 'Indexes, the query planner, and tools for finding slow queries.',
},
{
title: 'Roles and permissions',
href: '/guides/database/postgres/roles',
description: 'The Postgres roles Supabase ships with and how to add your own.',
},
{
title: 'Deployment & Branching',
href: '/guides/deployment',
description:
'Preview environments, branching, migrations, and production readiness for your database changes.',
},
],
}
export const databaseMultigresWhatYouGet: ContentListingGroup = {
id: 'database-multigres-what-you-get',
heading: 'What you get',
description:
'When you enable Multigres on a project, your database runs as a small cluster instead of a single instance:',
type: 'grid',
items: [
{
title: 'Automatic failover',
description:
'If a node fails, another in the cluster is promoted within seconds, without you having to intervene.',
},
{
title: 'No connection changes',
description:
'Use the same connection string. Coordination is transparent to your application.',
},
{
title: 'Consensus-backed durability',
description: 'Writes are acknowledged only after the cluster agrees they are durable.',
},
],
}