Content Calendar
1. Updated Major Feature Clusters
A. Vision: Home for Indie Data Publishers
- Best place to publish data (free + paid)
- Markdown-native
- Structured, discoverable
- Multi-author publications
B. Author & Publication Layer
- Multi-author support
- Publisher profiles
- Avatars (Gravatar + generated)
- Clean publication pages
C. AI-Native Publishing Layer (NEW Major Arc)
- Official DataHub CLI
- Well-documented publishing API
- Token-based authentication
- Agent-ready endpoints
- CI/CD publishing
- Scriptable workflows
Framing:
“Programmatic publishing for data.”
D. Monetisation Layer (End of March)
- Paid publications
- Paid datasets
- Subscription tiers
- Publisher dashboards
2. Revised Timeline (Now → End of March)
Late February — Vision & Foundations
Post 1 “DataHub: The Home for Indie Data Publishers”
Post 2 “Multi-Author Publications Are Live”
Post 3 “Markdown-First Data Publishing”
Goal: establish platform legitimacy.
Early March — AI-Native Publishing Launch
This becomes a distinct mini-launch arc.
Post 4
“Introducing the DataHub CLI”
Content:
datahub publish dataset.csv- Works from terminal
- Works in GitHub Actions
- Works in scripts
Post 5
“DataHub API: Programmatic Data Publishing”
Content:
- REST endpoints
- Metadata schema
- Example curl
- Example Python snippet
- Token auth
Post 6
“Let AI Publish to DataHub”
Content:
- Example: agent generates dataset
- Agent publishes via API
- Automated update workflow
- Use cases: daily stats, market feeds, research bots
This sequence creates technical credibility before monetisation.
Mid-to-Late March — Payments Arc
Post 7
“Subscriptions for Data Are Coming”
Preview:
- Paid datasets
- Subscriber-only access
- Revenue model for data publishers
Post 8
“Earn Recurring Revenue From Your Data”
Launch post.
This sequencing matters:
AI publishing → then AI can publish paid data → then recurring revenue.
3. Why AI Before Payments Makes Sense
- Establishes DataHub as infrastructure, not just a site.
- Attracts technical publishers early.
- Creates automation use cases.
- Makes monetisation feel like a natural extension.
- Differentiates from Substack before you compete on pricing.
It signals: this is not a clone — this is programmable.
4. Optional: Tactical Framing for AI Posts
Keep tone consistent with overall vision. For example:
- “Substack for Data — Now With a CLI”
- “Publishing Data Without a Browser”
- “Automate Your Data Publication”
No need to reposition the whole brand.