Standard Data
Key Mapping Grid
primary-* / accent-* with your own colour scale.
$ velocityx add key-mapping-gridBuilt for astro.
Full docs for Key Mapping Grid →
Needs a licence key — buy lifetime access here, then
velocityx login once.
| Control | Action | Target |
|---|---|---|
| Left Stick X CC 1 Filter cutoff | ||
| Right Trigger CC 11 Expression | ||
| D-Pad Up Note C4 Kick drum | ||
| Touchpad X/Y CC 20 / CC 21 Pan / reverb send | ||
| Face Button A Note On Sample trigger Velocity-sensitive | ||
- Framework
- astro
- Source
- 75 lines
- KeyMappingGrid.astro
- Runtime
- Static markup
- zero client JS
- Theme
- 14 tokens
- re-themes from your scale
- Dark mode
- Built in
- dark: variants
- Accessibility
- 1 ARIA
- attributes and roles
Props
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
| rows | Row[] | No | [ { control: "Left Stick X", action: "CC 1", target: "Filter cutoff" }, { control: "Right Trigger", action: "CC 11", target: "Expression" }, { control: "D-Pad Up", action: "Note C4", target: "Kick drum" }, { control: "Touchpad X/Y", action: "CC 20 / CC 21", target: "Pan / reverb send" }, { control: "Face Button A", action: "Note On", target: "Sample trigger", note: "Velocity-sensitive" }, ] | |
| title | string | No | "Default mapping" | |
| caption | string | No | ||
| className | string | No | "" |
Using it
The smallest call that compiles — required props only. The import is
written for your own file at src/components/Example.astro;
adjust the relative import if yours sits elsewhere.
Everything optional is in the table above, with its default.
---
import KeyMappingGrid from './velocity/key-mapping-grid/KeyMappingGrid.astro';
---
<KeyMappingGrid />Built from Key Mapping Grid's own prop signature and the path the CLI installs it to, so it can't drift from either.
Accessibility
- ARIA attributes
- aria-hidden
- Screen readers
- Ships screen-reader-only text
Read from the source, not asserted — anything not listed simply isn't in this component's markup.
Behaviour
- Ships client JS
- No — renders to static markup
- Dark mode
- Carries its own dark: variants
Theming
This component paints from 14 steps of
your theme scale — no hardcoded colours, and no font-family of
its own, so your type cascade wins. Override the variables and it follows.
accent-300accent-400accent-500accent-700primary-50primary-200primary-300primary-400primary-500primary-600primary-700primary-800primary-900primary-950Get the Velocity preset and CSS theme from the public source guide. The CLI theme command is not available on npm yet.
File this creates
The CLI writes this path into your project — nothing
else moves. Paths are under your source root, which defaults to
src/; pass
--dest if yours is elsewhere.
-
src/components/velocity/key-mapping-grid/KeyMappingGrid.astro75 lines
Copy the paths
src/components/velocity/key-mapping-grid/KeyMappingGrid.astroKey Mapping Grid — questions
How do I install Key Mapping Grid?
Run velocityx add key-mapping-grid . The CLI writes the source straight into your project — it is not a runtime package dependency.
Do I need a licence for Key Mapping Grid?
Yes. It is part of the lifetime library — buy access at https://aidxn.com/shop/velocity-x-component-library/, authenticate once, and install it. Your lifetime licence includes future component updates.
Can I edit Key Mapping Grid after installing it?
Yes — the files are yours once written. The CLI compares its lockfile hash before upgrades and refuses to overwrite code you changed.
Does Key Mapping Grid ship JavaScript to my users?
No. It renders to static markup with no client-side JavaScript of its own.
Will Key Mapping Grid match my brand colours?
Yes. It paints entirely from your theme scale — 14 steps of primary-* / accent-* — with no hardcoded hex values and no font-family of its own. Override the theme CSS variables and it follows your design system instead of ours.
Does Key Mapping Grid pull in any dependencies?
No external ones. Every component in the library is built with react/react-dom or plain Astro only — no GSAP, Radix, Swiper or Headless UI — which is what makes dropping it into an existing project safe.
Set up & reference
All docs →Install this component:
$ velocityx add key-mapping-grid- 2. Install the theme — run this first, once per project Do this once per project, before your first component.
- The palette gotcha — this one bites silently Silent failure — the component renders, just unstyled.
- Your edits are safe by default What happens to your changes when you upgrade.
- You own the code What you are actually buying.
Related components
More from Standard Data.
primary-* / accent-* with your own colour scale.
astroprimary-* / accent-* with your own colour scale.
astroprimary-* / accent-* with your own colour scale.
astroA compliance-grade record of who did what and when, grouped under calendar-day headers with a severity tag per row and a details disclosure that reveals the structured change data only when someone needs it — built for security and admin audit trails, not a social activity stream.
astro