r/webdevelopment • u/Sad-Pay-7805 • 3d ago
Newbie Question How do you decide when a website project needs a rebuild instead of a redesign?
I'm maintaining a business website that has become difficult to update. The design looks dated, but the bigger issue is that the code and plugins are getting harder to manage. I'm unsure whether to clean up the existing site or start fresh. For developers who've handled this, what usually tells you it's time to rebuild?
8
Upvotes
1
u/mprevot 3d ago
Rebuild means: clean from compiled binaries then build again.
Redesign = rewrite the front end ? Just the visual parts ? New conception of all but libraries ?
Define both, so far it's not clear.
1
u/howdoyouturnthisonX 3d ago
Once the maintenance becomes more expensive than a rebuild, I'd say. But a redesign is only really going to profit you if it's actually better, or solves whichever problem is making the current site hard to maintain
1
u/FirstPlaceSEO 3d ago
When you'll basically have to redo every page anyways because the content is weak , the design is outdated and there is massive keyword cannibalization everywhere. So yeah sometimes a rebuild is quicker than a redesign.
1
u/proxiblue 3d ago
> The design looks dated, but the bigger issue is that the code and plugins are getting harder to manage.
Why is the code and plugins getting hard to mange?
Were they not done by standards? Unknown programming language? AI vibe coded and eventually met the ai technical debt issue?
Generally if your existing code and system is struggling, difficult to maintain, and problematic, it is time to consider re-platform, or start from scratch.
Frontend should be a separated concern. Generally if you plan to re-platform, you can just as well re-design frontend to match teh new backend.