Topic: Web Design Best Practices

I have gotten pulled into a project that is a redesign of an existing website, however the project lead has gotten deep into the *flashy* stuff without covering the basics. This has caused the project to become a bit nebulous. Initial mockups have been tossed asside and the current approach is to string a number of DHTML effects together ultimately resulting in a website.

I want to get this project back on track but I do not have the clout to directly redirect these efforts.

I am looking for some resources on Web Design best practices that might be able to give further weight to any arguements that I put forth towards getting things back on track.

The way that I would optimally want this project to work would be along the lines of:

0. Gather requirements for the website (goals, target audience, browser support, etc)
1. Gather content that will be a part of the site.
2. Create a sitemap form the content.
3. Define a mapping between content and presentational elements (homepage, main content page, sub content page)
4. Create graphical mockups for all of the different page types.
5. Turn mockups into XHTML/CSS mockups
6. Refactor mockups into workable pages (templating, AJAX, transition effect, etc).
7. Combine the content with the presentation layer to result in a working website.

With references that outline best practices for website design from a project management perspective I am hoping that I can pull the project back. Things like check lists, the correct questions to ask the client, or even an outline of how to run a web design project would be helpful.

I am also interested in any experiences you have had or advice you might offer.

Dan @ Code Town

Since I was thinking about this I decided to write some of my ideas down.

I hope my writing is not too aweful. If you have any ideas on this let me know.

http://www.codetown.org/WebDesignBestPractices.doc

Dan @ Code Town

Good stuff!

I assume your best practices refers not to your specific situation as described in the initial post, but an all encompassing generic pre-sales questionnaire for a web design/development job?

If that's the case you look a little short on scope questions, specifically technology, talent, time and budget. This is a sure fire way to end a project in dissappointment. Clearly establishing scope ASAP is imperative to good relationship building and there's no better marketing than satisfied and loyal customers.

technology - You seem to assume html and server side scripting but be sure you don't forget that a lot of clients will expect Flash, Flash Comm server, streaming media, SSL, certs, gateway etc etc and that will all have influence on your network/server choice and talent requirements.

talent - tally the talent required to pull off the technology requirements within the allotted timeline.

time - there's always some kind of expectation regarding timeline, it's good to guage what they think it *should* take, measure it against what it will *actually* take and use the exchange as a factor in pricing/acceptance of contract. Are you going to be working a lot of overtime? Paying employees/subs overtime? Are you facing a client with unrealsitic expectations (and do you want to work with them)?

budget - Most potential customers that don't know you or your level of integrity will not want to talk about their budget. A lot of the smaller customers will get a look of shame on their face when you ask because they haven't even considered it, they just have a "feeling about what they have to spend". massively opinionated, ymmv: I try like heck to break both those barriers in the inital meeting (at least nicely float the fact that it helps massively to know), again, for the reason of building good relationships and weeding out the kinds of people I don't care to deal with (the kinds that just bring grief along with their tight purse strings! Funny how these types tend to be one in the same).



(Edited by JKMabry on 04-21-2006 22:56)

Great stuff, yes most (if not all) of what I mentioned was situational. I will work in the items you mentioned (if you don't mind) it will help to make the guide more well rounded.

Dan @ Code Town

oh heck yes, love to read the next version!