-
Notifications
You must be signed in to change notification settings - Fork 92
Finding and Using Images
When adding an image to a page/essay, it is generally best to use the <param ve-image>
tag. This tag has significant benefits over using basic Markdown such as
![Image accessibility description goes here](http://exampleurl.com/image.png)
By using the <param ve-image>
tag, your image will automatically be shown in the right-hand pane of your essay within a specialized Mirador viewer. Mirador has the following benefits:
- Zoom, display, compare images
- Create a gallery of images
- Compare and annotate images
- Automatic titling
The <param ve-image>
requires two additional attributes: title
and url
. The title
contains the description of the image which will be displayed underneath and is important for accessibility purposes. The url
is the address where the image is stored. Here is an example:
<param ve-image title="Roasted Coffee Beans" url="https://upload.wikimedia.org/wikipedia/commons/c/c5/Roasted_coffee_beans.jpg">
The <param ve-image>
tag supports the following image types:
- .png
- .jpg
- .tiff (a high-resolution format, often used in cultural heritage)
We are currently working on support for the .svg filetype. For the url
, generally it is preferred to link to a hosted image instead of uploading an image to your GitHub Repository.
The <param ve-image>
supports a variety of additional attributes that are documented here.
For most images, this is the best practice. Ideally, the image is hosted on a stable URL of some kind in a cultural heritage collection. If you have a copy of the image and the right to use it, you can also upload it to the Wikimedia Commons and link to it there.
This approach may make sense if you have an image whose rights are cleared, but that is not of general interest to the public (and therefore not appropriate for Wikimedia Commons. This makes sense for small, site-specific images like navigation arrows or buttons. Keep in mind that GitHub does enforce limitations on repository (and therefore image) sizes, so any uploaded images should be small in size.
It is a good practice to create a /images/
directory in your GitHub repository to hold sitewide images. For images that are likely to appear on a single page, include those images in the directory for that page (alongside the README.md file).
An ideal use-case for uploading an image to your GitHub repository is for a site (or page) banner.
The banner image for a particular page is declared in the <param ve-config>
tag with the banner attribute:
<param ve-config
banner="http://example.jpg">
Read more about the attributes for the param ve-config
tag.
When editing a banner image for your site, aim for:
- Height- ~400 pixels
- Width- 1200-1600 pixels
- .jpg file type
- ≤ 150 kb in size
To specify a banner for your whole site, include a link to the image in the config.json
file for the site, like so:
{
"title": "Visual Essays Documentation",
"banner": "/images/banner.jpg",
"acct": "JSTOR-Labs",
"repo": "ve-docs",
"ref": "main",
"logo": "/images/labs.jpg",
"favicon": "/images/favicon.ico",
"css": "https://cdn.jsdelivr.net/gh/jstor-labs/ve-docs@main/css/docs.css",
"nav": []
}
Juncture, brought to you by the JSTOR Labs team
Information for Content Creators
Information for Site Owners/Administrators
- Juncture Technical Architecture
- How Juncture Uses Github
- International Image Interoperability Framework (IIIF)
- Linked Open Data (LOD)