324 private links
A react-style library (but only 4 kB!). It is so small and uses JSX.
A component created with Atomico can be used in Html, Vue, Preact, React, Svelte, Solid or any other library.
This seems relevant for small projects or one that needs little interaction without using bare JS. The Lit library needs for example a lot of boilerplates. Here we need a function.
It uses WebGL for it.
Unstyled, accessible components for building high‑quality design systems and web apps in React.
We need this in other frameworks!
Using finite-state machines seems to be a good idea!
A collection of framework-agnostic UI components patterns like an accordion, menu, and dialog that can be used to build design systems for React, Vue, and Solid.js
A collection of UI components made with HTML and CSS
It is possible to display high, medium and low screen sizes by popularity
Another collection of CSS loaders and spinners
Another list of CSS spinners
Customizable CSS loaders and spinners
Another background css pattern generator
Another one: https://patternizer.com/4rvv
Useful for flat design
Looks complete
This is the crux of the Yard-sale model. In a free market, one person ends up with all of the wealth – completely by chance.
Looks like the monopoly game. It is inevitable. This effect is the following:
When you lose, the maximum amount you can wager goes down. So you can't win back what you lost in one coin flip.
When you win, the maximum amount you can wager goes up. So you could potentially lose more than what you won in the first game.
Besides I like the work done on the interface to make it interactive 👍
A game where you need to pick the design that is most correct. Test your attention to details!
- Due to color vision deficiencies, it’s a good idea to always complement error messages with an icon
- Additionally, it might be a good idea to guide users towards specific issues of the form with an error summary.
- Never cover user inputs
- First of all, we avoid tooltips that open on hover and display the tooltip only once tapped or clicked.
- Error message position:
- they should be placed above input for various reasons, but it costs layout shifts. In doubt, a collapsible accordion instead might be a better idea there.
- they should be placed inline in tables. One of the simpler patterns is to display the error message in the same row where the content lives.
- Avoid toast error messages
- Establish stop-words for your error messages: they should never be used. See Error messages
- Provide Examples Of Correct Input or guide the user to the expected input. For example, "IBAN starts with the country code. For example, DE or AT.
- Display Error Summary on the top
- Additionally, you might want to adjust the favicon and the title of the document if errors do appear,