Skip to content

Add AEO citation blocks (40-60 word summaries) to key pages#63

Open
rachaelrenk wants to merge 7 commits into
mainfrom
rachaelrenk/aeo-citation-blocks
Open

Add AEO citation blocks (40-60 word summaries) to key pages#63
rachaelrenk wants to merge 7 commits into
mainfrom
rachaelrenk/aeo-citation-blocks

Conversation

@rachaelrenk
Copy link
Copy Markdown
Contributor

@rachaelrenk rachaelrenk commented May 11, 2026

Summary

Adds answer-first introductory paragraphs (40-60 word citation blocks) to the top high-value docs pages to improve AI answer engine citability (AEO). Each citation block is a concise, self-contained summary placed at the top of the page that directly answers "What is this feature?" — optimized for extraction by ChatGPT, Perplexity, Google AI Overviews, and similar AI systems.

What changed

53 files edited across three phases. 54 pages already had good intros and were left unchanged. 10 deep procedural pages (self-hosting) were skipped.

Phase 1: Tier 1 pages (12 files edited, 3 already good)

Site root, quickstart, agents overview, local/cloud/CLI agents overviews, capabilities overview, Warp Drive overview, text editing, Blocks, Code, Oz CLI reference, API and SDK reference. Also fixed "open-source" to "open source" per style guide.

Phase 2: Tier 2 pages (9 files edited, 9 already good)

Model choice, Agent Profiles, Teams, Admin Panel, Code Review, Command Palette, Sessions, Supported Shells, Plans and billing.

Phase 3: High-value remaining pages (32 files edited, 42 already good)

  • Capabilities: Full Terminal Use, Slash Commands, Task Lists
  • Cloud agents: Slack integration, cloud providers, demo issue triage
  • Local agents: Active AI, code diffs, interactive code review, interacting with agents, terminal/agent modes, generate, and all 5 agent-context sub-pages (blocks, images, selections, URLs, @ context)
  • Code: Vim keybindings, file tree, find and replace
  • Warp Drive: Workflows, Notebooks, Prompts, Environment Variables, Agent Mode Context, Warp on the Web
  • Reference: CLI agent profiles, troubleshooting, Warp Drive context, reference index
  • Getting started: Agents in Warp, Agent FAQs

Remaining pages (not in this PR)

~220 lower-priority pages are tracked in a separate Notion item for incremental rollout:

  • terminal/ (~65 pages) - deep reference pages
  • guides/ (~55 pages) - tutorial format, needs different pattern
  • enterprise/ (~12 pages) - procedural setup guides
  • support-and-community/ (~18 pages) - billing, privacy, troubleshooting
  • getting-started/ (~10 pages) - migration guides
  • changelog/ (~7 pages) - release notes
  • self-hosting/ (~10 pages) - deep procedural

Writing guidelines followed

Each citation block:

  1. Starts with the feature name and a direct definition
  2. Includes 1-2 key differentiators
  3. Stays between 40-60 words
  4. Uses present tense and active voice
  5. Avoids meta-references ("this page covers")
  6. Includes the product name (Warp or Oz) at least once
  7. Uses "agents" not "AI agents" per terminology standards

Notion task

https://www.notion.so/warpdev/Add-citation-blocks-40-60-word-summaries-to-key-pages-for-AEO-35943263616d807ebdbbcb9d8af8d267

Plan

Add AEO Citation Blocks to Key Docs Pages


Conversation

Co-Authored-By: Oz oz-agent@warp.dev

Add answer-first introductory paragraphs to Tier 1 docs pages to improve
AI answer engine citability. Each citation block is a concise 40-60 word
summary placed at the top of the page that directly answers 'What is this
feature?' in a self-contained, extractable format.

Pages updated:
- Site root (index.mdx), quickstart, agents overview
- Local agents, cloud agents, CLI agents overviews
- Capabilities, MCP, Warp Drive, Blocks, Code, Editor overviews
- Oz CLI and API/SDK references, Enterprise overview

Co-Authored-By: Oz <oz-agent@warp.dev>
@cla-bot cla-bot Bot added the cla-signed label May 11, 2026
@vercel
Copy link
Copy Markdown

vercel Bot commented May 11, 2026

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

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview, Comment May 12, 2026 6:16pm

Request Review

@oz-for-oss
Copy link
Copy Markdown
Contributor

oz-for-oss Bot commented May 11, 2026

@rachaelrenk

I'm starting a first review of this pull request.

You can view the conversation on Warp.

I completed the review and no human review was requested for this pull request.

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

Copy link
Copy Markdown
Contributor

@oz-for-oss oz-for-oss Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overview

This PR adds answer-first citation blocks to Tier 1 docs pages. The changes are documentation-only and generally align with AEO guidance; I found one terminology/style issue in the updated landing page copy.

Concerns

  • The landing page now hyphenates open-source, but the docs terminology guide prefers open source in prose.

Verdict

Found: 0 critical, 0 important, 1 suggestions

Approve with nits

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

Comment thread src/content/docs/index.mdx Outdated
rachaelrenk and others added 2 commits May 12, 2026 07:09
Replace 5 of 9 em dashes with commas, periods, or rewording. Keep em
dashes only where they serve as strong contrast or parenthetical asides
(cloud agents, code, blocks, editor).

Co-Authored-By: Oz <oz-agent@warp.dev>
Co-authored-by: oz-for-oss[bot] <277970191+oz-for-oss[bot]@users.noreply.github.com>
Add 40-60 word answer-first citation blocks to 9 more pages:
- Model choice, Agent Profiles, Teams, Admin Panel
- Code Review, Command Palette, Sessions, Supported Shells
- Plans and billing

Also fix 'open-source' -> 'open source' on index.mdx per style guide.

9 Phase 2 pages already had good intros and were left unchanged:
Skills, Rules, Codebase Context, Environments, Secrets,
Integrations, Planning, Code Editor, Managing Cloud Agents.

Co-Authored-By: Oz <oz-agent@warp.dev>
Add 40-60 word answer-first citation blocks to remaining high-value pages:
- Capabilities: Full Terminal Use, Slash Commands, Task Lists
- Cloud agents: Slack integration, cloud providers, demo issue triage
- Local agents: Active AI, code diffs, interactive code review,
  interacting with agents, terminal/agent modes, generate, voice,
  and all 5 agent-context sub-pages (blocks, images, selections,
  URLs, @ context)
- Code: Vim keybindings, file tree, find and replace
- Warp Drive: Workflows, Notebooks, Prompts, Environment Variables,
  Agent Mode Context, Warp on the Web
- Reference: CLI agent profiles, troubleshooting, Warp Drive context,
  reference index
- Getting started: Agents in Warp, Agent FAQs

42 pages already had good intros and were left unchanged.
10 deep procedural pages (self-hosting) were skipped.

Co-Authored-By: Oz <oz-agent@warp.dev>
@rachaelrenk
Copy link
Copy Markdown
Contributor Author

/oz-review

@oz-for-oss
Copy link
Copy Markdown
Contributor

oz-for-oss Bot commented May 12, 2026

@rachaelrenk

I'm re-reviewing this pull request in response to a review request.

You can view the conversation on Warp.

I completed the review and no human review was requested for this pull request.

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

Copy link
Copy Markdown
Contributor

@oz-for-oss oz-for-oss Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overview

This PR adds answer-first citation blocks across many high-value documentation pages. The prose-only diff does not introduce security-sensitive code or configuration, but it does miss the PR's stated 40-60 word constraint on multiple added blocks.

Concerns

  • Several added citation blocks are under the PR's stated 40-word minimum, including agent-platform/getting-started/faqs.mdx (27 words), reference/cli/troubleshooting.mdx (29 words), and additional blocks in local-agent context, code editor, Warp Drive, reference, and sessions pages. Since consistent 40-60 word AEO blocks are the core acceptance criterion for this PR, expand or revise the under-length blocks before merge.
  • One added block introduces an additional Hashicorp Vault occurrence; use the official HashiCorp Vault capitalization.

Verdict

Found: 0 critical, 1 important, 1 suggestions

Request changes

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

Save or sync environment variables to load into your terminal sessions.
---

Environment Variables in Warp Drive let you save, sync, and load environment variables into your terminal sessions with a click. Support for both static values and dynamic secrets from external managers like 1Password, LastPass, and Hashicorp Vault keeps credentials secure and out of source code.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 [SUGGESTION] Use the official HashiCorp capitalization for the brand name.

Suggested change
Environment Variables in Warp Drive let you save, sync, and load environment variables into your terminal sessions with a click. Support for both static values and dynamic secrets from external managers like 1Password, LastPass, and Hashicorp Vault keeps credentials secure and out of source code.
Environment Variables in Warp Drive let you save, sync, and load environment variables into your terminal sessions with a click. Support for both static values and dynamic secrets from external managers like 1Password, LastPass, and HashiCorp Vault keeps credentials secure and out of source code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants