Getting Started

Introduction

Inkline is a UI component library, published as a native package for seven frameworks.

Inkline is a UI component library. You install one package for the framework you already use, import the components, and ship.

There is no wrapper layer and no shared runtime. @inkline/react is React components, @inkline/vue is Vue components, @inkline/svelte is Svelte components — each one native to its framework, each one built from the same source so the API and the visual result match across all seven.

Who it's for

You are building an application in React, Vue, Svelte, Solid, Angular, Qwik or Astro and you want accessible, themeable components without adopting a design system you cannot restyle.

Inkline is a good fit when:

  • You want the same component API across more than one framework — a team running a React app and a Vue admin panel gets one set of components, one theme, and one mental model.
  • You want to restyle everything, not override it. Components carry no baked-in brand; their appearance comes from design tokens you control. See Theming.
  • You want the behavior without the styling. Every component ships a headless counterpart — the same structure, state and accessibility wiring, no classes.

It is not a good fit if you need a large catalog today. Inkline ships eight components.

What's in the box

Each framework package exports the same eight styled components:

IBadge · IButton · ICheckbox · IFieldGroup · IHamburgerMenu · IInput · IRadioGroup · ISwitch

and, from the /headless subpath, the unstyled parts they are composed from (IButtonBase, IInputControlBase, ISwitchLabelBase, and so on).

Browse them under Components, where each one has a code sample for every framework.

How it is built

One source, compiled to seven native outputs. Each component is written once as a .uf.tsx file, and Unframework compiles it to idiomatic React hooks, Vue <script setup>, Svelte runes and an Angular standalone component, with no shared runtime tagging along.

You don't need to know any of that to use the library. Unframework is a separate product with its own documentation, and nothing on these pages requires it.

Next steps

  1. Installation — add the package for your framework.
  2. Your first component — render a button and pass it props.
  3. Theming — make the components match your brand.
  4. Framework support — what each target supports, and where it differs.
Copyright © 2026