A redesign may clarify a service, support a different audience or resolve a difficult publishing process. Those goals determine the page structure and visual direction. We review the existing site, representative content and important actions before deciding whether the project should retain the platform, rebuild it or migrate to another suitable arrangement. Changing the domain is not a requirement for a new design.
The proposal identifies page types, responsive layouts, supplied or commissioned assets, content preparation and included functions. Decide which text and images must remain exact and which changes the business wants to approve. Useful documents, enquiry routes, external destinations and existing URLs should be included in the inventory. A migration also needs a way to reconcile approved changes made to the old site while the replacement is being built.
Development and CMS work should lead to a website the nominated editors can maintain. Acceptance includes representative pages and actions, the agreed URL treatment and ordinary editing tasks. Account ownership, release authority, recovery arrangements and continuing technical care need their own explicit responsibilities. A domain move adds coordination work to that project; it does not automatically transfer every service associated with the old address.
