Starting before design, before coding anything. What steps need to be taken to fully implement a working website?
EDIT
I mean both from a technical and a non-technical perspective.
|
Starting before design, before coding anything. What steps need to be taken to fully implement a working website? EDIT I mean both from a technical and a non-technical perspective. |
||||
|
|
|
|||
|
|
The Pragmatic Press publishes a good book called "Web Design for Developers" which covers this topic. As a developer, I really enjoyed it. I think most people looking to build a web presence would find it useful. |
|||
|
|
|
Some of it depends on the purpose of the site. If you're building a personal site for your own interests then @JustinScott above covers about everything really well. I would probably look for an ISP and get the domain name concurrent with the other steps though... If it's a commercial site, you'll want to meet with a client to gather their goals and needs for the various sections, then put together a "requirements" doc to state exactly what will be delivered for each part. This way you have a blueprint to work off of that they've agreed to (signed) so you can later say "that's out of scope" when they want something else added or changed. Out of scope things can be added, but there should be a cost in either time, money or both. The other steps fall are about the same for commercial or more formal projects, with a section for Q&A/Testing/Fixing Issues after the development and before the release. Finally... there's the never ending "maintenance" phase of projects where you dread having ever started working on it in the first place :-) |
|||
|
|