Stanford-branded theme

[Camille Villa]

[GG]

@anarchivist Are there any special considerations we need to make, branding-wise, given we're including (I think?) Hoover into the stanford-arclight instance? In other words, our usual branding includes the standard Stanford footer, but also includes a SUL footer and a "Stanford Libraries" logo in the top brand bar.

Is that okay that Hoover is included within an application that is branded as Stanford Libraries? Or should we think about doing this a bit differently to make it feel less of a SUL-based app?

[María A. Matienzo]

@ggeisler (apologies for the delay; catching up from DLF).

At a first pass, I think it's less critical to address specific considerations for our local instance of ArcLight - especially for this phase, which focuses on just updating the test instance.* My assumption here is that ArcLight is like (or perhaps may become integrated into) SearchWorks, which is branded with the Stanford Libraries logo and SUL footer:

Of course, SearchWorks also contains holdings of non-SUL libraries, like some of the coordinates (Hoover, GSB, Lane, Crown) and Tanner:

* Changes in branding may come up as we get more feedback on our local instance, but that's not work we intend to complete immediately.

[GG]

Okay @anarchivist, the analogy to Searchworks makes perfect sense, thanks!

[jvine]

This is a basic set of specs to make Arclight correspond fairly closely with SearchWorks. Details will require tweaking, and @ggeisler will likely have more input. Goal is to get a SearchWorks-y starting point.

Header and search bar

• Start with base styles from My Library Account for body, headings, <a> and colour variables.
• Add Feedback link (and form!) to topbar
• Replace Arclight logo w SUL logo; link to library.stanford.edu
• Move Bookmarks from topbar to al-masthead
• Suppress the History link
• Add icons to al-masthead links
• Style header area as in My Library Account

Search results

• Facets match SearchWorks style
• Individual results are in boxes with same spacing as SW.
• The search results and controls are substantially different from SW, but the SW styling turned out to be messy to achieve and maintain. For now, use "default" button styling with $stone for the "active" state.
• Remove the .navbar styling from around the h2.facets-heading to correct its alignment

Component page w tabs

• Overall tab borders are $cloud
• Inactive tabs have $stone background
• Selected nav has $sage background

Tool box on component page

• Use $blue for the Request button as in My Library & SW.

General notes

• all borders should be $cloud
• any references to pixel-specific font sizes should be removed