Library item 1: a small library item that adds a "Page updated last..." with a date that updates on save. Hope it works! Here's what the code looks like: Last update: <!-- #BeginDate format:Am1 -->October 29, 2007<!-- #EndDate -->

Library item 2: a back button! This will come in handy for the photo album pages. I've generated them with Dreamweaver, but they don't link back. With this button, I won't have to separated code each page. Just plug and play code: <center><input type=button value="Back" onClick="history.go(-1)"></center> (courtesy of The JavaScript Source!! http://javascript.internet.com).

Library item 3: Return to top - a small library item to put at the bottom of a page so the reader can go to the top! It has to be complemented on each page with a named anchor id="top". I added this code to the template, so it will be inserted on all pages. Here's the code: <div><p align="right"><a href="#top">Top</a></p> </div>. PROBLEM: I want this to be at the bottom of the page, just above the footer. How to code it, CSS-wise?

Code snippet 1: This snippet actually encloses the library item#1. Hopefully, I can add this snippet to webpages to show when I've created a web page (which needs to be editable, hence a snippet). By enclosing the library item, I think I'll include code to show whenever the page is updated. Hope it works! Here's the code: <div class="date"> Page created: mm/dd/yy last update: <!-- #BeginDate format:Am1 -->October 29, 2007<!-- #EndDate --></div>. The CSS styles the DIV to be right-aligned, with smaller text. PROBLEM: how do I get the DIV to stay at the bottom of the page, just above the footer?

Code snippet 2: This snippet puts a generic breadcrumbs onto a page, and then I will correct the suggested text. At first I put this into a template, but I might forget to change the names! As a snippet, I'll be more conscious of adding something, and of the need to update it - I hope! Here's the code: <div id="breadCrumb"><a href="http://krypton.fhda.edu/%7Eraupmart/hw/requirements.html">Martha's COIN74b </a> / <a href="#">Europe 2006 </a> / <a href="#">Day # </a> / <a href="#">Country</a> / <a href="#">City</a> / <a href="#">Excursion</a> / </div>.

Storyboard proposal: My final project for COIN74b will be a personal web site about a trip we took to Europe in 2006. As such, "Europe 2006" will focus on showing the photos and videos we took while there. The intended audience is my family and friends, and our fellow tourmates. I will also strive to add other information about the places we saw, for personal enrichment. For me, it's a way to re-live the experience, and to share it at the same time. A secondary purpose is to create a set of tools (snippets and library items) and templates that can be used for other tours taken (Turkey in 1996 and Morocco in 1998) and yet to come. The general outline is already evident on the index page: Europe 2006. Most of the links do NOT work, but these few do: day 1, Windsor; Black Forest (with placesaver images and text).

Comment on usability: Usuability is essential! What's the point of putting something online, if it's not useful, i.e., "readable" and "accessible" to one's intended audience. That being said, I must admit most of my work online is personal, and very few people ever see it. So, theoretically, I could just satisfy my own preferences. Nevertheless, one never knows what the future entails, and it makes sense to write for the widest possible audience. So - it's worth learning about various typical usability/accessibility issues, "just in case"...