What are you building? ๐
10.01.2025 15:12 โ ๐ 0 ๐ 0 ๐ฌ 1 ๐ 0@honzatmn.bsky.social
Design systems and design engineering. Leading product and design at Supernova.io
What are you building? ๐
10.01.2025 15:12 โ ๐ 0 ๐ 0 ๐ฌ 1 ๐ 0Not @ariakitjs, but @ariakit.org of course
10.01.2025 10:27 โ ๐ 0 ๐ 0 ๐ฌ 0 ๐ 0A nice new example from @ariakitjs: Command Menu with Tabs โค๏ธ
It has it all โ tabs, multi-column layout (grid), full keyboard navigation, solid API.
ariakit.org/examples/di...
โฆ and let people follow the example ๐ฅ
Any mentionable benefits you got from this strategy? How did it work in large orgs where you worked at?
So itโs for the content of the folder/folder items if I understand correctly
TreeFolderItems or TreeItems would maybe work better for me
I guess you want to avoid using prop? <TreeFolder items={children}>{item}</TreeFolder>
Design system teams should be actively refactoring the codebase to drive adoptionโrather than only asking others to do it. Major benefits for the system come from it too.
Whatโs your take on this?
Looks solid, great that the virtualization is considered from initial API designs ๐
Whatโs not fully clear just from these examples โ what is a difference between TreeFolder and TreeLevel?
Thank you also for the example with virtualization. Will there be also ComboboxRenderer, similarly as SelectRenderer?
Have you considered merging these 2 components together somehow? There are many similarities between them, and I see "searchable selects" more often now (especially in B2B patterns)
Thank you!
Tag looks awesome, and the example with integrated combobox is amazing โ exactly what I was saying "it would be great to have it" ๐
I also welcome the change with the "integrated" combobox provider within Select component, which should make the last example a bit simpler too
Are the experimental features available somewhere already? ๐ Even if it's for testing still, happy to be part of that and provide feedback
Also curious about what changes are coming to Combobox API. Any chance there is public RFC/API design doc?
Thanks for any details you can already share
Tldr: From the first look, it appears very promising and as a good "base components companion" to my favorite Ariakit.
And not to forget that Base UI is still still in v1.0.0-alpha.
I really look forward to trying it out and seeing how Base UI will evolve in the future.
After Radixโs useful (but polarizing?) asChild prop, I wondered how Base UI would approach it.
They kept it simple: a `render` prop that can accept either a component or a function. Clean, flexibleโthoughts?
base-ui.com/react/handb...
Tooltip has also one interesting prop: `trackCursorAxis`. It gives some flexibility to design decisions.
Additionally, it has a `hoverable` property that you can use when you need the tooltip to be interacted with further (e.g., when it contains a link)
If you've been working with dialogs or popovers, you know the struggles with focus management.
Base UI provides props to manage focus when opening but also when closing a dialog.
This will save some headaches.
Expandable components like Accordion or Collapsible feature a useful prop called `hiddenUntilFound`.
What does it do? It simply expands the item when someone searches for it using the built-in browser search. Great attention to detail.
Radix is dead, long live the Rad... @base-ui.com! ๐
Design system creators, this is a must-explore library of React UI components. There is a lot of built-in functionality and interesting API design choices.
A few examples in a thread ๐งต
What a great question. This article by @maggieappleton.com will explain it much better than I ever could and adds a list of interesting folks to follow on top of it
maggieappleton.com/design-engin...
Did you try to update to the latest version? I think it appeared after, together with a changelog
17.12.2024 13:02 โ ๐ 1 ๐ 0 ๐ฌ 1 ๐ 0A list of applications from Raycast Wrapped: including Figma, Cursor, PhpStorm, Github Desktop, or Linear.
Tell me you're a design engineer without telling me you're a design engineer ๐พ
Thanks for latest @raycast.com Wrapped!
Imagine a call with a prototype in hands
28.11.2024 17:09 โ ๐ 0 ๐ 0 ๐ฌ 1 ๐ 0If you want a really good deep dive into testing with screen readers, I strongly advise reading this guide by @sarasoueidan.com
www.sarasoueidan.com/blog/testing...
#a11y #screenReaders #accessibility
An infographic. There are six panels. 1. "Slow internet. Alt text is shown in place of unloaded images." a drawing shows a phone with poor signal, and alt text is visible where the image should have loaded. 2. "Findabillity. Alt text helps to search content." A drawing shows someone searching 'dog with banana' and a post is shown underneath without the words 'dog' or 'banana'. It is implied to be part of the alt text. 3. "Screen readers. Alt is read out to people using text-to-speech software". There is a drawing of the output a screen-reader would show when viewing an image with alt text on bluesky. 4. "Translation. Alt text can be translated". A drawing shows a post being translated. The alt text is also translated into german. 5. "Readability. Text in images can be made legible" There is a drawing of some truly awful handwriting inside a speech bubble. The alt text clarifies what the text is supposed to say. 6. "Disambiguation. Description helps clarify intent." There is a drawing of a post with a picture of a creature. This is styled after the famous optical illusion of a rabbit and a duck. The alt text clarifies that the animal is a rabbit. It definitely looks more like a duck.
Generally we think of alt-text as the domain of those with accessibility needs.
However alt-text is useful for many reasons, which benefit your viewers, as well as you, the creator!
๐
03.07.2023 19:56 โ ๐ 3 ๐ 0 ๐ฌ 1 ๐ 0Goldman Sachs' design system has a page called "Design System Concepts" ๐ก
It's an effective way to show that their naming isn't random, but rather intentional, leading to a more coherent API and language ๐
https://design.gs.com/foundation/design-system-concepts
A new resource on @figma.com community โ a blueprint for a button component ๐
It's an example of how to build a well-usable component with some useful Figma tricks applied. Copy/paste it to your files and tweak it to your liking ๐จ
https://www.figma.com/community/file/1242237541978933162