Notion Content Calendar: Properties Reference
Purpose: Quick reference for Notion database properties and their values Database: Content Calendar
π Property Definitions
Account (Select)
Purpose: Primary poster/owner of the content
Options:
- Robert
- Uttam
- Luke
- Greg
Usage: Set this to the person who will create/post the content
Linear issue (URL)
Purpose: Link each calendar row to exactly one Linear Marketing issue so sprint work, owners, and status stay traceable.
Rules:
- Required for every active row β create or paste the issue URL when the row represents real work (not scratch ideas you will delete the same day).
- Jadyn verifies during weekly Notion β vault sync; gaps block treating the row as ready for publish planning.
Platform (Select)
Purpose: Where the content will be published
Options:
- Newsletter
- Blog
- YouTube
Usage: Most weekly cadence posts are LinkedIn, but can expand to other platforms
Status (Select)
Purpose: Current stage in content workflow
Options (in workflow order):
- Idea - Initial concept, not yet structured
- Outline - Structure/outline created, ready to draft
- First Draft - Initial draft complete, needs review
- Design - In design/visual creation phase
- Approved - Ready to publish/schedule
Workflow: Idea β Outline β First Draft β Design β Approved
Topic Tags (Multi-select)
Purpose: Content categorization and themes
Options:
- Brand POV - Brand positioning and point of view
- Services versus Products - Service vs. product positioning
- Org Development - Organizational development topics
- Thought Leadership - Industry insights and perspectives
- B2B Services - B2B service-related content
- Data & AI - Data and AI topics
- Personal - Personal stories/reflections
- GTM - Go-to-market strategy and tactics
- Coaching - Coaching and development content
Usage: Select 1-3 tags that best describe the content topic
Pillars (Select)
Purpose: Content pillar/theme alignment with weekly cadence
Options:
- Service - Service-focused content (Monday/Tuesday)
- Build-In-Public - Behind-the-scenes, process, learnings (Wednesday)
- Partner - Partner features and collaborations (Thursday)
- Reflection - Weekly reflections and personal insights (Friday)
- Reaction - Ad-hoc/opportunistic content (as needed)
Mapping to Weekly Cadence:
| Day | Pillar | Account(s) |
|---|---|---|
| Monday | Service | Robert (primary), Uttam reposts |
| Tuesday | Service | Uttam (primary), Robert reposts |
| Wednesday | Build-In-Public | Robert or Uttam |
| Thursday | Partner | Robert or Uttam |
| Friday | Reflection | Robert and Uttam (both post) |
| Ad-hoc | Reaction | Any account |
StoryBrand Pillar (Select)
Purpose: StoryBrand Framework pillar for structuring content (primarily for Service posts)
Framework: Based on StoryBrand Framework by Donald Miller
Options:
- Character - The hero/customer (who the story is about)
- Problem - The challenge/obstacle the hero faces
- Guide - Brainforge as the guide/mentor
- Plan - The solution/process Brainforge provides
- Success - The positive outcome/transformation
- Failure - What happens if the problem isnβt solved
- Call-To-Action - The invitation to take action
Usage:
- Primarily used for: Service posts (Monday/Tuesday)
- Helps structure content according to StoryBrand narrative framework
- Each post can focus on one pillar or incorporate multiple
- See
storybrand-framework.mdfor Brainforgeβs common answers to each pillar
StoryBrand Framework Flow:
Character (customer) β Problem β Guide (Brainforge) β Plan β Success/Failure β Call-To-Action
π Typical Workflow
For Weekly Cadence Posts (LinkedIn)
-
Create entry in Notion calendar
- Set Date to posting day
- Set Account to primary poster
- Set Platform to LinkedIn
- Set Pillar based on day of week
- Set Status to Idea or Outline
- Add Topic Tags (1-3 relevant tags)
- Add Topic/Title in title field
-
As content progresses:
- Update Status: Idea β Outline β First Draft β Design β Approved
- Refine Topic Tags if needed
- Add Notes with context/requirements
-
When approved:
- Status = Approved
- Ready to publish/schedule
- Update vault
content-calendar.mdif needed
π Example Entry
For Monday Service-Focused Post:
Date: Monday, January 26, 2026
Account: Robert
Platform: LinkedIn
Pillar: Service
StoryBrand Pillar: Problem (primary focus)
Status: First Draft
Topic Tags: B2B Services, Data & AI
Title: "Solving the 'we don't know how many valid active users we have' problem"
Notes: Focus on fragmented data problem and process-centric approach
π― Quick Reference
Most Common Combinations:
Monday/Tuesday (Service Posts):
- Account: Robert or Uttam
- Platform: LinkedIn
- Pillar: Service
- StoryBrand Pillar: Problem, Guide, Plan, or Success (varies by post)
- Topic Tags: B2B Services, Data & AI, Services versus Products
Wednesday (Build in Public):
- Account: Robert or Uttam
- Platform: LinkedIn
- Pillar: Build-In-Public
- Topic Tags: Thought Leadership, Personal, Org Development
Thursday (Partner Feature):
- Account: Robert or Uttam
- Platform: LinkedIn
- Pillar: Partner
- Topic Tags: Partner-related, B2B Services
Friday (Reflections):
- Account: Robert and Uttam (separate entries)
- Platform: LinkedIn
- Pillar: Reflection
- Topic Tags: Personal, Thought Leadership, Reflection
π Related Files
content-calendar-mapping.md- Full mapping guideweekly-posting-cadence.md- Posting schedule detailscontent-calendar.md- Current calendar snapshotstorybrand-framework.md- Brainforgeβs StoryBrand workshop answers
Last Updated: [Date] Maintained By: GTM Team