 |
Photo credit: Brian W. Tobin, uploaded via Flickr, Creative Commons License |
4.1 Project Management:
In this section, out tutor introduces us to the planning stage of website development. Factors to consider here include such things as the ultimate goals for your site, budgetary constraints, who the key players will be in the development and operation of the site, and timeline for development.
Our tutor advises that the undertaking of a website project begin with a questionnaire completed by the client. She uses such a document to garner information about the client’s mission, goals, expectations for expenditure and return on same, and generally develop on overall picture of the direction that the project will need to assume.
With the information from the questionnaire on-hand, we are advised to create a design document, or what amounts to rough framework from which to launch the design process.
From there, we formulate a more specific document known as the project plan. The project plan will spell out some specifics, such as the responsibilities of each member of the development team, the protocols for communication and escalation of decision points, flowcharts for the design process and benchmarks for progress. The project plan is a reference document for everyone involved in the project, defining their role and responsibilities, as well as identifying who the go-to principals are regarding each aspect of the project. Furthermore, the project plan is a dynamic document that evolves along with the project. The plan must delegate responsibility for keeping the plan itself up-to-date.
Finally, our tutor wraps up this section by stressing the importance of development team communication. She then proceeds to shamelessly plug the various products and services offered by Adobe to facilitate your development team’s collaboration. After all, this tutorial *is* an Adobe publication. Say…couldn’t you just go for the refreshing taste of a Coca-Cola right about now?
4.2 Site Development:
I) Site Definition and Planning
Copyright - We are advised in this section to be mindful of applicable copyright law as it applies to the content of our site. This applies both to reserving the rights to the original content that we create, as well as to avoid infringing on the copyrighted works of others.
Accessibility - We are reminded that the World Wide Web Consortium (W3C) has issued standards for making websites accessible by those with disabilities. Our tutor explains how to find the current Web Content Accessibility Guidelines (WCAG) for reference, and urges us to incorporate these guidelines into our site design.
- Screen Readers – One aspect of accessibility is compatibility with screen reading software. Our tutor advises as to the popular screen reading applications in use today, and directs us to the WCAG guidelines pertaining to compatibility with same.
Maintaining Consistency – Consistency throughout your site is important in that the user should always have a sense of orientation as to what portion of your site is currently displayed, how to get there, and how to get back to the top level. Consistency can be preserved by maintaining elements such as fonts, colors, page sizes throughout. Also, navigation links should be placed uniformly across all pages.
One tool for achieving consistent look and feel is using the cascading style sheet (css) in the design of one’s site. I do hope that we will be discussing those in more detail later.
Furthermore, in my personal opinion, a link to the top-level home page should in all cases be available near the top left corner of every page (often taking the form of a company/organizational logo). Also, and again in this writers opinion, a “bread crumb trail” showing the path to the current page, and links back to any level along the way, should also be displayed near the top left corner of every page. For example: Home\Support\Replacement Parts\Transporters\Heisenberg Compensators. In this example, I could locate the Heisenberg Compensator that I require on the current page. Then, if I also needed to find an anti-matter injector for my warp drive, I need not navigate all the way back to the home page again; I could simply click back to the Replacement Parts level, and navigate from there.
Content vs. Design – In this section, we are given a demonstration as to just how different some identical content can appear based on design changes achieved through the use of cascading style sheets. Check it out: http://csszengarden.com
Fonts – Font sizes can be specified in the page design as either absolute or relative. Absolute sizing can be specified in inches, mm/cm or points, but those specifications have more to do with print sizes than screen display size. In many if not most cases, the graphics adapter is not aware of the monitor size, and thus cannot calculate how to display a 1” font size on the user’s screen.
Alternatively, font sizes can be specified in terms of absolute pixel size, or sized relative to the user’s default browser settings.
Font definition is another consideration. If you specify content to display in a font that is not installed on the user’s system, the text will not display as you intended. It is good practice to specify commonplace alternative fonts for the browser to use, lest the browser revert to the user’s default font, leaving you with no control over how the content will appear.
Finally, be aware that if you include text-as-image in your site, as does the header of this blog, note that screen reader software will not be able to read the image as text. Therefore, you should make accommodations for that use case.
Web-Safe Colors – Back in the day, there was a palette of 216 colors that were considered “web-safe”, meaning that most client hardware would display them properly. Venturing outside of this palette left you site vulnerable to improper display on some systems. This is generally not a matter of concern today.
Browsers – Not all browsers are created equal, and not all content will display exactly as intended in all browsers. Each browser has its quirks, and therefore one would do well to check one’s page across common platforms and clients.
As of this writing, Firefox is the dominant client with a share of approximately 42%. Other widely-used browsers are Internet Explorer and Chrome, each holding a share of about 25% (although the former is steadily losing ground, while the latter is increasing in popularity). At the very least, you should check you site for functionality with these “big three”.
Also, be advised that functionality may vary by platform as well. That is, just because your site works with Firefox on a PC does not automatically mean that it will work with Firefox for Mac or Linux.
Design Principles – We are reminded here of the old adage “know your audience”. The principle being that one should consider carefully the demographic one is trying to reach when forming one’s site design. Examples given here include large fonts for seniors, or fun, interactive content for kids.
Also discussed here are guidelines governing the use of graphics. For instance, the so-called “rule of thirds” dictates that when a graphic image is displayed on screen, the important portions of that image should appear corresponding to the intersections of the lines on an imaginary tic-tac-toe grid drawn on the screen. So too should one take care to create balance and symmetry on a page displaying graphical content.
Lastly, our tutor offers a few pointers on good design vs. bad. Pages that are too “busy”, tightly compressed, or have inconsistent themes, colors or fonts can make a page feel unwelcoming. Not clear on the concept? Just point your browser over to http://cmdshiftdesign.com/ilovesmekitty, or http://mizzpheonixrightxxxx.piczo.com/ (if you have a *really* strong stomach). You should probably let somebody know that you are going there, however, so they can send help if you don’t come back soon.
Usability & Readability – It is unquestionably worth considering how practical your site will be to the intended end-user. These considerations mandate that one must consider page size and corresponding load-time, the necessity of plug-ins to display page content, whether to use cookies, JavaScript, etc.
Finally, an easily overlooked but oh-so important item to remember when making design choices: Keep your documentation updated! You will likely change your plans ub-teen-kazillion times during the design process. If you don’t keep your design plans up-to-date to reflect all of these design change decisions, you’ll likely be left dumbfounded some day, asking yourself “why the hell did I do foo there, when the plan called for bar?”
II) Information Architecture
Visual Heirarchy – A tree-like diagram, or sitemap is helpful in defining a big picture of the various pages contained in your site, and the appropriate levels at which each should exist. Every site needs a “home” page, or a landing point for a browser pointed to your URL. This is regarded as a level one page. From there, and in fact from every page below, should exist a consistent set of site navigation links, each pointing to a level two page, such as Products, Support, Locations, Contact, etc. From there, pages cascade down into logical lower levels, as alluded to previously, i.e. Home\Support\Replacement Parts\Engines\Warp Drive\Anti-matter Injectors\.
 |
Site Hierarchy Tree |
Wire Frames – Wire framing a page simply involves using blank placeholders to arrange content on your page, without having had to decide on the actual look of the content elements themselves. For instance, where should the site navigation links be? How about the company logo? If there needs to be a log in form, where should it be? You can easily play around with a wire frame design to decide on the best placement for these elements, without being distracted by the look of the elements themselves. Below is the wire frame example that our tutorial uses.
 |
Page Wireframe |
Our tutor also discusses site wire frames, but there seems to be little distinction between the site wire frame and the site hierarchy tree discussed above.
Flowcharts – This section covers the use of flowcharts to define processes that may need to occur within the scope of one’s site. The tutor discusses the process of logging in to a site, but we can also imagine processes such as adding items to a shopping cart, processing a payment, or changing one’s contact information. To anyone who has done any significant programming, the use of flowcharts to define processes should be familiar.
Storyboards – Storyboarding is the next step taken after wire framing. Generally, this involves filling-in the elements of the wire frame page layout with mock-ups of the desired content.
4.3 Site Testing
Site Testing Overview – When one’s site is has all the pieces assembled, it’s time to start testing it out for functionality. Our tutor suggests that it’s best to get some fresh eyes on your design, and seek beta testers from outside the web development team. You should ask them to complete some tasks that you want users to be able to do on your site, such as navigate to the locations page and find a local store near their star system, of find a parts diagram for galaxy-class starship impulse thruster power coupling. Beta testers can give you important feedback on their experiences using the site, which you can use to streamline the design.
Usability Testing – After beta testing and tweaking is complete, you will need to conduct a full-fledged usability test on your site. This is a comprehensive test that will require significant planning, resources and documentation. We are advised that usability tests require tester recruitment and demographic data collection regarding same. Your site needs to be hosted on the same hardware during testing as it will be when rolled-out. You need well-defined tasks to give to testers and a model for collecting feedback. Less obvious concerns must also be considered, such as how to compensate testers, and whether non-disclosure agreements with testers are applicable.
Of course, and as always, be certain to document everything; rinse and repeat as needed.