docs: PostgreSQL landing page (Proxy / Encryption SDK / Drizzle / Supabase / EQL hub)

[coderdan]

Summary

The old docs had databases/postgres — a hub page that introduced the four ways to use CipherStash with Postgres (Proxy, Encryption SDK, Drizzle, Supabase) plus EQL underneath. The new docs have all the leaf pages but no umbrella, which hurts discoverability for users who arrive thinking "I have a Postgres database, what are my options?"

Current state

Today users land on one of:

• cipherstash/proxy/index.mdx — proxy-only context
• cipherstash/encryption/index.mdx — SDK-only context
• cipherstash/encryption/drizzle.mdx
• cipherstash/encryption/supabase.mdx

… with no single page that frames the trade-offs across them ("when do I want Proxy vs the SDK?", "do I need EQL if I'm using the SDK?").

Suggested page

content/stack/cipherstash/postgres.mdx (or as the Postgres tab landing in the IA) covering:

• One-paragraph framing: "you have a Postgres database; here's how CipherStash plugs in"

• Decision matrix:

  If you want…	Use
  Zero application code changes, transparent encryption at the wire	Proxy
  Application-level control, ORM-agnostic	Encryption SDK
  First-class Drizzle integration	Drizzle adapter
  First-class Supabase integration	Supabase wrapper

• One-line "what is EQL" with a link, and where it fits under each option

• Cross-link to docs: add CREATE INDEX guide for encrypted columns (self-hosted vs Supabase paths differ) #4 (CREATE INDEX guide) for index setup

Reference material

Old page in cipherstash-js-suite git history at apps/docs/src/app/(articles)/databases/postgres/page.md (commit 1c3d40ed^).

A parallel dynamodb.mdx hub already exists at content/stack/cipherstash/encryption/dynamodb.mdx so the precedent is set.

[calvinbrewer]

Addressed. Created content/stack/cipherstash/postgres.mdx as the missing umbrella, mirroring the existing cipherstash/supabase.mdx top-level hub pattern.

Covers:

• One-paragraph framing: "you have a Postgres database; here's how CipherStash plugs in"
• Decision matrix mapping intent → product (Proxy / Encryption SDK / Drizzle / Supabase)
• One-line "what is EQL" with link to reference/eql-guide
• Cross-link to the new indexes page (docs: add CREATE INDEX guide for encrypted columns (self-hosted vs Supabase paths differ) #4) for index setup
• A "How these compose" section showing that Proxy + SDK can coexist (different services in the same stack), and that Drizzle/Supabase wrappers sit on top of the SDK

IA: added a new ---Postgres--- group at the top of cipherstash/meta.json containing postgres and supabase together, before ---Encryption---. Groups the database-level entry points visually in the sidebar.

Pending review on a working branch.