Step 3: Edit Resources Locally

If you want to make any changes to your configuration before applying to your destination account, you can do so at this step! You can navigate to your files and make any changes, just make sure to save before proceeding.

Tips & Tricks

If you don’t want to copy something from your source account to the destination, just delete the file!
If you are going between Production and Sandbox, you may run into some discrepancies. Stay patient! You might need to return to this step during Step 5 to fix any of these errors locally before applying.
If your account configuration includes a repository (e.g., a Search frontend built using Jambo/Theme): If you want to create a brand new repo, make sure the repoConfig looks like this:
```
    "repoConfig": {
        "targetRepoName": "${{youraccount_targetRepo}}"
    },
```
If you want to copy an existing repo (that is set as a template repo in the github UI or via the –pages-force-template command in the previous step) make sure it looks like this:
```
    "repoConfig": {
        "targetRepoName": "${{youraccount_targetRepo}}",
        "templateRepo": "https://github.com/big-ol-sandbox/your-repo-url"
    },
```
You can find your repo URL for the repoConfig.templateRepo in the Sites section of your account.

Note

Variables are commonly used in Solution Templates so that you can replace certain values to be relevant to your brand. For example, ${{youraccount_targetRepo}} allows you to name your destination repository. Make sure that the name is unique and doesn’t contain spaces!

To add variables to your configuration files, use the following syntax: ${{insertVariablePrompt}} where the insertVariablePrompt string will be surfaced to your user as a prompt during the Apply step.

<% elem.innerText %>