blog: replace the launch article's animated scenes with plain prose

The scroll-driven illustration system (factory components, sf-* styles,
the motion dependency) is gone; the opening steps become ordinary
paragraphs and the closing scene is dropped. The meta image returns so
social cards render again; the hero stays as the cover.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0171qibvmqZmkQmQ7rLYFLFf

Author: ankur-arch

apps/blog/content/blog/building-the-stack-for-the-next-million-products/factory/primitives.tsx

@@ -9,29 +9,21 @@ metaDescription: "Prisma is building a software factory: one environment where a
 excerpt: "We are building a software factory: one environment where a builder can describe what they want and an agent can build it, run it, inspect it, fix it, and keep going."
 heroImagePath: "/building-the-stack-for-the-next-million-products/imgs/hero.svg"
 heroImageAlt: "The shortest path from an idea to working software: a request card, a short path through build, deploy and iterate, and a running application showing a usage limit warning."
+metaImagePath: "/building-the-stack-for-the-next-million-products/imgs/meta.png"
 pinned: true
 tags:
   - "announcement"
   - "platform"
   - "ai"
 ---
 
-import { Scrolly, Step } from "./factory/scrolly";
-import { CtaScene } from "./factory/scenes";
-
 **Prisma should give humans and agents the shortest path from an idea to working software.**
 
-<Scrolly>
-  <Step stage="build">
-    Today that path is still broken across code, databases, deployment, logs, previews, and developer tooling. We want those pieces to behave like one system instead of a collection of hand-offs.
-  </Step>
-  <Step stage="deploy">
-    That idea has been taking shape across Prisma for a while. [Prisma ORM](https://www.prisma.io/orm) simplified working with data. [Prisma Postgres](https://www.prisma.io/postgres) made isolated databases available on demand. [Prisma Compute](https://www.prisma.io/compute) gave applications a place to run.
-  </Step>
-  <Step stage="iterate">
-    Together, they let builders and agents move from code changes to a running application without stitching the infrastructure together themselves.
-  </Step>
-</Scrolly>
+Today that path is still broken across code, databases, deployment, logs, previews, and developer tooling. We want those pieces to behave like one system instead of a collection of hand-offs.
+
+That idea has been taking shape across Prisma for a while. [Prisma ORM](https://www.prisma.io/orm) simplified working with data. [Prisma Postgres](https://www.prisma.io/postgres) made isolated databases available on demand. [Prisma Compute](https://www.prisma.io/compute) gave applications a place to run.
+
+Together, they let builders and agents move from code changes to a running application without stitching the infrastructure together themselves.
 
 > The stack should fit inside the conversation.
 
@@ -127,8 +119,6 @@ That is the stack we want to build.
 
 Prisma Compute is the newest step toward that vision. It works with the coding agents you already use, including Claude, Codex, and Composer, and comes with Prisma Postgres and [Object Storage](https://www.prisma.io/docs/storage) so you can give an agent a real project, let it build against real infrastructure, and run what it made.
 
-<CtaScene />
-
 <Button asChild variant="ink" size="2xl">
   <a href="https://console.prisma.io/">Start building in Prisma Console</a>
 </Button>

apps/blog/content/blog/building-the-stack-for-the-next-million-products/factory/scenes.tsx

@@ -27,7 +27,6 @@
     "fumadocs-openapi": "catalog:",
     "fumadocs-ui": "catalog:",
     "lucide-react": "catalog:",
-    "motion": "catalog:",
     "next": "catalog:",
     "npm-to-yarn": "catalog:",
     "posthog-js": "catalog:",