Skip to content

Add the Lokum AI banner and footer to the README - #16

Merged
amirkiarafiei merged 1 commit into
mainfrom
docs/readme-banner
Sep 3, 2026
Merged

amirkiarafiei merged 1 commit into
mainfrom
docs/readme-banner

Conversation

@amirkiarafiei

Copy link
Copy Markdown
Member

Two 4:1 images from the team, placed as framing rather than decoration:

  • the İznik tile mural directly under the heading, above the tagline
  • the bazaar photograph as the last thing on the page, after the licence

Resized before committing

Both were 4128 px wide as generated, and GitHub renders a README at roughly 900 px, so the originals were serving about 4.5x more pixels than anyone sees on the first thing a visitor loads.

as generated committed
banner-tiles.jpeg 3.66 MB 401 KB
footer-lokum.jpeg 1.96 MB 112 KB
total 5.62 MB 516 KB (11x smaller)

2000 px is still double the display width, so they stay sharp on a retina screen. The banner carries its own lettering, which is what a bad resize damages first, and it is unchanged at render size.

Two details

Alt text describes each picture rather than naming the file: GitHub prints it when an image fails to load, and a screen reader reads it aloud.

No em dashes. The README had none before, and mini-courses/CLAUDE.md bans them.

Scope

The root README.md is outside the content pipeline. CONTENT_ROOT is mini-courses/, so the app reads only the category READMEs; nothing here reaches the build, the link gate or the corpus tests. npm test stays at 2053 passing.

Independent of #15, which touches only corpus files and tests/. Either can merge first.

Two 4:1 images from the team, placed where they read as framing rather than
decoration: the Iznik tile mural directly under the heading, the bazaar
photograph as the last thing on the page.

Both were 4128 px wide as generated, and GitHub renders a README at roughly
900. Resized to 2000 px, which is still double the display width so they stay
sharp on a retina screen, and the pair went from 5.62 MB to 516 KB. The
banner's own lettering is the thing that would have shown a bad resize first,
and it is unchanged at render size.

Alt text describes each picture rather than naming the file, because GitHub
prints it when an image fails to load and a screen reader reads it aloud.

The root README is outside the content pipeline: CONTENT_ROOT is
mini-courses/, so the app reads only the category READMEs. Nothing here
reaches the build, the link gate or the corpus tests.
@amirkiarafiei
amirkiarafiei merged commit aeb0bbd into main Sep 3, 2026
1 check passed
@amirkiarafiei
amirkiarafiei deleted the docs/readme-banner branch September 3, 2026 22:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant