🌐 Qwiki Manual
User Guide / Authoring & Content Formats / HTML Pages & Interactive Forms

HTML Pages & Interactive Forms

When Markdown isn't enough—for bespoke landing dashboards, rich formatted tables, or collecting feedback and RSVPs—Standalone Qwiki supports native HTML Pages (.html) and Interactive Forms (.form.json) via built-in page-type extensions.

HTML Pages (page-html)

HTML pages render inside a clean, sandboxed container with theme integration and a 🖨️ Print / Save as PDF toolbar action.

SunEditor WYSIWYG visual HTML editor inside Standalone Qwiki

Visual WYSIWYG vs. Protected Raw Mode

Click ✏️ Edit HTML on any HTML page to edit it in place:

  • SunEditor WYSIWYG Mode: Standard rich HTML pages open in SunEditor, giving you visual formatting, tables, image insertion from the Qwiki Gallery, and a code-view toggle.
  • Automatic Script/Style Protection: If your HTML page contains ,, or `` tags (for example, a custom interactive dashboard), Standalone Qwiki automatically disables the visual WYSIWYG editor and opens the raw HTML editor instead—preventing the visual editor from stripping your scripts or styles.
Note

If an administrator disables the page-html extension in Settings ➔ Extensions, Qwiki strips heavy SunEditor CDN assets from the frontend and switches existing HTML documents to safe read-only viewing.

Interactive Forms (page-form)

Interactive Forms let teams collect surveys, bug reports, intake requests, or event RSVPs without setting up a database or third-party form SaaS. Submissions are stored in companion .submissions.json files alongside the form schema.

Interactive Form schema builder showing field configuration and form options

Building & Editing a Form

  1. Click New Document in the sidebar and select Interactive Form (or click ✏️ Edit Form on an existing form).
  2. Add and reorder fields using the visual builder (+ Add Field), choosing from presets such as text inputs, text areas, email, select dropdowns, checkboxes, radio buttons, and dates.
  3. Configure optional form protections and notifications:
    • Anti-spam honeypot to filter automated bot submissions without CAPTCHAs.
    • Email alerts (sent via Qwiki's configured SMTP server) or webhook notifications on each submission.
  4. Click Save Changes to update the .form.json schema.

Reviewing & Exporting Submissions

Authorized users can click 📋 View Responses in the form view to:

  • Browse submitted entries in a clean table.
  • Refresh submissions live, delete individual entries, or clear all responses.
  • Export CSV for analysis in Excel, LibreOffice Calc, or Google Sheets.

When a form document is deleted to the Trash Bin, its .submissions.json companion file moves safely with it so response data is never orphaned or lost.