After we know what we want to do and the order to follow, we make sure our ideas fly. Usually, we create a proof of concept version of a site that employs code, markup, and graphics from already completed sites to prove to ourselves, our bosses, and to other important people outside our company (such as our publishers or customers) that our ideas work and we know what were doing. More important, we give our intended audience a glimpse of our content, layout, and navigation so that those users have a chance to react and respond to our approach early in the development process (when making changes or adding functionality or content is easiest).
Proof of concept may require new graphics and new markup; at this stage, we create them as quickly as possible using only standard tools (we talk about those tools in the Lots of Hard Work section later in this extra). Quick productions of missing items are simply crude representations of what we really want. We dont like to waste time up front to develop high-quality objects because we often remove or change them in the final version. Basically, we build place-holders for everything. At this point, the only useful thing about our Web construct is that it works and it provides a view of our primary concepts, designs, and navigation techniques.
Extra 10 Main Page | Previous Section | Next Section
E-mail: HTML For Dummies
Webmaster: Natanya Pitts, LANWrights
Revised -- January 16, 1998