Level 1: What they say
Level 2: What they think & feel
Level 3: What they do
Level 4: Why they do it

There is for example different reasons for a cancellation: https://www.linkedin.com/feed/update/urn:li:activity:7140680577552117760/

The wheel of emotions https://uca.edu/bewell/files/2020/11/Feelings-Wheel-Learn-How-to-Label-Your-Feelings.pdf

Observe instead of asking whereas possible: https://www.smashingmagazine.com/2026/05/four-levels-customer-understanding/#observe-and-diagnose-don-t-validate

Practical ways to uncover user needs:

• Exposure hours, when every employee must be exposed to their customers for at least 2 hours every 6–12 weeks.
• Live UX testing, where we invite everyone in the company to join and observe.
• Co-design with users, where we show new features and ask users to rank them.
• Helpdesk insights, where we ask for frequent complaints and questions from the support every 3–6 months.
• Listening in, where we tune in on a customer service call, web chat, or eavesdrop where users hang out.

1. Clarity is job #1
2. Interfaces exist to enable interaction
3. Conserve attention at all costs
4. Keep users in control
5. Direct manipulation is best
6. One primary action per screen
7. Keep secondary actions secondary
8. Provide a natural next step
9. Appearance follows behavior
10. Consistency matters
11. Strong visual hierarchies work best
12. Smart organization reduces cognitive load
13. Highlight, don't determine, with color
14. Progressive disclosure
15. Help people inline
16. A crucial moment: the zero state
17. Great design is invisible
18. Build on other design disciplines
19. Interfaces exist to be used

A small efficient website.

The header is different: it's a text. It's always the same and only the rest of the view changes.

The editor: https://editor.graphite.art/

A wireframe tool that uses real wireframe

Like I mentioned, we have a base monorepo project at the studio that contains:

1. “apps”
2. Astro website
3. Design system software (Navi)
4. “packages”
5. CSS system
6. Data system
7. Design tokens
8. UI components/regions (Astro and web components)

Le mode sombre est optimal lorsque l'environnement est faiblement éclairé, l'écran de type OLED économise de l'énergie et pourrait aider à maintenir la productivité sous stress.

Le Dark Mode est perçu comme moderne, sophistiqué, high-tech et mystérieux.

Le light mode inspire confiance et professionnalisme.

Comment créer un bon dark mode:

• les teintes noires et blanches magiques pour le dark mode:

  background-color: #181818;
  color: #fafafa;

• augmenter la taille du texte (1.2rem / 20% plus grand pour le texte courant)
• utiliser des polices grasses, jamais de light, mais des graisses regular ou medium
• laisser le choix du dark ou light mode

I can’t stress enough how even a modest amount of pre-thinking, sketching or even just making a checklist beats jumping into a code editor or design tool, regardless of whether you’re doing a small ticket at work, building a personal site or even starting a whole client project. Sitting down and thinking away from the tools really helps you to consider what is actually important, what is a nice to have, how you measure improvement and importantly, what the process of iterations/cycles look like.

following

And while this is certainly a positive thing in many ways, it puts us in a riskier position when it comes to communicating our work.

Why? Because the only thing more dangerous to a design system’s funding case than a lack of understanding of what it is, is a false understanding of what it is. Particularly when that false understanding is often built on a collection of common myths that have elbowed their way, without nuance, into the psyche of our organisations’ leaders. Myths like:

• 10x faster
• don't need a design system team
• design system eradicate duplication effort
• bake accessibility into components and the job is done

Open the website twice. Got it?

A scroll-animated website well built

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 :)