Standup
Standup
Rising:
- Last: 🚀 Completed criteria 5 (Data Explorer component) https://github.com/datopian/next.datahub.io/issues/4
- Next: 🚩 does not have anything to work on atm
Rufus
- Last:
- Co-coding with Leo - see journal notes from yesterday
- Working on Planning Stream a lot - see https://github.com/datopian/next.datahub.io/commit/f4ec16cb94a738699d9065583267f681d2042af7
- Processed a whole bunch of the GDrive stuff
- Moved most of Product Vision doc into issue tree etc
- Next
- Working on Planning Stream
- Integrate all of old Product Vision in GDoc
- Working on Planning Stream
Rufus
- Working on Planning Stream
- Processed a whole bunch of the GDrive stuff
- Moved most of Product Vision doc into issue tree etc
NTS: are we over-complicating it? Issue tree seems a lot (and repeats itself with e.g. hypothesis tree)
- Can we prune a bit?
- What do we focus on?
Asides
Came across https://squidfunk.github.io/mkdocs-material/ - a nice documentation site. However, most interesting was the intriguing sponsorship model https://squidfunk.github.io/mkdocs-material/insiders/ whereby some stuff gets released to insiders early (and only gets released to everyone else when a certain funding goal is reached). pricing
Also interesting to see the list of alternatives https://squidfunk.github.io/mkdocs-material/alternatives/ - esp docz which is mdx based static publishing (https://www.docz.site)