Workflow

Keep in mind were talking structural presentations, not visual presentations when your working on charting your site at this point. (Yeah, I know, but we'll get to that soon... You'll thank me later, I promise). Before we can design a page visually, it has to be determined what each page needs as far as user interaction and informational needs for your viewers

The goal is to create a plan that will enhance the efficiency (such as how easy it is to date), useful less, and navigational usability of the site. We also take note that any logical relationships of this page to the others on the site or on other people's Web pages.

Bonnie's bed and breakfast

Pictures of the building

Where were located

Times of year were opened

Phone number

Organizations we along to

Frequently asked questions

Optional elements of this area with notes on links and elements that can be easily changed were updated:

Photographs of the outside of the building

photos can change seasonally

clicked here to see the building in spring/winter/fall/summer

link "clicked here to find out about the history of BB&B"

Link to "photographs of each room"

Caption is under each photo

where we're located

text directions

view a GIF of a map

download a GIF of a map

link to an "area" section

Time of year were opened

Text with dates

A table calendar that shows when rooms are available (updated weekly)

Links to different months of the year

Forms to stand for availability of rooms

Links to seasonal deals

Links to seasonal events

Maybe sell ad space to local vendors

WORKFLOW BASICS

Wall there's no set way that a site's workflow should be set up, there's a lot to be learned from traditional editorial workflow, such as a magazine that is applicable to putting together the workflow process for a WebSite, especially if it's to be a site that is regularly updated.

Numbers of team: freelance writers, freelance artists, editors, copy editors, art director, HTML production department. In the Web world, we can curled many of the same steps-however, since the median is different, changes may be reflected as so:

Article is conceived by editorial team.

Article assigned to writer by editor.

Writer reads article.

Writer turns in article to editor.

Editor reads article and edits it.

Editor discusses article with art director.

Editor turns article over to copy editor.

Copy editor turns article with changes back to editor.

Editor makes changes, turns into art department.

Editor, editor-in-chief, art director, the HTML production head discussed art and layout.

Art department pairs rough layout on paper, plans art.

art director assigns art.

Artist creates art.

Artist turns into art.

Art HTML production department pairs initial online layout.

Editor reviews layout.

Editor approves layout.

Copy editor reads copy and layout form, returns changes to editor.

Editor approves changes, returns layout to art department.

HTML production department pairs new version of layout and places final art.

Copy editor re-reads story, makes any final changes (fitting text, filling in missing captions, and so on).

HTML production department produces final layout.

Managing editor, editor, copy editor, and art director approve final layout.

HTMLtested on server.

HTML files do live.

If you're a one-person team, then your flow may go like this.

Determine your stories content.

Write your story.

Re-read article and edits.

Determine accompanying arts.

Create art (or purchase clip art).

Prepare initial online layout.

Review layout.

Re-read copy and layout form.

Make editorial changes.

Prepare new version of layout.

Review new version of layout.

Make any final changes.

Put files on server.

Test files on server.

HTML files do live.