Approving Changes

When a development request is ready for review, you'll approve or request modifications before it goes live.

Review Process

When implementation is complete, you'll be notified that a request is ready for review.

1. Open the Request

Navigate to the request and go to the Preview tab.

2. Preview Changes

Click Open Preview to see the changes in your draft environment.

3. Review Carefully

Check that:

• The implementation matches your request
• Content is correct and complete
• Styling looks right
• No broken elements or errors

4. Approve or Request Changes

• Approve — Changes deploy to production
• Request Changes — Provide feedback for iteration

Preview Environment

The preview/draft environment shows your site with pending changes.

Accessing Preview

• Click Preview in the request details
• Or navigate to your dev site directly (usually dev.yoursite.com)

Preview Features

• Full site functionality
• Latest code changes
• Pending text overrides applied
• Performance similar to production

Preview vs. Production

Aspect	Preview	Production
URL	dev.yoursite.com	yoursite.com
Changes	All pending	Approved only
Users	Just you/team	Public
Data	Test data ok	Real data

What to Check

Visual Review

• [ ] Layout matches the request
• [ ] Colors and fonts are correct
• [ ] Images display properly
• [ ] Responsive on mobile and tablet

Functional Review

• [ ] Links work correctly
• [ ] Forms submit properly
• [ ] Interactive elements function
• [ ] No console errors

Content Review

• [ ] Text content is accurate
• [ ] No placeholder content
• [ ] Spelling and grammar correct
• [ ] SEO metadata set

Performance Review

• [ ] Page loads quickly
• [ ] Images are optimized
• [ ] No layout shifts

Providing Feedback

If changes are needed, provide clear feedback:

Good Feedback

The testimonials section looks great, but I need a few adjustments:

1. **Photo size** - Make the customer photos smaller (60px instead of 80px)
2. **Quote formatting** - Add quotation marks around the quotes
3. **Background color** - Change from white to light blue (#e6f0ff)
4. **Spacing** - Add more padding between cards

Please also fix the broken link on the third testimonial name.

Feedback Best Practices

• Be specific about what needs to change
• Reference exact elements or locations
• Provide correct values (colors, sizes, text)
• Prioritize critical issues first

Approving Changes

When you're satisfied:

1. Click Approve Changes
2. Confirm the approval
3. (Optional) Add release notes

What Happens Next

After approval:

1. Pull request is merged
2. Site builds automatically
3. Deploys to production
4. Request marked complete
5. Version number updates

Deployment Time

Typical deployment takes:

• Build: 1-5 minutes
• Deploy: 1-3 minutes
• DNS propagation: Instant to 5 minutes

You'll be notified when deployment completes.

Rollback

If issues appear after deployment:

Quick Rollback

1. Go to Revisions in your site
2. Find the previous stable version
3. Click Rollback
4. Confirm

What Rollback Does

• Reverts to the previous version
• Creates a new release with the old code
• Does not delete the problematic changes
• You can still access the reverted version

Multiple Reviewers

For teams with multiple approvers:

Approval Settings

Configure in site settings:

• Any approver — First approval deploys
• All approvers — Everyone must approve
• Majority — More than half must approve

Approval Status

See who has reviewed:

Review Status:
✅ Jane Doe - Approved
⏳ John Smith - Pending
✅ Sarah Johnson - Approved

Status: 2/3 approved (waiting for John)

Automatic Approval

For trusted development partners, enable auto-approval:

Settings

In site settings → Development:

• Auto-approve minor changes — Patch versions deploy automatically
• Auto-approve from users — Specific users can auto-approve
• Auto-approve types — Widget config, text overrides, etc.

WARNING

Use auto-approval carefully. Always review major changes.

Request Iteration

If you request changes:

Iteration Process

1. Your feedback goes to the GitHub issue
2. Copilot or a developer addresses it
3. Updated PR is created
4. You're notified to review again

Iteration Limits

• Most requests resolve in 1-2 iterations
• Complex requests may need 3-4
• After 5 iterations, manual intervention may be needed

Breaking Up Large Requests

If a request keeps iterating:

1. Approve what's working
2. Cancel the remaining issues
3. Submit new, smaller requests

Best Practices

Review Promptly

• Queued requests wait for earlier ones
• Prompt reviews keep the queue moving
• Set up email notifications

Be Thorough

• One careful review beats multiple quick ones
• Test on different devices
• Check edge cases

Communicate Clearly

• Specific feedback reduces iterations
• Use screenshots when helpful
• Reference exact locations

Know Your Limits

• Don't approve if unsure
• Ask questions before approving
• Request partner review for complex changes

Next Steps

• Tracking Progress — Monitor request status
• Submitting Requests — Create new requests
• Analytics — Monitor site performance after changes