TIFY is a slim and mobile-friendly IIIF document viewer built with Vue.js. It supports IIIF Presentation API and Image API version 2 and 3.

Check out the demo.

Continue reading to learn how to integrate TIFY into your website or application and about its options and API, visit the website for usage examples, or have a look at the documentation.

Embedding TIFY

Add an empty HTML block element with an id and a set height:

<div id="tify" style="height: 640px"></div>

Include TIFY:

• Either via npm (recommended):

   npm install tify

  • If you are using a build tool like Vite, import the required files and create a TIFY instance:

     import 'tify/dist/tify.css'
     import Tify from 'tify'
    
     new Tify({
       container: '#tify',
       manifestUrl: 'https://iiif.io/api/cookbook/recipe/0009-book-1/manifest.json',
     })

  • Otherwise, upload everything from node_modules/tify/dist to your web server and add this to the HTML output:

     <link rel="stylesheet" href="tify.css?0.34.5">
    
     <script type="module">
     import Tify from './tify.js?0.34.5'
    
     new Tify({
       container: '#tify',
       manifestUrl: 'https://iiif.io/api/cookbook/recipe/0009-book-1/manifest.json',
     })
     </script>

    Adjust the paths as needed. Appending ?0.34.5 prevents caching issues when upgrading.

• Or use a CDN like jsDelivr or UNPKG:

   <link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/tify@0.34.5/dist/tify.css">
  
   <script type="module">
   import Tify from 'https://cdn.jsdelivr.net/npm/tify@0.34.5/dist/tify.js'
  
   new Tify({
     container: '#tify',
     manifestUrl: 'https://iiif.io/api/cookbook/recipe/0009-book-1/manifest.json',
   })
   </script>

Upgrading

If you are are upgrading from any previous version, have a look at the upgrading guidelines.

Configuration

TIFY takes an options object as its only parameter. While optional, you usually want to set container and manifestUrl.

See config.js for a documentation of all available options.

An example with most options set to non-default values:

new Tify({
  container: '#tify',
  language: 'de',
  manifestUrl: 'https://example.org/iiif-manifest.json',
  pageLabelFormat: 'P (L)',
  pages: [2, 3],
  pan: { x: .45, y: .6 },
  translationsDirUrl: '/translations/tify',
  urlQueryKey: 'tify',
  urlQueryParams: ['pages'],
  view: '',
  viewer: {
    immediateRender: false,
  },
  zoom: 1.2,
})

Customizing

Many aspects of the theme can be modified with SCSS variables or CSS custom properties, allowing you to easily adapt TIFY’s appearance to your website. See the theme settings file for all available variables.

API

TIFY provides an API for controlling most of its features, see API documentation.

Build Setup

You need to have Node.js v18.0 or above, npm (usually comes with Node.js) and git installed.

Install dependencies:

npm install

Run in development mode with hot reload and automatic linting:

npm run dev

Build for production with minification:

npm run build

The production build will be stored in dist.

Running Tests

Run unit tests: npm run test:unit

Run end-to-end tests:

• Development build: npm run dev
• Production build: npm run build && npm run test:e2e

Translations

Translations reside in public/translations. Each language is represented by a JSON file, where the file name is the language’s ISO 639 alpha-2 code. Each file consists of a single object of key-value pairs; the key is the original English string, the value is the translation.

The key $language denotes the native name of the translation’s language.

There are more special keys starting with $; while all other keys are to be translated literally, these keys serve as placeholders for longer sections of text, see src/strings.json.

English keys (but not translated values) may contains translation hints in square brackets, e.g. View [noun] should be treated as a noun, not as a verb.

To create a new empty translation, run node build/create-translation.js and follow the prompts.

To check all translations for validity and completeness, use npm run test:i18n or npm run test:i18n:fix, the latter adding missing keys, removing unused keys, and sorting keys.

---