How to adapt the Content Creator OS for your channels, audience, team size, and publishing workflow.
1. Solo Creator vs. Content Team
2. Adding or Removing Channels
3. Integrating with Publishing Platforms
4. Content Repurposing Workflow
5. Tracking Revenue & Sponsored Content
7. Publishing Cadence Strategies
The system is built for solo creators by default. No changes needed — all the "Author" fields default to you.
Quick wins for solo use:
1. Add an "Author" Relation pointing to a new "Team Members" database with: Name, Role (Writer / Editor / Social Manager / SEO), Expertise Areas.
2. Add an "Editor" Relation on Blog Posts for the review step.
3. Create author-specific views: Filter by Author = [name] on each database.
4. Add a "Review Status" property to Blog Posts: Pending Review / Changes Requested / Approved.
5. Create an "Assignments" board view grouped by Author → see workload balance.
1. Separate databases per client or content vertical.
2. Add a "Client" Select property to all databases.
3. Create a "Content Briefs" database for assignment specifications.
4. Add "Due Date" (internal deadline) separate from "Publish Date" (external deadline).
5. Track time spent per content piece with a "Hours Spent" Number property.
1. Add "YouTube" to the Channel Multi-select options.
2. Add these properties to the Editorial Calendar (or create a separate "Videos" database):
3. Create a "Video Production" Board view: Script → Recording → Editing → Thumbnail → Upload → Published.
1. Add "Podcast" to channels.
2. Add properties: Episode Number, Guest Name, Recording Date, Edit Status, Show Notes URL, Downloads.
3. Create a "Podcast Pipeline" board view: Planning → Guest Booked → Recorded → Edited → Published.
If you don't do social media:
1. Keep the Social Posts database but don't actively use it.
2. Remove social-related views from your dashboard.
3. Remove "Social Promoted" checkbox from Blog Posts.
4. Focus your Editorial Calendar on Blog + Newsletter only.
1. Add properties to Blog Posts: "Cross-posted to dev.to" (Checkbox), "dev.to URL" (URL), "dev.to Views" (Number).
2. Add a step to your publishing workflow: after blog publish, cross-post within 24 hours.
3. Track cross-post performance in the Content Analytics database with Channel = "dev.to".
1. Add a "Ghost Status" Select to Blog Posts: Draft / Scheduled / Published.
2. Add a "Ghost URL" URL property for the published post URL.
3. Automation: Use Ghost's webhook on post.published → Zapier → Update Notion Blog Posts status to "Published".
1. Add a "WordPress ID" Number property for the post ID.
2. Add a "WordPress URL" URL property.
3. Automation: WordPress → Zapier → Notion API. Trigger on post publish.
1. The Newsletter Issues database already tracks everything Substack provides.
2. After each send, manually update: Open Rate, Click Rate, Unsubscribes, Subscriber count.
3. Automation: Substack doesn't have native webhooks, but you can use their API or manual CSV export.
1. Add URL properties per platform on Blog Posts.
2. Cross-post within 24-48 hours of original publish.
3. Always set canonical_url to your main blog to avoid duplicate content SEO penalties.
High-performing content should be repurposed across channels. Here's the workflow:
| Original Format | Repurpose To | Effort |
|---|---|---|
| Blog post (2000+ words) | Twitter/X thread (key takeaways) | 30 min |
| Blog post | LinkedIn post (personal angle) | 20 min |
| Blog post | Newsletter feature | 15 min |
| Blog post | dev.to cross-post | 10 min (reformatting) |
| Blog post | YouTube video (tutorial) | 4-8 hours |
| Twitter thread (viral) | Blog post (expanded) | 2-4 hours |
| Conference talk | Blog post (transcript + cleanup) | 2 hours |
| Newsletter edition | Twitter thread (highlights) | 20 min |
1. Add a "Repurposed From" Relation on the Editorial Calendar (self-relation) to link repurposed content to originals.
2. Add a "Repurpose Score" formula (see formulas/FORMULAS.md) that flags high-performing content not yet repurposed.
3. Create a "Repurpose Opportunities" view: Filter where Repurpose Score is high AND content hasn't been repurposed.
4. Use the Editorial Calendar status "Repurposed" for derivative content.
The Newsletter Issues database already has Sponsor and Revenue fields. Extend it:
1. Create a "Sponsors" database: Sponsor Name, Contact Email, Rate (per issue), Contract Start, Contract End, Issues Sponsored (Relation → Newsletter Issues), Total Revenue (Rollup).
2. Add a "Sponsored" Checkbox to Social Posts for paid promotions.
3. Track total revenue per month with a formula or manual summary.
1. Add an "Affiliate Links" database: Product Name, Affiliate URL, Platform, Commission Rate, Clicks (monthly), Revenue (monthly).
2. In Newsletter Issues and Blog Posts, add a "Contains Affiliate Links" Checkbox.
3. Track which content drives the most affiliate revenue.
If you sell digital products or courses:
1. Add a "Conversions" Number property to Blog Posts and Newsletter Issues.
2. Track which content drives the most sales.
3. Add "Conversion Goal" Select: Newsletter Signup / Product Purchase / Course Enrollment / Consultation Booking.
1. List your top 3 areas of expertise.
2. Identify 2-3 audience pain points you can address.
3. Cross them to find 4-6 pillar themes.
4. Each pillar should have enough depth for 10+ pieces of content.
Frontend Developer:
DevOps / Platform Engineer:
Data Engineer:
Mobile Developer:
To change your pillars:
1. Edit the Content Pillar Select property on all databases (Editorial Calendar, Blog Posts, Content Analytics).
2. Re-categorize existing content to the new pillars.
3. Update your Content Style Guide page.
4. Plan 2-3 seed pieces for each new pillar.
| Channel | Frequency | Time Commitment |
|---|---|---|
| Blog | 2x per month | 8-12 hours/month |
| Social | 3x per week | 3 hours/month |
| Newsletter | Monthly | 2 hours/month |
| Total | 13-17 hours/month |
| Channel | Frequency | Time Commitment |
|---|---|---|
| Blog | Weekly | 16-24 hours/month |
| Social | Daily | 5-8 hours/month |
| Newsletter | Bi-weekly | 4 hours/month |
| Total | 25-36 hours/month |
| Channel | Frequency | Time Commitment |
|---|---|---|
| Blog | 2x per week | 32-40 hours/month |
| Social | 2-3x daily | 10-15 hours/month |
| Newsletter | Weekly | 8 hours/month |
| YouTube | Bi-weekly | 16-24 hours/month |
| Total | 66-87 hours/month |
Key insight: Start at the Beginner level. Only add channels when you can sustain consistent quality. Inconsistent posting is worse than less frequent but reliable publishing.
Blog publish → Social promotion:
Newsletter send → Analytics update:
Monthly analytics import:
For developers who want more control:
# Pseudocode: Weekly content summary
1. Query Blog Posts database → count by status
2. Query Social Posts database → sum engagement metrics for published posts this week
3. Query Newsletter Issues database → get latest issue's open/click rates
4. Generate a summary and post it to your dashboard page or Slack
1. Batch your content creation. Write 2-3 blog outlines on Monday, draft on Tuesday-Wednesday, edit on Thursday, publish on Friday. Don't context-switch between creation and editing.
2. Review analytics monthly, not daily. Daily analytics checking is a productivity killer. Set a monthly review date and make data-driven decisions at that cadence.
3. Kill underperforming content pillars. If a pillar consistently gets low engagement after 5-6 pieces, replace it. Don't force content your audience doesn't want.
4. Repurpose your top 20%. Most of your traffic will come from 20% of your content. Repurpose those winners aggressively. Let the rest serve as SEO long-tail.
5. Build in public. Share your content metrics, experiments, and learnings. Your audience loves transparency, and it creates a meta-content pillar for free.
*Questions? Contact [email protected]*
Get the full Content Creator OS for Devs and unlock everything.
Get the complete guide with every chapter unlocked, including code samples, diagrams, and best practices.
Access all interactive tools with complete data, all workload profiles, and the full scenario library.
Downloadable source code, configuration files, and working examples from every chapter.
Free updates for life. Every new chapter, tool, and improvement included.