Comments on: Best Practices in Web Development: Part 1

By: Jason

Jason — Sun, 15 Feb 2009 11:40:08 +0000

I am tester by profession and I would say that this kind of details even help us to build our test strategy. Why not to out all these in a eBook and offer it from this blog?

By: Mayur

Mayur — Mon, 19 Jan 2009 04:11:27 +0000

Hey thanks for sharing this info Joe. The Info architecture bit is good reading. I’m struggling with this aspect of a site right now actually.

By: Joe Dolson

Joe Dolson — Sat, 13 Sep 2008 17:57:25 +0000

Thanks for mentioning that, Tedd - it’s certainly true! In my own practice, I develop every site on a CMS; I haven’t done a static site in years. This is partly because it’s easier for the client to take a role in publishing or changing their site, and it’s partly because it’s easier for ME to manage the site, if that’s necessary. As such, it’s easy for me to forget how important it is to discuss the client’s need for involvement — my normal plan is to assume they will want to be able to update the site themselves.

In part 5 of this series, I do address client training and long-term site management, but bringing this aspect of development into the initial requirements phase is very important.

Thanks!

By: tedd

tedd — Sat, 13 Sep 2008 17:43:15 +0000

Great start.

One additional consideration in your “Establishing Site Requirements” should include what are the client’s expectations and requirements regarding back-end development, if any.

For example:

Do they want a CMS allowing them to change their site?

Do they want a back-end to add/delete product to their site?

Do they need training for any of this?

All site development should consider if the client is going to be involved and responsible for the end-result of their site.