Skip to content

feat: refresh the Solutions tab - #5587

Merged
carlotas19 merged 66 commits into
neondatabase:mainfrom
yasell:feat/new-use-case-pages
Aug 21, 2026
Merged

feat: refresh the Solutions tab#5587
carlotas19 merged 66 commits into
neondatabase:mainfrom
yasell:feat/new-use-case-pages

Conversation

@yasell

@yasell yasell commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

This PR rebuilds the Solutions tab end to end.

Adds four use-case pages (full-stack apps, branching workflows, bursty workloads, large databases), rewrites /platforms, and repoints both entry points at them: the Solutions dropdown and the use-cases index.

Two superseded pages are retired with permanent redirects.

This is an integration branch for seven PRs, so the whole tab lands in one merge and no intermediate state ships a nav link to a page that does not exist yet: #5539, #5540, #5546, #5549, #5553, #5554, #5578.

Carlota Soto and others added 30 commits August 14, 2026 06:25
Introduces a long-form use case page for developers building apps on
Neon's backend primitives, with agent-first setup and links to docs
and Build on Neon templates.
Deploys the Databricks-backed positioning from the backend beta launch
post in the AI Gateway section, adds the neon init hero image, and moves
the audience note into an admonition.
Builds out Lakebase Postgres, Object Storage, and Functions with
positioning from the product posts, and embeds the homepage service
videos as autoplay, no-controls animations in each product section.
New long-form use case page covering the branching narrative: one branch per
developer, per pull request, per preview, and per test run, plus restore,
automation, customer case studies, and how the branch model now extends to
Object Storage, auth, and Functions.
Switch quotes to the avatar-based QuoteBlock element used on the AI agents
page, add diagrams to the developer, pull request, and restore workflows,
expand the lakebase architecture explanation with the standard-vs-lakebase
diagram, and move scattered inline links into three admonitions.
Makes the autoscaling argument for variable traffic: provisioning a fixed
instance for peak wastes compute and still degrades under spikes, while
Lakebase Postgres allocates compute as load changes. Sources its numbers
from the compute autoscaling report and quotes customers with spiky
workloads.
Uses the zoomed autoscaling graphic as the hero and regenerates the social
preview from it. The chart legend was pale in the source and inverted to
near-black, so relight it to a readable gray. Simplifies two headings and
adds a highlight block making the 2026 argument against fixed compute.
Keys the flat background out of the hero so only the chart sits on the
page background. Keyed pixels are set to black as well as transparent,
since Next image optimization only preserves PNG alpha under /docs/ and
these pages are always dark.
Argues that conventional Postgres becomes operationally heavy at multi-TB
scale, then shows how Lakebase architecture keeps restore, branching, and
replicas independent of size. Sources recovery stats from the restores
survey and cost framing from the traconiq migration.
Updated subtitle for clarity and impact.
Frames Lakebase as the reason restore, environments, replicas, and API
ops get simpler, then hands off to each practical section in turn.
Replaces the two stats that the figures now carry, and credits the
restores survey as the source below them.
@vercel

vercel Bot commented Aug 19, 2026

Copy link
Copy Markdown

@yasell is attempting to deploy a commit to the neondatabase Team on Vercel.

A member of the Team first needs to authorize it.

@vercel

vercel Bot commented Aug 21, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
neon-next Ready Ready Preview Aug 21, 2026 12:42pm

Request Review

@carlotas19
carlotas19 merged commit 6b47e1f into neondatabase:main Aug 21, 2026
2 of 4 checks passed
@yasell
yasell deleted the feat/new-use-case-pages branch August 21, 2026 15:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants