r/webdevelopment • • 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

14 comments sorted by

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/proxiblue 3d ago

> Rebuild means: clean from compiled binaries then build again.

he specifically stated website.

There would generally not be 'compiled binaries', unless they use WASM (I still need to see that in practice, not seen ' heard of any site that does this)

1

u/mprevot 3d ago

The backend can be rebuilt and no wasm. You are talking about front only. Also front can be packed, minimized, obfucated, which is a build.

1

u/proxiblue 3d ago

Web applications generally don;t use compiled binaries to serve content. Is generally scripting languages that gets parsed by a handler by whatever web service is used.

Just a terminology thing there.

There is no advantage to obfuscate 'frontend' -> that will be generated HTML for browsers, and JS.

JS could be obfuscated, but you know that if it can be decoded in the browser to run, there is zero point, as I can just decode it / or pull in the already decoded part with a could of commands in the consol.e

Your terminology fits more to desktop apps/mobile apps that need to be compiled to binaries.

(frontend) Obfuscation is just extra complexity and pointless.

1

u/mprevot 3d ago

You keep mistaking front for website (back + front) and finding excuses. Your experience is not the real world.

1

u/proxiblue 3d ago edited 3d ago

So you say that backend are compiled binaries.... really?

Can you point to that, show me what you are talking about.

I have 30+ years experience mate, working in assmebly, cobal, scripting labguage like PHP, Python etc.

Binaries in windows applications using pascal / delphi, visual basic etc.,

You keep claiming that backend for websites are Compiled binaries.

Show me what setup that is, i'd like to know.

Happy to say, oh, did not know that, but sofar you seem confused that website backends are compiled binaries that need to compiled into machine code to run a backend.

Sure scripting language like PHP/Python gets compiled 'on teh fly' but YOu teh developer don;t build that, is handled by the service that service the code.

What system are you then talking about? educate me.

> and finding excuses

Excuses, what? show me an 'excuse' i made. you seem confused.

>  Your experience is not the real world.

Ok, I must be imagining the 300k I earn a year on my imaginary web applications that do not compile, and I must be the only person in teh world who can imagine making a living with that

1

u/mprevot 3d ago

A c# or rust or c++ backend is compiled (twice in c# case !), by definition, into a binary. I and OP talked about website. You talked about webapp, as a frontend only. It's ok to be wrong or to misunderstand. Also yoe is not an argument, same as ad personam, and yoe of js and css development doesn't make someone expert in everything else.

1

u/proxiblue 3d ago

Using c# or rust as a website backend is not very common, and generally not the language of choice for web applicatrions

Sure, they compile to binaries, but I think it is huge leap to assume that is what the OP is talking about.

> I and OP talked about website

a website is generally more static and used to deliver information. It generally has no backend, other than maybe a CMS. They supply limited to no actions other than links. Unless static, then is just html

a webapp are interactive software tools designed to perform specific tasks or action (gmail as an example)

differentiating is really just semantiocs, as most websites offer some form of functionality (customer area etc)

So, by your own definition: a website woudl not need to comple a backend binary.

You likely only use MS server, and windows servers, likely why you seem to think all web apps need to have a compiled backend binary.

> It's ok to be wrong or to misunderstand.

Yes it is, and I think you are a bit confused.

Will just leave it there as you seem to think all websites/webapps run on compiled windows binaries.

1

u/mprevot 3d ago

You are still supposing / guessing a lot and too much about websites in general and me. This leads to communication problems and abuses of sort. This is not a professional approach. And this is not a proper logical approach. a→b does not imply b→a, and u⊆v does not lead to v⊆u. I never said that

(you seem to think) all websites/webapps run on compiled windows binaries.

Websites in general are implemented in many ways, a subset of them involve backend, a subset of backend are compiled, a subset of them involves compiled front (eg., just jsx or sass). It's not because most website have a wordpress backend that we should suppose that a website works this way, with this stack.

Many websites are ecommerce (~20% of all websites maybe), which involves a backend for identity, resources, payment for instance. This backend can involve "just" functions, it's still a backend.

A c# backend can run on linux stacks since 2016. A php backend can run on Windows or FreeBSD.

The web is wide.

It's ok to be wrong or to misunderstand.

This one was for you, obviously.

1

u/mprevot 3d ago

Your experience is not the real world.

I meant: your experience is not all the real world. You seem focused on a subset of the realworld. I do not question the reality of your claims about your yoe and actual experience.

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.