# A Complete Guide to Enterprise Website Redesign > [!question] Lingering Questions > - The guide is vendor-authored (WordPress VIP) — how much of the CMS-selection framing quietly favors headless/VIP-style architecture over a fair, vendor-neutral comparison? > [!tip] Article Ideas > - A vendor-neutral CMS evaluation rubric to counter publisher-framed guides like this one. > - Pull the six-phase redesign model into a reusable, brand-agnostic WordPress redesign checklist. > [!link] Cross Reference > - [[3. Resources/MOCs/Open Source Governance MOC]] — the governance-gate argument (RACI matrices, steering committees) generalizes past enterprise web redesigns to any large multi-stakeholder software decision. > [!quote] Vocabulary > - **Redesign vs. refresh** — a refresh updates visual styles or surface copy; a full redesign reconstructs the underlying architecture and technology stack. > - **Headless CMS** — separates the backend content repository from the presentation layer, delivering content as raw data via APIs to any frontend. ## Bib capsule WordPress VIP publishes a soup-to-nuts framework for redesigning a large organization's website: strategy, a six-phase process, CMS selection, and post-launch measurement. ## Author's thesis Enterprise website redesigns fail on organizational complexity — stakeholder alignment, governance, compliance, content-migration risk — far more often than on visual design, so the guide's structure (phase gates, RACI matrices, formal migration planning) treats redesign as a governance problem with a design component, not the reverse. ## Key arguments (≤3) 1. **Content migration is the highest-risk phase** — moving content, updating URLs, and preserving SEO equity can silently cost organic traffic if not planned as its own workstream. 2. **Redesign and refresh are different projects** — a redesign rebuilds architecture and stack; conflating it with a refresh under-scopes budget and timeline. 3. **Missing governance triggers scope creep** — without a formal governance framework (RACI, steering committee), decision delays and unbounded scope changes follow. ## Claim atoms ### Content migration is a redesign's highest-risk phase > [!quote] ID:rw_01kx13cxbmrs60r63b1sp6n0p5 > Content migration is the highest-risk phase of any site redesign because it involves moving content, updating URLs, and SEO preservation to avoid losing organic traffic or rankings. Content migration section — anchors why redirect maps and SEO-equity audits must be planned early; the phase teams most underestimate. ### Redesign rebuilds architecture; refresh only restyles > [!quote] ID:rw_01kx13cxbmrs60r63b1sp6n0p5 > Unlike a website refresh, which only updates visual styles or surface-level copy, a full enterprise website redesign reconstructs the underlying architecture and technology stack. Definition section near the top — the single most useful scoping distinction for stakeholders arguing budget and effort. ### Missing governance framework causes scope creep > [!quote] ID:rw_01kx13cxbmrs60r63b1sp6n0p5 > Omitting a formal governance framework triggers scope creep and decision delays. Governance and stakeholder-alignment section — justifies RACI matrices and steering committees as risk controls, not bureaucracy. ### Traditional CMS couples backend to frontend; headless separates > [!quote] ID:rw_01kx13cxbmrs60r63b1sp6n0p5 > A headless CMS architecture separates the backend content repository from the presentation layer entirely, delivering content as raw data via APIs to any frontend framework or digital channel. CMS architecture section — the clearest one-line articulation of the headless value proposition for multi-channel delivery. ## Permanent candidates - **Phase-gate governance converts redesign risk into checkpoints** — generalizes beyond web redesign to any large multi-stakeholder project. Promoted below. ## Processing checklist - [x] Port existing deep-read analysis into Konik Literature format - [x] Promote the phase-gate governance permanent candidate - [x] Connect into the relevant MOC - [ ] Draft a URL redirect-map + SEO-equity preservation checklist template - [ ] Write an evidence-backed enterprise redesign case study to counter citation-free vendor guides ## Metadata - Source: [[3. Resources/Readwise/Articles/A Complete Guide to Enterprise Website Redesign]] ## Links - [[3. Resources/MOCs/Open Source Governance MOC]] — the governance-gate / RACI argument is a general large-project-decision pattern this MOC already tracks in other domains.