Wellcome Collection is a free museum and library that aims to challenge how we all think and feel about health.

Digital media and services are vital to our mission. They include:

• A unified search for all our collections, both on our website and as open APIs
• Access to millions of digitised images through IIIF APIs, shared with open and permissive licences
• Long-form narrative content published at https://wellcomecollection.org/stories

Our GitHub account contains the code and configuration we use to build and run these services. Everything we've made is open source, made available under an MIT licence.

We work in the open, so that others can learn from our mistakes and successes.

• The Wellcome Collection website is the public face of our digital offering, and it pulls in content from a variety of services. (repo: wellcomecollection.org).

• Our account services allow users to manage their library membership, and will allow them to order items from the library's closed stores (pending release).

• Our editorial content – including stories, exhibitions, and events – is stored and managed in Prismic. We use the Prismic API to fetch content and display it on the site.

• The catalogue API powers our unified collections search. It's backed by a pipeline that combines data from different library and archive catalogues. (repos: catalogue-api, catalogue-pipeline)

• Our storage service is the long-term preservation repository for our digital collections. It keeps our files in cloud storage providers, stores multiple copies for redundancy, and verifies every copy is stored correctly. (repo: storage-service)

• We have workflow systems that process new content before it's uploaded to the storage service. Currently we use intranda's Goobi for digitised content and Artefactual's Archivematica for born-digital content. (repos: goobi-infrastructure, archivematica-infrastructure)

• We make images available through IIIF APIs, an open standard used by many libraries and museums. Our IIIF services are provided by Digirati, and fetch images from the storage service. This includes both the APIs and the pre-processing required to make images available.