Infinite Scroll checklist

*If in doubt, always prefer pagination.

• With infinite scroll, always integrate a footer reveal.
• Consider separating “old” and “new” items visually.
• Provide an option to continue browsing later.
• Consider using “load more” + infinite scroll together.
• Consider using pagination + infinite scroll together.
• Change the URL as new items are loaded in and expose it to users.
• Allow users to jump to any page with a pagination drop-down.
• Consider using scrollbar range intervals.
• Consider allowing users to pin or bookmark items/areas of interest.
• Make sure accessibility and performance are major considerations in the implementation.

I totally agree and it felt natural to me

Memory and local storage are great for “private” state — settings, caches, history. URL parameters are good for the “public” state, so that one could bookmark or forward the stateful link.

LOL

A framework for building a web app in Rust 🤔
May be useful someday.

It's true that the Rust ecosystem is growing and tools are coming. But we lack the knowledge of how we can put things together. Here it fills the gap.

Comparing common concepts of web frameworks daily usage.

For each concept, an example in the framework is provided.

I would also prefer an open web instead of limited super-apps.

What will happens when the web content will be published to these platforms only, as it is currently the case with the different channels ?

I’m saying: consider the options, weigh them up against the norm and test them out. As long as you have a good reason behind the implementation, it kind of doesn’t matter what others think.

Why zoom is deactivated on some websites ? What is the advantage ?

You can force it though:

In Firefox find the settings, select “Accessibility” and activate “Zoom on all website”
In Chrome find the settings, select “Accessibility” and check “Force enable zoom”

A blog made of different component. We can see them on hover.

Instead, we can mix 3 or 4 designs together to create something unique. For example, maybe I’ll take the color scheme from one site, the general layout and spacing from another, and the typography styles from the third!

When I’ve mentioned this strategy to actual designers, they laugh and say that it’s what they all do. I think this is their version of the “joke” that programmers spend half their time googling things.

A report of all important event concerning the web

Icons, Illustrations, Elements, Emojis

A feedback about typography on the web

Minimal web framework based on XML syntax

Focus on privacy, protection against malicious code; encryption (of everything); extending the web; make it fast; easy to publish; customization per user; first-class experience for non-English-speakers; improve accessibility

May be useful someday

There is no institution that regularly releases new versions of the web, and recently happily announced this one.

I totally agree. The web is now a bunch of technologies together: older ones and new ones. Both useful for some cases.

One of the reasons that I advocate for SQLite on the server is that I've noticed that servers written on SQLite generally require less maintenance than those written on Postgres. I've also found that servers written in ways that can be deployed as static binaries tend to require less maintenance than those with more complicated deployment setups.