Adding article with links to old website versions

[ddsjoberg]

@cicdguy this PR adds an article with links to older versions of the website
This is not ready for merging and is a Draft PR.

• The "Version" dropdown menu needs to be updated with a link to this article's location. I think we discussed the dropdown including "Dev, Release, Prior Releases". I am not sure where this menu is being populated, but would probably be simplest to merely add it to the _pkgdown.yml ?

Thank you for your Pull Request! We have developed this task checklist from the Development Process Guide to help with the final steps of the process. Completing the below tasks helps to ensure our reviewers can maximize their time on your code as well as making sure the admiral codebase remains robust and consistent.

Please check off each taskbox as an acknowledgment that you completed the task or check off that it is not relevant to your Pull Request. This checklist is part of the Github Action workflows and the Pull Request will not be merged into the devel branch until you have checked off each task.

• Place Closes #<insert_issue_number> into the beginning of your Pull Request Title (Use Edit button in top-right if you need to update)
• Code is formatted according to the tidyverse style guide. Run styler::style_file() to style R and Rmd files
• Updated relevant unit tests or have written new unit tests, which should consider realistic data scenarios and edge cases, e.g. empty datasets, errors, boundary cases etc. - See Unit Test Guide
• If you removed/replaced any function and/or function parameters, did you fully follow the deprecation guidance?
• Update to all relevant roxygen headers and examples, including keywords and families. Refer to the categorization of functions to tag appropriate keyword/family.
• Run devtools::document() so all .Rd files in the man folder and the NAMESPACE file in the project root are updated appropriately
• Address any updates needed for vignettes and/or templates
• Update NEWS.md under the header # admiral (development version) if the changes pertain to a user-facing function (i.e. it has an @export tag) or documentation aimed at users (rather than developers)
• Build admiral site pkgdown::build_site() and check that all affected examples are displayed correctly and that all new functions occur on the "Reference" page.
• Address or fix all lintr warnings and errors - lintr::lint_package()
• Run R CMD check locally and address all errors and warnings - devtools::check()
• Link the issue in the Development Section on the right hand side.
• Address all merge conflicts and resolve appropriately
• Pat yourself on the back for a job well done! Much love to your accomplishment!

[cicdguy]

Damn. This is so nice.
I think at some point we'll need it for other packages also.

Before we merge this in, we'll need to clean up the HTML pages a bit to remove the $Versions$ dropdown item from the navbar. I'll do that.

[github-actions]

Package	Line Rate	Health
admiral	98%	✔
Summary	98% (4404 / 4473)	✔

[ddsjoberg]

@cicdguy I used the base R pipe here which is available for R 4.1 and later. We don't ever run pkgdown workflow on older versions of R, right?

[cicdguy]

Yes, we only run pkgdown for R 4.1+. Not for older versions.

[ddsjoberg]

@cicdguy just to put this on your radar in case it's not already taken care of. When we use a package in a pkgdown article (not a vignette), we add the following to the DESCRIPTION file Config/Needs/website: gert. The vanilla pkgdown workflow from Posit will see this and install any of the packages listed here during the pkgdown build.

I am not sure if we are also performing this same check and installing these article dependencies into our images.