Each report will need a markdown page as in pages/2024-12-04-report.md
that will serve as the shell
page for the report with an include that points to a file in pages/includes
,
such as pages/includes/2024-12-04-report.html
. To make a new report that is its own page,
you need to follow these (currently manual) steps:
- Update the reference date in the
src/report.Rmd
file and render the file as an html fragment. - Copy the rendered html fragment in
src/report.html
topages/includes/YYYY-MM-DD-report.html
, whereYYYY-MM-DD
is the reference date. - Copy an existing markdown page such as
pages/2024-12-04-report.md
topages/YYYY-MM-DD-report.md
and point the included file in that document to the html fragment from step 2. - Edit the
site-config.yml
to add a newtext
andhref
field at the top of themenu:
header, following the format of the other entries that are there, for theYYYY-MM-DD
that you have built. - Test out the build locally. (See instructions below)
- If the site looks good, submit a PR to the repo and this should trigger a rebuild of the site.
You might want to build the site locally to test out whether the changes you made have worked. You will need to have Docker installed to do this.
- Run the following command in a terminal to install the site builder tool:
docker pull ghcr.io/hubverse-org/hub-dash-site-builder:main
- Navigate to the root directory of this repo in a terminal window.
- Run the following command in a terminal window:
docker run --platform=linux/amd64 --rm -ti -v "$(pwd)":"/site" ghcr.io/hubverse-org/hub-dash-site-builder:main bash render.sh
- Open the file
pages/_site/index.html
in a web browser.
Any new commit will cause the website to rebuild. If you don't have a commit to make you can open a new issue and then add a new comment on an issue with the words
/hub build site
Further instructions about how the hubdashboard app works can be found at the app website.
Build progress can be monitored at the hub-dashboard-control-room Actions page.