Development workflow Intro
A redesign starts with an inventory, not a mockup
You cannot protect a page that is not on your list. Three inventories — pages, templates, top entry screens — settle both the scope and the schedule.
Technote
Redesigning a site that is already live
Redesigning a site that already has traffic and revenue — changing without losing, and what to verify once it ships.
8 articles
SEO Intro
Leave the screens that already work alone
Scope is set by data, not taste. Screens that bring traffic and conversions get a surface refresh — their structure stays where it is.
SEO Practical
Keeping your URLs is a design decision
Redraw the information architecture and addresses change. If they must, the 301 map ships with the change — it is a deliverable, not an afterthought.
Development workflow Practical
Review on staging, not in screenshots
A screenshot is one moment under ideal conditions. States, edge cases and real content only surface on staging — and staging has conditions of its own.
Development workflow Practical
Do not swap everything at once
A full swap makes every problem appear at the same moment — which means none of them can be attributed. So you switch one template at a time.
Themes & plugins Practical
Three reasons old content breaks in a new design
Inline styles baked into the body, shortcode remnants from plugins that are gone, hard-coded widths. These are where a new design system stops being honoured.
SEO Practical
The fortnight after launch: what to watch
A few unsettled days after launch are normal. A decline that persists for two weeks is not. Here is what to watch across indexing, speed and conversion.
Development workflow Advanced
Never deploy without a way back
A rollback is not one button. It is two tracks — code and database — with an order to reverse them in, written down before you deploy.