Why UI Registry — when to use it

Problem

The same components (button, slider, modal) keep getting reinvented across CzG projects. Each copy drifts a little — a different padding, a different focus outline, a different ARIA detail. After a few projects there is no consistent UI even though every project tried to do the same thing.

Solution

Central registry of Latte / SCSS / JS / Vue components, distributed via a CLI. Components are physically copied into the project — no runtime package, no automatic updates. Once installed, the code is yours; edit it freely.

The registry just makes sure every project starts from the same baseline and can pull in updates explicitly when ready.

When to use the registry

  • New projects — primary source of UI components
  • Patterns reused across projects (button, slider, modal, dropdown, breadcrumb)
  • Components where it makes sense to keep a shared upgrade path

When NOT to use it

  • Highly project-specific UI — keep it local, do not pollute the registry
  • PHP backend logic — that belongs in a Composer package
  • One-off prototypes that will not be reused

Live preview

The full gallery, source files, and install snippets live at ui.czechgroup.cz (basic auth: dev / dev for the dev environment).

Další kategorie