Next Tier Pages Template

Included in the basic page template:

• common styles (css), scripts, includes files (header, navigation bar, footer)
• simple row/column structure which can be altered to best display the content.

---

How rows and columns work in responsive design is illustrated by this web page:

Next Tier Template with Rows

Content providers should review this and other draft pages before consulting with the web manager about the pages for which they are responsible.

Update 3/25/14 People Responsible for Web Content

Preparations for a meeting of those responsible for LS web content is underway.

Email sent to participants 3/24/14:

Caveat:  This is a large group of people who are responsible for the content on LS Web pages.  This doesn't necessarily mean that you do the actual page input.  Think big picture.  What is said.  How it appears.  How it fits in with other content.

I'd love to have everyone in the same room to express ideas but with a group this large it may not be possible.  So, I've created a Doodle scheduling poll with some possible meeting times the beginning of April.  We may have to have one or two different meetings that can accommodate people's schedule.  You are expected to meet with only one of those.  If you cannot meet, please talk with your team/group to make sure that at least one person with appropriate knowledge can attend.  I would like for a member of the IL team to be at both meetings.

For those of you representing services -- Reference, Circulation, Info Lit, eResources -- who have lots of content on the LS Web Presence, no matter where, please be prepared to talk about what you think will be happening in the next 3 years so we can make our site flexible enough to include those plans.

Email sent to participants 3/25/14:

After consulting the doodle, I've determined that the best times are on Friday, 4 April.  Choose your meeting time and send me an email so that I'll know who is attending what.
Group One:  10am-noon HBC 301.7
Group Two:    2pm-4pm  HBC 215.0

I'll give an outline of how the site will be generally organized and show the draft pages for an idea of what to expect.  You should

• Be prepared to talk about your plans (vis-a-vis web content) for the next 3 years.
• Be prepared to listen to other content planners and discuss possibilities.

The Web Team will take all information into consideration when planning the LS Web Presence and new site redesign and organization.

Update: 3/17/14 -- Instructions for the first review of draft pages

Web Team First Exploration of the Draft Pages:

Caveat: 
The LS Web Site redesign is based upon a responsive design template created by Robert Ferguson, IRT Multimedia Developer.  All elements are meant to be responsive to the size of the screen you are using so that we do not have to have a separate mobile website.  (Note: The catalog will not be part of this redesign.) DEADLINE: 3/31/14

Please test on a PAC, on your iPad or other tablet, on your phone.

This exploration is for the purpose of determining content and arrangement on the home page and to illustrate what the next tier of pages might look like, there are examples:

• A simple information page
• A simple information pages to explore branding with logos like Know How
• A page to replace very long information pages with a printable more info brochure. (Note: We will use either this format or break the long pages into multiple pages.)

DRAFT HOME PAGE - WHAT TO LOOK FOR ...
What should be there and what we might change.  Before deciding, look at all the elements on the page:

• The Navigation Bar which will be on every page of the web site.
• Note: the Services menu cannot be any longer and display correctly but what is there is up for grabs.
• The body of the page.  Notes:
• The only element that isn’t up for review is the upper right column with the heading Overview.  This short section will be used to toggle changing information like alerts and announcements.  If there is nothing to announce, etc., then the overview info will occupy that place.
• I’ve consulted Adrian on the Find Books, Articles, Videos box.  I’ve tested some elements on whomever was handy as I was working on the section.
• The Footer which will also be on every page.

Consolidate your comments into two emails to the whole Web Team –

• one email about the Home Page; 
• another about your thoughts regarding next tier pages. 

We will take these comments and come up with a draft to use when testing with students.  Ashley and I will come up with a common testing method.

Progress as of 7 March 2014

Finished:

• Draft of home page design
• Drafts of next tier pages:
• Simple info page can be used for many current pages, e.g., gen-info or faqs
• Simple info page for Know How / Information Literacy
• Using the Know How logo on the left sidebar
• Longer page information
• Multiple columns looks too busy.
• If not multi-columned, pages are too long for new look.
• Longer pages like DL and other sites (ECS, Centers, etc.) often repeat information that already exists.
• Suggest linking to the info rather than repeating.
• Can create a print-friendly page with all the linked info on it.
• Created a footer to be used on every page.
• Created pertinent CSS to make everything work.
• Created standard "includes" files:
• header-home (for home page only)
• header-next (for all next tier pages)
• navbar (to be included on all pages)
• footer-LS (to be included on all pages)

To Do Next:

For week after Spring Break

• Create a draft print-friendly page example for long pages.
• Make all draft example pages comply with includes, etc.
• Pull into a directory for test groups to look at (LS Web Team right now)
• Create a launch page explaining Responsive design and what we should look for.
• Gather suggestion for links to add or delete
• navbar / footer (exception Services which has reached its workable length)
• content for different sections on the home page (exceptions Overview which is a section that will toggle with alerts, announcements, etc.)

For People Responsible for Page Content by end of March

• Create  a document template to illustrate where their input might go.
• Create directory/folder structure for them to see.
• Create a  pathway/process for input to be given to Web Team.