This code determines the theming for MIT Libraries' hosted platforms from Springshare, Lyrasis, and Aeon:
- https://archivesspace.mit.edu
- https://libguides.mit.edu
- https://libcal.mit.edu
- https://libanswers.mit.edu
- https://mit-ddc.libanswers.com/
- https://libguides.mit.edu/staff
- https://mit.aeon.atlas-sys.com/
Each platform's branding materials are contained in a separate directory. For each platform, there are usually three files:
custom-head.html- The stylesheets, javascript, and other head elements that control presentation and behavior.custom-header.html- the HTML markup for the top navigation.custom-footer.html- the HTML markup for the footer at the bottm of the page.
"Deploying" these files is a manual process. For Springshare platforms, the files must be copied and pasted into the platform's 'Look & Feel' interface. To access the 'Look & Feel' interface, first log in to LibApps. There is often a 'Look & Feel' link in the 'Admin' menu, but it some cases you'll have to navigate to the 'System Settings' dashboard first.
The 'Look & Feel' interface in LibApps has separate textarea
elements in which you can paste the header, footer, and head code.
Note that the corresponding box for head is usually labelled 'Custom JS/CSS'.
The LibGuides directory also includes custom-analytics.html, which can be found in the 'Custom Analytics' tab of
'System Settings'. This is currently Google Analytics tracking code, which we are running alongside Matomo (in
custom-head.html) for QA purposes. Once we are satisfied that the Matomo data replicates our GA data, we will remove
the GA code and move the Matomo code to Custom Analytics.
For Aeon and ArchivesSpace, the files must be emailed to staff at Atlas and Lyrasis respectively for placing on their servers.
- The MIT Libraries Brand Guide is a great starting point
- Design system based on this branding package
- GitHub repository for that design system