Project: Consolidate the Analysis (Vision & Plan) - 2022-02-01
Project: Consolidate the Analysis (Vision & Plan) - 2022-02-01
Closing: 2022-03-14
- Most stuff processed out of GDrive etc to here or other relevant location (e.g. SCQH spreadsheet)
- Have a clear outline in pages plus starting projects in e.g. pages-v0.1.0-readme-with-csv-table-preview and website-next-datahub-plus-pages-v0.1
- 💡 focus on what is needed right now and create projects
Also processed all unchecked tasks here out to inbox or elsewhere.
Insights
💡 Insights
- Create focus: key docs are about what we are doing now …
- Separate definition of what we are doing and how from why and context =>
- PRODUCT focuses solely on current product
- Context issue tree / scqh should be in background / business case or something
- hypothesis tree re current MVP should be where ???
- That said do we want some essential motivating context? aka "start with why"?
- Let's just experiment and see … 🙂
Plan
Purpose: have one path into project going from top level vision to concrete plan
- consolidate the materials we have
- start point: top level scqh etc
- create a plan at top level
- detailed next steps plan
Outcome visioning: main README is starting point for the project and there is a clear path (or tree) to drill down into the project (or drill-up to get an overview) in 2 key directions: PRODUCT and PLAN. That is we have:
- README (entry point with links) Largely done b/c very simple
- pages ✅2022-02-18 have a fairly complete product doc
- BONUS: business-case.md background
- product-commentary
- PLAN
- ARCHITECTURE
Brainstorm & Organizing
- Collect a list of all the existing documents ✅2022-02-17 SEE BELOW
- Review and process all meeting docs in Gdocs as of 2022-02-15 ✅ in inbox below and processing done
- Review journal stuff in this docs repo
- Review GDrive
- Collect all docs ✅ see list below
- Process old tech inbox
- Process new project folder: https://drive.google.com/drive/folders/1-vaIJglTNUZMG04ZBPBuDVpxQtIv539r
- Process all docs ✅2022-02-18 DONE
- Collect all docs ✅ see list below
- Finalize main issue tree: https://docs.google.com/spreadsheets/d/1sprrkUeMRa3nrma4HvY_k-T0zGYttXJikqe9XPPmSiA/edit#gid=772392380 ✅ completed on 4 Feb
- Create the root README with the materials we already have (do we migrate from google docs) ✅ started on the root README 2022-02-15
- What is current SCQH and its state? 🔑 Old Feb 2021 brainstorm that is unfinished
- Do we need a proper SCQH for DataHub Pages? 🔑 Rufus would say no for now. We don't need it now => leave creating an SCQH
- What is the current consolidated plan of work? ✅ have a clear outline in pages plus starting projects in pages-v0.1.0-readme-with-csv-table-preview and website-next-datahub-plus-pages-v0.1
Workspace
Inbox of Existing Docs
Journal
- 2022-02-14 - lots to process here …
- 2022-01-31 ✅ merged
GDocs Meetings
- 4 Feb meeting incl Hypothesis Tree sketch in GDocs 👍👍 ✅ Moved to pages
- Hypothesis tree
- 2 Feb 2022 - team coordination (not much) ✅ merged everything in (mainly to README)
- 31 Jan 2022 meeting notes ✅ merged content here in various locations including that day's journal 2022-01-31
GDrive Docs
- Product Vision (GDoc)
- Move all issue tree type stuff to issue tree and answer there
- Integrate vision into pages (where aligned) OR archive somewhere e.g. product-commentary ✅2022-02-18 merged in
- Landing Page Copy (GDoc)
- Value Proposition Analysis (GDoc) ✅2022-02-18 listed in Job Stories Value Proposition and don't think crucial to process further right now
- Datopian Product Issue Tree / Hyp Tree incl DataHub [ACTIVE]
- Review each sheet in spreadsheet and identify if any actions
- DataHub Pages Cloud Architecture ✅ in pages-architecture
- [DEP] DataHub Next Product Vision [Feb 2021] - listed as DEP but still has content
- portal.js branding ✅ moved to portaljs
- MVP outline in appendix (feb 2021) ✅ moved to 2021-02-03
- Appendix: Rufus notes [Feb 2021] - basically a feature list ✅ merged to feature tree https://coggle.it/diagram/YgpxWTL-yUb82LfW/t/datahub-pages-feature-tree
- SCQH https://docs.google.com/document/d/1NTOSbHKH6DGVZB65v3GXD0pm46tnLlShgPRZNU_y4S4/edit#heading=h.wrg7mhcad0bp (old brainstorm only DataHub SCQH from july 2020) ✅ WONTFIX for now as 🔽 LOW priority
Old (Feb 2021) DataHub Product Vision and Plan
- https://tech.datopian.com/datahub/v3/ ❓ could move into here but why bother? (would be good-ish practice. alternative is back-publish/blog
- gitlab.com/datopian/core/tech/datahub/ - PLAN etc
Lower priority
- DataHub Next vs Vercel - Feb 2021 by Anu - 2.5 pages with a few ideas (nothing super crucial) - brainstorm by Anu about what we can learn from Vercel in Feb 2021 ✅ MOVED to journal 2021-02-21
- DataHub Product Options and Evolution - good diagram with useful context on high level product evolution. Fits with next item. Could probably go to product context or commentary for now.
- The Data Value Journey re DataHub Pages - this is basically business case / product context showing where DataHub Pages fits in the overall value journey
- What framework do we use for frontend of DataHub (and CKAN v3)? (Next.js or Express.js) - Feb 2021 - mainly an analysis by Rising (and Rufus). Not that important right now. ✅2022-02-17 WONTFIX
- CKAN Next Gen 🖌️ - diagram with a few screenshots of what a next gen showcase page could look like with a layout sketch. 💬 suggest this goes into a page with ideas for showcase page ✅ merged to ../notes/dataset-showcase
- https://coggle.it/diagram/XwM2fshG0AglV4rq/t/datahub-job-stories-focused-on-the-power-users (Feb 2021) - list of job stories in coggle form ✅2022-02-18 moved into Job Stories Value Proposition
- Even older git-based datahub vision (2020) - https://github.com/datopian/datahub-git-based **✅ MOVED to product-commentary
Product ✅ moved to pages
Core offer: elegantly present your data - fast, easy and repeatable
Self-service: you add DataHub Pages (portal.js template) to your repo and self-publish on your deployment platform of choice (e.g. vercel, netlify etc)
Cloud: DataHub Pages in our cloud, you just integrate your GitHub repo in a couple of clicks … and have your data turned into a beautiful site that updates on every push**
