Discussion/Improvement: How can we improve the library of resources?

[cassidoo]

Right now the library of resources is a bit bland, but we also don't want it to be useless because we just throw everything in there.

[adiati98]

I think when there is a description the post it doesn't look bland at all because it occupies the whole screen.
So, we might want to have a description for each post. We can add more width to the description to make it a bit occupied, just like the title (see screenshot below in the green box).

Another thing that I see and might be helping the UI and UX (probably can also make the page feel less blend) is to make the navbar non-transparent. Currently, it's kind of distracting when we scroll, then the navbar hits a post. The texts are overlapping as in the screenshot and screen recording below.

gh-maintainer-library.mp4

[adiati98]

Looking at the first paragraph, maybe we can make the font bigger for the desktop and make it two lines catch more attention and encouraging folks to add their post?

Maybe it's just me, but my eyes drown right away to the post as they have bigger fonts. 😅

For the two lines, I'm talking something like:

Stories and interviews featuring maintainers of your favourite open source projects!

Have a maintainer story to share? [Add it here!](https://github.com/github/maintainermonth/issues/new?assignees=&labels=&template=add-to-library.yaml&title=TITLE)

However, on mobile, the font size in all parts looks almost the same.

[The-Best-Codes]

As far as general site improvements, what about accessibility? I haven't seen a lot of ARIA stuff in the code, it might be good to do.

[adiati98]

I think as long as semantic HTML can cover (for example, <button>) the most part, we don't really need ARIA.

But color contrast would be something that we want to look into.

Do you have something in mind where to implement ARIA, @The-Best-Codes ?

[The-Best-Codes]

@adiati98 Somehow I must have missed this in the code! Looking at the site with developer tools, I see that about everything I was thinking should have an aria attribute has one, so I guess this is not a concern. Sorry 😅

[adiati98]

@The-Best-Codes, don't be sorry! I'm learning about accessibility and have an interest in it, so it's nice to have discussions about it and learn from each other. 😊

[karasowles]

Thanks all, and thanks @LadyKerr for tackling this on-stream today for Rubber Duck Thursday! https://www.youtube.com/live/ugu4trHcn0M

[ashleywolf]

Picking this back up for 2026 — wanted to share what's shipped since this thread and ask for fresh feedback.

What's updated:

• Library descriptions: All 33 entries now have descriptions, so the page no longer has the empty-row look.
• Header overlap: The nav has a solid purple background, so it shouldn't visually clash with content underneath when scrolling.
• Schedule filtering (Add schedule event type filters #393): The /schedule page has an event type filter so it's easier to scan when there are a lot of events.
• Card and chip rendering (Fix schedule card text clipping #396, Fix event detail page title wrapping and chip layout #397): Long titles, locations, and chip layouts now wrap cleanly across the home and schedule pages.

Still open from this thread:

• Adriana's suggestion to bump the library intro typography on desktop and split it into two lines so the "Add it here!" CTA gets more attention.

What we'd love feedback on:

• Does the library still feel bland with descriptions in place, or is that fixed?
• Would topic-based filtering (similar to the schedule's event type filter) make the library more useful?
• Any other resources pages — partner pack, ships, security challenge — that feel undercooked?

Thanks @adiati98, @The-Best-Codes, and @karasowles for the original feedback, and @LadyKerr for the stream session.

[jsoref]

Library and its items aren't sufficiently visually distinct on mobile:

Initially I thought that everything was transparent and that I'd see the curve at the top right as I scrolled down:

But once I scrolled far enough down, I discovered that entries are opaque:

Consider styling this Library differently

I'm not suggesting green, that's just Chrome for Android's selection background color.