JSONata — Transformation playground

Developer ToolsSee it livetry.jsonata.org

Structured input data fills the left pane while an expression and its evaluated result are stacked on the right.

JSONata — Transformation playground — captured interface — Viewport capture · opening screen

Public demo · 2026-09-08Open full image ↗

Why this pattern works

Keep input, transformation, and output visible together when explaining a data operation.

Design notes

Surface: JSONata — Transformation playground
Navigation: A narrow top toolbar exposes sharing and help actions.
Layout: Three resizable work areas separate source JSON, transformation expression, and output.
Density: Dense data is balanced by short expression and result panels.
Color: White and gray panes with a dark teal toolbar and syntax colors.
Type: Small sans-serif labels keep tools and content visually separate.
Pattern: Keep input, transformation, and output visible together when explaining a data operation.
States: This capture records the visible state only. Loading, error, and later workflow states were not verified.
Don't: Adapt the interface pattern with original content, branding, and data; do not infer behavior from a still image.

Make it your own

Turn this reference into a useful brief for your project. Copy it into the AI tool you already use.

Your project

Use withI want to

Tech stack

Add constraints

What should the tool respect?

Preview & edit prompt

Prompt text

# My project
[Describe the product, audience, and screen you want to improve]

Stack: Use the existing project stack
Task: Implement the interface and verify the result in the existing project.

## Tool guidance (Any AI tool)
Use available project tools to inspect, implement, and test. State any unavailable capabilities.

# Design reference: JSONata — Transformation playground
Source: https://try.jsonata.org/
Swipefile reference: https://swipefile.design/ref/ui-jsonata/
Captured: 2026-09-08. This is a dated reference, not a claim about the current live product.
Capture scope: one viewport. Do not infer unseen page sections or a complete user flow.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

## Reference notes
- surface: JSONata — Transformation playground
- nav: A narrow top toolbar exposes sharing and help actions.
- layout: Three resizable work areas separate source JSON, transformation expression, and output.
- density: Dense data is balanced by short expression and result panels.
- color: White and gray panes with a dark teal toolbar and syntax colors.
- typography: Small sans-serif labels keep tools and content visually separate.
- pattern: Keep input, transformation, and output visible together when explaining a data operation.
- states: This capture records the visible state only. Loading, error, and later workflow states were not verified.
- dont: Adapt the interface pattern with original content, branding, and data; do not infer behavior from a still image.

Useful for: Keep input, transformation, and output visible together when explaining a data operation.

## Acceptance criteria
- Existing project conventions, design tokens, working functionality, and unrelated changes are preserved.
- Two or three reference principles clearly support the user's task; conflicts are resolved in favor of usability and the existing product.
- Reusable components and semantic HTML express the interface. Available licensed assets are used; important UI text is never rendered as a bitmap.
- Every visible control has a defined behavior. Loading, empty, error, success, disabled, and long-content states are specified where relevant. Demo data is clearly labeled.
- Navigation and content adapt at 375px, 768px, and 1440px without horizontal page overflow. Keyboard use, visible focus, labeled inputs, at least 44px touch targets, readable contrast, and reduced motion are supported.
- Verification distinguishes rendered behavior from proposals and identifies anything still requiring a backend or external service.

## Quality bar
Clear hierarchy, consistent spacing, restrained surfaces, and purposeful motion. Avoid decorative gradients, excessive cards, placeholder buttons, and invented metrics unless the project calls for them. Do not claim a feature is connected or tested without evidence.

Assembled in your browser. No API key or AI request needed. Changing the fields refreshes the preview.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

Useful for: Keep input, transformation, and output visible together when explaining a data operation.

JSONata — Transformation playground

Make it your own

Keep exploring

Help improve Swipefile?