On 31 Oct, 22:52, David <d33lici... DeleteThis @gmail.com> wrote:
> I need your help. I am doing a project to refersh a few websites, as
> is normally done every year.
I've done this loads of times, never done it well.
The industry standard practice is to piss moneey all over the problem,
effectively re-developing an existing site entirely from scratch. This
is obviously expensive. Even better is to change underlying CMS
platform, so you can have a huge ETL problem in moving the content
across too. Then you end up with the "first project on a new platform"
problem, so the reworked site looks terrible anyway.
This is stupid, but that's web-company management for you 8-(
What's _supposed_ to happen is that you lightly re-skin the
presentation only, so as to make the site look fresh and new, whilst
not having to do any work at all with the underlying content layers.
This depends on the pre-condition of having a CMS (program or manual
process) that supports doing this! You have to have such a system in
place _first_, i.e. bbefore the earlier "stale" system was put
together.
If you have a visually stale system that's also incapable of
supporting useful re-skinning, then you _must_ fix that problem before
re-skinning it.
If you don't fix this first, then you can't re-style the site - you
can only re-develop it from scratch. The end result might look the
same, but the costs don't.
If you have a system that's incapable of re-skinning and needs visual
re-design, then you should the lack of skinning ability before the re-
design, probably as simultaneous pieces of work. This is still
expensive (it's still a re-development) but _hopefully_ you're now in
a better position and the 3rd design re-skinning in the future will
now be cheap.
The risk is that the "change the platform to make the future better"
requirement gets forgotten and that it turns into merely another
expensive platform change for no benefit. That's pointless, but
depressingly common practice.
>> Stay informed about: Refresh Websites