Closed hackartisan closed 1 month ago
Things that are required to be on every page:
all these except accessibility are on princeton.edu (it's higher up on that site)
Maybe re-write this ticket as a "campus footer" and "app footer" distinction.
Not sure if the balance is quite right
Nothing in the middle
Reverse
@beth-german these are great!
Further discussion in slack lux channel
Matthew suggests using this link for the copyright link in the footer: https://library.princeton.edu/about/policies/copyright-and-permissions-policies
@beth-german should we call the link something other than "Copyright Infringement"? Like maybe "Copyright policy"?
"Library Copyright Policy" or "Copyright Policy"?
I think it's clear it's the library policy if you follow the link, probably the shorter version is okay.
User story
We agreed on the last mockup provided below in comments.
The top part of the new footer includes a lot of elements that are primarily relevant for the library website. We'd like to be able to just include the bottom part, but there a few things it needs to always have:
Acceptance criteria
.rubocop_todo.yml
create a new ticket to address the rubocop todo.Implementation notes, if any