Devise a way to keep the gh-pages branch up to date

We should figure out how we want gh-pages to work:

• should it have the same contents as the "parent" repository? if so, we should find a way to keep the README.md and dependent files (i.e. artifacthub-repo.yml, CONTRIBUTING.md, LICENSE, etc.) up to date
  • we should be aware that oftentimes relative links will break
• should it be a completely separate / dedicated site? if so, how do we ensure that it is easy / sane to build / that information stays up to date?
  • Need to ensure index.yaml and artifacthub-repo.yml stay up to date

For reference, paired PRs (#36, #39)

To do:

• investigate possibilities
• decide on a direction
• implement automation to ensure that the gh-pages branch can easily be monitored / kept up to date

Review paired PRs #36 and #39, then compare the gh-pages branch with the parent repository and the listed files, including README.md, artifacthub-repo.yml, CONTRIBUTING.md, LICENSE, and index.yaml. Decide whether gh-pages mirrors the parent or is a dedicated site, accounting for relative links. Done means a direction is chosen and automation is implemented to keep the branch up to date and monitorable.