I'm building a TypeScript data grid where config reads like English

EliteGrid — Tue, 26 May 2026 17:15:01 +0000

I've integrated a lot of data grids over the years.

Every time, the experience was the same — open the docs, search for the
prop I need, find three different ways to do the same thing, pick one,
get it wrong, Google it, eventually get it working, and forget how I did
it by the next project.

I'm a developer. I shouldn't need tribal knowledge to configure a UI component.

So I started building EliteGrid.

The core idea: grouped config API

Most grids dump every option at the top level. Hundreds of flat props with
no consistent naming pattern. You end up memorizing prop names instead of
understanding a mental model.

EliteGrid uses a grouped, namespaced config API. Every feature has its own
namespace:

<EliteGrid
  data={rows}
  columns={columns}
  sorting={{ multi: true }}
  filtering={{ debounce: 300 }}
  pagination={{ pageSize: 25 }}
  selection={{ mode: 'multi' }}
  editing={{ trigger: 'doubleClick' }}
  appearance={{ theme: 'dark', density: 'compact' }}
/>

Config that reads like English. TypeScript autocompletes every property.
You never need to guess a prop name.

The architecture

EliteGrid is built on a microkernel with 13 independent plugins communicating
through a shared event bus and data store:

DataSource — raw data ingestion and normalization
RowModel — row lifecycle, identity, and memoization
ColumnModel — column definitions, width, visibility, pinning
Sort — single and multi-column sort with custom comparators
Filter — text, number, date, and boolean filters per column
Pagination — client-side and server-side pagination
Selection — single and multi-select with keyboard support
Edit — inline editing with sync/async validation
Viewport — visible row calculation and scroll management
Export — CSV export with custom formatters

Each plugin is completely independent. No circular dependencies.
No hidden coupling. Zero runtime dependencies on the core.

We currently have 662 passing tests across the engine.

Accessibility by default

Full WCAG 2.1 AA compliance ships as part of the default experience.
Zero configuration required.

Full ARIA Grid Pattern implementation
Screen reader announcements for all state changes
Complete keyboard navigation — Arrow keys, Home, End, PageUp, PageDown
Roving tabindex focus management
prefers-reduced-motion respected
Windows High Contrast mode supported

Every user deserves a great grid, not just sighted mouse users.

Docs as a first-class feature

The goal: a junior developer should be able to integrate EliteGrid
from the docs alone — no AI, no Stack Overflow, no tribal knowledge.

That's a high bar. We're treating it as a product requirement, not
an afterthought.

Where we are

✅ Core engine — 13 plugins, 662 passing tests
✅ Grouped config API
🔨 React and Vue adapters — building now
🔨 Interactive sandbox on StackBlitz — building now
⏭ Public npm launch — coming soon

Community version will be free and open source.

Follow along

If this sounds like the grid you've been waiting for, join the waitlist at elitegrid.dev — one email when the sandbox is ready, one at launch.

I'd love to hear what you think in the comments. What matters most to you in a data grid?