31–40 of 44 posts
What is specific in this UI design system pertaining to 'travel projects'?
- Seat: https://beta.orbit.kiwi/components/visuals/seat/
- Stopover arrow: https://beta.orbit.kiwi/components/visuals/stopoverarrow/
That's a big red flag for an open-source design system.
Design-wise, the Figma files look nice but are poorly built. Most of the text and colors don't use styles, and the few color styles they use are in a private library.
There's some documentation (good) but the components make a lot of mistakes. You're better off starting from scratch.
The title ("Orbit – open-source design system documentation") is a bit confusing to me (I'm a technical writer so anything with "documentation" catches my eye). It seems like the provided link is just the documentation for a collection of open source web components? Or is the documentation itself open source? I'm not trying to be pedantic here, just asking in case I'm missing something. In other words it seems like t…
I also have some trouble figuring out which of the following ways to parse it (open-source) ((design system) documentation) (open-source design) (system documentation) (open-source (design system)) (documentation)
These nouns connect arbitrarily like molecules in a liquid, forming one completely opaque (and barely palatable) whole.
The title ("Orbit – open-source design system documentation") is a bit confusing to me (I'm a technical writer so anything with "documentation" catches my eye). It seems like the provided link is just the documentation for a collection of open source web components? Or is the documentation itself open source? I'm not trying to be pedantic here, just asking in case I'm missing something. In other words it seems like t…
I used to work at Kiwi.com when Orbit was started. It grew into such an impressive framework! It’s been advertised as “components for your travel site” for a long while but it’s totally appropriate for any kind of site.
I've been doing a lot of research into design systems and one thing that's lacking in most of these documentation sites is examples build with the component library. It's hard for me to get a feel for it without being able to click through a real application. Also, paid managed services on the backend are super common. I want a paid frontend component library. There are very few of these and I think there's room for…
For more general use I guess it’s hard to compete with the likes of Material UI.
The title ("Orbit – open-source design system documentation") is a bit confusing to me (I'm a technical writer so anything with "documentation" catches my eye). It seems like the provided link is just the documentation for a collection of open source web components? Or is the documentation itself open source? I'm not trying to be pedantic here, just asking in case I'm missing something. In other words it seems like t…
Yep, sorry, it's probably a bit confusing. The whole design system is open-source, from its components to also the documentation. You can find it on the GitHub repository: https://github.com/kiwicom/orbit/tree/master/docs
I've been doing a lot of research into design systems and one thing that's lacking in most of these documentation sites is examples build with the component library. It's hard for me to get a feel for it without being able to click through a real application. Also, paid managed services on the backend are super common. I want a paid frontend component library. There are very few of these and I think there's room for…
Check out their main site kiwi.com for examples.
This is part of a trend with enterprise design teams of open-sourcing their design systems. In some cases, there are direct benefits to clients and partners. Otherwise, it's a status project / time-filler.
The problem I have with all these self-promotion frameworks (i.e. CSS frameworks open sourced by commercial entities) is that they are inherently at the mercy of said companies. Take Zurb Foundation for example, as far as I can tell its basically become abandonware. Foundation 7 has been promised forever and yet we're still stuck with Foundation 6 which has all sorts of bugs and gotcha's that will catch people out be…
I think Material UI is going pretty strong, too? They've just released a beta of version 5. I think overall the comes-from-corporate-entity frameworks are probably still a better bet than the one-persons-pet-project ones - there are loads of those, too.
> By default, our libraries use Circular Pro, which isn’t an open font. That's a big red flag for an open-source design system. Design-wise, the Figma files look nice but are poorly built. Most of the text and colors don't use styles, and the few color styles they use are in a private library. There's some documentation (good) but the components make a lot of mistakes. You're better off starting from scratch.