feat: Add Multi-Agent Workflow SEO article (5,400 searches/month)#321
feat: Add Multi-Agent Workflow SEO article (5,400 searches/month)#321LindsayLiu777 wants to merge 2 commits into
Conversation
Add comprehensive article on multi-agent workflow patterns with 7 detailed workflow diagrams: - Development team pipeline - Support swarm architecture - Content production workflow - Code migration system - QA fortress framework - Data pipeline orchestration - Documentation system This is a clean PR containing only the Multi-Agent Workflow article files.
gusye1234
left a comment
There was a problem hiding this comment.
Code Review — PR #321
Summary
This PR adds a new SEO article (multi-agent-workflow-patterns.mdx) and 7 SVG diagrams. The content itself is well-written, but the article will not appear in the blog due to metadata format and missing required fields.
Critical Issues
1. Wrong metadata format — article won't load
The article uses YAML frontmatter (--- blocks), but the blog system loads metadata via:
// src/web/src/lib/blog/posts/import-mdx.ts
const mod = await import(`@/content/${slug}.mdx`);
return mod.metadata;Without remark-frontmatter + remark-mdx-frontmatter plugins (not configured in next.config.ts), YAML frontmatter is NOT exported as mod.metadata. The working articles in this repo use:
export const metadata = { slug: '...', title: '...', ... };See why-we-built-alook.mdx, ai-agent-team.mdx, personal-ai-company.mdx for the correct format.
Fix: Replace the YAML frontmatter with export const metadata = { ... };
2. Missing required fields — validateMetadata will skip the post
BlogPost type (src/web/src/lib/blog/types.ts) requires: slug, title, date, author, excerpt, readingTime.
The article is missing:
excerpt(hasdescriptioninstead — wrong field name)readingTime
Even if the metadata format were fixed, validateMetadata() would log a warning and skip the article.
Minor Issues
-
No newline at end of files — all 8 added files are missing trailing newlines (
\ No newline at end of file). -
Inconsistent asset path convention — existing blog images use subdirectories (
/blog/ai-agent-team/hero.png), but these SVGs are flat in/blog/(/blog/workflow-1-dev-team-pipeline.svg). Not a bug but breaks the pattern. -
Extra fields unused —
keywords,canonical,imagein frontmatter aren't part of theBlogPosttype. If you want SEO meta tags, that's a separate feature — these fields currently go nowhere.
Checklist
- Functionality: Article will NOT appear — metadata is unparseable
- Code Quality: Content is well-structured and readable
- Security: SVGs are clean (no scripts/event handlers)
- Tests: Should verify the article loads in the blog index after fixing metadata
- Project Syncing: Asset directory convention not followed
- Convert YAML frontmatter to JavaScript export in multi-agent-workflow-patterns.mdx - Change 'description' field to 'excerpt' to match BlogPost type - Add required 'readingTime' field (7 min read) - Add trailing newlines to all 8 files (7 SVGs + 1 MDX) - Ensure metadata matches the expected BlogPost format Without these changes, the article won't appear in the blog at all.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Summary
Changes
This PR adds:
multi-agent-workflow-patterns.mdx- The main article contentContext
This is part of our SEO content strategy targeting high-value AI agent-related keywords.
Testing