Files
vercel__workflow/docs/app/[lang]/worlds/page.tsx
christopherkindl 3c7875ad73 [docs] upgrade @vercel/geistdocs to 1.19.0 (#3170)
* chore: upgrade @vercel/geistdocs to 1.17.1

Picks up the new footer (Footer no longer takes a config prop), the
heading font-weight change to 450, and the tightened navbar OSS-menu
marks. Also switches the site's own navbar logo from the vendored
geistcn LogoWorkflow fallback to the package's LogoWorkflowSdk, using
its new tuned default height instead of a hardcoded 15.

Fixes a resulting regression: navbarOssProducts entries lacked an `id`,
so resolveOssProducts' `product.id !== activeProduct` filter evaluated
to `undefined !== undefined` (false) for every entry and emptied the
OSS flyout. Added stable `id`/`label` values to each entry.

* refactor: use default navbarOssProducts list instead of a custom override

The manual navbarOssProducts array (with local logo imports/heights) is
no longer needed now that the package's DEFAULT_OSS_PRODUCTS list
already includes all these SDKs with proper id/label/section values.
navbarActiveProduct: 'workflow-sdk' now handles self-exclusion instead.

* fix: use bg-background-200 for docs surfaces to match the template

The docs, cookbook, and v5 route layouts plus the shared DocsLayout
container hardcoded bg-background-100 (pure white), so /docs/* pages
rendered on a lighter surface than the rest of the site. Switch them to
bg-background-200, matching the geistdocs template's page background.

* style: adopt package text-heading-* utilities for homepage headings

The marketing homepage headings hardcoded font-semibold (weight 600)
plus manual responsive sizes/tracking, so they rendered heavier than
the docs headings that now use Geist's 450 heading weight. Swap each
display heading to the package's text-heading-* utilities, which bundle
the 450 weight, line-height, and tracking, mapped across breakpoints to
the nearest design-system size. Inline label/emphasis spans keep their
own weight.

* style: adopt package text-heading-* utilities for worlds headings

Extends the homepage heading change to the /worlds section: the world
listing, detail, compare, and building-a-world pages plus their
components hardcoded font-semibold display headings. Swap each to the
package's text-heading-* utilities (450 weight + line-height +
tracking), mapped across breakpoints to the nearest design-system size.
Mono stat numbers, per-benchmark item labels, and the dialog title keep
their own weight.

* style: remove the bordered grid framing from the homepage

The homepage sections were wrapped in a grid divide-y border-y sm:border-x
container, drawing side borders and divider lines between every section.
Drop that framing so the sections flow with whitespace separation.

* style: remove vertical column dividers from homepage sections

Drop the divide-x column dividers still drawn inside the use-cases
(3-col), feature-grid (2-col), and templates sections, so no vertical
lines remain after the section-grid removal. Section padding keeps the
columns visually separated.

* style: make the homepage "Get started" CTA button rounded-full

* style: use text-heading-* for the feature-grid paragraph text

The two 2-col feature blurbs ("Deep integration with AI SDK.",
"Durable agents by default.") hardcoded their size/leading/tracking
plus font-medium/font-semibold weights. Those manual sizes already
equal text-heading-20/24, so swap to text-heading-20 lg:text-heading-24
— same sizes, but the Geist 450 heading weight (lead drops 600 -> 500
via the utility's [&>strong] rule). The lead stays gray-1000 for
emphasis; body stays gray-900.

* style: fade out the run-anywhere provider logos at the left/right edges

Add linear-gradient masks to the flanking cloud-provider logo groups in
the "Run anywhere, no lock-in" viz so they fade to transparent toward
the outer edges, leaving the centered code block untouched.

* style: widen the right-edge fade on the Vercel dashboard viz

The "Workflow SDK on Vercel" dashboard is offset off the right edge, so
the existing to_left black_10% mask fell off-screen and the visible
right edge hard-clipped. Widen it to black_40% so the dashboard fades
out gradually at the visible right edge.

* style: add spacing between the Vercel, use-cases, and templates sections

Wrap the UseCases and Templates sections with a top margin so there's
clear separation between "Workflow SDK on Vercel", "Build anything with
AI Agents", and "Get started" now that the section dividers are gone.

* style: widen the homepage layout from 1080px to 1200px

* style: align use-cases code block and templates cards with the Vercel section

Switch the "Build anything with" and "Get started" sections from
grid-cols-3 / [1fr_2fr] to [1fr_1.5fr], matching the "Workflow SDK on
Vercel" section above so their code block and cards share the same
right-hand column. The wider text column also lets "Build anything with"
sit on one line. Normalize both to outer padding + column gap so the
code block and cards line up exactly.

* style: extend use-cases/templates content to the right layout edge

Drop the right padding at md+ (md:pr-0) so the code block and template
cards reach the same right edge as the "Workflow SDK on Vercel"
dashboard above, which bleeds to the container edge. Mobile keeps its
padding.

* style: remove the divider between the two feature cards

Drop divide-y/lg:divide-y-0 from the feature grid so no border shows
between "Deep integration with AI SDK" and "Durable agents by default".

* refactor: position homepage sections on a shared 12-col grid

Replace the ad-hoc [1fr_1.5fr] + md:pr-0 + lg:pl-* positioning on the
Vercel, use-cases, and templates sections with a shared grid-cols-12
layout (text col-span-5, visual col-span-7), matching the vercel.com
marketing grid convention. The Vercel dashboard becomes a proper grid
cell instead of an absolutely-offset right-bleed, so all three
sections' visuals align by the grid columns with no magic values.

* style: align homepage width with the navbar content

Widen the homepage container from max-w-[1200px] to the site's
max-w-[1448px] (matching the navbar/footer) and reduce the section
gutters from sm:px-12 to sm:px-6, so section content lines up with the
navbar's content edges (right edge flush at the same column as the
navbar and footer). Also convert the "Reliability-as-code" section to
the shared grid-cols-12 layout (col-span-5 text / col-span-7 code
example), replacing its lg:grid-cols-[330px_1fr] magic values.

* refactor: handle homepage horizontal padding at the root container

Move the mobile/desktop gutter (px-4 sm:px-6) onto the homepage root
container and remove the horizontal padding from every section
component. Section content still aligns with the navbar/footer content
edges, but the gutter is now defined once instead of repeated per
section. Inner-element padding (tab buttons, visual internals) is
unchanged.

* style: left-align content sections on mobile + fix run-anywhere/o11y viz

- Left-align the centered content sections on mobile only (FeatureCardWide,
  TweetWall heading, Frameworks, Run-anywhere heading/buttons), restoring
  their centered layout at sm and up.
- Make the "Inspect every run" timeline span edge-to-edge by shifting its
  gantt from a 14-col grid (content in cols 2-13) to a flush 12-col grid.
- Constrain the run-anywhere viz cluster to the code block width so the
  provider cards (AWS/Docker/etc.) overlap behind the code block again.

* style: anchor run-anywhere provider cards to overlap the code block

Position the flanking provider-card groups relative to the centered
code block (right/left calc(50%+140px)) instead of the section edges,
so the cards sit behind and overlap the code block regardless of the
section width.

* style: make the reliability-as-code example fill its column to the right edge

Drop max-w-3xl mx-auto from the workflow/non-workflow code examples so
they fill the col-span-7 cell, aligning the code block's right edge with
the layout's right content edge (matching the tabs and other sections).

* style: split feature-card copy into a title + description

Break the AI SDK / durable-agents feature blurbs into a heading and a
separate muted description with a gap (matching the other sections)
instead of one inline paragraph, and drop the trailing periods from the
feature titles so they read as headings.

* update

* update

* style: give the tweet cards a bg-background-100 surface

* fix(swc-playground): pin monaco-editor to 0.55.1

The lockfile refresh resolved the unpinned `monaco-editor: "latest"` from
0.55.1 to 0.56.0, breaking the workflow-swc-playground Turbopack build.

0.56.0 rewrote its exports map to reroot subpaths under `esm/vs/`
("./*": "./esm/vs/*.js"). monaco-vim@0.4.4 deep-imports
`monaco-editor/esm/vs/editor/editor.api` and
`.../common/commands/shiftCommand`, which now map to
`esm/vs/esm/vs/...` — a path that does not exist. Under 0.55.1
("./*": "./*") both specifiers resolve to real files.

monaco-vim 0.4.4 is the latest published release, so pinning
monaco-editor is the only available fix.

* update

---------

Signed-off-by: christopherkindl <53372002+christopherkindl@users.noreply.github.com>
2026-07-31 10:21:15 -07:00

180 lines
7.1 KiB
TypeScript

import { Button } from '@vercel/geistdocs/components/button';
import type { Metadata } from 'next';
import Link from 'next/link';
import { PlainGlobe } from '@/app/[lang]/(home)/components/vercel-com-visuals/plain-globe';
import { Badge } from '@/components/ui/badge';
import { WorldsFilteredGrid } from '@/components/worlds/WorldsFilteredGrid';
import { getWorldsData } from '@/lib/worlds-data';
export const metadata: Metadata = {
title: 'Worlds | Workflow SDK',
description:
'The World abstraction allows workflows to run anywhere — locally, on Vercel, or on any cloud. The runtime, queues, and persistence are modular and entirely swappable.',
openGraph: {
images: ['/og/worlds'],
},
};
export default async function WorldsPage() {
const data = await getWorldsData();
// Sort worlds: official first, then community, alphabetically within each group
const sortedWorlds = Object.entries(data.worlds).sort(([, a], [, b]) => {
if (a.type === 'official' && b.type !== 'official') return -1;
if (a.type !== 'official' && b.type === 'official') return 1;
return a.name.localeCompare(b.name);
});
return (
<div className="[&_h1]:tracking-tighter [&_h2]:tracking-tighter [&_h3]:tracking-tighter sm:mt-24">
<div className="mx-auto w-full max-w-[1080px]">
{/* Hero Section */}
<section className="relative px-4 overflow-hidden text-center h-[340px]">
{/* Globe backdrop */}
<div className="absolute inset-0 flex items-center justify-center pointer-events-none">
<div className="w-[85%] translate-y-[20%]">
<PlainGlobe />
</div>
</div>
{/* Content */}
<div className="relative z-10 mt-32 sm:mt-28 mx-auto w-full max-w-3xl space-y-3 sm:space-y-5">
<h1 className="text-center text-balance text-heading-40 sm:text-heading-48 xl:text-heading-64">
Worlds
</h1>
<p className="text-balance text-muted-foreground sm:text-xl leading-relaxed">
The World abstraction allows workflows to run anywhere — locally,
on Vercel, or on any cloud. The runtime, queues, and persistence
are modular and entirely swappable.
</p>
</div>
</section>
{/* Filters + World Cards */}
<WorldsFilteredGrid worlds={sortedWorlds} />
{/* Last Updated */}
<div className="px-4 pb-8 text-center text-xs text-muted-foreground">
Last updated: {new Date(data.lastUpdated).toLocaleString()}
{data.commit && (
<>
{' · '}
Commit:{' '}
<a
href={`https://github.com/vercel/workflow/commit/${data.commit}`}
target="_blank"
rel="noopener noreferrer"
className="font-mono hover:underline"
>
{data.commit.slice(0, 7)}
</a>
</>
)}
</div>
{/* Provider Benchmarks Section */}
<section className="border-t px-4 py-12 sm:py-16">
<div className="flex flex-col lg:flex-row gap-8 items-start justify-between">
{/* Left: Text content */}
<div className="space-y-4 mt-4 max-w-md">
<div className="flex items-center gap-2.5">
<h2 className="text-heading-24 sm:text-heading-32">
Provider Benchmarks
</h2>
<Badge variant="outline" className="text-sm">
Coming soon
</Badge>
</div>
<p className="text-muted-foreground max-w-md">
See how workflows compare across the different worlds deployed
on different providers. Lower execution time means faster
workflows.
</p>
{/* <Button variant="secondary" size="lg" className="mt-2" disabled>
Coming Soon
</Button> */}
</div>
{/* Right: Benchmark preview visualization */}
<div className="w-full lg:max-w-lg min-w-0 space-y-3">
{/* Header row */}
<div className="flex items-center gap-3 text-xs text-muted-foreground uppercase tracking-wider">
<div className="w-16" />
<div className="flex-1" />
</div>
{/* Benchmark bars */}
{[
{
name: 'Local',
time: 10.76,
color: 'bg-green-700 dark:bg-green-600',
},
{ name: 'Vercel', time: 19.37, color: 'bg-blue-700' },
{ name: 'AWS', time: 25.82, color: 'bg-blue-700' },
{ name: 'GCP', time: 25.82, color: 'bg-blue-700' },
].map((provider) => {
const maxTime = 25.82;
const width = (provider.time / maxTime) * 100;
return (
<div
key={provider.name}
className="flex items-center gap-4 w-full"
>
<div className="w-14 text-sm truncate text-right text-muted-foreground">
{provider.name}
</div>
<div className="w-full h-8 bg-gray-100 rounded-md overflow-hidden">
<div
className={`h-full rounded-md transition-all ${provider.color}`}
style={{ width: `${width}%` }}
/>
</div>
<div className="w-13 shrink-0 text-right font-mono text-gray-900 text-sm">
{provider.time.toFixed(2)}s
</div>
</div>
);
})}
<p className="text-xs text-gray-900 text-right pt-1">
For illustration purposes only
</p>
</div>
</div>
</section>
{/* Learn More Section */}
<section className="border-t px-4 py-8 sm:pt-24 sm:pb-16 sm:px-12">
<div className="max-w-2xl mx-auto text-center space-y-4">
<h2 className="text-heading-32 sm:text-heading-40">
Learn more about worlds
</h2>
<p className="text-muted-foreground">
To learn more about how worlds work or to create your own, check
the docs. You can also build a custom world to connect workflows
to any storage or queuing backend.
</p>
<div className="flex justify-center gap-3 mt-8">
<Button asChild size="lg">
<Link href="/worlds/building-a-world">
World Interface Docs
</Link>
</Button>
<Button asChild variant="outline" size="lg">
<a
href="https://github.com/vercel/workflow/blob/main/worlds-manifest.json"
target="_blank"
rel="noopener noreferrer"
>
Submit Your World
</a>
</Button>
</div>
</div>
</section>
</div>
</div>
);
}