Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Consider info.json sizes[] as a follow-up

Open
  • Is something wrong?
#537 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
javascript
Domain
api

Research direction

Start by locating the existing upgrade logic and how it reads IIIF Image API info.json metadata. Check how the sizes[] list could constrain upgrades when available, then verify that the implementation does not probe beyond the master or use cache-busting custom widths.

Written by the indexing model from the issue text.

Description

enhancement

IIIF Image API 2.1 and 3.0 both encourage servers to advertise pre-rendered sizes via the sizes array in info.json. Picking from that list (when available) gives a hard ceiling so the upgrade logic never probes past the master, and avoids cache-busting custom widths. Out of scope for this PR — worth a separate issue.

Dominant language
JavaScript
Stars
2
Forks
3
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CenterForDigitalHumanities/TPEN-interfaces

All issues in CenterForDigitalHumanities/TPEN-interfaces

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.