Website Content Updater
name: website-updater
description: >
Reviews and updates website pages. Creates PRs for content changes,
handles page-specific patterns, and ensures consistency.
triggers:
- update the website
- website copy
- landing page
- fix the homepage
MCP connectors
| Connector |
Purpose |
| GitHub |
Push changes, create PRs for site updates |
Review Workflow
Step 1: Audit Current State
Before making changes, review:
- Fetch the live page via
WebFetch to see current copy
- Read the source files in the repo
- Note what needs updating and why
Step 2: Make Changes
- Edit source files directly
- Follow page-specific patterns (below)
- Maintain consistent voice and formatting across pages
Step 3: Create PR
git checkout -b content/website/YYYY-MM-DD-description
# make changes
git add [changed files]
git commit -m "content: update [page] - [what changed]"
# create PR for review
Step 4: Preview
- Run the local dev server if available
- Verify changes render correctly
- Check mobile responsiveness
- Verify all links work
Page-Specific Patterns
Homepage
- Hero: one sentence value proposition + one sentence supporting detail
- Social proof: specific numbers or customer logos, not vague claims
- CTA: one primary action, one secondary
- Keep above-the-fold tight - no scrolling to understand what you do
Product/Features Page
- Lead with the problem each feature solves
- Use before/after or with/without framing
- Screenshots or GIFs for every feature
- Keep descriptions to 2-3 sentences per feature
Pricing Page
- Make the recommended plan obvious
- List what's included, not what's excluded
- Address "What happens when I hit the limit?" upfront
- Include FAQ section for common pricing questions
About Page
- Team section: real photos, real titles, one sentence per person
- Mission: what you do and why, in 2 sentences
- Values: only if they're specific enough to be actionable
Blog Index
- Show title, date, author, and reading time
- Category filters should work
- Featured post gets prominent placement
Content Rules
- No em dashes. Use hyphens (-) or colons (:).
- No "cutting-edge", "revolutionary", or "world-class"
- Specific numbers beat vague claims ("500+ teams" beats "many teams")
- Every page should have exactly one primary CTA
- Alt text on every image
- Meta descriptions on every page (under 160 characters)
- Check that Open Graph tags are set for social sharing
Self-improvement
After the CAO reviews and approves website copy:
- Move the final version from
_drafts/ to _published/
- Diff what was drafted vs what the CAO kept - identify patterns in her edits to headlines, CTAs, or page structure
- Update
content/website/_insights.md with what worked and what she changed
- If her edits reveal a new rule (e.g. "hero must mention the ICP by name", "never use more than one CTA per section"), add it to the Content Rules or Page-Specific Patterns sections above
- If a page performs well (high conversion, low bounce), save it to
content/website/_examples/ with performance annotations
1---2name: website3description: Website Content Updater4---5# Website Content Updater67```yaml8name: website-updater9description: >10 Reviews and updates website pages. Creates PRs for content changes,11 handles page-specific patterns, and ensures consistency.12triggers:13 - update the website14 - website copy15 - landing page16 - fix the homepage17```1819---2021## MCP connectors2223| Connector | Purpose |24|-----------|---------|25| GitHub | Push changes, create PRs for site updates |2627## Review Workflow2829### Step 1: Audit Current State30Before making changes, review:31- Fetch the live page via `WebFetch` to see current copy32- Read the source files in the repo33- Note what needs updating and why3435### Step 2: Make Changes36- Edit source files directly37- Follow page-specific patterns (below)38- Maintain consistent voice and formatting across pages3940### Step 3: Create PR41```bash42git checkout -b content/website/YYYY-MM-DD-description43# make changes44git add [changed files]45git commit -m "content: update [page] - [what changed]"46# create PR for review47```4849### Step 4: Preview50- Run the local dev server if available51- Verify changes render correctly52- Check mobile responsiveness53- Verify all links work5455---5657## Page-Specific Patterns5859### Homepage60- Hero: one sentence value proposition + one sentence supporting detail61- Social proof: specific numbers or customer logos, not vague claims62- CTA: one primary action, one secondary63- Keep above-the-fold tight - no scrolling to understand what you do6465### Product/Features Page66- Lead with the problem each feature solves67- Use before/after or with/without framing68- Screenshots or GIFs for every feature69- Keep descriptions to 2-3 sentences per feature7071### Pricing Page72- Make the recommended plan obvious73- List what's included, not what's excluded74- Address "What happens when I hit the limit?" upfront75- Include FAQ section for common pricing questions7677### About Page78- Team section: real photos, real titles, one sentence per person79- Mission: what you do and why, in 2 sentences80- Values: only if they're specific enough to be actionable8182### Blog Index83- Show title, date, author, and reading time84- Category filters should work85- Featured post gets prominent placement8687---8889## Content Rules9091- No em dashes. Use hyphens (-) or colons (:).92- No "cutting-edge", "revolutionary", or "world-class"93- Specific numbers beat vague claims ("500+ teams" beats "many teams")94- Every page should have exactly one primary CTA95- Alt text on every image96- Meta descriptions on every page (under 160 characters)97- Check that Open Graph tags are set for social sharing9899## Self-improvement100101After the CAO reviews and approves website copy:1021031. Move the final version from `_drafts/` to `_published/`1042. Diff what was drafted vs what the CAO kept - identify patterns in her edits to headlines, CTAs, or page structure1053. Update `content/website/_insights.md` with what worked and what she changed1064. If her edits reveal a new rule (e.g. "hero must mention the ICP by name", "never use more than one CTA per section"), add it to the Content Rules or Page-Specific Patterns sections above1075. If a page performs well (high conversion, low bounce), save it to `content/website/_examples/` with performance annotations
getnao