EnterUI
DocsComponentsThemesExamplesDonation
Get Started
  • OverviewStart with the EnterUI package model.
  • Introduction
  • Installation
  • SSR & Next.js
  • SolidJS Renderer
  • Styling Philosophy
  • Theming
  • Accessibility
  • Production Checklist
  • Migration & Versioning
  • Troubleshooting
  • New components
  1. EnterUI
  2. /Docs
  3. /Getting Started
  4. /Overview
Updated 9 October 2026

Overview

Refined component renderer packages built on the FroggDesign visual language.

EnterUI component system

EnterUI turns the FroggDesign visual language into production-ready component packages for dashboards, SaaS apps, internal tools, and product interfaces. React is the primary renderer, with a SolidJS renderer for stateless and presentational primitives.

Current coverage193 component pages · React + SolidJSRoot showcase previews one component per card, with public alias exports documented on canonical component pages and a growing SolidJS renderer.

Package boundary

Applications consume public package exports only. Import theme CSS once, then the renderer CSS.

@froggdesign/enter-ui-react@froggdesign/enter-ui-solid@froggdesign/enter-ui-utils@froggdesign/theme@froggdesign/tokens

#Find your starting point

  • New to EnterUI: read Introduction, then Installation. Choose the Next.js guide or SolidJS renderer for your app.
  • Build a page: start with Foundations, then Layout and Utilities. Add Inputs, Scheduling, and Navigation and Overlays as needed.
  • Build a dashboard: explore Data and Analytics, then Product Operations for feedback, account surfaces, and workflows.
  • Prepare to ship: review Accessibility and the Production Checklist. Use Troubleshooting when something goes wrong.
  • Explore updates and complete products: see New components and Examples.

The sidebar groups components by task, with basic building blocks before advanced workflows. Previous and Next follow the same order.

#Install

Code
pnpm install @froggdesign/enter-ui-react @froggdesign/theme
app/layout.tsx
import "@froggdesign/theme/styles.css";
import "@froggdesign/enter-ui-react/styles.css";

SolidJS apps use @froggdesign/enter-ui-solid and @froggdesign/enter-ui-solid/styles.css. See SolidJS for current coverage.

#Component Families

Core interface

Button, IconButton, Link, Card, Badge, Text, List, Alert, Avatar, Separator, Tabs, Accordion, Disclosure, and copy-friendly primitives for polished product surfaces.

Read more

Forms and input

Form, Field, Fieldset, ValidationSummary, Input, CurrencyInput, MaskedInput, URLInput, Select, Combobox, MultiSelect, TagsInput, DatePicker, CronInput, RecurrenceEditor, and scheduling controls.

Read more

Data operations

Table, DataTable, DataGrid, SavedViews, SortMenu, DensityToggle, ColumnVisibilityMenu, BulkEditPanel, FilterBuilder, KanbanBoard, TransferList, and operational table utilities.

Read more

Product shell

AppShell, Header, Sidebar, SideNav, NavigationRail, WorkspaceSwitcher, AppSwitcher, PageLayout, SplitView, PageHeader, Toolbar, Breadcrumb, and navigation primitives.

Read more

Feedback and workflow

Toast, Banner, Progress, Spinner, Skeleton, EmptyState, LiveRegion, Announcer, ActivityTimeline, ReleaseStepper, AgendaList, and audit-friendly workflow components.

Read more

Analytics

MetricCard, ComparisonMetric, TrendIndicator, Meter, Gauge, Sparkline, LineChart, AreaChart, StackedBarChart, Heatmap, BarChart, DonutChart, and Legend without a heavy chart dependency.

Read more

#Foundation Packages

Tokens

@froggdesign/tokens owns primitive and semantic design values.

Theme

@froggdesign/theme publishes FroggDesign --fd-* CSS variables for light and dark mode.

React

@froggdesign/enter-ui-react exports React components, .eui-* classes, and component-facing variables.

SolidJS

@froggdesign/enter-ui-solid exports SolidJS primitives with the same visual contract.

Utilities

@froggdesign/enter-ui-utils owns small helpers such as cn.

#Design Direction

EnterUI provides consistent components for everyday product workflows. Neutral surfaces carry hierarchy. Green appears as a small success or selection signal, not as a dominant theme. Components should feel ready for repeated product work, not like decorative demos.

#Next Steps

  • Read Introduction for the package model.
  • Follow Installation to wire the CSS correctly.
  • Use Theming and Styling Philosophy before writing custom UI.
NextIntroduction
On this page
  • Find your starting point
  • Install
  • Component Families
  • Foundation Packages
  • Design Direction
  • Next Steps