@alaarab/ogrid-mcp 2.5.8 → 2.6.0

package/bundled-docs/guides/accessibility.mdx

@@ -5,21 +5,21 @@ title: Accessibility
 
 # Accessibility
 
-Good accessibility isn't just compliance — it's building software that works for everyone. A keyboard user in a tight workflow shouldn't have to reach for the mouse. A screen reader user deserves the same experience as anyone else.
+Good accessibility isn't just compliance. It's building software that works for everyone. A keyboard user in a tight workflow shouldn't have to reach for the mouse. A screen reader user deserves the same experience as anyone else.
 
-OGrid is built with this in mind. Keyboard navigation, screen reader support, high contrast mode, and ARIA semantics are all baked in — you don't configure them, you just benefit from them.
+OGrid is built with this in mind. Keyboard navigation, screen reader support, high contrast mode, and ARIA semantics are all baked in. You don't configure them; you just benefit from them.
 
 ## What's built in by default
 
 You get all of this without any extra setup:
 
-- Full keyboard navigation — arrow keys, Tab, Home/End, Ctrl+Arrow, all working like a spreadsheet
+- Full keyboard navigation: arrow keys, Tab, Home/End, Ctrl+Arrow, all working like a spreadsheet
 - Screen reader announcements for sort, filter, edit, selection, and pagination changes
 - Proper ARIA roles and attributes on the grid, rows, cells, and headers
 - `:focus-visible` indicators so keyboard users always know where they are
 - Focus trapping in dropdowns and popovers (Escape always gets you out)
 - High contrast mode support via CSS custom properties with system color fallbacks
-- Semantic HTML — real `<table>`, `<thead>`, `<th>`, `<td>` elements that assistive tech understands
+- Semantic HTML: real `<table>`, `<thead>`, `<th>`, `<td>` elements that assistive tech understands
 
 The one thing you do need to add: an `aria-label` on the grid. It's one prop.
 
@@ -113,7 +113,7 @@ Key attributes and what they do:
 | `aria-expanded` | Open/closed state of filter dropdowns |
 | `aria-current="page"` | Current page in pagination |
 
-The status bar uses `role="status"` with `aria-live="polite"` — it announces changes without interrupting what the user is doing.
+The status bar uses `role="status"` with `aria-live="polite"`, so it announces changes without interrupting what the user is doing.
 
 ## Screen reader support
 
@@ -221,22 +221,22 @@ npm install --save-dev jest-axe
 
 Automated tests catch structural issues but can't cover everything. Before shipping:
 
-- [ ] Navigate the entire grid using only the keyboard — no mouse
+- [ ] Navigate the entire grid using only the keyboard (no mouse)
 - [ ] Enable VoiceOver (`Cmd+F5`) or NVDA and navigate through sort, filter, edit
-- [ ] Test at 200% zoom — nothing should overflow or become unusable
-- [ ] Toggle Windows High Contrast Mode — all content should remain visible
+- [ ] Test at 200% zoom: nothing should overflow or become unusable
+- [ ] Toggle Windows High Contrast Mode: all content should remain visible
 - [ ] Verify `aria-label` is set on the grid (one of the most common misses)
 
 ## Known limitations
 
 **Virtual scrolling:** When `virtualScroll.enabled` is true, only visible rows are in the DOM. Screen readers won't know the full dataset size unless you set `aria-rowcount` on the grid wrapper manually.
 
-**Custom cell renderers:** If you use `renderCell` to render custom content inside cells, you're responsible for making that content accessible — ARIA attributes, keyboard interaction, announcements. The grid provides the structure; your custom content needs to carry its own accessibility.
+**Custom cell renderers:** If you use `renderCell` to render custom content inside cells, you're responsible for making that content accessible: ARIA attributes, keyboard interaction, announcements. The grid provides the structure; your custom content needs to carry its own accessibility.
 
 ## Resources
 
-- [ARIA Grid Pattern](https://www.w3.org/WAI/ARIA/apg/patterns/grid/) — the spec OGrid follows
+- [ARIA Grid Pattern](https://www.w3.org/WAI/ARIA/apg/patterns/grid/) -- the spec OGrid follows
 - [WCAG 2.1 Quick Reference](https://www.w3.org/WAI/WCAG21/quickref/)
-- [axe DevTools Browser Extension](https://www.deque.com/axe/devtools/) — free in-browser auditing
+- [axe DevTools Browser Extension](https://www.deque.com/axe/devtools/) -- free in-browser auditing
 
 Found an accessibility issue? [Open an issue](https://github.com/alaarab/ogrid/issues) and tag it `accessibility` with your browser, screen reader version, and reproduction steps.

package/bundled-docs/guides/framework-showcase.mdx

@@ -7,9 +7,9 @@ description: OGrid in React, Angular, Vue, and Vanilla JS — same API, native c
 
 # Framework Showcase
 
-OGrid works with your existing design system — not against it. React, Angular, Vue, and Vanilla JS are all fully supported, and every framework shares the same headless core so features stay in sync across all of them.
+OGrid works with your existing design system, not against it. React, Angular, Vue, and Vanilla JS are all fully supported, and every framework shares the same headless core so features stay in sync across all of them.
 
-Every grid below is live. Sort, filter, edit, select, copy-paste, undo — it all works.
+Every grid below is live. Sort, filter, edit, select, copy-paste, undo. It all works.
 
 ---
 
@@ -17,11 +17,11 @@ Every grid below is live. Sort, filter, edit, select, copy-paste, undo — it al
 
 The short version:
 
-- **Starting from scratch?** Pick the Radix variant for your framework — it's the lightest, with no peer dependencies beyond the framework itself.
-- **Already using a design system?** Pick the matching package — Fluent, Material, Angular Material, PrimeNG, Vuetify, or PrimeVue — and the grid components will use your existing components for buttons, inputs, and popovers.
+- **Starting from scratch?** Pick the Radix variant for your framework. It's the lightest, with no peer dependencies beyond the framework itself.
+- **Already using a design system?** Pick the matching package (Fluent, Material, Angular Material, PrimeNG, Vuetify, or PrimeVue) and the grid components will use your existing components for buttons, inputs, and popovers.
 - **No framework?** Use `@alaarab/ogrid-js` for a full-featured grid with just a CDN import.
 
-Switching between UI libraries later is straightforward — you change the import and the wrapper provider if required. The grid configuration (columns, data, event handlers) doesn't change.
+Switching between UI libraries later is straightforward. You change the import and the wrapper provider if required. The grid configuration (columns, data, event handlers) doesn't change.
 
 ---
 
@@ -31,7 +31,7 @@ Three design systems, all sharing the same hooks from `@alaarab/ogrid-react`. Yo
 
 ### Radix UI — lightweight default
 
-The default React package. Radix primitives are bundled in — no separate peer dependency to install. It's a good starting point for new projects or when you want minimal overhead.
+The default React package. Radix primitives are bundled in, no separate peer dependency to install. It's a good starting point for new projects or when you want minimal overhead.
 
 ```bash
 npm install @alaarab/ogrid-react-radix
@@ -53,7 +53,7 @@ export default function App() {
 
 <ShowcaseRadixDemo />
 
-### Fluent UI — Microsoft ecosystem
+### Fluent UI — Microsoft stack
 
 If you're building for Microsoft Teams, SharePoint, or any Microsoft 365 integration, Fluent is your pick. The grid uses native Fluent components for headers, filters, and inputs so it blends naturally.
 
@@ -76,7 +76,7 @@ export default function App() {
 
 ### Material UI — Google's Material Design
 
-If your app already uses MUI, this drops right in. The grid uses MUI components and respects your `ThemeProvider` — including custom palettes and typography.
+If your app already uses MUI, this drops right in. The grid uses MUI components and respects your `ThemeProvider`, including custom palettes and typography.
 
 ```bash
 npm install @alaarab/ogrid-react-material @mui/material @emotion/react @emotion/styled
@@ -101,7 +101,7 @@ export default function App() {
 
 ## Angular
 
-Signals-based reactivity with standalone components — no NgModule, no boilerplate. All three packages share the same services from `@alaarab/ogrid-angular`.
+Signals-based reactivity with standalone components. No NgModule, no boilerplate. All three packages share the same services from `@alaarab/ogrid-angular`.
 
 ### Radix (Angular CDK) — lightweight default
 
@@ -137,7 +137,7 @@ npm install @alaarab/ogrid-angular-material @angular/material @angular/cdk
 
 ### PrimeNG
 
-For teams in the PrimeFaces ecosystem, PrimeNG integration means dialogs, dropdowns, and inputs all look native.
+For teams already on PrimeFaces, the PrimeNG integration means dialogs, dropdowns, and inputs all look native.
 
 ```bash
 npm install @alaarab/ogrid-angular-primeng primeng
@@ -155,7 +155,7 @@ Composition API composables built with `ref()` and `computed()`. All three packa
 
 ### Radix (Headless UI) — lightweight default
 
-Headless UI Vue components bundled in — no peer dependencies beyond Vue 3. Good starting point for new Vue projects.
+Headless UI Vue components bundled in, no peer dependencies beyond Vue 3. Good starting point for new Vue projects.
 
 ```bash
 npm install @alaarab/ogrid-vue-radix
@@ -204,7 +204,7 @@ npm install @alaarab/ogrid-vue-primevue primevue
 
 ## Vanilla JS / TypeScript
 
-No framework, no virtual DOM — just a container element and a class constructor. A built-in CSS theme covers light and dark mode with CSS custom properties you can override.
+No framework, no virtual DOM. Just a container element and a class constructor. A built-in CSS theme covers light and dark mode with CSS custom properties you can override.
 
 ```bash
 npm install @alaarab/ogrid-js
@@ -240,7 +240,7 @@ See [Premium Inputs](../features/premium-inputs) for usage and the full list of
 
 ## Related
 
-- [Quick Start](../getting-started/quick-start) — get a grid running in 60 seconds
-- [Vanilla JS Guide](../getting-started/vanilla-js) — full JS API documentation
-- [Theming Guide](./theming) — customize colors and styling
-- [Premium Inputs](../features/premium-inputs) — advanced cell editors
+- [Quick Start](../getting-started/quick-start) -- get a grid running in 60 seconds
+- [Vanilla JS Guide](../getting-started/vanilla-js) -- full JS API documentation
+- [Theming Guide](./theming) -- customize colors and styling
+- [Premium Inputs](../features/premium-inputs) -- advanced cell editors

package/bundled-docs/guides/mcp.mdx

@@ -6,7 +6,7 @@ sidebar_position: 1
 
 # Editor Integration (MCP)
 
-`@alaarab/ogrid-mcp` connects your AI coding assistant to OGrid documentation — so instead of switching tabs to look things up, you can just ask your editor while you code.
+`@alaarab/ogrid-mcp` connects your AI coding assistant to OGrid documentation. Instead of switching tabs to look things up, you can ask your editor while you code.
 
 It also includes a **live testing bridge** that lets your editor read and control an OGrid instance running in your browser in real time.
 
@@ -18,7 +18,7 @@ MCP (Model Context Protocol) is a standard that lets editors like Claude Code an
 - Pull up specific API references without leaving your editor
 - Inspect and interact with a running grid during development
 
-You don't need to understand the protocol to use it — just run one command and your editor gains access.
+You don't need to understand the protocol to use it. Run one command and your editor gains access.
 
 ## Connect to your editor
 
@@ -28,7 +28,7 @@ You don't need to understand the protocol to use it — just run one command and
 claude mcp add ogrid -- npx -y @alaarab/ogrid-mcp
 ```
 
-That's it. The docs are bundled in the package — no config file needed.
+That's it. The docs are bundled in the package, no config file needed.
 
 ### Claude Desktop
 
@@ -72,13 +72,13 @@ Show me how to use the formula engine in Vue.
 Help me migrate from AG Grid to OGrid.
 ```
 
-The MCP server searches through the full documentation — features, API references, getting started guides, and code examples — and returns the relevant sections along with your context.
+The MCP server searches through the full documentation (features, API references, getting started guides, and code examples) and returns the relevant sections along with your context.
 
 ---
 
 ## Available tools
 
-These are what the MCP server provides to your editor. You don't call them directly — your editor uses them automatically when you ask questions.
+These are what the MCP server provides to your editor. You don't call them directly; your editor uses them automatically when you ask questions.
 
 ### `search_docs`
 
@@ -89,9 +89,9 @@ search_docs query="server-side data" framework="react"
 ```
 
 Parameters:
-- `query` (required) — what you're looking for
-- `framework` (optional) — `react`, `angular`, `vue`, or `js`
-- `category` (optional) — `features`, `getting-started`, `guides`, or `api`
+- `query` (required): what you're looking for
+- `framework` (optional): `react`, `angular`, `vue`, or `js`
+- `category` (optional): `features`, `getting-started`, `guides`, or `api`
 
 ### `list_docs`
 
@@ -133,7 +133,7 @@ Resources can be read by your editor without calling a tool explicitly.
 
 | Resource | Description |
 |----------|-------------|
-| `ogrid://quick-reference` | Key API overview — props, column definitions, IOGridApi, filter types |
+| `ogrid://quick-reference` | Key API overview: props, column definitions, IOGridApi, filter types |
 | `ogrid://docs/{path}` | Any documentation page by path (e.g. `ogrid://docs/features/filtering`) |
 | `ogrid://migration-guide` | Step-by-step guide for migrating from AG Grid to OGrid |
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@alaarab/ogrid-mcp",
-  "version": "2.5.8",
+  "version": "2.6.0",
   "description": "MCP server for OGrid documentation",
   "type": "module",
   "bin": {