The goal was to show how you can use patterns from the GOV.UK Design System to design complex case working systems.

The prototype was complete user flows with URL changes. No validators, only examples of flows with the existing design system.

That’s 100x harder to do with Figma. The audience is focused on the Figma navigation instead of experiencing the design. It also hides problems: transitions, loading states, error states adn edge cases.

20 questions pour comprendre quels sont les "dark patterns" utilisés.

En savoir plus sur les apparences trompeuses https://apparences-trompeuses.beta.cnil.fr/html/savoir-plus.html

Et sur le test https://apparences-trompeuses.beta.cnil.fr/html/apropos.html

SVG filters can be applied to HTML tags with: filter: url(#distort).

There are examples what we can do with a website :)

There is also a list of webrings on it:
https://whitep4nth3r.com/webring/

A thoughtful post about prioritizing new development in a project.

Friction exists to make us notice what we’re doing. [...] Bad friction is friction without purpose. It exists by accident, or through neglect. It asks more from the user without offering anything in return. [...] Good friction is different. It’s intentional. It’s added with a clear reason, and it earns its place in the experience — often through utility.

Good frictions:

• Holding ⌘Q to quit a browser session is a deliberate pause before closing everything
• A brief delay after sending an email, allowing you to undo before it’s final
• Intentional pagination instead of infinite scrolling is progress with awareness
• A warning when an email mentions an attachment but none is included is a small check before sending

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

« Le design, c'est faire des produits utilisables, limiter frictions, risques et déceptions »

« Idées reçues : pas la peine de demander aux utilisateurs, les designeurs ne savent faire que du cliquodrome, pas besoin d'UX pour le backoffice »

Intéressant, les orateurs disent bien qu'ils ne travaillent qu'avec des gens convaincus des beautés du libre. Sinon, la migration ne se passera pas bien. Il y a assez de travail avec les gens qui sont volontaires, il ne faut pas perdre de temps avec les autres. (C'était dit moins brutalement.)

But here’s what happened while everyone celebrated the democratization: the real challenge should have shifted from “how do we build this?” to “what should we build that people actually want?”

The barrier to building dropped to zero. The bar for what users expect shot through the roof.

Skills that matter now:

1. Understanding real user needs (not assumptions)
2. Business literacy (understanding the economics)
3. Communication skills (translating needs into solutions)
4. Craft and polish (building something truly outstanding)

When the market gets flooded with mediocre-but-functional products, users become more discerning, not less. They start caring more about how products make them feel, not just what features they have.
Start optimizing for user understanding, clear communication, business value, and thoughtful execution.

Ne soyons pas fâchés avec l’IA : c’est un outil, et c’est l’usage que nous en faisons qui détermine sa pertinence. De mon côté, je ne me sens pas menacée par ces outils.

Ce qui m’inquiète davantage, c’est l’idée que leur existence puisse laisser croire que l’on peut, à terme, se passer de l’expertise — comme si l’outil suffisait à remplacer la pensée, la méthode et l’intention du designer.

Le souci, c’est que quand la création devient trop accessible et que le content management4 se réduit à la simple production de visuels ou de posts, on perd de vue l’essentiel. Un contenu n’a de valeur que s’il sert un objectif — informer, convaincre, orienter, faire agir. Le rôle du design n’est pas de générer des images, mais de provoquer un effet mesurable. C’est exactement la logique du Design Thinking5 appliqué au graphisme : commencer par comprendre les besoins et les objectifs, pour créer un contenu qui fonctionne réellement.

• Link and button states
• color modes
• variables
• any kind of state
• viewport sizes
• anything scrolling or mouse movement related
• variable content
• units & math
• animations & transitions
• device specific details (touch screens, low-bandwidth situations)
• media handling

from https://shaarli.lyokolux.space/shaare/4Rg2EQ

A website full of design resources.

It’s a pretty broad range of topics but always through a common lens of design and creative thinking.
All resources and links are shared purely because I think they are cool, interesting or helpful.

Pick a collection of color and share the URL

Great stuff!

I’ve said it before and I’ll say it again: design is deciding. The best designers are the best deciders.

the important work is making the decision and moving on to the next stage. If the actual outputs at each stage are mediocre, that seems to be okay, as long as they’re just good enough to inform a go/no-go decision.

and a testimony from an experienced designer without experience with Figma.