Use the existing Quarto site as the main website.
pecanproject.github.io/betydata should replace and eventually map to betydb.org. The main page should be a landing page for BETY data, not a package-reference page. This project is data first, so the first thing users see should be an overview of the dataset, what replaced the old BETYdb site, and where to find tables, schema, policy, and provenance information.
Pull in design elements and content from betydb.org home page (if we bring in sponsors we will need to add many), logo, perhaps font and colors, enough to pay homage to and retain 'brand recognition' of the original. BUT, we should de-emphasize the bioenergy part, since the db scope has expanded greatly, and link to PEcAn.
Package documentation can live within that same site, for example under /package/ or /betydata-package/, but it should not be the primary landing page. Some users will care most about the CSV tables and data documentation rather than the R package itself.
I could imagine a site structure like this:
- Home: BETY data overview, what this site replaces, key entry points
- Data: tables, schema / join map, constraints, data policy, provenance / snapshots
- Package: installation, quick start, vignettes, exported dataset documentation
- Contribute: corrections, verification workflow, and future ingest tools
If it becomes useful later, we could add pkgdown-style reference pages as part of the broader site, but I would not make pkgdown the main website.
Use the existing Quarto site as the main website.
pecanproject.github.io/betydatashould replace and eventually map tobetydb.org. The main page should be a landing page for BETY data, not a package-reference page. This project is data first, so the first thing users see should be an overview of the dataset, what replaced the old BETYdb site, and where to find tables, schema, policy, and provenance information.Pull in design elements and content from betydb.org home page (if we bring in sponsors we will need to add many), logo, perhaps font and colors, enough to pay homage to and retain 'brand recognition' of the original. BUT, we should de-emphasize the bioenergy part, since the db scope has expanded greatly, and link to PEcAn.
Package documentation can live within that same site, for example under
/package/or/betydata-package/, but it should not be the primary landing page. Some users will care most about the CSV tables and data documentation rather than the R package itself.I could imagine a site structure like this:
If it becomes useful later, we could add pkgdown-style reference pages as part of the broader site, but I would not make pkgdown the main website.