31 May 2009

Page 3 Level Ponderings

Starting work on page 3 level design. (5/31/09) Progress noted in green. (6/4/09) Further progress noted in blue. (6/7/09)

Use as base http://library.austincc.edu/mp4-page3-tutorials.htm [Note: nothing there yet has changed (5/31/09) except underlying stylesheet.] Changes reflected in page named, mp4-page3-tutorials.php.

  • Style sheet = csslayout-page3.css
  • Have changed "topsection" to correlate to smaller graphic 756x50. Now named topsection3.
  • Removed height style for "topmenubar." [Note: should do this across the board.]
  • Page renamed with extension "php" so that we can use php command lines in the file.
    • Have used "php includes" for the topsection and the footer so that the constant top part and footer part do not have to be hardcoded into the level 3 pages. {Includes allow the inclusion of external files in the body of the page; in this case, included are topsection3.htm and footer-other.htm.}
  • Maybe use LEFTNAV style instead of main-content1 on left sidebar on this level page and ff. (See left-navigation.txt.) Created a new "navlist" for left sidebar. Includes code for indication of current page.
  • Include javascript for breadcrumbs on this level page and ff. Make into a division instead of table.
    • Put in columnhead for main-content3 (right large column)
    • Added embedded styles and modified from original:
      • #control, .breadcrumb
      • Actually, used a new style class "crumbs".
Have created two test pages to illustrate function of lefnav menu:
-- Tutorials (http://library.austincc.edu/help/mp4-page3-tutorials.php)
-- Research Shortcuts (http://library.austincc.edu/help/mp4-page3-shortcuts.php)

Help by Subject

I rather like the way that Boston College does its Help by Subject page. Perhaps we could adapt our page to emulate this approach.
http://www.bc.edu/libraries/help/subject.html

Possibly we can anticipate that Red (and some others) might want a simple listing of databases by subject. This will be possible when Adrian finishes her CASE input. That will result in a generated page of e-resources A-Z and a subject list of e-resources. See, for example, the database listing at Texas State (http://catalog.library.txstate.edu/search/y)

28 May 2009

Subtle Color chart

I've started a chart reflecting some subtle colors. (Well, maybe some aren't so subtle.)

Anyone can add possibilities to this chart.

http://irtstaff.austincc.edu/peloquin/09Redesign/redesign09-maybe-colors.xls

Tier Two Thoughts

This page will have the same topsection and topmenubar as Home.

See the document
http://irtstaff.austincc.edu/peloquin/09Redesign/TierTwo-Divs-classes.doc

Possible Changes:
  • Smaller footer (?? footer2)
  • Sidebar menu -- Should it remain the same? [[probably]]
  • Currently the large content area uses style div main-content3 with an inline style changing the width to 565 px. Should probably be given it it's own style name -- ?? "right-content" -- with similar styles and that added to the main style sheet (now called csslayout_homepage[2].css)
    • Note: We will eventually call the stylesheet something like "csslayout-library.css"
    • Should we have a separate stylesheet for tier two? Probably not, but we should for other following pages -- e.g., list of tutorials or AtoZ list -- because they will have a smaller topsection and possibly a breadcrumb trail.

09Redesign Pages CSS Divs/Classes

In organizing my thoughts for the redesign, I've created a graphic which outlines the major CSS Divisions and Classes. The stylesheet is adapted to fit our needs from Edward Terry's master stylesheet so as to maintain the look of the ACC website while enabling our content to fit the needs of the students and faculty.

The document with the descriptive outlines can be found at
http://irtstaff.austincc.edu/peloquin/09Redesign/Home-Divs-classes.doc

As the second tier and following pages firm out, I'll create a similar document to guide the persons who convert the pages.

The intention is that templates be created for those second and ff pages so people don't really have to know the names of divisions and classes, but it may help with troubleshooting.

All stylesheets created will be made known to all persons who will be working on the conversion. Changes to stylesheets will affect many pages, so any variations should be coordinated with the persons working on pages. If only one page is affected, then the change should be reflected in the embedded style on the page and documented by comments.