- ➕2024-03-29 https://github.com/datasets/awesome-data/issues/330
- ➕2024-03-26 alphabetically sort my orgs and repos
- ➕2024-01-11 back-post introducing datahub pages to datahub.io/blog for Feb 7 2022 (when we had this).
- Why bother? This is now old and depends on things that have now moved.
- Turn this into a blog post: https://github.com/datopian/portaljs/discussions/899
Ideas
Asides: shaping our messaging in broader "data portal" space
Promoting our headless approach: we should talk/write about this constantly. This is what "DataHub/PortalJS" has become.
Hypothesis: promoting our approach to building (CKAN-based) DMS using a decoupled approach … Would reap dividends …
=> Qu: what would you call this product.
Ans: atm we call this PortalJS + CKAN and implement it with PortalJS + CKAN. Can we get a simpler name?
=> How do we market this?
Start focused, consistent messaging about approach we are taking with decoupled frontend
Over last 5y+ we have been developing an innovative approach to creating XXX it provides these benefits
- Unified data experiences
- Decoupled approach implies easier and faster to customize
Example discussion:
- Client arrives wanting a CKAN Data Portal
- We say absolutely and we can use our DataHub [Portal] tech that integrates with CKAN to give you a next generation frontend with these features …
