Malformed sizes attribute on meetup thumbnails; project images lack dimensions
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 75/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- html, jekyll, yaml
- Domain
- frontend
Research direction
The malformed sizes value comes from the events preset in _data/picture.yml, so start there and move the fallback width into a size: key. Then check how .meetup-thumbnail renders on desktop to choose the right size. For the project images, find where the img.ogimage markup is generated on the /projects/ page and add width and height attributes. Done when the rendered sizes attribute is valid and all 10 project images have dimensions.
Written by the indexing model from the issue text.
Description
Summary
Two image-markup problems:
- Malformed
sizeson meetup thumbnails. Theeventspicture preset outputs
sizes="((max-width: 600px)) 100vw, () 690px".
()isn't a valid media condition, so browsers throw that entry away and fall back to100vw. The cause is in_data/picture.yml: thedefault:size is written undersizes:as if it were a media query named "default". In jekyll_picture_tag the fallback size goes in a separatesize:key. There's also only one candidate (690w), sosrcsetgives the browser nothing to choose between. - Images on the Projects page have no dimensions. The 10 project images (
img.ogimage, loaded from each project's own site) have nowidthorheight.aspect-ratio: 1.91/1in.ogimagestops most of the layout shift, but it's worth confirming with Lighthouse CLS on/projects/.
Evidence (2026-10-14)
Rendered HTML from https://civictech.ca/ and /projects/. Playwright counted noDims=10 on /projects/.
Suggested fix
events:
formats: [webp]
widths: [345, 690]
sizes:
mobile: 100vw
size: 345px
Check the size against how wide .meetup-thumbnail actually renders on desktop. For project images, add width="1200" height="628" (the standard OG image ratio).
Related: #156
Generated by Claude Code
- Dominant language
- HTML
- Stars
- 1
- Forks
- 6
- Avg merge
- 1d 52m
- Merged PRs (30d)
- 7
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from CivicTechTO/civictech.ca
-
accessibility
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
CivicTechTO/civictech.ca#192 ·
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
CivicTechTO/civictech.ca#189 ·
-
accessibility
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
CivicTechTO/civictech.ca#184 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
CivicTechTO/civictech.ca#101 ·
-
accessibility good first issue
Difficulty 1/5 Under an hour Newbie friendliness 76/100
CivicTechTO/civictech.ca#97 · 2 comments ·
All issues in CivicTechTO/civictech.ca
Similar issues
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
paipai1999/POS-system#2 ·
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
r-afael/better-yt-recommendations#24 ·
Maintainers usually reply within 1 day
-
good first issue ui
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
calagopus/panel#285 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 Under an hour Newbie friendliness 88/100
adobe/react-spectrum#10909 ·
Maintainers usually reply within 1 day