content-calendar-mapping

Content Calendar: Notion to Vault Mapping

Purpose: Connect Notion content calendar database to vault for agent access Notion Database: Content Calendar Status: Active - Team-wide content planning database

---

🎯 Overview

This is a team-wide content calendar database in Notion that tracks:

• Content topics and themes
• Posting schedule
• Primary and secondary posters
• Content status (planned/draft/published)
• Post performance (if tracked)

Goal: Make this calendar accessible to agents so they can:

• Generate content drafts based on scheduled topics
• Check what’s coming up in the calendar
• Reference posting cadence and themes
• Track content performance

---

📅 Weekly Posting Cadence

Current Cadence (10 posts/week target)

Day	Content Theme	Primary Poster	Secondary Action
Monday	Service-Focused Post	Robert	Uttam reposts
Tuesday	Service-Focused Post	Uttam	Robert reposts
Wednesday	Build in Public	Robert or Uttam	Other account reposts
Thursday	Partner Feature	Robert or Uttam	Other account reposts
Friday	Weekly Reflections	Robert and Uttam	Both post individually

See: weekly-posting-cadence.md for detailed cadence documentation

---

🔗 Notion Database Structure

Database ID

• Notion URL: https://www.notion.so/brainforge/2ef7908b126880d5ae42d7f8d8ff9393
• Database ID: 2ef7908b126880d5ae42d7f8d8ff9393

Database Properties

Actual Notion Database Properties:

1. Account (Select)

   • Options: Robert, Uttam, Luke, Greg
   • Purpose: Primary poster/owner of the content

2. Platform (Select)

   • Options: LinkedIn, Newsletter, Blog, YouTube
   • Purpose: Where the content will be published

3. Status (Select)

   • Options: Idea, Outline, First Draft, Design, Approved
   • Purpose: Current stage in content workflow

4. Topic Tags (Multi-select)

   • Options: Brand POV, Services versus Products, Org Development, Thought Leadership, B2B Services, Data & AI, Personal, GTM, Coaching
   • Purpose: Content categorization and themes

5. Pillars (Select)

   • Options: Reflection, Partner, Build-In-Public, Service, Reaction
   • Purpose: Content pillar/theme alignment

6. StoryBrand Pillar (Select)

   • Options: Character, Problem, Guide, Plan, Success, Failure, Call-To-Action
   • Purpose: StoryBrand Framework pillar for structuring content (primarily for Service posts)
   • Framework: Based on StoryBrand Framework by Donald Miller
   • See: storybrand-framework.md for Brainforge’s common answers

Additional Properties (likely also in database):

• Date - When to post/publish
• Title/Topic - Content headline or topic
• Notes - Additional context or requirements
• Linear issue (URL) — Required for each row that represents real sprint work; links the row to Linear Marketing. See notion-properties-reference.md.

Mapping to Weekly Cadence:

• Pillars map to weekly themes:
  • Service → Monday/Tuesday Service-Focused Posts
  • Build-In-Public → Wednesday Build in Public
  • Partner → Thursday Partner Feature
  • Reflection → Friday Weekly Reflections
  • Reaction → Ad-hoc/opportunistic content

---

📂 Vault File Structure

Primary Location

• File: knowledge/sales/content/content-calendar.md — current/upcoming content snapshot
• Purpose: Agent-readable snapshot of calendar (updated weekly or as needed)

Supporting Files

• File: knowledge/sales/content/weekly-posting-cadence.md — posting schedule and themes
• File: knowledge/sales/content/content-themes.md — theme definitions and guidelines (create if needed)
• File: knowledge/sales/content/posting-guidelines.md — best practices and requirements (create if needed)

---

🔄 Sync Process

Option 1: Manual Weekly Sync (Recommended for now)

Frequency: Weekly (Monday morning)

Steps:

1. Open Notion content calendar database
2. Filter for upcoming week (or next 2 weeks)
3. Export or copy relevant entries
4. Confirm every copied row has a Linear issue URL in Notion — create/link Marketing issues if missing
5. Update knowledge/sales/content/content-calendar.md with:
   • Date
   • Account (primary poster)
   • Platform
   • Pillar (theme)
   • Topic Tags
   • Status
   • Topic/Title
   • Linear issue (full URL from Notion)
   • Any special notes

Format for content-calendar.md:

# Content Calendar - Week of [Date]
 
## Monday, [Date]
- **Account**: Robert
- **Platform**: LinkedIn
- **Pillar**: Service
- **StoryBrand Pillar**: Problem (or other pillar)
- **Topic Tags**: [B2B Services, Data & AI]
- **Status**: First Draft
- **Topic**: [Topic from Notion]
- **Linear issue**: https://linear.app/brainforge/issue/MKT-###
- **Notes**: [Any special requirements]
 
## Tuesday, [Date]
- **Account**: Uttam
- **Platform**: LinkedIn
- **Pillar**: Service
- **Topic Tags**: [Services versus Products]
- **Status**: Outline
- **Topic**: [Topic from Notion]
...

Status Mapping:

• Idea → Planned/early stage
• Outline → Planned with structure
• First Draft → Draft ready for review
• Design → In design/visual creation
• Approved → Ready to publish

Pillar to Weekly Cadence:

• Service → Monday/Tuesday (Service-Focused Posts)
• Build-In-Public → Wednesday
• Partner → Thursday
• Reflection → Friday (Weekly Reflections)
• Reaction → Ad-hoc content

Option 2: Notion API Integration (Future)

If using Notion API:

• Query database weekly via API
• Auto-update content-calendar.md
• Can be automated with agent or script

Notion API Setup (if needed):

1. Create Notion integration
2. Grant access to content calendar database
3. Use database ID: 2ef7908b126880d5ae42d7f8d8ff9393
4. Query with filters for upcoming dates

---

🤖 Agent Usage

Content Agent Access

Agents can read:

• knowledge/sales/content/content-calendar.md — see what’s scheduled
• knowledge/sales/content/weekly-posting-cadence.md — posting rhythm
• knowledge/sales/content/content-themes.md — theme requirements (if present)

Agents can help with:

• Generating drafts based on scheduled topics
• Checking calendar for upcoming content needs
• Suggesting topics based on cadence
• Drafting posts aligned with themes

Example Agent Prompt:

"Check the content calendar for next week and draft a Service-Focused post 
for Monday's slot. Primary poster is Robert."

---

📝 Next Steps

Immediate (This Week)

• Review Notion database structure and document actual properties
• Create initial content-calendar.md snapshot (next 2 weeks)
• Document content themes in content-themes.md
• Set up weekly sync reminder/process

Short-term (This Month)

• Test Content Agent with calendar-driven drafts
• Refine calendar format based on agent usage
• Document posting guidelines

Long-term (Future)

• Consider Notion API integration for auto-sync
• Add content performance tracking
• Build agent workflow for calendar-driven content creation

---

📚 Related Files

• weekly-posting-cadence.md - Detailed posting schedule
• content-themes.md - Theme definitions (create if needed)
• ../agents/memory/positioning.md - Messaging for content
• ../agents/memory/message-templates.md - Post templates

---

Last Updated: [Date] Maintained By: GTM Team Sync Frequency: Weekly (Monday mornings)