How repair works
Understand the failure. Make the change. Check the result.
A repair needs to solve the problem people are experiencing and leave the site in a state you can maintain.
1. Reproduce the problem
Start with the affected URL, the steps a visitor takes and what happens instead of the expected result. Note when it began, who is affected and any recent update or hosting change. If the failure is intermittent, those details help narrow it down.
2. Protect the current site
Confirm who controls the accounts, what backup or export exists and whether it can be restored. Use a separate test copy when practical. Decide how a failed release would be reversed before changing the live site.
3. Agree on the repair
Explain the likely cause, remaining questions and proposed work. Choose a concrete check, such as submitting an inquiry and finding the saved record, or completing a mobile menu task without blocked controls. Keep unrelated redesign work separate from the immediate fix.
4. Release and repeat the checks
Test the repaired task and nearby behavior that could be affected. Check relevant screen sizes, keyboard use and error messages. A payment or message test should use the agreed isolated method rather than contacting real customers.
5. Leave a clear handoff
Record what changed, what was checked, how to reverse the release and anything still unresolved. Ongoing maintenance or additional work is discussed as its own scope.
Tell us what stopped working
Share the affected page, what you expected to happen and what happened instead. Use Contact Us at the bottom right or email Faith Forge Labs. A short description is enough to start; leave out passwords and private customer information.
Prepare your inquiry