Developer Docs for new DataHub components (WIP)

[rufuspollock]

If i am writing a component to go into DataHub Cloud or Selfhosted page ...

What information/variables do i have access to?

Example for motivation (or root page of a project):

• A component that displays a count of the number of files in this project
• Creating the "network map" that obsidian has i.e. all the files link to / from this file
  • It needs the links and back_links attribute for this file (if they exist) with names and urls of those items
• create a file listing on the project root page or each "directory" page
  • requires the tree or at least the tree to one level down from this
• displays all the images in this repo in a nice gallery ...
  • requires the tree for this repo with file types

Assumptions:

• no more than 100-1000 files in the repo (no massive repos!)

Questions

• What backend data/metadata is made available to components in the page?
• If we want a "plugin" architecture we want to have a standard way to pass info
  • Could differ depending on the type of plugin

How do i customize / enhance DataHub (Cloud) pages?

• Create new components
• Create new layouts
• Custom css for my site ...
• Setting the config
• Create new markdown plugins especially for "special" backtick sections e.g. a csv or a view section or something ... ❌ (ignore for now)
  • NB: i suspect most of these should basically be converting to inputs to a component so this just a "remark" wrapper around the first item.