The RAMP Stack
← Projects
From application intent to interface

CHKDescribe the data. Build the app.

CHK turns application definitions into interfaces. Describe what people need to see or enter, and let the framework assemble the pages and controls.

CHK logoBUILT ON RAMP
INSIDE CHK

Define displays, forms, and the main sections of an application in Rust. CHK uses those definitions to create a structured interface with navigation and input handling. It currently targets Pelican UI and connects application pages to changes in AIR data.

01

Declare what matters

Describe the information your application presents and collects, without selecting and positioning every underlying UI component.

02

Flows come together

Forms, displays, and roots provide a common vocabulary for building pages and navigating between application sections.

03

Stay connected to changes

Watch AIR instances and collections to refresh pages as data changes. Form validators can also respond to changing dependencies.

A CLOSER LOOK

Describe the information. Build the interface.

Choose the data, actions, and flow that make your app useful. CHK brings them together with Pelican’s components.

↳ Conceptual flow. CHK currently builds interfaces with Pelican UI.
YOU DESCRIBE

What matters.

DisplayYour information
FormYour inputs
SectionYour app structure
↓
CHK + PELICAN UIA consistent interfaceComponents · Validation · Navigation
↗ KEEP EXPLORING

Part of a bigger picture.

Explore the RAMP stack