A dialog transition. It can be definitely useful instead of heavy implementations. Here is a lightweight implementation without JS.

Emergence is a creative platform exploring the boundaries between art, design, and craftsmanship. Our name is inspired by the concept of emergence—the idea that individual elements, when combined, create something greater than the sum of their parts. We believe that collaboration between artists and makers, across disciplines like glasswork, furniture, lighting, textiles, and jewelry, transforms art into a collective experience.

a thing you absolutely cannot do is nest one interactive control inside another

it has few examples.

Upload the JSON output of the stats and visualize it

Done subtly and in moderation scroll fade can look fine†. Alas and to my dismay, subtlety is not a virtue of scroll fade proponents. Nor is timing. I’ve built too many websites that got almost to the finish line before I was hit with a generic scroll fade request. Fade what? Everything! Make everything fade into view! It’s too static, you know? Make it pop!

Winning arguments against: accessibility, impact on core web vitals

It's very chromium dependent though

Oh ok: the new UA styles will have uniform headings and not :is(article, aside, nav, section)

The use of a lot of icons in menus is a bad pattern.
12px icons are also too small for details.

A 3D engine relying on HTML and CSS.

A list of demos built with GSAP

A cross platform UI library to build to apple, android, web.

The project is available under https://github.com/water-rs/waterui

A Menu. 37 Items that redirects to other small and text only pages. That's great :)

Dioxus is the promise of having a single code base for your mobile apps and web apps and desktop apps.

The project goal is to be a real fullstack framework. A single code base for the client and for the server.

After server side rendering and client side rendering:

So boom, third generation, full stack, best of both worlds. We do the render on the server like before, and we stream it to the client, which can display it as it’s being received. But alongside that rendered HTML, the server also sends the structured data that it used to render the HTML.

Now the whole point of having the server stream markup is that we can show it early before the app is even loaded on the client.

Dioxus offers many hooks prefixed use_ to add reactivity. "If you break the rules of hooks, you don’t get a build error or even a runtime error. You just get a weird behavior, which can be hard to debug."

A second issue is

So does Dioxus spark joy? Not yet. In the meantime, I’ll be doing Rust on the backend, and TypeScript on the frontend.

The Dioxus team is doing a lot of hard, interesting work. They have a Flexbox implementation that they’re sharing with Servo. They’re doing their own HTML and CSS renderer now to make desktop applications without a full-fledged web engine.

Un client léger de 13MB à héberger soi-même.

C'est entièrement pilotable au cliver, mono ou multi-colonnes, les messages privés ont un fond hachuré pour bien les distinguer du reste et les re-pouet sont aussi différencié.

Some creative ideas on small screens. The post lists examsle:

• Use horizontal scrolling
• Push elements off-canvas
• Build scrollable mini-spreadspread
• Orientation responsive layout

Against toast notifications