iamnbutler/vitesse

Vitesse is an (upcoming) open-source UI toolkit for gpui, the fast, native Rust GUI library.

Vitesse

Note: To be renamed to gpui-kit shortly.

Vitesse is an open-source UI toolkit for gpui, the fast, native Rust GUI library.

Overview

As gpui is still in early development things will likely change in both concept and code, but here is the current plan for Vitesse:

Three key components are currently being planned.

A set of headless UI primitives in the vein of headlessUI or Radix Primitives. This will be the core of Vitesse, and will be used to build the other two sublibraries. It will be a set of composable, accessible, unstyled components that can be used to build fully custom UIs without imposing any style or layout decisions on the developer. It will also serve as an example of how to build primitive UI element with gpui.

A unopinionated color library, with an optional set of opinionated themes. This will be a set of color constants and functions for working with colors. It will also include a set of themes that can be used to style the headless UI primitives. The themes will be designed to be used as is, or to be extended to create custom themes.

A set of styled components. This will be a set of components built on top of the headless UI toolkit that provide a set of common UI elements with a default style.

Designed to make bootstrapping an apps UI seemless, these components will come with baked in styles and larger elements built from composing primitives. They will be designed to be used as is, or to be extended to create custom components.

These components are designed to make it fast and easy to bootstrap a gpui app. The components will come with in-built styles and larger elements forged by composing primitives.

Next Steps

The initial steps for Vitesse will be to study and learn from existing UI libraries, and start exploring how to build primitives.

Contributing

Contributions are welcome! As this is a component system there will be a lot of conversation around API design and component patterns, so we recommend starting a discussion before starting work on a PR.