The guarantee is that if something we developed or implemented breaks within the first year, we will fix it at no extra charge. This does cover items specified during the course of the project that might have been overlooked. It does not cover functionality that is not specified or out of scope. And it does depend on us applying regular updates to WordPress core and plugins (in fact, that's the main thing that might cause something to break -- a change in a plugin that changes how any custom code we write operates).
Here are some examples of things we routinely cover with the guarantee:
- A plugin gets updated and breaks something in the theme, especially if those are theme customizations we created
- A new browser version (in our supported list) comes out and changes how the site is rendered
- You discover a page on the site that does not look right in a supported browser
- Some business functionality we created on the site stops working after an update
- An integration to a 3rd party service stops working due to a published API change (note that we cannot do anything about changing features of a 3rd party service, or fix something that has been intentionally removed by a third party)
- Recovery of accidentally deleted items (for code, we have full history available. Content recovery is generally only available if it's in an available backup, which happens nightly and at each deployment, with some backups kept around up to 60 days).
Some things we don't cover:
- Adding functionality to take advantage of new browser features or new systems
- Fixing custom code created by other firms
- New functionality
- Things not specified in the proposal/Scope of Work, or in a completed user story/sprint plan
- Training or support (these are covered by our support and retainer plans)
- Intentional changes in behavior/user experience of a contributed plugin, WordPress core, or 3rd party service
Here are some examples of things we routinely cover with the guarantee:
- A plugin gets updated and breaks something in the theme, especially if those are theme customizations we created
- A new browser version (in our supported list) comes out and changes how the site is rendered
- You discover a page on the site that does not look right in a supported browser
- Some business functionality we created on the site stops working after an update
- An integration to a 3rd party service stops working due to a published API change (note that we cannot do anything about changing features of a 3rd party service, or fix something that has been intentionally removed by a third party)
- Recovery of accidentally deleted items (for code, we have full history available. Content recovery is generally only available if it's in an available backup, which happens nightly and at each deployment, with some backups kept around up to 60 days).
Some things we don't cover:
- Adding functionality to take advantage of new browser features or new systems
- Fixing custom code created by other firms
- New functionality
- Things not specified in the proposal/Scope of Work, or in a completed user story/sprint plan
- Training or support (these are covered by our support and retainer plans)
- Intentional changes in behavior/user experience of a contributed plugin, WordPress core, or 3rd party service