How to plan a safe website redesign migration
Plan a redesign migration around content, URLs, data, forms, testing and a rollback route before launch day.
THE BUILD LOG
Development concepts, implementation choices and real-world web craft.
33 articles to explore
Plan a redesign migration around content, URLs, data, forms, testing and a rollback route before launch day.
Choose a small application database by data relationships, transaction needs, hosting support, recovery and team skills.
Prioritise speed fixes using important visitor journeys, measured causes and before-and-after checks rather than one score.
Test navigation, reading, forms, accessibility and performance on real mobile devices before approving a website.
Plan online payments around the customer journey, responsibility, failed transactions, refunds and safe tests.
Prepare a CMS migration by inventorying content, mapping fields, protecting URLs and testing a representative import.
Compare web development proposals against the same brief, assumptions, ownership terms, tests and running costs.
Review third-party website scripts for purpose, data access, page speed, security and a clear removal plan.
Use a repeatable deployment checklist for approvals, backups, secrets, smoke tests, monitoring and rollback.
Map CMS permissions to editorial tasks, approval needs and private data access rather than giving everyone administrator rights.
Build a usable page first, then add JavaScript convenience. Learn where progressive enhancement matters most for business content, forms and navigation.
Plan website search around visitor tasks: decide what to index, label results clearly, handle empty searches and use query evidence to improve content.