marcomezzavilla

Message received loud and clear.

Just to clarify why there aren’t any demos right now: I originally built the site mostly for myself, as a quick reminder for simple things whose syntax is easy to forget.

The use case was simple: I have my editor open, quickly check the site, copy those 2 or 3 lines, and get back to work, already knowing exactly what they do.

Sharing it publicly came later, so demos/screenshots weren’t really part of the original idea.

That said, I’m happy to take the criticism on board, even if I don’t always agree with the delivery :)

It wasn’t, but I’d be curious to know what specifically gave you that impression.

You’re right: it doesn’t identify the device type, so the title is misleading.

The intended point is that device type is often the wrong thing to detect: a touchscreen laptop may expose both coarse and fine pointers, while a tablet may be connected to a mouse or trackpad. The snippet detects available input capabilities instead, which is usually what the interface should respond to.

I wasn’t particularly careful with the titles, but this one should be "Detect input capabilities". Thanks for the heads-up!

Features built directly into the browser, without requiring a framework or third-party library.

If the term is confusing, I’m open to better wording.

Agree to disagree. I don’t think preferring an in-place reveal makes navigation to a dedicated page a cheap UI/UX decision, it was a deliberate choice.

Each note has a stable URL that can be shared or bookmarked and can be indexed independently. A dedicated page also leaves room for longer content or links to related notes.

Flip interactions also behave differently on touch devices and require more care around keyboard accessibility. It’s a valid alternative, but I don’t see navigation to a standalone document as something inherently undesirable on the web.

Yeah, it makes perfect sense. It’s definitely on my "I really should do this, but…" list.

Not AI, just not a native speaker.

I often end up there by accident and have a laugh every time.

Sure. I was thinking of fairly narrow cases, not ordinary page scrolling:

- A swipe/drag carousel with visible arrows or dots, especially a looping carousel where the native scrollbar does not represent a meaningful start and end

- An accordion or expanding panel that animates to reveal all of its content. During the transition, its intermediate height may briefly produce a scrollbar (and a visual flash), even though the fully expanded state does not need one

- Highly visual or experimental interfaces where scrolling is communicated through another control, or where the scrollable area is decorative and scrolling is not required to access the content

If you mean the "Hide scrollbars" note, I agree 100% (:

There are a few specific situations where it can be useful, but I added the caveat precisely because it’s generally not a good practice.

You’re absolutely right, thanks for the feedback. I initially included live examples (mostly through CodePen), but they were taking too much time to maintain, so I stopped.

The Bash entry was really just a half-finished personal note that I never properly edited. It’s probably out of scope too.

That’s fair, "tricks" may be overselling it. The website is meant to be a small, opinionated collection of features I want to remember, not a replacement for an authoritative reference like MDN. I can probably make that positioning clearer.

This article is very close to the idea behind a small website I’ve been maintaining mostly as a reference for myself, but which others might find useful too: https://htmlcat.net

It’s a collection of short "post-it" notes about useful native HTML, CSS, and JavaScript features. It seemed directly relevant to the thread.

Corrections and suggestions are very welcome!

Bad: responsive design

Uhmmm, ok

I do not think the comparison really holds up.

Tailwind can produce wildly different and highly customized results; Bootstrap generally cannot. They are different approaches, and preferences are obviously valid, but I do not think they are really comparable in that sense.

Personally, I think vanilla CSS is great, but Tailwind offers a similar level of versatility while also making the way styles are written more uniform, which matters when you are working in a team and do not want everyone reinventing the wheel.

And with components, I do not think the repetition is nearly as bad as people claim.

LÖVE seems amazing, I’ve always looked at it with curiosity. There’s also the legendary Harvard CS50’s Introduction to 2D Game Development, which now uses it in its latest version.

But I’m wondering: why do mature tools like this sometimes end up on Hacker News’ front page without any particular news (like new releases or updates)? It’s just a curiosity, not a critique.

Location: Padova, Italy

Remote: Yes

Willing to relocate: No

Technologies: HTML, CSS, JS, PHP / Tailwind CSS, React / Kirby CMS, Laravel, Astro / Figma, Design System

Résumé/CV: https://docs.google.com/document/d/1SDfANuQWNheaSgmlGeOScBXe... (personal website: https://marcomezzavilla.com)

Email: hub@marcomezzavilla.com

—

Design engineer. I build and improve digital products, from interface design to code. I am neither a designer nor a pure developer; I feel most comfortable in the middle ground.

I've built a minimal bookmark manager (https://pin.garden) that I've been using myself. It’s fast, bare-bones, and distraction-free. No animations, a single font, no images. I intentionally used "boring" tech: PHP and a flat-file CMS. Now I'm curious to see how much traffic it can handle before it breaks.

You can check the live stats here: https://cloud.umami.is/share/XqWkO0u0Jmc0DZuv

Kirby is by far the most fun CMS I've ever worked with.

I’m really impressed by its unrivalled flexibility when it comes to managing content. Everything about Kirby feels refined, functional and consistent. Congratulations to the whole team for the excellent work!