Initial commit
This commit is contained in:
Zhongwei Li
707
skills/content-brief-generator/references/content_frameworks.md
Normal file
707
skills/content-brief-generator/references/content_frameworks.md
Normal file
@@ -0,0 +1,707 @@
|
||||
# Content Structure Frameworks
|
||||
|
||||
Proven frameworks for organizing and writing compelling content.
|
||||
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
Content frameworks are repeatable structures that guide writing and ensure your content achieves its goals. Use these templates to outline before writing.
|
||||
|
||||
---
|
||||
|
||||
## AIDA (Attention, Interest, Desire, Action)
|
||||
|
||||
**Best for:** Marketing copy, sales pages, landing pages, email campaigns
|
||||
|
||||
### Structure
|
||||
|
||||
**1. Attention (Headline/Hook)**
|
||||
- Grab attention immediately
|
||||
- Promise a benefit
|
||||
- Create curiosity
|
||||
|
||||
**2. Interest (Build engagement)**
|
||||
- Explain the problem
|
||||
- Show you understand their pain
|
||||
- Present relevant information
|
||||
|
||||
**3. Desire (Create want)**
|
||||
- Show benefits and outcomes
|
||||
- Provide social proof
|
||||
- Paint a picture of success
|
||||
|
||||
**4. Action (Drive conversion)**
|
||||
- Clear call-to-action
|
||||
- Remove friction
|
||||
- Create urgency
|
||||
|
||||
### Example Outline
|
||||
|
||||
```markdown
|
||||
# Stop Wasting Hours on Manual Testing [Attention]
|
||||
|
||||
## Testing doesn't have to be painful [Interest]
|
||||
- Current state of manual testing
|
||||
- Why it's time-consuming
|
||||
- Hidden costs of bugs in production
|
||||
|
||||
## Automated testing changes everything [Desire]
|
||||
- Save 20 hours per week
|
||||
- Catch bugs before deployment
|
||||
- Team testimonials
|
||||
- ROI calculator
|
||||
|
||||
## Start automating today [Action]
|
||||
- Free trial (no credit card)
|
||||
- 5-minute setup
|
||||
- CTA button
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## PAS (Problem, Agitate, Solve)
|
||||
|
||||
**Best for:** Blog posts, emails, social media, persuasive content
|
||||
|
||||
### Structure
|
||||
|
||||
**1. Problem**
|
||||
- Identify the pain point
|
||||
- Show you understand it
|
||||
- Make it relatable
|
||||
|
||||
**2. Agitate**
|
||||
- Amplify the problem
|
||||
- Show consequences of inaction
|
||||
- Create urgency
|
||||
- Use emotion
|
||||
|
||||
**3. Solve**
|
||||
- Present your solution
|
||||
- Show how it solves the problem
|
||||
- Provide proof
|
||||
- Call-to-action
|
||||
|
||||
### Example Outline
|
||||
|
||||
```markdown
|
||||
# Problem: Your API is slow
|
||||
- Users complain about response times
|
||||
- You're losing customers
|
||||
- You don't know why
|
||||
|
||||
# Agitate: It's getting worse
|
||||
- Every 100ms delay = 1% revenue loss
|
||||
- Competitors are faster
|
||||
- Your reputation suffers
|
||||
- Engineers are overwhelmed debugging
|
||||
|
||||
# Solve: Our monitoring platform
|
||||
- Real-time performance tracking
|
||||
- Identify bottlenecks instantly
|
||||
- Optimize before users notice
|
||||
- Case study: 50% faster in 2 weeks
|
||||
- CTA: Start free trial
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Inverted Pyramid
|
||||
|
||||
**Best for:** News articles, technical documentation, business content
|
||||
|
||||
### Structure
|
||||
|
||||
**1. Most important (Lead)**
|
||||
- Who, what, when, where, why (5 Ws)
|
||||
- Key information first
|
||||
- Answer main question
|
||||
|
||||
**2. Supporting details**
|
||||
- Context and background
|
||||
- Additional facts
|
||||
- Quotes and data
|
||||
|
||||
**3. Background information**
|
||||
- Less critical details
|
||||
- Historical context
|
||||
- Related information
|
||||
|
||||
### Example Outline
|
||||
|
||||
```markdown
|
||||
# Lead (Most important)
|
||||
Next.js 14 released today with major performance improvements:
|
||||
- 50% faster builds
|
||||
- Built-in caching
|
||||
- Server Actions stable
|
||||
|
||||
# Supporting details
|
||||
- How Server Actions work
|
||||
- Performance benchmarks
|
||||
- Migration guide from v13
|
||||
- Developer quotes
|
||||
|
||||
# Background
|
||||
- History of Next.js
|
||||
- Previous version features
|
||||
- Future roadmap
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Storytelling Arc
|
||||
|
||||
**Best for:** Case studies, brand stories, narrative content, testimonials
|
||||
|
||||
### Structure
|
||||
|
||||
**1. Setup (Character & Context)**
|
||||
- Introduce protagonist
|
||||
- Set the scene
|
||||
- Establish normal state
|
||||
|
||||
**2. Conflict (Challenge)**
|
||||
- Problem arises
|
||||
- Stakes are established
|
||||
- Tension builds
|
||||
|
||||
**3. Resolution (Solution)**
|
||||
- How problem was solved
|
||||
- Journey and obstacles
|
||||
- Transformation
|
||||
|
||||
**4. Takeaway (Lesson)**
|
||||
- What was learned
|
||||
- Broader implications
|
||||
- Call-to-action
|
||||
|
||||
### Example Outline
|
||||
|
||||
```markdown
|
||||
# Setup
|
||||
- Meet Sarah, CTO of startup
|
||||
- Team of 20 engineers
|
||||
- Managing infrastructure manually
|
||||
|
||||
# Conflict
|
||||
- Infrastructure costs spiraling
|
||||
- Deployment taking 4 hours
|
||||
- Engineers frustrated
|
||||
- Investors questioning spend
|
||||
|
||||
# Resolution
|
||||
- Discovered our platform
|
||||
- Implemented in 2 weeks
|
||||
- Automated deployments
|
||||
- Cut costs 60%
|
||||
|
||||
# Takeaway
|
||||
- Infrastructure-as-code is essential
|
||||
- Right tools unlock velocity
|
||||
- CTA: See how you can automate
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## How-To / Tutorial
|
||||
|
||||
**Best for:** Educational content, guides, tutorials, instructions
|
||||
|
||||
### Structure
|
||||
|
||||
**1. Introduction**
|
||||
- What you'll learn
|
||||
- Why it matters
|
||||
- Prerequisites
|
||||
- Time estimate
|
||||
|
||||
**2. Step-by-step instructions**
|
||||
- Numbered sequential steps
|
||||
- One action per step
|
||||
- Screenshots/code examples
|
||||
- Expected results
|
||||
|
||||
**3. Troubleshooting**
|
||||
- Common errors
|
||||
- Solutions
|
||||
- How to get help
|
||||
|
||||
**4. Conclusion**
|
||||
- What you accomplished
|
||||
- Next steps
|
||||
- Related resources
|
||||
|
||||
### Example Outline
|
||||
|
||||
```markdown
|
||||
# How to Deploy a Next.js App to Vercel
|
||||
|
||||
## Introduction
|
||||
- What you'll build
|
||||
- Prerequisites: Node.js, Git, Next.js app
|
||||
- Time: 10 minutes
|
||||
|
||||
## Steps
|
||||
1. Create Vercel account
|
||||
- Go to vercel.com
|
||||
- Sign up with GitHub
|
||||
- Screenshot
|
||||
|
||||
2. Connect repository
|
||||
- Click "New Project"
|
||||
- Select repo
|
||||
- Screenshot
|
||||
|
||||
3. Configure settings
|
||||
- Framework: Next.js
|
||||
- Build command
|
||||
- Environment variables
|
||||
|
||||
4. Deploy
|
||||
- Click "Deploy"
|
||||
- Wait for build
|
||||
- View live site
|
||||
|
||||
## Troubleshooting
|
||||
- Build fails: Check Node version
|
||||
- ENV vars missing: Add in settings
|
||||
|
||||
## Next Steps
|
||||
- Custom domain
|
||||
- CI/CD integration
|
||||
- Performance monitoring
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Listicle
|
||||
|
||||
**Best for:** Top X articles, roundups, comparison posts, curated lists
|
||||
|
||||
### Structure
|
||||
|
||||
**1. Introduction**
|
||||
- Why this list matters
|
||||
- How items were selected
|
||||
- Quick overview
|
||||
|
||||
**2. List items (typically 5-10)**
|
||||
- Each item: Title + description
|
||||
- Benefits and features
|
||||
- Examples or screenshots
|
||||
- Why it's on the list
|
||||
|
||||
**3. Conclusion**
|
||||
- Summary
|
||||
- Recommendation
|
||||
- CTA
|
||||
|
||||
### Listicle Types
|
||||
|
||||
**Numbered (Ranked):**
|
||||
- Best to worst
|
||||
- Most to least important
|
||||
- Sequential order
|
||||
|
||||
**Bulleted (Unranked):**
|
||||
- Equal weight
|
||||
- Any order
|
||||
- No hierarchy
|
||||
|
||||
### Example Outline
|
||||
|
||||
```markdown
|
||||
# 7 Essential VS Code Extensions for Python Developers
|
||||
|
||||
## Introduction
|
||||
- Why VS Code for Python
|
||||
- How we selected these
|
||||
- All are free
|
||||
|
||||
## List
|
||||
1. Pylance
|
||||
- What it does
|
||||
- Key features
|
||||
- Installation
|
||||
- Screenshot
|
||||
|
||||
2. Python (Microsoft)
|
||||
- Core extension
|
||||
- Debugging features
|
||||
- Why it's #1
|
||||
|
||||
[Continue for 7 items]
|
||||
|
||||
## Conclusion
|
||||
- Start with top 3
|
||||
- Try others as needed
|
||||
- CTA: Share your favorites
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Comparison / Versus
|
||||
|
||||
**Best for:** Product comparisons, alternative posts, decision content
|
||||
|
||||
### Structure
|
||||
|
||||
**1. Introduction**
|
||||
- What's being compared
|
||||
- Why it matters
|
||||
- Quick verdict (optional)
|
||||
|
||||
**2. Overview of each option**
|
||||
- Brief description
|
||||
- Key features
|
||||
- Ideal user
|
||||
|
||||
**3. Head-to-head comparison**
|
||||
- Feature by feature
|
||||
- Use table format
|
||||
- Pros and cons
|
||||
|
||||
**4. Use cases**
|
||||
- When to use Option A
|
||||
- When to use Option B
|
||||
- Special scenarios
|
||||
|
||||
**5. Verdict**
|
||||
- Recommendation
|
||||
- Decision framework
|
||||
- CTA
|
||||
|
||||
### Example Outline
|
||||
|
||||
```markdown
|
||||
# React vs Vue: Which Framework to Choose in 2024
|
||||
|
||||
## Introduction
|
||||
- Both are popular
|
||||
- Key differences matter
|
||||
- We'll help you decide
|
||||
|
||||
## React Overview
|
||||
- Created by Facebook
|
||||
- JSX syntax
|
||||
- Large ecosystem
|
||||
- Best for: Enterprise
|
||||
|
||||
## Vue Overview
|
||||
- Progressive framework
|
||||
- Template syntax
|
||||
- Gentle learning curve
|
||||
- Best for: Rapid development
|
||||
|
||||
## Feature Comparison
|
||||
|
||||
| Feature | React | Vue |
|
||||
|---------|-------|-----|
|
||||
| Learning curve | Steep | Gentle |
|
||||
| Performance | Excellent | Excellent |
|
||||
| Ecosystem | Huge | Growing |
|
||||
|
||||
## Use Cases
|
||||
- Choose React if: Large team, TypeScript
|
||||
- Choose Vue if: Solo dev, quick prototype
|
||||
|
||||
## Verdict
|
||||
- No wrong choice
|
||||
- Context matters
|
||||
- CTA: Try both with tutorial
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Ultimate Guide / Pillar Content
|
||||
|
||||
**Best for:** Comprehensive resources, cornerstone content, authority building
|
||||
|
||||
### Structure
|
||||
|
||||
**1. Introduction (Table of Contents)**
|
||||
- What's covered
|
||||
- Who it's for
|
||||
- How to use guide
|
||||
- Jump links to sections
|
||||
|
||||
**2. Fundamentals**
|
||||
- Basic concepts
|
||||
- Terminology
|
||||
- Why it matters
|
||||
|
||||
**3. Deep Dive Sections**
|
||||
- Multiple major sections
|
||||
- Each could be standalone post
|
||||
- Comprehensive coverage
|
||||
|
||||
**4. Advanced Topics**
|
||||
- Expert-level content
|
||||
- Edge cases
|
||||
- Best practices
|
||||
|
||||
**5. Resources**
|
||||
- Tools and software
|
||||
- Further reading
|
||||
- Related guides
|
||||
|
||||
**6. FAQ**
|
||||
- Common questions
|
||||
- Quick answers
|
||||
|
||||
### Example Outline
|
||||
|
||||
```markdown
|
||||
# The Complete Guide to API Authentication (2024)
|
||||
|
||||
## Table of Contents
|
||||
[Jump links to all sections]
|
||||
|
||||
## Introduction
|
||||
- Why authentication matters
|
||||
- What you'll learn
|
||||
- Who this is for
|
||||
|
||||
## Part 1: Authentication Basics
|
||||
- What is authentication vs authorization
|
||||
- Common methods overview
|
||||
- Security principles
|
||||
|
||||
## Part 2: API Keys
|
||||
- How they work
|
||||
- Implementation guide
|
||||
- Pros and cons
|
||||
- Best practices
|
||||
|
||||
## Part 3: OAuth 2.0
|
||||
- OAuth flow explained
|
||||
- Implementation
|
||||
- Use cases
|
||||
- Security considerations
|
||||
|
||||
## Part 4: JWT Tokens
|
||||
- How JWT works
|
||||
- Implement in Node.js
|
||||
- Refresh tokens
|
||||
- Security tips
|
||||
|
||||
## Part 5: Best Practices
|
||||
- Security checklist
|
||||
- Performance optimization
|
||||
- Error handling
|
||||
- Testing authentication
|
||||
|
||||
## Tools & Resources
|
||||
- Libraries and frameworks
|
||||
- Testing tools
|
||||
- Further reading
|
||||
|
||||
## FAQ
|
||||
- 10+ common questions
|
||||
|
||||
## Conclusion
|
||||
- Key takeaways
|
||||
- Choose right method
|
||||
- Next steps
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Feature Announcement
|
||||
|
||||
**Best for:** Product launches, new feature releases, updates
|
||||
|
||||
### Structure
|
||||
|
||||
**1. Headline + Visual**
|
||||
- Clear announcement
|
||||
- What's new
|
||||
- Eye-catching graphic
|
||||
|
||||
**2. The Problem**
|
||||
- What users struggled with
|
||||
- Why we built this
|
||||
|
||||
**3. The Solution**
|
||||
- How feature solves it
|
||||
- Key benefits
|
||||
- Demo or video
|
||||
|
||||
**4. How It Works**
|
||||
- Step-by-step
|
||||
- Screenshots
|
||||
- Technical details
|
||||
|
||||
**5. Availability**
|
||||
- Who can use it
|
||||
- How to access
|
||||
- Pricing (if applicable)
|
||||
|
||||
**6. What's Next**
|
||||
- Future improvements
|
||||
- Feedback request
|
||||
- Related features
|
||||
|
||||
### Example Outline
|
||||
|
||||
```markdown
|
||||
# Introducing Real-Time Collaboration
|
||||
|
||||
[Hero image/GIF]
|
||||
|
||||
## The Problem
|
||||
- Users couldn't work together
|
||||
- Version conflicts
|
||||
- Lost changes
|
||||
|
||||
## The Solution
|
||||
- Live cursors
|
||||
- Instant updates
|
||||
- Conflict resolution
|
||||
- 50ms latency
|
||||
|
||||
## How It Works
|
||||
1. Invite team members
|
||||
2. See who's online
|
||||
3. Work simultaneously
|
||||
4. Changes sync instantly
|
||||
|
||||
## Available Now
|
||||
- All Pro plans
|
||||
- No additional cost
|
||||
- Enable in settings
|
||||
|
||||
## What's Next
|
||||
- Comments coming soon
|
||||
- Video chat integration
|
||||
- We'd love your feedback
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Thought Leadership / Opinion
|
||||
|
||||
**Best for:** Industry commentary, trend analysis, hot takes
|
||||
|
||||
### Structure
|
||||
|
||||
**1. Strong Opening**
|
||||
- Contrarian take or
|
||||
- Bold prediction or
|
||||
- Provocative question
|
||||
|
||||
**2. Current State**
|
||||
- What most people think
|
||||
- Common assumptions
|
||||
- Status quo
|
||||
|
||||
**3. Your Perspective**
|
||||
- Why you disagree or
|
||||
- What others are missing
|
||||
- Your unique insight
|
||||
|
||||
**4. Evidence**
|
||||
- Data and examples
|
||||
- Trends you're seeing
|
||||
- Expert opinions
|
||||
|
||||
**5. Implications**
|
||||
- What this means
|
||||
- Who's affected
|
||||
- What should change
|
||||
|
||||
**6. Call-to-Action**
|
||||
- What readers should do
|
||||
- Discussion prompt
|
||||
- Share thoughts
|
||||
|
||||
### Example Outline
|
||||
|
||||
```markdown
|
||||
# Microservices Are Overrated (And Here's Why)
|
||||
|
||||
## Opening
|
||||
- Everyone wants microservices
|
||||
- Most don't need them
|
||||
- Monoliths are underrated
|
||||
|
||||
## Current State
|
||||
- Industry trends
|
||||
- Why microservices are popular
|
||||
- What blogs/consultants say
|
||||
|
||||
## My Perspective
|
||||
- Complexity costs
|
||||
- Most apps aren't at scale
|
||||
- Premature optimization
|
||||
|
||||
## Evidence
|
||||
- Case studies of failures
|
||||
- Cost analysis
|
||||
- When microservices make sense
|
||||
|
||||
## Implications
|
||||
- Start with monolith
|
||||
- Extract services later
|
||||
- Focus on business value
|
||||
|
||||
## Conclusion
|
||||
- Challenge the hype
|
||||
- Make informed decisions
|
||||
- Share your experience
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Framework Selection Guide
|
||||
|
||||
**Choose framework based on:**
|
||||
|
||||
| Goal | Best Framework |
|
||||
|------|----------------|
|
||||
| Drive conversions | AIDA, PAS |
|
||||
| Educate/inform | Inverted Pyramid, How-To |
|
||||
| Build authority | Ultimate Guide, Thought Leadership |
|
||||
| Compare options | Comparison, Listicle |
|
||||
| Tell story | Storytelling Arc |
|
||||
| Announce feature | Feature Announcement |
|
||||
|
||||
**Multiple frameworks:**
|
||||
- Can combine frameworks
|
||||
- Example: Storytelling intro + How-To body
|
||||
- Adapt to your needs
|
||||
|
||||
---
|
||||
|
||||
## Template for Any Framework
|
||||
|
||||
```markdown
|
||||
# [Compelling Title]
|
||||
|
||||
## Hook (First 100 words)
|
||||
- Grab attention
|
||||
- State problem or benefit
|
||||
- Include primary keyword
|
||||
|
||||
## Body (Main content)
|
||||
- [Apply chosen framework]
|
||||
- Use subheadings
|
||||
- Include examples
|
||||
- Add visuals
|
||||
|
||||
## Conclusion
|
||||
- Summarize key points
|
||||
- Reinforce main takeaway
|
||||
- Clear CTA
|
||||
|
||||
## Additional Resources
|
||||
- Internal links
|
||||
- External references
|
||||
- Further reading
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
**Remember:** Frameworks are starting points, not rigid rules. Adapt them to your content needs and audience.
|
||||
Reference in New Issue
Block a user