You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to restructure the website as a quarto website. That way we can improve the UX over how things appear in GitHub md docs, and generally make the site more approachable. We could eventually also add things like a shinylive-based dataset explorer (both for each dataset and for finding datasets). Most importantly, though, we could move the datasets to releases, and make it much more possible for contributors to clone the repo without breaking their machines.
Some requirements:
We can't break old code. TidyTuesday is used for examples, assignments, gists, etc. We need to leave a sentinel behind for any CSVs that we delete, ideally in a way that readr::read_csv() will continue to work, if possible.
The new site can't require any extra work to build (ie, it needs to be all GHA-based, without manual moving of files or anything like that on a weekly basis).
One option I've considered is archiving this repo and starting a new repo in the dslc-io org. If we do that, we need to ensure that {tidytuesdayR} is ready (on CRAN) for the changeover, and we need to have a clear strategy to make sure nobody gets lost.
The text was updated successfully, but these errors were encountered:
I would like to restructure the website as a quarto website. That way we can improve the UX over how things appear in GitHub md docs, and generally make the site more approachable. We could eventually also add things like a shinylive-based dataset explorer (both for each dataset and for finding datasets). Most importantly, though, we could move the datasets to releases, and make it much more possible for contributors to clone the repo without breaking their machines.
Some requirements:
readr::read_csv()
will continue to work, if possible.One option I've considered is archiving this repo and starting a new repo in the dslc-io org. If we do that, we need to ensure that {tidytuesdayR} is ready (on CRAN) for the changeover, and we need to have a clear strategy to make sure nobody gets lost.
The text was updated successfully, but these errors were encountered: