Skip to main content

✍️ Content Creation Guide

This guide covers best practices for creating 60-second MongoDB educational episodes.

The 60-Second Format​

Every MongoDB Minute episode follows a structured 60-second format designed to deliver maximum value in minimal time.

Script Structure​

Section Breakdown​

1. Hook (0-5 seconds)​

Purpose: Grab attention immediately

Best Practices:

  • Start with a question or surprising fact
  • Use numbers or statistics when possible
  • Create curiosity or urgency
  • Avoid generic openings

Example:

"Did you know that most MongoDB performance issues come from just one missing index?"

2. Problem/Context (5-15 seconds)​

Purpose: Establish the problem or context

Best Practices:

  • Be specific, not generic
  • Relate to common developer pain points
  • Set up the solution clearly
  • Keep it concise

Example:

"When your queries are slow, it's often because MongoDB is scanning entire collections instead of using an index."

3. Tip/Solution (15-45 seconds)​

Purpose: Deliver the core educational content

Best Practices:

  • One clear, actionable tip
  • Show the solution, don't just describe it
  • Use simple language
  • Include a brief code example if relevant

Example:

"Create a compound index on the fields you query most. For example, if you filter by category and sort by date, create an index on both: db.products.createIndex({ category: 1, date: -1 })"

4. Quick Win/Proof (45-52 seconds)​

Purpose: Demonstrate the benefit or result

Best Practices:

  • Show the impact (faster queries, cleaner code, etc.)
  • Use concrete examples
  • Make it tangible

Example:

"This single index can reduce query time from 500ms to under 10ms."

5. CTA + Tease (52-60 seconds)​

Purpose: Drive engagement and preview next content

Best Practices:

  • Clear call to action (subscribe, like, comment)
  • Tease the next episode topic
  • End with energy

Example:

"Subscribe for more MongoDB tips! Next week, we'll cover how to optimize aggregation pipelines."

Writing Tips​

Keep It Simple​

  • Use everyday language
  • Avoid jargon unless necessary
  • Explain technical terms briefly
  • One concept per episode

Be Specific​

  • Use concrete examples
  • Include numbers and metrics
  • Show, don't just tell
  • Reference real scenarios

Stay Focused​

  • One tip per episode
  • Don't try to cover everything
  • Cut unnecessary words
  • Test timing while writing

Make It Actionable​

  • Give viewers something to do
  • Provide clear next steps
  • Include code examples when relevant
  • Link to resources

Episode Metadata​

Title Guidelines​

  • Clear and descriptive: "Optimizing MongoDB Queries with Compound Indexes"
  • SEO-friendly: Include key terms
  • Action-oriented: Use verbs when possible
  • Length: 40-60 characters ideal

Category Selection​

Choose the most relevant category:

  • Data Modeling: Schema design, relationships, embedding
  • Indexing: Index types, performance, optimization
  • Atlas: Cloud features, monitoring, backups
  • Vector & AI: Vector search, embeddings, AI integration
  • Atlas Search: Full-text search, relevance tuning
  • Aggregation: Pipeline stages, data transformation
  • Security: Authentication, authorization, encryption
  • Migration: Moving data, schema changes
  • New Features: Latest MongoDB capabilities

Difficulty Levels​

  • Beginner: No prior MongoDB knowledge required
  • Intermediate: Basic MongoDB experience helpful
  • Advanced: Deep technical knowledge required

Visual Suggestions​

Use the "Visual Suggestions" field to guide video production:

  • Screen recordings: What to show
  • Code examples: Which files or snippets
  • Diagrams: Visual aids to include
  • Animations: Transitions or effects

Example:

"Show MongoDB Compass query execution plan. Highlight the 'COLLSCAN' vs 'IXSCAN' difference. Use split screen to show before/after query times."

Add platform-specific URLs when videos are published:

  • YouTube: Full video URL
  • TikTok: Short-form video link
  • LinkedIn: Professional post link
  • Instagram: Reel or post link
  • X (Twitter): Tweet or video link

Quality Checklist​

Before submitting for review, ensure:

  • All 5 script sections are complete
  • Total script timing is ~60 seconds when read aloud
  • Title is clear and descriptive
  • Category and difficulty are appropriate
  • Visual suggestions are helpful
  • Social links are added (when available)
  • No typos or grammatical errors
  • Technical accuracy verified

Using AI Generation​

MongoDB Minute includes AI-powered episode generation:

  1. Click "AI Generate Episode" from the dashboard
  2. Provide a topic or prompt
  3. Review and edit the generated content
  4. Save and submit for review
AI Best Practices
  • Use AI as a starting point, not final content
  • Always review and edit generated scripts
  • Verify technical accuracy
  • Add your personal voice and style

Next Steps​

Once your episode is complete:

  1. Review your content using the checklist above
  2. Submit for technical review (see Workflow System)
  3. Make revisions if requested
  4. Get final approval
  5. Record your video
  6. Publish and share!