Rufus Planning
Rufus Planning
Plan of work for DataHub Next
- How do we approach this? From a job story (achieve this outcome) or a more technical perspective (build this thing)?
- Had this discussion before with
- What is outcome vision for v1-pre1 and stages in between
- What is current v1 product goal?
Visions
-
datahub.io/@owner/repo/
renders README including relative links to data files- Key issue is handling the links to other files
- can render additional markdown files
- render existing data package stuff from github.com/datasets
- local wiki: can create data-rich
- ๐ avoids need for remote loading and processing issues. At most requires moving
Scratch
How do i build a markdown-x-plus-data site? What is the decision tree?
Including an answer to questions like:
- Why are we moving to server side rendering
- When do i use SSG vs SSR and why?ยงo
Decision tree items
- How technically sophisticated is the user?
- Do we want to upgrade the framework?
- Do i want to
Roughly 2 options
- Use a framework:
- ๐
- Markdown rendering: can have full MDX imports etc
- Upgrades will be a bit painful. That's life. That's what you see with all other frameworks
- SSG
- Use a "product" approach
- In this case the input has to be limited
- e.g. markdown in this structure is more limited
- can't import whatever you want: have a defined set of components
- e.g. markdown in this structure is more limited
- Server side render
- Why? Because
- ๐ live re-rendering
- In this case the input has to be limited