link to pages env var doc

_kbarticlespages/repository-best-practices.md

@@ -30,7 +30,7 @@ A repository does *not need* to be public in order for Pages to be able to build
 
 #### Pros
   - Test/Make changes to a website without exposing commits to the public
-  - Safeguard sensitive data such as API keys, access tokens or other credentials in any configuration files by storing them as environment variables in `config.yml` for Jekyll sites or using `dotenv` to load values from a separate `.env` file for 11ty, Gatsby and Node.js websites as an additional layer of privacy.
+  - Safeguard sensitive data such as API keys, access tokens or other credentials by [using environment variables](https://cloud.gov/pages/documentation/env-vars-on-pages-builds/) in the build runtime.
   *Websites on Pages are all published publicly, user's configuration settings and static site build engine factor into what is included in the site build output.*
 
 #### Cons