Version Control WP-Engine via Git
# Version Control WP-Engine
## Step 1: WP-Engine Staging
Staging Workflow
Fix/Make Necessary Changes
Copy live site to staging
Push to live
Delete staging site to clear clutter
// This will snaapshot of the live site at its current state
## Possible optimization to WPEngine staging
### Using the "Site & Environments Feature"
### Quick WP Engine Vocab
* "Site" -> ​"the container for related environments"
* "Environments" -> "allow you to work with multiple iterations of your site, making changes in development, creating a working staged copy in staging" -> You may copy an enviroment
### Using 'Site and Environments' utility
    "On WP Engine, each account can create sites made up of multiple environments: production, staging, and development. These environments allow you to work with multiple iterations of your site, making changes in development, creating a working staged copy in staging for your stakeholders, and only pushing changes to your live, production website when you are truly ready."

    "If your production website has an issue, you can easily copy to staging and troubleshoot and resolve the issue. Another option is to use development to create and test a new design, when you’re ready you can copy those changes to production. These environments all work independently which means you’ll never have to worry about changes to one environment impacting another."
Usages for WPEngine Enviroments
Production
Staging
Development
// Site currently being hosted and displayed to clients
// Environment used to review and test before deployment to production
// Environment used to build and experiment before deploying to Staging or Production
New website features
Current site modifications
Hosting 
## Step 2: Git Integration
Setup:
Add WPEngine's remotes
Initialize Git Repo 
Pull site locally via Backup zip provided by WPEngine