All rOpenSci packages now have a pkgdown website that’s updated with each commit to master. With the way the system works at the moment, we cannot use pkgdown’s “auto” mode (creating a website for the released version at the root, and one for the dev version under dev/).
The website might document behaviors/functions that are not released on CRAN. Should this be avoided (by using a dev branch until release)? If not, how to make it clear?
By using a lifecycle badge in the function? (see drake reference)
Opinions are welcome.