DevOps:Doc/FlexForm
Tag: Manual revert |
→How is it different from PageForms?: -- more details added Tags: Reverted Visual edit |
||
| Line 1: | Line 1: | ||
=== | === How is FlexForm different from PageForms? === | ||
'' | While '''PageForms''' is built around the traditional concept of editing a single page's template through a dedicated <code>Special:FormEdit</code> screen, '''FlexForm''' approaches MediaWiki as a modern web application platform. Instead of forcing your forms into a rigid, pre-defined wiki syntax, FlexForm uses '''100% native HTML5 standards''' combined with powerful backend data processing. | ||
'''FlexForm''' is an | * '''Native HTML5 vs. Custom Wiki Syntax:''' With PageForms, you have to learn a proprietary form-markup language and fight its generated DOM to style it. FlexForm uses standard HTML5 <code><nowiki><form></nowiki></code> and <code><nowiki><input></nowiki></code> elements (<code><nowiki><_form></nowiki></code>, <code><nowiki><_input></nowiki></code>). If it exists in the HTML5 specification, it works in FlexForm out of the box—giving you total freedom with Bootstrap, Chameleon, custom CSS, and JavaScript. | ||
* '''In-Context UX (No more leaving the page):''' PageForms pulls users out of their workflow to a separate Special Page just to edit data. FlexForm renders '''anywhere on any page'''—and you can place multiple independent forms on a single page. Put forms inside modals/popups, tabs, or accordions so users view and edit information in the exact same place. | |||
* '''Decoupled from Single Templates:''' PageForms is tightly coupled to one page and its templates. FlexForm decouples the UI from the storage layer: show users ''only'' the exact fields they need to see, and let a single form submission update '''multiple templates across multiple different pages''' simultaneously. | |||
* '''Multi-Action Workflows in One Submit:''' A single FlexForm submission is an entire workflow engine. In one click, a user can create or edit multiple pages, upload and process multiple files, convert uploaded Word or Excel documents directly into structured wiki pages/JSON, and trigger custom emails or webhooks. | |||
* '''Enterprise Security by Design:''' Because anyone can edit wiki pages, raw HTML forms are normally a security risk. FlexForm solves this with a built-in Validated Security Model (cryptographic tokens, strict server-side parameter whitelisting, and XSS protection), ensuring users can only submit what the form author explicitly intended. | |||
==== Quick Comparison: PageForms vs. FlexForm ==== | |||
{| class="wikitable" | |||
|'''Feature / Capability''' | |||
|'''PageForms''' | |||
|'''FlexForm''' | |||
|- | |||
'''FlexForm''' | |'''Form Syntax''' | ||
|Proprietary MediaWiki form markup | |||
|'''Standard HTML5''' (with wiki-specific extensions) | |||
|- | |||
|'''Where Forms Live''' | |||
|Dedicated <code>Special:FormEdit</code> page (or limited <code>autoedit</code> link) | |||
|'''Anywhere:''' inline on any page, multiple forms per page, modals, or tabs | |||
|- | |||
|'''Scope of a Single Submit''' | |||
|Edits 1 page and its tightly coupled template(s) | |||
|Creates/edits '''multiple pages''', multiple templates, or specific slots at once | |||
''' | |- | ||
|'''Data Formats''' | |||
|Wikitext templates | |||
''' | |Wikitext templates, '''JSON (e.g., JSON Schema)''', and MCR Slots | ||
|- | |||
''' | |'''File Uploads & Processing''' | ||
|Basic single-file upload field | |||
|Multi-file dropzones, '''automatic Word/Excel-to-Wiki conversion''', custom naming | |||
|- | |||
|'''Post-Submit Actions''' | |||
|Saves the page | |||
|Saves page(s), '''sends templated emails''', triggers webhooks/extensions | |||
|- | |||
|'''Styling & UI Freedom''' | |||
|Rigid layout; hard to customize with modern CSS frameworks | |||
|'''100% flexible:''' native support for Bootstrap, Chameleon, and custom JS | |||
|} | |||
Revision as of 18:30, 11 November 2026
How is FlexForm different from PageForms?
While PageForms is built around the traditional concept of editing a single page's template through a dedicated Special:FormEdit screen, FlexForm approaches MediaWiki as a modern web application platform. Instead of forcing your forms into a rigid, pre-defined wiki syntax, FlexForm uses 100% native HTML5 standards combined with powerful backend data processing.
- Native HTML5 vs. Custom Wiki Syntax: With PageForms, you have to learn a proprietary form-markup language and fight its generated DOM to style it. FlexForm uses standard HTML5
<form>and<input>elements (<_form>,<_input>). If it exists in the HTML5 specification, it works in FlexForm out of the box—giving you total freedom with Bootstrap, Chameleon, custom CSS, and JavaScript. - In-Context UX (No more leaving the page): PageForms pulls users out of their workflow to a separate Special Page just to edit data. FlexForm renders anywhere on any page—and you can place multiple independent forms on a single page. Put forms inside modals/popups, tabs, or accordions so users view and edit information in the exact same place.
- Decoupled from Single Templates: PageForms is tightly coupled to one page and its templates. FlexForm decouples the UI from the storage layer: show users only the exact fields they need to see, and let a single form submission update multiple templates across multiple different pages simultaneously.
- Multi-Action Workflows in One Submit: A single FlexForm submission is an entire workflow engine. In one click, a user can create or edit multiple pages, upload and process multiple files, convert uploaded Word or Excel documents directly into structured wiki pages/JSON, and trigger custom emails or webhooks.
- Enterprise Security by Design: Because anyone can edit wiki pages, raw HTML forms are normally a security risk. FlexForm solves this with a built-in Validated Security Model (cryptographic tokens, strict server-side parameter whitelisting, and XSS protection), ensuring users can only submit what the form author explicitly intended.
Quick Comparison: PageForms vs. FlexForm
| Feature / Capability | PageForms | FlexForm |
| Form Syntax | Proprietary MediaWiki form markup | Standard HTML5 (with wiki-specific extensions) |
| Where Forms Live | Dedicated Special:FormEdit page (or limited autoedit link)
|
Anywhere: inline on any page, multiple forms per page, modals, or tabs |
| Scope of a Single Submit | Edits 1 page and its tightly coupled template(s) | Creates/edits multiple pages, multiple templates, or specific slots at once |
| Data Formats | Wikitext templates | Wikitext templates, JSON (e.g., JSON Schema), and MCR Slots |
| File Uploads & Processing | Basic single-file upload field | Multi-file dropzones, automatic Word/Excel-to-Wiki conversion, custom naming |
| Post-Submit Actions | Saves the page | Saves page(s), sends templated emails, triggers webhooks/extensions |
| Styling & UI Freedom | Rigid layout; hard to customize with modern CSS frameworks | 100% flexible: native support for Bootstrap, Chameleon, and custom JS |