uoregon-libraries / uolib-primo-nui

University of Oregon Libraries implementation of the Primo New UI
0 stars 0 forks source link

Add footer to Primo #85

Open MargaretA-UO opened 3 months ago

MargaretA-UO commented 3 months ago

As we update the public website, I understand there is a desire for all associated sites to adapt their look and feel to align more closely with the main web site. One thing we haven't done yet which might be a fairly gentle lift is to add a footer to Primo that echoes libweb. This is not urgent, and maybe we want to wait until the New Discovery Experience next year, but wanted to get it on the list. Here's a doc someone wrote up about how to do this, although I'm sure it's more basic than you actually need. Maybe I'll try it myself!
At some point. https://docs.google.com/document/d/1RZTD9V8m4bHvLTl10pyFY0XbVJ6tgmsD/edit#heading=h.gjdgxs Thanks. Margaret

jechols commented 3 months ago

I'm going to beat this dead horse yet again: we should not standardize our sites beyond very minimal branding. We should make it clear users are on a different application. We should push back against anybody suggesting we standardize vendor sites. We should push back hard and repeatedly.

Making vendor sites look like our main properties is confusing to users and extremely costly to us. Even making in-house sites look like our Drupal site has proven very difficult, and we often have a lot more control there than vendor sites. Long-term costs are routinely overlooked, but when Cosmic (the UO Drupal theme) changes, having to modify half a dozen vendors in ways that are specific to those vendors, and then modify half a dozen local sites on a variety of stacks... it just isn't sustainable.

So while a footer in itself doesn't seem like a big lift, the more things we do, small as they all seem, the more time we spend maintaining all the little pieces.

</rant>

MargaretA-UO commented 3 months ago

I hear what you are saying. I wasn’t thinking about capacity.

In my time managing web projects at previous jobs, this was a persistent usability goal – to not disorient users, and to give them consistently familiar cues and links.

At the least, I think we should have similar links available in the footer, so people don’t get stranded. M

From: Jeremy Echols @.> Sent: Thursday, August 15, 2024 10:04 AM To: uoregon-libraries/uolib-primo-nui @.> Cc: Margaret Alexander @.>; Author @.> Subject: Re: [uoregon-libraries/uolib-primo-nui] Add footer to Primo (Issue #85)

I'm going to beat this dead horse yet again: we should not standardize our sites beyond very minimal branding. We should make it clear users are on a different application. We should push back against anybody suggesting we standardize vendor sites. We should push back hard and repeatedly.

Making vendor sites look like our main properties is confusing to users and extremely costly to us. Even making in-house sites look like our Drupal site has proven very difficult, and we often have a lot more control there than vendor sites. Long-term costs are routinely overlooked, but when Cosmic (the UO Drupal theme) changes, having to modify half a dozen vendors in ways that are specific to those vendors, and then modify half a dozen local sites on a variety of stacks... it just isn't sustainable.

So while a footer in itself doesn't seem like a big lift, the more things we do, small as they all seem, the more time we spend maintaining all the little pieces.

— Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https:/github.com/uoregon-libraries/uolib-primo-nui/issues/85*issuecomment-2291728475__;Iw!!C5qS4YX3!CnRKvVZ2XCAnm3Oui33Ouvg0iYrD9ZPgMrYYBNHO5zONng4ANYWVCpyZtihm6sof2fL0S0DopLsS4GFLqGFVVMoL5cj2$, or unsubscribehttps://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/ASE4BQANJO4K4BFWRBNPUM3ZRTNRPAVCNFSM6AAAAABMSQDDX2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJRG4ZDQNBXGU__;!!C5qS4YX3!CnRKvVZ2XCAnm3Oui33Ouvg0iYrD9ZPgMrYYBNHO5zONng4ANYWVCpyZtihm6sof2fL0S0DopLsS4GFLqGFVVLtTvv1N$. You are receiving this because you authored the thread.Message ID: @.**@.>>

jechols commented 3 months ago

So first: it's possible I'm assuming too much. When I worry about these topics, it's because of previous attempts at extreme brand alignment. Our old ILLiad site (I don't know how to find it now) and our old Scholars' Bank site used to have headers and footers that matched the library Drupal theme almost perfectly.

This was Scholars' Bank in 2017:

image

This was the library homepage at the same time:

image

It was so close, but we could never make it quite the same. It took a lot of time to try and keep things in sync. After a while we'd forgot something, and the two would diverge just enough to be really confusing. Occasionally links would be different or even broken. Or the zoomed-in / mobile views would totally diverge, stuff like that. Then there were problem reports where people wouldn't know what site they were on, so we'd just get "the library site is busted" and have to try and figure out from their description which service they were talking about.

If that kind of alignment isn't what you're talking about, we can kill this conversation :)

MargaretA-UO commented 3 months ago

That SB site looks awesome! I bet it was a lot of work. And yeah, exact matching probably shouldn’t be a goal. I’d settle for at least a nod and similar links.

From: Jeremy Echols @.> Sent: Thursday, August 15, 2024 10:52 AM To: uoregon-libraries/uolib-primo-nui @.> Cc: Margaret Alexander @.>; Author @.> Subject: Re: [uoregon-libraries/uolib-primo-nui] Add footer to Primo (Issue #85)

So first: it's possible I'm assuming too much. When I worry about these topics, it's because of previous attempts at extreme brand alignment. Our old ILLiad site (I don't know how to find it now) and our old Scholars' Bank site used to have headers and footers that matched the library Drupal theme almost perfectly.

This was Scholars' Bank in 2017:

image.png (view on web)https://urldefense.com/v3/__https:/github.com/user-attachments/assets/d8202f5a-13a1-4ef6-ad8f-20492be3d003__;!!C5qS4YX3!CEnPwQf7ffk5jbcY2MAx-80PXMFwZ5lkw9sXLA0N4mLOUfWHX1q9pk69j6fMzBeri34M6_htKbp5Oka41BQMl3mEM8-v$

This was the library homepage at the same time:

image.png (view on web)https://urldefense.com/v3/__https:/github.com/user-attachments/assets/11ba244a-fbee-40cb-8a10-bfb55619deb9__;!!C5qS4YX3!CEnPwQf7ffk5jbcY2MAx-80PXMFwZ5lkw9sXLA0N4mLOUfWHX1q9pk69j6fMzBeri34M6_htKbp5Oka41BQMl7dSWa1t$

It was so close, but we could never make it quite the same. It took a lot of time to try and keep things in sync. After a while we'd forgot something, and the two would diverge just enough to be really confusing. Occasionally links would be different or even broken. Or the zoomed-in / mobile views would totally diverge, stuff like that. Then there were problem reports where people wouldn't know what site they were on, so we'd just get "the library site is busted" and have to try and figure out from their description which service they were talking about.

If that kind of alignment isn't what you're talking about, we can kill this conversation :)

— Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https:/github.com/uoregon-libraries/uolib-primo-nui/issues/85*issuecomment-2291853009__;Iw!!C5qS4YX3!CEnPwQf7ffk5jbcY2MAx-80PXMFwZ5lkw9sXLA0N4mLOUfWHX1q9pk69j6fMzBeri34M6_htKbp5Oka41BQMl0ohfBct$, or unsubscribehttps://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/ASE4BQDFCMB4AMKUHOJS5DLZRTTEBAVCNFSM6AAAAABMSQDDX2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJRHA2TGMBQHE__;!!C5qS4YX3!CEnPwQf7ffk5jbcY2MAx-80PXMFwZ5lkw9sXLA0N4mLOUfWHX1q9pk69j6fMzBeri34M6_htKbp5Oka41BQMlwAy2MZV$. You are receiving this because you authored the thread.Message ID: @.**@.>>

jechols commented 3 months ago

Heh, I hated that SB site's look. I don't love the current look, either, but I like that it's clearly its own property 😁