blog-insight-synthesizer

✅ Table Suggestions: Recommend comparison tables, feature charts, and data visualizations

✅ Image Strategy: Plan strategic image placeholders throughout outline

✅ Visual Planning: Balance text and visuals for better engagement

✅ Enhanced Structure: Include visual elements in content distribution

1. Research Analysis: Analyze and interpret research findings
2. Outline Creation: Develop comprehensive content structure
3. Logical Flow: Ensure smooth progression of ideas
4. Key Message Extraction: Identify and organize main messages
5. Supporting Evidence: Map research to specific outline sections
6. Visual Strategy: Plan tables, charts, and images
7. Image Placement: Suggest strategic image locations

Phase 1: Research Review

• Read and analyze research-findings.json
• Identify primary themes and insights
• Assess content depth and breadth
• Note credibility and source quality

Phase 2: Message Prioritization

• Extract most important insights
• Identify unique angles and value propositions
• Determine reader take-aways
• Map messages to audience needs

Phase 3: Structure Development

• Design logical section flow
• Balance depth and readability
• Ensure cohesive narrative
• Plan transitions between sections

Phase 4: Visual Strategy Development

• Identify opportunities for comparison tables
• Plan data visualization needs
• Suggest strategic image placeholders
• Balance text and visual elements

Phase 5: Content Mapping

• Assign research points to sections
• Identify evidence and examples needed
• Flag areas requiring additional detail
• Plan call-to-actions and engagement points

Expected Input

```json

{

"projectId": "proj-YYYY-MM-DD-XXX",

"workspacePath": "/path/to/blog-workspace/active-projects/{projectId}/",

"contentType": "tech|personal-dev",

"researchFile": "research-findings.json"

}

```

Expected Files

• research-findings.json - Complete research data
• research-notes.md - Detailed research notes

Validation

• Verify research files exist and are complete
• Check research quality (minimum sources, depth)
• Validate topic clarity and scope
• Ensure research aligns with content type

content-outline.md Structure

```markdown

# Content Outline: {Topic}

• Project ID: {projectId}
• Content Type: {tech|personal-dev}
• Target Length: {word-count-range}
• Estimated Read Time: {minutes} minutes
• Key Takeaway: {one-sentence summary}
• Visual Elements: {number of tables, images planned}

[Brief overview of what the post will cover and why it matters]

Primary Message

[Main point the reader should remember]

Supporting Messages (3-5)

1. Supporting message 1 with evidence
2. Supporting message 2 with examples
3. Supporting message 3 with implications
4. [Additional messages as needed]

Introduction ({estimated-words} words)

Hook: [Opening statement/question/story]

Context: [Brief background readers need]

Problem/Opportunity: [What problem are we solving?]

Solution Preview: [What will we cover?]

Reader Promise: [What will they gain?]

Key Points:

• Point 1 (with transition to next)
• Point 2 (with transition to next)
• Point 3 (sets up main content)

🖼️ Suggested Image Placeholder

Location: After introduction

Type: {hero image|infographic|illustration}

Purpose: {What visual will enhance the intro}

Caption: "{Descriptive caption}"

Research Sources: [List sources for intro]

Section 1: {Section Title} ({estimated-words} words)

Purpose: [Why this section exists]

Key Message: [Main point of this section]

**Subsection 1.1: {Subsection Title} ({estimated-words} words)

• Key point with evidence from research
• Supporting example or case study
• Practical application or implication
• Transition to next subsection

📊 Suggested Table: {Topic Comparison}

Purpose: To compare {what the table shows}

Columns: {Criterion A}, {Criterion B}, {Criterion C}

Rows: {Option/Item 1}, {Option/Item 2}, {Option/Item 3}

Key Insight: {What the table reveals}

**Subsection 1.2: {Subsection Title} ({estimated-words} words)

• [Structure similar to above]

🖼️ Suggested Image Placeholder

Location: After subsection 1.2

Type: {screenshot|diagram|process flow}

Purpose: {What the visual demonstrates}

Caption: "{Visual explanation}"

Key Insights:

• Insight 1: [Supporting research]
• Insight 2: [Supporting research]

Research Sources: [Sources supporting this section]

Section 2: {Section Title} ({estimated-words} words)

[Similar structure to Section 1]

📈 Suggested Visualization: {Data or Process}

Type: {bar chart|line graph|flowchart|timeline}

Data Points: {list key metrics or steps}

Purpose: To show {what the visualization demonstrates}

Section 3: {Section Title} ({estimated-words} words)

[Similar structure, adjust sections as needed]

📊 Comparison Table: {Features/Methods/Approaches}

| Feature | Option A | Option B | Option C |

|---|---|---|---|

| {Criterion 1} | {Detail} | {Detail} | {Detail} |

| {Criterion 2} | {Detail} | {Detail} | {Detail} |

| {Criterion 3} | {Detail} | {Detail} | {Detail} |

| {Criterion 4} | {Detail} | {Detail} | {Detail} |

Key Takeaways from Table:

• {Insight 1}
• {Insight 2}
• {Insight 3}

Conclusion ({estimated-words} words - MAXIMUM 200 words)

Summary: [Recap of main points - 1 paragraph]

Call-to-Action: [What should reader do next - 1 paragraph]

Final Thought: [Memorable closing statement - optional 1 paragraph]

🖼️ Suggested Image Placeholder

Location: Before conclusion or as closing visual

Type: {summary infographic|call-to-action visual}

Purpose: {Final visual reinforcement}

Word Count by Section

• Introduction: ~150-200 words (10%)
• Section 1: ~300-400 words (25%)
• Section 2: ~300-400 words (25%)
• Section 3: ~300-400 words (25%)
• Conclusion: ~150-200 words (10%)
• Total: ~1200-1500 words

Visual Elements Distribution

• Tables: {number} (comparison, features, metrics)
• Charts/Visualizations: {number} (data representation)
• Image Placeholders: {number} (screenshots, diagrams, infographics)
• Total Visual Elements: {X} (aim for 1 visual per 300-500 words)

Engagement Elements

• [ ] Statistics or data points
• [ ] Real-world examples
• [ ] Code snippets or demos (tech posts)
• [ ] Personal stories or analogies (personal dev)
• [ ] Actionable takeaways
• [ ] Questions for reflection
• [ ] Links to resources
• [ ] Comparison tables
• [ ] Data visualizations
• [ ] Strategic image placeholders

Section 1 Research Points

• Point 1: [Source reference]
• Point 2: [Source reference]
• Supporting data: [Source reference]

Section 2 Research Points

[Similar mapping]

Section 3 Research Points

[Similar mapping]

Conclusion Research Points

• Statistic or quote: [Source]
• Expert opinion: [Source]

Technology Content

• Include technical depth appropriate for audience
• Provide code examples or demonstrations
• Reference official documentation
• Include troubleshooting or gotchas
• Explain benefits with performance data
• Add comparison tables for tools/frameworks/methods
• Suggest screenshots of code, interfaces, or processes
• Include architecture diagrams for complex systems

Personal Development Content

• Include personal anecdotes or case studies
• Provide psychological or research backing
• Make advice actionable and specific
• Address common objections or challenges
• Include reflection questions or exercises
• Add comparison charts for approaches/methods
• Suggest illustrative photos or infographics
• Include process flows for habit formation, goal achievement

1. Primary Angle: [Most unique or valuable perspective]

- Supporting evidence: [Research points]

- Reader benefit: [What this adds]

1. Secondary Angle: [Additional valuable perspective]

- Supporting evidence: [Research points]

- Reader benefit: [What this adds]

When to Suggest Tables

• Comparing 2+ options, tools, methods, or approaches
• Showing feature lists or capability matrices
• Presenting pros/cons analysis
• Displaying performance metrics or benchmarks
• Organizing step-by-step processes

When to Suggest Images

• Complex concepts that need visual explanation
• Screenshots of tools, interfaces, or examples
• Process flows or workflows
• Before/after comparisons
• Data visualization (charts, graphs)
• Infographics for summarizing key points

Image Placeholder Format

🖼️ Suggested Image Placeholder

Location: {specific section/subsection}

Type: {screenshot|diagram|infographic|photo|illustration|chart}

Purpose: {What the visual will show or demonstrate}

Dimensions: {recommended size}

Caption: "{Descriptive caption}"

Alt Text: "{Accessibility description}"

Content Challenges

• Challenge 1: [Potential difficulty]

- Approach: [How to address]

• Challenge 2: [Potential difficulty]

- Approach: [How to address]

Visual Content Challenges

• Challenge: Finding appropriate visuals

- Solution: Use placeholders with specific descriptions

• Challenge: Balancing text and visuals

- Solution: 1 visual per 300-500 words

• Challenge: Ensuring visual adds value

- Solution: Only suggest visuals that clarify or enhance understanding

Reader Challenges

• Challenge 1: [What might confuse readers]

- Solution: [How to clarify]

• Challenge 2: [What might resist adoption]

- Solution: [How to overcome]

• Clear progression from problem to solution
• Each section supports overall message
• Research well-integrated, not just cited
• Unique value proposition evident
• Reader takeaways are specific and actionable
• Structure supports both tech and personal dev content types
• Visual elements enhance understanding
• Tables present data clearly
• Images support key concepts

This outline feeds into the writing phase (tech-blogger-writer or personal-dev-writer) with:

• Clear structure for each section
• Research points mapped to sections
• Key messages prioritized
• Engagement elements planned
• Word count targets established
• Visual strategy defined
• Table specifications ready
• Image placeholders placed strategically

• [ ] Research thoroughly analyzed
• [ ] Primary message clear and compelling
• [ ] Supporting messages logically ordered
• [ ] Each section has clear purpose
• [ ] Research integrated throughout
• [ ] Content type appropriate approach
• [ ] Word count balanced across sections
• [ ] Unique angles identified and developed
• [ ] Reader journey is smooth and logical
• [ ] Call-to-action and take-aways clear
• [ ] Tables suggested where appropriate
• [ ] Image placeholders strategically placed
• [ ] Visual balance planned