rufuspollock
NoteOriginal issue: https://github.com/datopian/portals-monorepo/issues/524 (but this is the official source)
Situation:
- Finished old product overview and "quasi" roadmap in April/May.
- Since then have launched PortalJS.org, working on cloud etc
Complication
- Not clear current state and focus and next steps
Acceptance
- Have a list of products **✅2023-10-21 see **
- Clarity about which will be worked on now (in next 1-2Q) ✅2023-10-21 PortalJS Cloud, Flowershow Cloud and MarkdownDB
- Goals for those products **✅2023-10-21 see the spreadsheet - added objectives for all the main ones **
- Bonus: review naming and descriptions from previous product outline
- Bonus: list of achievements this year and in last 6m especially ✅2023-10-21
List of Products
Achievements
- Product roadmap: (March 2023) Product vision and roadmap - breakthough 🎉🚀 https://github.com/datopian/portals-monorepo/blob/main/docs/notes/product-plan-for-2023-jan-2023.md
- This was a breakthrough in clarity and introduced all the core terminology and concepts that we use going forward
- Created monorepo for all our portal frontend work https://github.com/datopian/portals-monorepo
- PortalJS.org: (May / June 2023) Identified our core stack and launched as an offer with new website and components.
- Flowershow: v2 release including switch to markdowndb and obsidian plugin
- DataHub.io: (March-April 2023) prototyped a next generation version of datahub.io based on PortalJS https://next.datahub.io/
- whilst not publicly launched this work informed PortalJS stack as well as development of markdowndb etc
- Flowershow Cloud: (exp Q4 2023) cloud offering of Flowershow publishing system for markdown based sites https://cloud.flowershow.app