Quickback CMS

A schema-driven admin interface that reads schema-registry.json generated by the Quickback compiler. Every table, column, action, view, and security rule is rendered automatically. Zero UI code per table.

Overview

The CMS generates its entire UI from your Quickback definitions. Define a table with columns, guards, masking, views, and actions in your feature files. Run the compiler. The CMS reads the resulting schema registry and renders a complete admin interface — data tables, inline editing, action dialogs, role-based access, and field masking — all without writing a single line of UI code.

Key Features

• Schema-driven — Zero UI code per table. Add a table, recompile, and it appears in the CMS.
• Dual view modes — Table browse mode for navigation and Data Table mode for spreadsheet-style editing.
• Role-based access — Owner, admin, and member roles with live switching. CRUD buttons hidden when unauthorized.
• Inline spreadsheet editing — Excel/Google Sheets-like editing with keyboard navigation (arrows, Tab, Enter, Escape).
• FK typeahead — Server-side search for foreign key fields with debounced queries and keyboard navigation.
• Field masking — Email, phone, SSN, and redaction patterns applied per role. Masked fields show a lock icon.
• Custom actions — Action dialogs with auto-generated input forms, access filtering, CMS metadata (icons, categories, confirmations), and side effects warnings.
• Views — Named column-level projections per role. "All Fields" plus custom views in the toolbar.
• Auto-form generation — Create and edit forms built from guards (createable/updatable fields).
• Display column auto-detection — FK labels resolved automatically from name, title, label, code, and other common patterns.

Architecture

The CMS sits at the end of the Quickback compilation pipeline:

Quickback Definitions (feature files)
        |
        v
    Compiler
        |
        v
  schema-registry.json
        |
        v
    CMS reads it
        |
        v
  Renders admin UI

Your feature definitions are the single source of truth. The compiler extracts all metadata — columns, types, guards, masking rules, views, actions, validation, and firewall config — into a static JSON file. The CMS consumes that file and renders the appropriate UI for each table.

Quick Start

1. Compile

quickback compile

The compiler automatically generates schema-registry.json alongside your compiled API output.

3. Point the CMS at Your Schema

The CMS reads the generated schema-registry.json to discover all tables, columns, security rules, and actions. In development, it can also run in demo mode with mock data and a role switcher for testing different access levels.

Next Steps

• Schema Registry — Understand the JSON format the compiler generates
• Connecting — Demo mode vs. live mode setup
• Table Views — Browse and Data Table view modes
• Inline Editing — Spreadsheet-style editing and FK typeahead
• Security — How the CMS enforces all four security layers
• Actions — Custom actions with input forms, access filtering, and CMS metadata
• Schema Format Reference — Full TypeScript types for schema-registry.json
• Components Reference — All CMS components and their props