Meeting Anu and Rufus
Meeting Anu and Rufus
Refs: agenda-anu-rufus
Rufus brainstorm
A history of what has happened?
- Last major strategy document was March / April 2023
- Did PortalJS.org in May-Jul 2023 and then sort of stopped
- Aug-Sep: took over datahub.io to promote our DMS and open data portal offering
- 🔮 that wasn't very effective in generating leads …
- Sep-Oct: launched Flowershow cloud system in alpha
- Jan: reboot with Daniela and Ola etc.
- Jan-Mar: launch of DataHub Cloud v1-alpha
- Apr: Rufus steps out explicitly and hands over to Daniela
- we never really completed planning together at this point
- started trying to do hypotheses explicitly
Where are we going with the product?
- Common core of a 'markdown-based publishing'. I would actually call this Flowershow as in 'Put your X (data/content) on show.
3-4 options
- Dataset publishing tool
- PKM publishing tool: 'Flowershow Cloud'
- Marketplace
One option: try and launch one option every 1m with 2m marketing follow-up and see what happens
Brainstorm of options in detail
- Data publishing. "CMS for data"
- Full data catalog …
- Simple data publishing: paste and go. More substack-y. ghost-y
- Github for data. (Hugging face are going for this quite a bit)
- Data publishing framework.
- PKM publishing
- Data marketplace
- Data newsletter. The place to find interesting data.
- Data community
Emphasize the github side of things in general?
PortalJS work
Goal: good landing page with a way to book a demo
What is NOT needed …
- docs
- examples
- …
What have we achieved since DataHub v2 …
Are we discarding 8 months of work No, not all!
- Moved to Github + R2 backend 🎉🎉
- New simple rendering framework based on Flowershow / PortalJS
- Still using publishing and using for
Nagging questions
- Can we converge Flowershow and PortalJS. Having 2 different names / frameworks for roughly the same thing seems annoying. We could have that PortalJS builds on Flowershow but still seems awkward. Could have "Flowershow data" which is subpart especially for data …