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

Imagine: AVIF/HEIC/HEIF variants are WebP; a failing filter serves the original (bundle #411)

Open Beginner friendly
#208 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
79/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Domain
documentation

Research direction

Start with the uploads and Imagine documentation pages named in the issue. Document the AVIF, HEIC, and HEIF variant format, failed filter behavior, cache removal command, and filter manager class behavior from the supplied bundle notes. Done when all four changes are clearly covered in the relevant pages.

Written by the indexing model from the issue text.

Description

Bundle #411 (issue #410), for the next 2.0.0 alpha. Document in the uploads / imagine pages:

  • An imagine variant of an AVIF, HEIC or HEIF original is saved as WebP (cache/<filter>/<name>.webp) unless the filter set sets format:, on every driver.
  • A filter that fails to generate (a codec the driver lacks, a corrupt image) is skipped and logged at error, and the media object list falls back to the original. It no longer 500s the resource or the page manifest.
  • Upgrade note: run bin/console liip:imagine:cache:remove (or --filter=<filter>) to remove old .avif/.heic variants.
  • The bundle sets its own class on liip_imagine.filter.manager unless the application has set one.
Dominant language
Vue
Stars
0
Forks
0
PR merge metrics
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 components-web-app/docs

All issues in components-web-app/docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.