Skip to content
Luthor Docs

Demo Usage and Persistence Guide

Demo Usage and Persistence Guide

Section titled “Demo Usage and Persistence Guide”

This page explains the interactive flows available in apps/demo.

Content loading

Section titled “Content loading”
  • The top bar provides a “Load Demo Content” action.
  • This injects prepared JSONB content from src/data/demoContent.ts into the editor.

Feature coverage panel

Section titled “Feature coverage panel”
  • The app groups extension names into functional categories.
  • Categories and ordering are defined in src/data/demoContent.ts.
  • Use this panel to verify whether expected capabilities are present in the active extension bundle.

Persistence panel workflow

Section titled “Persistence panel workflow”

The panel supports three common flows:

  1. Save payload
    • captures current editor state (JSONB-oriented payload)
    • writes payload into textarea for inspection/copy
  2. Restore payload
    • parses textarea JSON and injects back into editor
    • reports errors if JSON is malformed
  3. Copy payload
    • copies payload text to clipboard for bug reports or test fixtures

Data fidelity expectations

Section titled “Data fidelity expectations”
  • JSONB payload is the fidelity-first path.
  • Restore behavior uses JSONB document content as the canonical source.

Theme behavior

Section titled “Theme behavior”
  • Theme toggle switches between light and dark display modes.
  • Theme preference is stored in local storage and restored on reload.

Troubleshooting tips

Section titled “Troubleshooting tips”
  • If restore fails, validate payload JSON format before retrying.
  • Clipboard actions may require secure context/permissions.
  • If seeded content does not appear, verify editor mount is ready and load action was triggered.
Section titled “Related docs”