Download Developing Effective Websites: A Project Manager`s Guide Roy

Transcript
132
Developing Effective Websites: A Project Manager’s Guide
individual pages? If the navigation bar and other design elements are consistently placed, designing the rest of the pages is usually a fairly straightforward
task.
Authoring tools make the job easier. The World Wide Web Consortium
(W3C) has developed a standard called cascading style sheets (CSS) that can help.
CSS attempt to address the problem of display by defining how various kinds of
content should be displayed in a consistent manner. Style sheets are one way to
create consistency across the site. The CSS can be embedded into a page, but its
true power is realized as a separate file that can be linked to other pages. Then, in
making one change to the style sheet, you can modify the entire site. A site can
also use embedded CSS on specific pages along with a linked style sheet. Of
course, for consistency’s sake, you will want to refrain from too much individual
design.
CSS also can help maintain the design integrity of the site after it has been
handed over to the client. Design specialists can create the style sheets during the
development process. When the site is handed over, developers can train inhouse personnel on how to use the CSS for new pages. Instruction, along with
documentation in the form of a mini-manual or sample HTML, is important because haphazard use of style sheets can also make a big mess. With a bit of handholding, however, nondesigners will be able to update the site with new content
while retaining the integrity of the design.
If the project is a database-driven site, graphic artists can prepare the standard template pages that draw information from the database. There is no need
to await the content in the database. It’s better to create the templates and set
them in place using sample or dummy data so they can be reviewed and tested
for usability.
DEVELOPMENT SITE
If you are working on a large or complex website, you may be using a development
server to build out and test the site before copying it to the live server, known as
the production server (Figure 9.2). As production work progresses, your team will
continue to post content and install programs to the development server. You
want this site to be accessible to members of the development team, but not to the
whole world on the Web. At best, it is an embarrassment for a work-in-progress
to be unveiled prematurely. Depending on the circumstances, exposing the site
can potentially cause more serious problems. The most secure option is for the
server to reside behind the firewall, on an intranet that is accessible only to those
within the company or coming from select Internet protocol (IP) addresses. The
site may even be posted “blind,” which means it’s available on the Web, but password protected or simply not yet assigned a domain name.