What good development covers
Use the list below as a working checklist. Each item is something you can verify or action directly on your own site.
- A content and page model that editors can maintain.
- Components with explicit variants and sensible defaults.
- Responsive layouts tested with realistic content.
- Navigation, forms, domains and redirects checked on the live site.
- Metadata, schema and performance considered before launch.
Support versus rebuild
Support is appropriate when the system is sound and the issue is local. A rescue or rebuild is safer when overrides, copied components, missing content structure or domain changes have made every fix unpredictable.
- Describe the exact page, viewport and failing action.
- Reproduce the issue on the published URL.
- Identify whether the cause is content, component, breakpoint or integration.
- Apply the smallest maintainable fix.
- Retest neighboring pages and the relevant mobile state.
Before you hand over
Here are the key things to get right. None of them are complicated on their own, but skipping one tends to undermine the rest.
- A component inventory with intended variants and usage notes.
- CMS collections documented: fields, who edits them and where they appear.
- A launch checklist covering domains, redirects, forms, metadata and analytics consent.
- A short recording walking through the editing workflow for the team.
Working with a developer
The smoothest Framer projects start with a content model, not a canvas. Agree the page types, collections and components first, then design inside that system. Retrofitting structure onto a freeform canvas is where most rescue projects begin.