Fix LP-to-docs 404 by prepending basePath to internal links, and update docs content

Internal links in OpenSourceCTA and Footer used plain <a> tags without
the Next.js basePath prefix, causing 404s on GitHub Pages where the
base path is /rollberry-docs. Also updates documentation content for
accuracy and adds multi-page capture docs.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: mokuwaki

content/docs/getting-started/introduction.mdx

@@ -11,7 +11,7 @@ Rollberry is a command-line tool that captures full-page scrolling videos of web
 Under the hood, Rollberry launches a real Chromium browser via [Playwright](https://playwright.dev/), navigates to your target URL, and records the viewport as it scrolls through the page. This means every CSS animation, lazy-loaded image, and dynamic element is captured exactly as a real user would see it.
 
 ```bash
-npx rollberry capture https://example.com
+rollberry capture https://example.com
 ```
 
 That single command produces a polished MP4 video of the full page in seconds.
@@ -45,13 +45,14 @@ A scrolling video provides a faithful representation of the user experience that
 
 - **Zero install** — Run directly with `npx`, no global installation required
 - **Real browser rendering** — Uses Playwright with Chromium for pixel-perfect captures
+- **Multi-page capture** — Stitch multiple URLs into one video sequentially
 - **Localhost support** — Capture local development servers with automatic retry logic
 - **Custom viewport** — Set any resolution to match your target devices
 - **Smooth scrolling** — Configurable scroll speed and duration
 - **FPS control** — Adjust frame rate for quality vs. file size trade-offs
 - **Wait conditions** — Wait for specific selectors or a fixed delay before capturing
 - **Hide overlays** — Remove cookie banners, sticky headers, and other floating elements
-- **Debug mode** — Save individual frames as PNGs for inspection
+- **Debug frames** — Save individual frames as PNGs for inspection
 - **Structured logs** — JSONL output for programmatic processing
 - **MP4 output** — Industry-standard video format that plays everywhere
 
@@ -64,7 +65,7 @@ Rollberry follows a straightforward capture pipeline:
 3. **Prepare** — Optional wait conditions are applied (timers, selector visibility, overlay hiding)
 4. **Capture** — The viewport is recorded as the page scrolls from top to bottom
 5. **Encode** — Captured frames are assembled into an MP4 video file
-6. **Output** — The video and metadata are saved to the output directory
+6. **Output** — The video and metadata are saved to `rollberry.mp4` by default
 
 The entire process is automated and typically completes in under 30 seconds for most pages.
 

content/docs/getting-started/quick-start.mdx

@@ -9,137 +9,130 @@ order: 2
 The simplest Rollberry command takes just a URL:
 
 ```bash
-npx rollberry capture https://example.com
+rollberry capture https://example.com
 ```
 
 This will:
 
-1. Launch a headless Chromium browser
-2. Navigate to `https://example.com`
-3. Wait 1 second for the page to settle
-4. Scroll from top to bottom over 5 seconds
-5. Save an MP4 video to `./rollberry-output/`
+1. Launch a headless Chromium browser.
+2. Navigate to `https://example.com`.
+3. Wait for the page to load.
+4. Automatically calculate the scroll duration based on page height (approx. 800px per second).
+5. Scroll from top to bottom at 60 FPS.
+6. Save an MP4 video to `./rollberry.mp4`.
 
-The output directory will contain the video file along with a `manifest.json` describing the capture.
+Rollberry also generates sidecar files: `rollberry.manifest.json` (metadata) and `rollberry.log.jsonl` (detailed logs).
 
 ## Viewing the output
 
-After the capture completes, open the output directory to find your video:
+After the capture completes, you will see your video file in the current directory:
 
 ```bash
-ls ./rollberry-output/
+ls rollberry.*
 ```
 
-You will see output similar to:
+You will see:
 
 ```
-capture-2026-03-19T10-30-00.mp4
-manifest.json
+rollberry.mp4
+rollberry.manifest.json
+rollberry.log.jsonl
 ```
 
 Open the MP4 file with any video player, or drag it into a browser window to preview.
 
 ## Customizing the viewport
 
-By default, Rollberry captures at 1280x720 pixels. To capture at a different resolution, use the `--viewport` flag:
+By default, Rollberry captures at 1440x900 pixels. To capture at a different resolution, use the `--viewport` flag:
 
 ```bash
 # Desktop full HD
-npx rollberry capture https://example.com --viewport 1920x1080
+rollberry capture https://example.com --viewport 1920x1080
 
 # Mobile viewport (iPhone-like)
-npx rollberry capture https://example.com --viewport 390x844
+rollberry capture https://example.com --viewport 390x844
 
 # Tablet viewport (iPad-like)
-npx rollberry capture https://example.com --viewport 768x1024
+rollberry capture https://example.com --viewport 768x1024
 ```
 
 The viewport format is `WIDTHxHEIGHT` in pixels.
 
 ## Adjusting scroll duration
 
-The `--duration` flag controls how long the scroll takes in seconds. A longer duration produces a slower, smoother scroll:
+By default, Rollberry uses `auto` duration. You can force a fixed duration (in seconds) using the `--duration` flag:
 
 ```bash
 # Quick 3-second scroll
-npx rollberry capture https://example.com --duration 3
+rollberry capture https://example.com --duration 3
 
 # Slow, detailed 15-second scroll
-npx rollberry capture https://example.com --duration 15
+rollberry capture https://example.com --duration 15
 ```
 
-For very long pages, you may want to increase the duration to avoid scrolling too quickly.
+## Specifying the output path
 
-## Specifying the output directory
-
-By default, output goes to `./rollberry-output`. Use `--output` (or `-o`) to change this:
+Use `--out` to change the output file path:
 
 ```bash
-npx rollberry capture https://example.com -o ./my-captures
+rollberry capture https://example.com --out ./captures/homepage.mp4
 ```
 
 ## Practical examples
 
-Here are a few real-world usage patterns to get you started:
+Here are a few real-world usage patterns:
 
 **Capture a landing page at full HD:**
 
 ```bash
-npx rollberry capture https://your-site.com \
+rollberry capture https://your-site.com \
   --viewport 1920x1080 \
   --duration 8
 ```
 
 **Capture a mobile view with cookie banner hidden:**
 
 ```bash
-npx rollberry capture https://your-site.com \
+rollberry capture https://your-site.com \
   --viewport 390x844 \
-  --hide-selectors ".cookie-banner, .consent-dialog"
+  --hide-selector ".cookie-banner" \
+  --hide-selector ".consent-dialog"
 ```
 
 **Capture a local development server:**
 
 ```bash
-npx rollberry capture http://localhost:3000 \
-  --wait 2000 \
+rollberry capture http://localhost:3000 \
+  --wait-for ms:2000 \
   --duration 10
 ```
 
 **Wait for a specific element before capturing:**
 
 ```bash
-npx rollberry capture https://your-site.com \
-  --wait-for-selector ".hero-image" \
+rollberry capture https://your-site.com \
+  --wait-for "selector:#hero-image" \
   --duration 6
 ```
 
-## What happens during a capture
+## Terminal output
 
 When you run a capture, Rollberry provides progress output in your terminal:
 
 ```
-Rollberry v0.1.3
-Capturing: https://example.com
-Viewport:  1280x720
-Duration:  5s
-FPS:       30
-
-[1/4] Launching browser...
-[2/4] Navigating to page...
-[3/4] Scrolling and capturing...
-[4/4] Encoding video...
-
-Done! Output saved to ./rollberry-output/capture-2026-03-19T10-30-00.mp4
-```
+rollberry capture https://example.com
 
-If anything goes wrong, Rollberry will display a clear error message. For help debugging issues, see the [Debugging](/docs/guides/debugging) guide.
+[1/3] Launching browser...
+[2/3] Navigating to page...
+[3/3] Scrolling and capturing...
+[########################################] 100%
 
-## Next steps
+/Users/you/project/rollberry.mp4
 
-Now that you know the basics, explore these topics:
+Capture complete: rollberry.mp4
+  Duration:  5.2s (312 frames at 60fps)
+  File size: 1.4 MB
+  Manifest:  rollberry.manifest.json
+```
 
-- [CLI Options Reference](/docs/reference/cli-options) — Full list of all available flags
-- [Capturing Multiple Pages](/docs/guides/multi-page) — Batch capture workflows
-- [Localhost Captures](/docs/guides/localhost) — Capture local dev servers
-- [Hiding Overlays](/docs/guides/hiding-overlays) — Remove cookie banners and sticky elements
+If anything goes wrong, Rollberry will display a clear error message. For help debugging issues, see the [Debugging](/docs/guides/debugging) guide.