Sync templates

.github/dependabot.yml

@@ -51,11 +51,6 @@ updates:
     groups:
       # Specify a name for the group, which will be used in pull request titles
       # and branch names
-      dependencies-major:
-        # Open a PR with all major version updates from "dependencies" in package.json
-        dependency-type: "production"
-        update-types:
-        - "major"
       dependencies-minor:
         # Open a PR with all minor version updates from "dependencies" in package.json
         dependency-type: "production"

.gitignore

@@ -152,6 +152,7 @@ wp-content/shield/
 /wp-content/plugins/wpengine-snapshot/snapshots
 /wp-content/mysql.sql
 /.wpe-devkit
+/site-archive-*-live-*-*/
 
 # Large and binary files
 # NOTE:

README.md

@@ -4,25 +4,19 @@ Default files for repositories in the @Andrews-McMeel-Universal organization.
 
 ## Environment Variables
 
-The environment variables for this project are sourced from Azure Key Vault Secrets. The `.env` file is what is read for local development.
+The environment variables for this project are sourced from Azure Key Vault Secrets.
+
+> :white_check_mark: Read about [Application Environment Variables](https://amuniversal.atlassian.net/l/cp/z7HWk0Ah) for information on how to use and edit environment variables in an application **before proceeding**.
 
 ### Retrieving Environment Variables
 
 You have options when generating a local `.env` file:
 
-- For a specific environment:
-  - `Get-Secrets.ps1 -Environment [ENVIRONMENT]`: Replace `[ENVIRONMENT]` with the environment of your choosing. If no environment is provided, it defaults to the "development" environment.
-- To specify an Azure Key Vault:
-  - `Get-Secrets.ps1 -KeyVaultName [KEY VAULT NAME]`: Replace `[KEY VAULT NAME]` with one of the key vault names under [Azure Key Vault Names](#azure-key-vault-names)
-
-More information on how to use environment variables and how to edit them in an application, here: [Application Environment Variables](https://amuniversal.atlassian.net/wiki/spaces/TD/pages/2796191745)
-
-### Azure Key Vault Names
+- To generate a `.env` file for a specific environment: In a PowerShell session, run `./Get-Secrets.ps1 -Environment [ENVIRONMENT]`. If no environment is provided, the script defaults to the "development" environment.
+- To generate a `.env` file for a specific key vault: In a PowerShell session, run `./Get-Secrets.ps1 -KeyVaultName [KEY VAULT NAME]`. You can find the available key vaults for this project below.
 
 Here are the available Azure Key Vault names for this project:
 
-```
-appname-development
-appname-staging
-appname-production
-```
+- `appname-development`
+- `appname-staging`
+- `appname-production`