Social Media Posting
Promise: 3x/week LinkedIn posting cadence held through Q2 2026 (June 30), with every post mapped to the active anchor moment.
Ongoing social media presence across Datopian's product portfolio. Primary focus is PortalJS Cloud on LinkedIn. Content maps to the monthly Anchor Moment; posting cadence is three times per week (Monday, Wednesday, Friday).
Plan of work
| Milestone / checkpoint | ETA | Expected outcome | Done | Completion date |
|---|---|---|---|---|
| May cadence | 2026-05-31 | 3x/week LinkedIn held, all posts mapped to May anchor moment | [ ] | |
| June cadence | 2026-06-30 | 3x/week LinkedIn held, all posts mapped to June anchor moment | [ ] | |
| Q2 review | 2026-06-30 | Cadence confirmed stable; any gaps noted and addressed for Q3 | [ ] |
Active Projects
- April LinkedIn carousel sequence — PortalJS Cloud
- Case studies
Why this exists
Datopian's products have no paid acquisition channel. Organic social is the primary lever for building visibility, credibility, and inbound interest. Without a consistent presence, each product remains invisible to the audiences most likely to become users or advocates.
Current priority
Hold the LinkedIn cadence and ensure every month's content has a clear anchor — no posting for the sake of posting.
Links
- Content calendar: https://www.notion.so/hblance/2fde1c5bccff8105b0b8eacaa830586d?v=2fde1c5bccff810e9dcf000c54d3729d
Notes
- Current cadence: 3x/week on LinkedIn
- Content should not close with sales intent — CTAs like "if your organisation faces similar challenges" signal sales intent and hurt organic reach.
- Channels in scope: LinkedIn (primary), Dev.to, Medium, Reddit, Bluesky, Hacker News, YouTube.
- Posting cadence depends on Anchor Moments being stable — if no anchor is defined for the month, social content loses its thread.
Recorded work and operating context — September 2026 scope review
- Content calendar automation: LinkedIn automation was recorded live for CKAN, Datopian and PortalJS; other channels/repurposing remained open. The dated source preserves the content/platform matrix, adaptation rules and canonical-URL guidance. Execution/evidence. Historical source.
