Building Content Suites

Content Suites generate multiple coordinated pieces. Here's how to plan and execute them effectively.

Planning Your Suite

Define the Collection Goal

Before creating a suite, answer:

• What's the overall purpose of this content collection?
• Who is the primary audience?
• What journey should readers take through the content?
• What should readers be able to do after consuming the suite?

Map the Content Structure

Sketch out your suite before building:

Pillar Page: "Complete Guide to DevOps"
├── Getting Started with DevOps
├── CI/CD Pipeline Fundamentals  
├── Infrastructure as Code
├── Monitoring and Observability
├── DevOps Culture and Teams
└── DevOps Tools Comparison

Identify Connections

Plan how pieces will reference each other:

• What should the pillar page link to?
• Which pieces are prerequisites for others?
• What's the recommended reading order?

Writing Suite Objectives

Include the Big Picture

Your objective should describe the entire collection:

"Create a comprehensive content hub for developers learning Kubernetes. The collection should take someone from 'what is K8s?' to 'I can deploy and manage production workloads.' Include beginner, intermediate, and advanced content clearly labeled."

Specify Individual Pieces

Use an outline to define each page:

1. Kubernetes Overview (beginner)
   - What K8s solves
   - Core concepts
   - When to use it
   
2. Your First Deployment (beginner)
   - Setting up local cluster
   - Deploying a sample app
   - Basic kubectl commands
   
3. Services and Networking (intermediate)
   - Service types explained
   - Ingress setup
   - DNS and service discovery

Define Shared Elements

Specify what should be consistent:

"Use 'cluster' consistently (not 'server' or 'environment'). Every page should include a 'Prerequisites' section and end with 'Next Steps' linking to related pages. Include a difficulty rating on each page."

Suite Size Strategy

Start Small

Begin with 3-5 pages rather than 15:

• Easier to review and refine
• Lower token investment to test approach
• Faster iteration on structure

Build Incrementally

Expand successful suites:

1. Create core pages (3-5)
2. Review and refine
3. Add supporting pages (3-5 more)
4. Continue based on needs

Consider Token Budget

Calculate your investment:

• 5 pages standard = 5 tokens + base
• 5 pages max mode = 20 tokens + base
• 10 pages with research + max = 80 tokens + overages

Consistency Best Practices

Terminology Alignment

In your objective, explicitly define key terms:

"Terminology: Use 'workspace' (not 'project' or 'organization'), 'member' (not 'user' or 'teammate'), 'integration' (not 'connection' or 'link')."

Structural Templates

Request consistent structure:

"Each page should follow this structure: Overview paragraph, Prerequisites box, Main content with H2 sections, Practical example, Common mistakes, Next steps."

Cross-Reference Pattern

Define how pages should link:

"Every page should link to at least 2 other pages in the suite. Use 'See [Page Title] for more details' format. Don't over-link— 2-4 internal links per page maximum."

Suite Types and Templates

Documentation Set

1. Overview/Introduction
2. Getting Started/Quick Start
3. Core Concepts
4. [Feature] Guides (multiple)
5. API/Configuration Reference
6. Troubleshooting/FAQ

Topic Cluster (SEO)

1. Pillar Page (comprehensive overview)
2-8. Supporting Posts (specific subtopics)
Each supporting post links to pillar.
Pillar links to all supporting posts.

Tutorial Series

1. Part 1: Foundations
2. Part 2: Basic Implementation  
3. Part 3: Advanced Features
4. Part 4: Production Considerations
5. Part 5: Troubleshooting & Tips

Comparison Collection

1. Overview: Choosing the Right [Category]
2. Option A Deep Dive
3. Option B Deep Dive
4. Option C Deep Dive
5. Comparison Matrix & Recommendations

Reviewing Suite Output

Check Consistency

• Are terms used the same way across pages?
• Is the structure consistent?
• Do cross-references work?

Verify Flow

• Does the reading order make sense?
• Are prerequisites clearly indicated?
• Does each page build on previous ones?

Check for Gaps

• Are any important topics missing?
• Is there redundant content between pages?
• Are all audience questions answered?

Editing Suite Content

After generation:

1. Review nav.json for structure
2. Read pages in intended order
3. Fix cross-reference links if needed
4. Add any missing internal links
5. Verify terminology consistency
6. Adjust length balance if some pages are too short/long