Customizing DLP Libraries - VTUL/dlp-access GitHub Wiki

The title is displayed over the cover image. It should probably be no longer than 40 characters. See the Cover Image section for title examples.

This is a mandatory element. The cover image creates a visually engaging homepage, immediately highlights the content of the collection, and individualizes the homepages for each digital library. The file size must be less than 600 KB to allow quick page loading. Compressed JPEGs work well. Images will need to fit an 1110px x 450px space. Images with different dimensions will automatically be zoomed in and cropped. The image could be an item from the digital library, a solid color, or a custom graphic. Please keep in mind that the image will be automatically darkened so that the title of the digital library will be readable as an overlay on top of the image.

Images must conform to the Image sizes guidelines.

Please provide:

• An image file (JPEG or PNG), max size 600 KB.
• Alternative text for the image

Examples:

Additional customization:

• font options: Crimson (default), Acherus, Gineso
• font size
• text style: Uppercase (default), lowercase, none

The statement is a mandatory element and is intended to provide a brief introduction to the digital library. An optional heading can appear above the statement. If no heading is provided, then only the statement will appear.

Please provide:

• Statement text
• Heading text (optional)

Examples:

This optional section highlights items from the digital library. Each block in the section will display the item's image and the first four lines of text from the title which fit in the block. Longer titles will be automatically truncated with an ellipses. This element can accept any number of items.

Please provide (for each item):

• An image file (JPEG or PNG), max size 600 KB.
• Title for the item
• Link to item on the production site (i.e. https://iawa.lib.vt.edu/archive/4610h699)

Example:

The multimedia section is optional and provides a space to highlight related video content.

Please provide:

• Heading text
• Statement text
• iframe embed code (i.e. <iframe src="https://www.youtube.com/embed/8fswmAtvCqI\" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>) Note, please remove any dimensions from the iframe code if they are automatically generated.
• Link URL (for button)

Example:

This optional section acknowledges affiliated sponsors or collaborating entities by displaying their logos. There is currently no limit for the number of sponsor logos this section can display.

Please provide:

• An image file (JPEG or PNG), max size 600 KB.
• Alternative text for the image
• Link URL for the organization's website

Example:

Additional customization:

• Background color: Maroon, orange, white, gray, light gray, teal, pink
• Background style: Solid background, divider line

This optional section is used to highlight up to four categories of items within the collection. Categories consist of any group of items that can be obtained through a search of the collection using specific search terms and a search filter. For example, in the image provided below, the first category can be obtained by searching for "Travel sketches" with a filter of "type". The caption text for each block is configured separately from the search terms.

Please provide (for each category):

• An image file (JPEG or PNG), max size 600 KB.
• Caption text for the block
• Search terms
• Filter
• Number of items that the search returns

Example:

Each digital library has the option to define a highlight color for the site. To define a highlight color, please provide the hexadecimal code for the color. If no custom highlight color is defined, then the highlight color will default to maroon (#861f41). At this time only one highlight color per digital library is able to be applied.

Please provide:

• Hexadecimal code for the color (i.e. #861f41)

Examples:

The DLP can host ancillary pages not central to digital collection access. The general process is:

1. Identify the pages and their titles that you'll need
2. Create an HTML file with the desired content for each page (Alternatively, a page can be authored using the HTML editor in the administrative portal for the site)
3. If providing an HTML file, please name the HTML files using the following guidelines: 1.) The filename should match the title of the page, 2.) It should be written in all lowercase, 3.) Use a dash ( - ) to separate words. For example, people.html, get-involved.html, digital-preservation.html.

See this example of the resulting DLP page from provided HTML.

Ancillary pages are intended for content that is closely related to the purpose of the digital library. They should provide context about the digital library, policies, guidelines, exhibits, etc. There are more appropriate platforms for staff pages, departmental pages, and the like. Conversations about where to host such content can be directed to the Web Strategy Committee.

This page displays information about the digital library.

Please provide:

• Text or HTML file

This page displays information regarding the terms/permissions for usage of materials in the digital library. This section can also include optional downloadable materials, such as permission forms.

Please provide:

• Text or HTML file
• Link URL for downloadable material (optional)

This information will appear in a sidebar on both the About and Permissions pages and lets users know how they can contact someone about the digital library. Multiple contacts can be included.

Please provide (for each contact):

• Contact's title
• Email
• Group
• Department
• Street Address
• City, State and Zip
• Phone number

Each digital library requires a domain name. Some examples include iawa.lib.vt.edu (International Archive of Women in Architecture) and swva.lib.vt.edu (Southwest Virginia Digital Archives). Domain names will need to be submitted to and approved by the Web Strategy Committee.

The DLP aims to support reasonable and supportable customization while ensuring that the base template(s) remain manageable on an aggregate level so that each template may still inherit changes from the common template. We welcome requests for further customization and will consider them based on the criteria in the following list. Please note that these criteria also influence scheduling or work, but that scheduling is also influenced by other factors.

1. How widely used do we expect this customization to be? The more widely adopted we can expect a feature to be, the more likely it is to be implemented. We want our limited resources to be used to support the features with the greatest impact.
2. How necessary is this feature to the user experience? If a collection is dependent on specialized features that can't be replicated to a reasonable degree with existing functionality, it's more likely to be implemented.
3. What is the difficulty of implementing and maintaining this customization? Features that are easier to implement and maintain are more likely to be implemented.