5a40b6fdc4
* feat: add OAC package refactor context file - Add comprehensive feature context for OAC package refactor - Document multi-IDE support architecture - Define community component registry (shadcn-like) - Outline flexible configuration system - Detail context file location flexibility - Define 7-phase implementation plan - Include CLI commands reference - Add community publishing guidelines * docs: add OAC refactor quick start guide - Add quick reference for Phase 1 implementation - Include project structure and file locations - Document configuration schema and defaults - Add testing strategy and validation steps - Include development workflow - Reference all related resources * feat: add critical user approval and context resolution systems CRITICAL FEATURES ADDED: 1. User Approval & YOLO Mode - Default: Interactive approval for all file operations - Always asks: local vs global install - Confirms before overwriting files - Shows diffs and file details - YOLO mode (--yolo): Skip confirmations, auto-resolve, report at end - Conflict strategies: ask, skip, overwrite, backup, yolo - Safety: backups, git detection, rollback support, audit log 2. Context Resolution System - Layered context resolution (6 priority levels) - Project override (.oac/context/) - highest priority - Project context (.opencode/context/) - IDE context (.cursor/, .claude/) - Project docs (docs/) - User global (~/.config/oac/context/) - OAC official (~/.config/oac/official/) - lowest priority - Smart resolution based on agent location (global vs local) - preferLocal config option - Context merging strategies - CLI commands for context management - Environment variable overrides - Validation and fallback support 3. Enhanced CLI Commands - All commands support --yolo, --dry-run, --local, --global - Context management: resolve, list, validate, override, sync - Detailed help and examples - Global flags for all commands This ensures users maintain full control over their projects while supporting both local and global workflows with intelligent context resolution. * feat: add component creation wizard and IDE feature parity system NEW FEATURES: 1. Interactive Component Creation - oac create (interactive wizard) - Create agents, skills, contexts, plugins, commands, tools - Template system for scaffolding - Auto-generate tests and boilerplate - Multi-IDE compatibility selection - Size optimization options 2. IDE Feature Parity & Capacity Management (CRITICAL) - Feature support matrix for all IDEs - OpenCode/Claude Code: Full support (all features) - Cursor: Limited (single file, no skills/plugins, 100KB limit) - Windsurf: Partial support - Adaptive installation based on IDE capabilities - Automatic feature filtering and warnings - Component merging for single-file IDEs (Cursor) - Capacity warnings and optimization - IDE-specific profiles 3. Enhanced CLI Commands - oac create [type] - Component creation wizard - oac templates - List available templates - oac compatibility <ide> - Check IDE compatibility - oac ides - List supported IDEs with features - oac ide info <ide> - Show IDE capabilities - oac optimize --for <ide> - Optimize for specific IDE - oac validate --ide <ide> - Validate IDE installation 4. Smart Installation - Detects IDE capabilities - Warns about unsupported features - Auto-filters components - Merges agents for Cursor - Embeds contexts for limited IDEs - Monitors file size limits - Suggests IDE-specific profiles This ensures users can easily create components and OAC gracefully handles different IDE capabilities with clear warnings and automatic optimization. * docs: add critical feedback from parallel agent review CRITICAL FINDINGS: Security Gaps (BLOCKER): - No component signing or verification - No malware/secret scanning - No permission system - Action: Add security layer in Phase 1 Missing Features (CRITICAL): - Discovery (browse, search, trending) - Lockfile for reproducibility - Version conflict management - Interactive onboarding - Progress indicators - Auto-detection for local/global Approaches to Rethink: - Context merging → Use composition instead - Always asking local/global → Auto-detect with smart defaults - Cursor agent merging → Router pattern instead Repository Structure: - Recommended: Monorepo with pnpm workspaces - Packages: core, adapters, registry, security, cli - Benefits: Shared deps, atomic commits, easier testing Community Workflow: - Component submission process - Automated security scanning - Manual review for verification - Moderation system Updated Priorities: - v1.0 MVP: Add 6 critical features (discovery, lockfile, security, etc.) - v1.1: Plugin system, workspace support, marketplace - v2.0: Enterprise features Documentation Needs: - Quick Start (5-minute guide) - CLI Reference (auto-generated) - Recipes/Cookbook - Component Creation Guide - Migration Guide Overall: Plan is 80% solid, needs 20% critical additions before Phase 1 * feat: add comprehensive agent customization and preset system CRITICAL FEATURE: Agent Customization & Personal Presets Problem: - Users want to customize agent prompts for their workflow - Users want to save personal configurations - Updates shouldn't overwrite customizations - Need easy way to view and edit agents Solution: Multi-Layer Customization System Layer 1: View Agent Configuration - oac show agent:openagent (view in pager) - oac edit agent:openagent (open in editor) - oac config show agent:openagent (config only) - oac export agent:openagent (export to file) Layer 2: Create Personal Preset - oac customize agent:openagent (create preset) - Copies to ~/.config/oac/presets/agents/ - Links to base agent for updates - Tracks customizations in metadata Layer 3: Edit Personal Preset - oac edit preset:my-openagent (edit in $EDITOR) - oac customize preset:my-openagent --interactive (wizard) - Auto-backup on save - Track modification history Layer 4: Use Personal Preset - oac use preset:my-openagent (activate) - oac use preset:my-openagent --global (set default) - oac presets list --active (show active) - Switch between presets and base agents Layer 5: Update Management (CRITICAL) - Smart update detection for base agents - Merge strategies: manual, auto-base, auto-merge, locked - Conflict resolution with user prompts - Show diffs before merging - Auto-backup before updates - Preserve user customizations by default Layer 6: Preset Sharing - oac export preset:my-openagent (export) - oac import preset ./preset.md (import) - oac share preset:my-openagent (share with team) - oac publish preset:my-openagent (publish to community) Layer 7: In-Place Editing (Advanced) - oac edit agent:openagent --in-place (risky, warns user) - Creates backup before editing - Warns that updates will overwrite - Recommends preset creation instead Update Strategies: - manual: User reviews every update - auto-base: Auto-update base, keep preset unchanged - auto-merge: Auto-merge, prompt on conflicts - locked: Never update base Configuration: - Preset metadata (.presets.json) - Update strategies per preset - Merge conflict resolution - Backup management - Warning preferences Edge Cases Handled: - In-place edits before updates - Multiple updates behind - Multiple presets for same base - Preset conflicts with IDE - Deleted base agent Best Practices: - Always create presets (safest) - Document customizations - Review updates before merging - Keep backups - Use descriptive names This ensures users can safely customize agents without fear of losing changes on updates, while still benefiting from base agent improvements. * docs: complete comprehensive user scenario analysis (16,014 lines) PLANNING PHASE COMPLETE: Documents Created (9 files, 400KB): - 00-INDEX.md (388 lines) - Planning index and overview - 01-main-plan.md (2,338 lines) - Complete feature specification - 02-quickstart-guide.md (450 lines) - Phase 1 quick reference - 03-critical-feedback.md (599 lines) - Parallel agent review - 04-solo-developer-scenarios.md (2,106 lines) - Individual workflows - 05-team-lead-scenarios.md (3,977 lines) - Team collaboration - 07-content-creator-scenarios.md (2,581 lines) - Non-technical users - 08-open-source-maintainer-scenarios.md (3,575 lines) - Community management - 09-SYNTHESIS.md (1,000+ lines) - Consolidated findings User Personas Analyzed (4/5): ✅ Solo Developer (Primary - 40% market) ✅ Team Lead (Secondary - 30% market) ✅ Content Creator (Emerging - 20% market) ✅ Open Source Maintainer (Future - 5% market) ⏸️ Enterprise Admin (Deferred to v2.0 - 5% market) Key Findings: Solo Developer (Primary User): - Setup must be < 2 minutes or they skip - Preview before committing (try mode) - Safe customization (presets) - Easy rollback/undo - Zero docs reading to start Team Lead (Secondary User): - Lockfile is non-negotiable (oac.lock) - Team configuration (oac-team.json) - Compliance monitoring (90%+ required) - Onboarding: 4-8 hours → 15 minutes (96% reduction) - Staged rollouts for updates Content Creator (Emerging - 20% market): - CLI is intimidating (need GUI wrapper) - Plain language mode (no jargon) - Visual undo (version history) - Templates and examples - Guided setup Open Source Maintainer (Future): - Security scanning pipeline (ClamAV + gitleaks) - Quality gates (70% test coverage) - Review/approval workflow - Deprecation workflow - Sustainability model Critical Additions to MVP: 1. Interactive onboarding wizard (all personas) 2. TUI browser with preview (solo dev, team lead) 3. Lockfile (oac.lock) (team lead) 4. Security scanning (all personas) 5. Try mode (solo dev) 6. Team configuration (team lead) 7. oac doctor health checks (solo dev) 8. Quality gates (maintainer) Market Opportunity: - v1.0: 70% market (solo + team) - v1.1: 90% market (+ content creators with GUI) - v2.0: 100% market (+ enterprise) Recommended Changes: - Expand MVP scope (+2 weeks, 9 weeks total) - Plan v1.1 for content creators (GUI wrapper) - Defer enterprise features to v2.0 - Build community features early (trust) Status: Ready to finalize plan and start implementation Confidence: Very High (95%+) Risk: Low (comprehensive analysis complete) * docs: add comprehensive final review of OAC planning FINAL REVIEW COMPLETE: Overall Assessment: CONDITIONAL GO ✅⚠️ Confidence Level: 85% (High, with conditions) Success Probability: 75% (with modifications) Key Strengths: ✅ Exceptional user research (16,000+ lines, 4 personas) ✅ Clear technical architecture (monorepo, TypeScript, Zod) ✅ Security-first mindset (signing, scanning, verification) ✅ Realistic scope management (v1.0 vs v1.1 vs v2.0) ✅ Comprehensive feature coverage Critical Gaps Identified: ❌ Discovery/Onboarding not in Phase 1 (but P0 in scenarios) ❌ Lockfile not in Phase 2 (but critical for teams) ❌ Security Pipeline not detailed in phases ❌ Progress UI not in Phase 1 (but needed for UX) ❌ Auto-detection not in Phase 1 (but reduces friction) Conditions for Go: 1. Add discovery/onboarding to Phase 1 (+3 days) 2. Add lockfile to Phase 2 (+2 days) 3. Add security pipeline to Phase 1 (+2 days) 4. Add progress UI to Phase 1 (+1 day) 5. Revise timeline: 7 weeks → 9 weeks Critical Action Items (6 days before Phase 1): 1. Add missing features to phases (2 days) 2. Define acceptance criteria (1 day) 3. Define testing strategy (1 day) 4. Design security pipeline (1 day) 5. Create monorepo structure (1 day) Top Risks: 🔴 Timeline Slip (70% probability, high impact) 🟡 Scope Creep (50% probability, high impact) 🟡 Context Merging Complexity (60% probability, medium impact) Recommendation: PROCEED WITH MODIFICATIONS - Complete 6 days of prerequisite work - Extend timeline to 9 weeks - Add missing features to phases - Define acceptance criteria and testing strategy Status: READY TO IMPLEMENT (with modifications) Next Steps: Complete prerequisites → Setup monorepo → Start Phase 1 * feat(context): Standardize context system with navigation, frontmatter, and MVI compliance - Add 77 navigation.md files across all context categories for token-efficient discovery - Standardize frontmatter format on 198+ context files (HTML comment format, 2026-02-15) - Compress 3 oversized guide files applying MVI principle (802 lines removed, 63% reduction) - Add context system analysis and planning artifacts in context-findings/ - Add task management enhancements (stage orchestration, planning subagents) - Document compression techniques and future optimization recommendations Context System Improvements: - All active directories now have navigation.md (200-300 tokens each) - 100% frontmatter compliance with priority/version/date metadata - Improved scannability through MVI compression (compact.md, organizing-context.md, creation.md) - Token efficiency increased for AI agent consumption Planning & Analysis: - Context system implementation plan and simplification analysis - ADR standard proposal and runtime permission architecture - SQLite context design for future scale (deferred until 500+ files) - Context discovery script analysis (rejected in favor of navigation-first) Task Management: - Enhanced task schema with stage orchestration support - New planning subagents (ADR, Architecture, Story Mapping, Prioritization) - Stage orchestrator for multi-stage workflow management - Session context management and lightweight handoff patterns Closes: context-simple-fixes task Ref: context-system-implementation analysis * fix: resolve markdown link validation errors in navigation files - Remove non-existent react-patterns.md link from react/navigation.md - Remove non-existent premium-dark-ui-quick-start.md link from design/navigation.md - Add skip patterns for pre-existing broken links in example/template files - Validation now passes: 215 files validated, 0 errors * fix: resolve all 119 broken markdown links across documentation - Update agent paths to new subagents structure (TestEngineer, ContextScout, etc.) - Fix animation file references (animation-ui.md → animation-components.md) - Update guide references (adding-agent.md → adding-agent-basics.md) - Convert non-existent example paths to placeholder text format - Add skip patterns for intentional example placeholders - Validation now passes: 232 files validated, 0 errors Co-authored-by: CoderAgent <coder@openagents.dev> --------- Co-authored-by: CoderAgent <coder@openagents.dev>
522 lines
10 KiB
Markdown
522 lines
10 KiB
Markdown
<!-- Context: content-creation/workflows | Priority: medium | Version: 1.0 | Updated: 2026-02-15 -->
|
|
|
|
# Content Remix and Repurposing
|
|
|
|
Strategies for maximizing content ROI by transforming existing content into multiple formats and reaching new audiences.
|
|
|
|
---
|
|
|
|
## Why Repurpose Content?
|
|
|
|
**Benefits**:
|
|
- **Efficiency**: Create once, use many times
|
|
- **Reach**: Different audiences prefer different formats
|
|
- **Reinforcement**: Repetition increases retention
|
|
- **SEO**: More content = more ranking opportunities
|
|
- **Longevity**: Extend content lifespan
|
|
|
|
**ROI**: One piece of pillar content can become 20+ pieces across formats.
|
|
|
|
---
|
|
|
|
## Content Atomization
|
|
|
|
### Breaking Down Pillar Content
|
|
|
|
**Pillar Content** (2000+ word blog post or 30+ min video):
|
|
|
|
**Can become**:
|
|
- 10-15 social media posts (key points)
|
|
- 5-7 short-form videos (TikTok/Reels)
|
|
- 3-5 email newsletters (sections)
|
|
- 1 infographic (visual summary)
|
|
- 1 podcast episode (audio discussion)
|
|
- 1 carousel post (step-by-step)
|
|
- 1 Twitter/X thread (breakdown)
|
|
- 5-10 quote graphics (pull quotes)
|
|
|
|
---
|
|
|
|
### Atomization Process
|
|
|
|
1. **Identify key points**
|
|
- Main takeaways
|
|
- Actionable tips
|
|
- Interesting statistics
|
|
- Compelling quotes
|
|
- Examples and stories
|
|
|
|
2. **Extract standalone pieces**
|
|
- Each point becomes content
|
|
- Add context if needed
|
|
- Make self-contained
|
|
|
|
3. **Adapt for each platform**
|
|
- Format appropriately
|
|
- Adjust length
|
|
- Optimize for platform
|
|
|
|
4. **Link back to original**
|
|
- Drive traffic to pillar
|
|
- Build authority
|
|
- Create content ecosystem
|
|
|
|
---
|
|
|
|
## Format Transformation
|
|
|
|
### Blog Post → Other Formats
|
|
|
|
**Blog Post → Video**:
|
|
- Use blog as script outline
|
|
- Add visual demonstrations
|
|
- Include on-screen text for key points
|
|
- Film yourself explaining concepts
|
|
|
|
**Blog Post → Podcast**:
|
|
- Discuss the topic conversationally
|
|
- Expand with additional insights
|
|
- Interview someone about the topic
|
|
- Add personal stories
|
|
|
|
**Blog Post → Infographic**:
|
|
- Extract key statistics and points
|
|
- Visualize data and processes
|
|
- Create scannable format
|
|
- Design for sharing
|
|
|
|
**Blog Post → Social Posts**:
|
|
- Pull out individual tips
|
|
- Create quote graphics
|
|
- Share key statistics
|
|
- Tease with hook + link
|
|
|
|
**Blog Post → Email Series**:
|
|
- Break into multiple emails
|
|
- One section per email
|
|
- Add personal commentary
|
|
- Include CTAs
|
|
|
|
---
|
|
|
|
### Video → Other Formats
|
|
|
|
**Video → Blog Post**:
|
|
- Transcribe video
|
|
- Edit for readability
|
|
- Add images/screenshots
|
|
- Optimize for SEO
|
|
|
|
**Video → Short-Form Videos**:
|
|
- Extract best moments
|
|
- Create standalone clips
|
|
- Add captions
|
|
- Optimize for platform (TikTok, Reels, Shorts)
|
|
|
|
**Video → Social Posts**:
|
|
- Pull quotes from video
|
|
- Create quote graphics
|
|
- Share key frames
|
|
- Tease with clip + link
|
|
|
|
**Video → Podcast**:
|
|
- Extract audio
|
|
- Add intro/outro
|
|
- Edit for audio-only
|
|
- Publish as episode
|
|
|
|
**Video → Carousel**:
|
|
- Screenshot key moments
|
|
- Add text overlays
|
|
- Create step-by-step
|
|
- Post on Instagram/LinkedIn
|
|
|
|
---
|
|
|
|
### Podcast → Other Formats
|
|
|
|
**Podcast → Blog Post**:
|
|
- Transcribe episode
|
|
- Edit and structure
|
|
- Add headings and formatting
|
|
- Include embedded player
|
|
|
|
**Podcast → Video**:
|
|
- Add visual element (waveform, images)
|
|
- Create video version
|
|
- Upload to YouTube
|
|
- Add chapters
|
|
|
|
**Podcast → Social Posts**:
|
|
- Pull interesting quotes
|
|
- Create audiograms
|
|
- Share key insights
|
|
- Tease episode
|
|
|
|
**Podcast → Email**:
|
|
- Summarize key points
|
|
- Include interesting moments
|
|
- Link to full episode
|
|
- Add show notes
|
|
|
|
---
|
|
|
|
## Cross-Platform Adaptation
|
|
|
|
### Platform-Specific Optimization
|
|
|
|
**LinkedIn**:
|
|
- Professional tone
|
|
- Industry insights
|
|
- Longer-form posts
|
|
- Document posts (carousels)
|
|
|
|
**Twitter/X**:
|
|
- Concise threads
|
|
- Quick tips
|
|
- Engaging questions
|
|
- Link to full content
|
|
|
|
**Instagram**:
|
|
- Visual-first
|
|
- Carousel posts
|
|
- Reels for video
|
|
- Stories for behind-the-scenes
|
|
|
|
**TikTok**:
|
|
- Short, punchy videos
|
|
- Trending audio
|
|
- Hook in first second
|
|
- Educational or entertaining
|
|
|
|
**YouTube**:
|
|
- Longer-form video
|
|
- Comprehensive coverage
|
|
- SEO-optimized
|
|
- Playlist organization
|
|
|
|
**Email**:
|
|
- Personal tone
|
|
- Exclusive insights
|
|
- Direct CTAs
|
|
- Curated content
|
|
|
|
---
|
|
|
|
## Update and Refresh Strategies
|
|
|
|
### When to Update Content
|
|
|
|
**Triggers**:
|
|
- Content is 12+ months old
|
|
- Information is outdated
|
|
- New data available
|
|
- Ranking has dropped
|
|
- Topic is trending again
|
|
- New examples available
|
|
|
|
---
|
|
|
|
### How to Update Content
|
|
|
|
**Minor Updates**:
|
|
- Update statistics and data
|
|
- Add recent examples
|
|
- Fix broken links
|
|
- Refresh images
|
|
- Update date stamp
|
|
|
|
**Major Updates**:
|
|
- Rewrite sections
|
|
- Add new sections
|
|
- Restructure for clarity
|
|
- Expand with new insights
|
|
- Improve SEO optimization
|
|
|
|
**Complete Refresh**:
|
|
- Rewrite from scratch
|
|
- New angle or perspective
|
|
- Current best practices
|
|
- Updated examples
|
|
- New format
|
|
|
|
---
|
|
|
|
### Republishing Strategy
|
|
|
|
**After updating**:
|
|
- Change publish date (or add "Updated: [date]")
|
|
- Announce the update on social media
|
|
- Email subscribers about refresh
|
|
- Resubmit to search engines
|
|
- Share as "new" content
|
|
|
|
---
|
|
|
|
## Content Series Creation
|
|
|
|
### Turning One Topic into a Series
|
|
|
|
**Blog Series**:
|
|
- Part 1: Introduction and overview
|
|
- Part 2: Deep dive into aspect A
|
|
- Part 3: Deep dive into aspect B
|
|
- Part 4: Advanced techniques
|
|
- Part 5: Case studies and examples
|
|
|
|
**Video Series**:
|
|
- Episode 1: The basics
|
|
- Episode 2: Step-by-step tutorial
|
|
- Episode 3: Common mistakes
|
|
- Episode 4: Advanced tips
|
|
- Episode 5: Q&A
|
|
|
|
**Email Course**:
|
|
- Day 1: Welcome and overview
|
|
- Day 2: Foundation concepts
|
|
- Day 3: Implementation
|
|
- Day 4: Optimization
|
|
- Day 5: Next steps
|
|
|
|
---
|
|
|
|
### Series Benefits
|
|
|
|
**For audience**:
|
|
- Comprehensive coverage
|
|
- Logical progression
|
|
- Easier to follow
|
|
- Builds anticipation
|
|
|
|
**For creator**:
|
|
- Easier to plan
|
|
- Batch creation
|
|
- Consistent posting
|
|
- Authority building
|
|
|
|
---
|
|
|
|
## Evergreen Content Maintenance
|
|
|
|
### Evergreen Content Strategy
|
|
|
|
**Characteristics**:
|
|
- Timeless topics
|
|
- Foundational concepts
|
|
- How-to guides
|
|
- Best practices
|
|
|
|
**Maintenance schedule**:
|
|
- Review quarterly
|
|
- Update annually
|
|
- Refresh examples
|
|
- Add new insights
|
|
|
|
---
|
|
|
|
### Evergreen Repurposing
|
|
|
|
**Regular resharing**:
|
|
- Share on social media quarterly
|
|
- Include in email newsletters
|
|
- Reference in new content
|
|
- Update and republish
|
|
|
|
**Seasonal angles**:
|
|
- "New year" version
|
|
- "Summer" edition
|
|
- "Back to school" spin
|
|
- Holiday tie-in
|
|
|
|
---
|
|
|
|
## Content Repurposing Workflows
|
|
|
|
### Workflow 1: Pillar → Atomized
|
|
|
|
1. **Create pillar content** (blog post or video)
|
|
2. **Extract key points** (10-15 takeaways)
|
|
3. **Create social posts** (one per key point)
|
|
4. **Design infographic** (visual summary)
|
|
5. **Record podcast** (discuss the topic)
|
|
6. **Create short videos** (key takeaways)
|
|
7. **Write email series** (break into parts)
|
|
8. **Schedule distribution** (spread over weeks)
|
|
|
|
---
|
|
|
|
### Workflow 2: Format Transformation
|
|
|
|
1. **Start with one format** (e.g., video)
|
|
2. **Transcribe to text** (blog post)
|
|
3. **Extract audio** (podcast episode)
|
|
4. **Create clips** (short-form videos)
|
|
5. **Design graphics** (quote cards)
|
|
6. **Write social posts** (teasers)
|
|
7. **Compile email** (summary + links)
|
|
|
|
---
|
|
|
|
### Workflow 3: Update and Refresh
|
|
|
|
1. **Audit existing content** (identify top performers)
|
|
2. **Check for outdated info** (stats, examples, links)
|
|
3. **Update content** (refresh information)
|
|
4. **Improve SEO** (optimize further)
|
|
5. **Republish** (new date or "updated" note)
|
|
6. **Promote again** (social, email)
|
|
7. **Monitor performance** (track improvements)
|
|
|
|
---
|
|
|
|
## Repurposing Calendar
|
|
|
|
### Monthly Repurposing Plan
|
|
|
|
**Week 1: Create Pillar**
|
|
- Publish comprehensive blog post or video
|
|
- Optimize for SEO
|
|
- Promote on main channels
|
|
|
|
**Week 2: Atomize**
|
|
- Extract key points
|
|
- Create social posts
|
|
- Design graphics
|
|
- Schedule distribution
|
|
|
|
**Week 3: Transform**
|
|
- Convert to different format
|
|
- Create short-form content
|
|
- Write email newsletter
|
|
- Publish across platforms
|
|
|
|
**Week 4: Refresh**
|
|
- Update old content
|
|
- Republish refreshed piece
|
|
- Promote updated content
|
|
- Plan next month
|
|
|
|
---
|
|
|
|
## Repurposing Tools
|
|
|
|
### Content Creation
|
|
|
|
**Transcription**:
|
|
- Otter.ai
|
|
- Descript
|
|
- Rev.com
|
|
|
|
**Video Editing**:
|
|
- Descript (video + transcription)
|
|
- Kapwing
|
|
- Adobe Premiere
|
|
|
|
**Graphic Design**:
|
|
- Canva
|
|
- Adobe Express
|
|
- Figma
|
|
|
|
**Social Media**:
|
|
- Buffer
|
|
- Hootsuite
|
|
- Later
|
|
|
|
---
|
|
|
|
### Content Management
|
|
|
|
**Organization**:
|
|
- Notion (content database)
|
|
- Airtable (content tracker)
|
|
- Trello (workflow management)
|
|
|
|
**Scheduling**:
|
|
- Buffer (social scheduling)
|
|
- ConvertKit (email automation)
|
|
- YouTube Studio (video scheduling)
|
|
|
|
---
|
|
|
|
## Repurposing Checklist
|
|
|
|
Before repurposing, verify:
|
|
|
|
- [ ] Original content performed well
|
|
- [ ] Content is still relevant
|
|
- [ ] New format suits the content
|
|
- [ ] Platform is appropriate
|
|
- [ ] Adapted for platform (not just copy-paste)
|
|
- [ ] Links back to original
|
|
- [ ] Optimized for new format
|
|
- [ ] Scheduled strategically
|
|
- [ ] Tracked for performance
|
|
|
|
---
|
|
|
|
## Common Repurposing Mistakes
|
|
|
|
### ❌ Copy-Paste Without Adaptation
|
|
Posting same content across platforms without optimization.
|
|
|
|
### ✅ Platform-Specific Adaptation
|
|
Tailoring content for each platform's audience and format.
|
|
|
|
---
|
|
|
|
### ❌ Repurposing Low-Performing Content
|
|
Wasting time on content that didn't resonate.
|
|
|
|
### ✅ Repurposing Winners
|
|
Focusing on proven, high-performing content.
|
|
|
|
---
|
|
|
|
### ❌ No Link Back to Original
|
|
Missing opportunity to drive traffic.
|
|
|
|
### ✅ Strategic Linking
|
|
Always linking back to pillar content.
|
|
|
|
---
|
|
|
|
### ❌ Overwhelming Audience
|
|
Posting too much repurposed content at once.
|
|
|
|
### ✅ Strategic Distribution
|
|
Spreading repurposed content over time.
|
|
|
|
---
|
|
|
|
## Repurposing ROI
|
|
|
|
### Measuring Success
|
|
|
|
**Metrics to track**:
|
|
- Total pieces created from one pillar
|
|
- Traffic to original content
|
|
- Engagement across formats
|
|
- Time saved vs. creating new
|
|
- Reach across platforms
|
|
|
|
**Example ROI**:
|
|
- 1 pillar blog post (4 hours)
|
|
- → 15 social posts (2 hours)
|
|
- → 1 infographic (1 hour)
|
|
- → 1 podcast episode (2 hours)
|
|
- → 5 short videos (2 hours)
|
|
- **Total**: 20+ pieces in 11 hours vs. 80+ hours creating from scratch
|
|
|
|
---
|
|
|
|
## Usage
|
|
|
|
Apply repurposing strategies to:
|
|
- Maximize content ROI
|
|
- Reach different audiences
|
|
- Maintain consistent posting
|
|
- Extend content lifespan
|
|
- Build content ecosystem
|
|
- Save time and resources
|
|
|
|
**Remember**: Repurposing isn't lazy—it's strategic. Your audience consumes content differently across platforms. Meet them where they are with the format they prefer.
|