Promise: Datopian is visibly present in the CKAN ecosystem — coordinated comms around the 20th anniversary, and a consistent ongoing presence that reinforces Datopian's role as co-steward.


This initiative covers everything related to Datopian's public role in the CKAN ecosystem: community communications, milestone moments, thought leadership, and the 20th anniversary.

Plan of work

Dates are not finalised — this tracks the initiatives we are running or planning to run, not a locked schedule.

Milestone / checkpointETAExpected outcomeDoneCompletion date
Community Voices questionnaire sent to contributorsTBDResponses collected from key CKAN community members[ ]
Community Voices responses publishedTBDStories and reflections live on anniversary page[ ]
20th anniversary campaign liveTBDCoordinated content published across channels[ ]
Ongoing comms cadenceMonthlyAt least one CKAN-related post or article per month[ ]

Active Projects

CKAN 20th Anniversary (2026)

CKAN turns 20 in 2026. Planned initiatives:

  • Community Voices — questionnaire collecting stories and reflections from people who built, shaped, and championed CKAN. Responses to be published on the anniversary page. Questionnaire doc
  • Anniversary page — a dedicated page preserving the project's history and community voices
  • Campaign content — coordinated posts across channels marking the milestone

Ongoing comms

  • Regular CKAN-related posts and articles reinforcing Datopian's co-stewardship role

Why this exists

CKAN is foundational to Datopian's credibility and positioning. Datopian's association with CKAN is one of its strongest trust signals — but it is underleveraged in marketing. Active co-stewardship communications strengthen Datopian's standing in the open data community, reinforce trust with institutional buyers, and create natural content moments throughout the year.

Current priority

Plan and execute comms around the CKAN 20th anniversary — the highest-visibility moment this initiative will have in 2026.

Notes

  • CKAN must never be positioned negatively. Messaging must attribute infrastructure cost/complexity problems to infrastructure models, not CKAN itself.
  • The 20th anniversary is a rare earned-media and community moment — plan early, coordinate with the broader CKAN community, not just Datopian.
  • Comms should reinforce Datopian's role as builder and steward, not just a vendor that happens to use CKAN.
Built with LogoFlowershow