Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Goals

  • Service display page -

    • do we want to have separate headers for different parts of the description that are consistent across all services or do we want to allow content creators to add their own headers?

  • Do we want to have an accordion menu on the left side that lists each service category and the services within that category - this would be the case for Policies and possibly resources

  • Top Navigation - Questions to ponder:

    • Should the navigation links be drop-downs or single links

    • color of the links? Black or red?

    • How do we want to handle the “Chat” link? Should this be a pop-up or go to a separate page?

    • Are “research” and “services” still the best items to have in the primary navigation?

  • Follow up from last meeting 1/4

    • The general contact forms can be consolidated and just use LibAnswers - so long as it can be linked to from several different places

    • The SCRC contact us form is different - I’m still working on trying to get Margery to accept a LibAnswers queue, but we may still need to create a separate form for her.

Discussion topics

Item

Notes

Service Display Page

The service display page layout occupied the entirety of the meeting today. We determined that for the services and policies page, we would adopt this three column layout with the service navigation on the left column.

Related groups and space: Significant time was given to the listing of related groups and spaces on the left side.

  • is it necessary to list related groups?

  • Jackie and Rachel shared a desire to rename “groups” to something else

Call-to-action buttons - at the web writing workshop yesterday, a good amount of time was dedicated to the best practice of using a call-to-action button to highlight an actionable item.

  • in our current model, we have a ‘access description’ and ‘access link’ fields that combined can create the label and link for one call-to-action button per service

  • we need to determine a standard location for this one call-to-action button per service, if it exists. The options for location are:

    • Option #1: Below the service title and above the description

    • Option #2: On the right column above the related spaces

Action items

  •  

Decisions