Move integration methods below use cases, extract to partial, update get-started page (#28753)

Author: kathayl

src/content/docs/browser-rendering/get-started.mdx

@@ -6,18 +6,12 @@ sidebar:
 ---
 import { Render } from "~/components";
 
-Cloudflare Browser Rendering allows you to programmatically control a headless browser, enabling you to do things like take screenshots, generate PDFs, and perform automated browser tasks.
+Cloudflare Browser Rendering allows you to programmatically control a headless browser, enabling you to do things like take screenshots, generate PDFs, and perform automated browser tasks. This guide will help you choose the right integration method and get you started with your first project.
 
-There are two ways to use Browser Rendering:
-- [REST API](/browser-rendering/rest-api/) for simple, one-off actions, like taking a screenshot, fetching HTML, or generating a PDF.
-- [Workers Bindings](/browser-rendering/workers-bindings/) for more complex, multi-step browser automation using [Puppeteer](/browser-rendering/puppeteer/) and [Playwright](/browser-rendering/playwright/).
-
-This guide will help you choose the right path for your needs and get you started with your first Browser Rendering project.
+<Render file="integration-methods" product="browser-rendering" />
 
 ## REST API
 
-The REST API is best for situations where you have an existing application and want to perform simple, stateless browser actions.
-
 ### Prerequisites
 - Sign up for a [Cloudflare account](https://dash.cloudflare.com/sign-up/workers-and-pages).
 - Create a [Cloudflare API Token](/fundamentals/api/get-started/create-token/) with `Browser Rendering - Edit` permissions.
@@ -33,12 +27,10 @@ The REST API can also be used to:
 
 - [Fetch HTML](/browser-rendering/rest-api/content-endpoint/)
 - [Generate a PDF](/browser-rendering/rest-api/pdf-endpoint/)
-- [and more...](/browser-rendering/rest-api/)
+- [Explore all REST API endpoints](/browser-rendering/rest-api/)
 
 ## Workers Bindings
 
-Workers Bindings are best for situations where you need to build more complex, multi-step browser automation workflows. You can use familiar tools like [Puppeteer](/browser-rendering/puppeteer/) and [Playwright](/browser-rendering/playwright/).
-
 ### Prerequisites
 <Render file="prereqs" product="workers" />
 
@@ -49,9 +41,10 @@ Workers Bindings are best for situations where you need to build more complex, m
   product="browser-rendering"
 />
 
-## Next Steps
-If you have any feature requests or notice any bugs, share your feedback directly with the Cloudflare team by joining the [Cloudflare Developers community on Discord](https://discord.cloudflare.com/).
+## Next steps
 
 - Check out all the [REST API endpoints](/browser-rendering/rest-api/)
 - Try out the [Playwright MCP](/browser-rendering/playwright/playwright-mcp/)
-- Learn more about Browser Rendering [limits](/browser-rendering/limits/) and [pricing](/browser-rendering/pricing/).
+- Learn more about Browser Rendering [limits](/browser-rendering/limits/) and [pricing](/browser-rendering/pricing/)
+
+If you have any feature requests or notice any bugs, share your feedback directly with the Cloudflare team by joining the [Cloudflare Developers community on Discord](https://discord.cloudflare.com/).

src/content/docs/browser-rendering/index.mdx

@@ -15,6 +15,7 @@ import {
 	LinkTitleCard,
 	Plan,
 	RelatedProduct,
+	Render,
 	AstroIcon,
 } from "~/components";
 
@@ -40,6 +41,10 @@ Programmatically load and fully render dynamic webpages or raw HTML and capture
 - [HTML elements](/browser-rendering/rest-api/scrape-endpoint/)
 - [Structured data](/browser-rendering/rest-api/json-endpoint/)
 
+## Integration methods
+
+<Render file="integration-methods" product="browser-rendering" />
+
 ## Key features
 
 - **Scale to thousands of browsers**: Instant access to a global pool of browsers with low cold-start time, ideal for high-volume screenshot generation, data extraction, or automation at scale
@@ -48,21 +53,6 @@ Programmatically load and fully render dynamic webpages or raw HTML and capture
 - **Session management**: [Reuse browser sessions](/browser-rendering/workers-bindings/reuse-sessions/) across requests to improve performance and reduce cold-start overhead
 - **Flexible pricing**: Pay only for browser time used with generous free tier ([view pricing](/browser-rendering/pricing/))
 
-## Integration methods
-
-- **[REST API](/browser-rendering/rest-api/)**: Simple HTTP endpoints for stateless tasks like screenshots, PDFs, and scraping.
-- **[Workers Bindings](/browser-rendering/workers-bindings/)**: Full browser automation within Workers using [Puppeteer](/browser-rendering/puppeteer/), [Playwright](/browser-rendering/playwright/), or [Stagehand](/browser-rendering/stagehand/).
-
-| Use case | Recommended | Why |
-| --- | --- | --- |
-| Simple screenshot, PDF, or scrape | [REST API](/browser-rendering/rest-api/) | No code deployment; single HTTP request |
-| Browser automation | [Playwright](/browser-rendering/playwright/) | Full control with built-in tracing and assertions |
-| Porting existing scripts | [Puppeteer](/browser-rendering/puppeteer/) or [Playwright](/browser-rendering/playwright/) | Minimal code changes from standard libraries |
-| AI-powered data extraction | [JSON endpoint](/browser-rendering/rest-api/json-endpoint/) | Structured data via natural language prompts |
-| AI agent browsing | [Playwright MCP](/browser-rendering/playwright/playwright-mcp/) | LLMs control browsers via MCP |
-| Resilient scraping | [Stagehand](/browser-rendering/stagehand/) | AI finds elements by intent, not selectors |
-
-
 ## Related products
 
 <RelatedProduct header="Workers" href="/workers/" product="workers">

src/content/partials/browser-rendering/integration-methods.mdx

@@ -0,0 +1,17 @@
+---
+{}
+---
+
+Browser Rendering offers multiple integration methods depending on your use case:
+
+- **[REST API](/browser-rendering/rest-api/)**: Simple HTTP endpoints for stateless tasks like screenshots, PDFs, and scraping.
+- **[Workers Bindings](/browser-rendering/workers-bindings/)**: Full browser automation within Workers using [Puppeteer](/browser-rendering/puppeteer/), [Playwright](/browser-rendering/playwright/), or [Stagehand](/browser-rendering/stagehand/).
+
+| Use case | Recommended | Why |
+| --- | --- | --- |
+| Simple screenshot, PDF, or scrape | [REST API](/browser-rendering/rest-api/) | No code deployment; single HTTP request |
+| Browser automation | [Playwright](/browser-rendering/playwright/) | Full control with built-in tracing and assertions |
+| Porting existing scripts | [Puppeteer](/browser-rendering/puppeteer/) or [Playwright](/browser-rendering/playwright/) | Minimal code changes from standard libraries |
+| AI-powered data extraction | [JSON endpoint](/browser-rendering/rest-api/json-endpoint/) | Structured data via natural language prompts |
+| AI agent browsing | [Playwright MCP](/browser-rendering/playwright/playwright-mcp/) | LLMs control browsers via MCP |
+| Resilient scraping | [Stagehand](/browser-rendering/stagehand/) | AI finds elements by intent, not selectors |