A form is an input, not a text box.
Every demo below posts to the same public endpoint a customer's static form uses. What changes is what the page does with the answer afterwards — a fish, a maze someone else has to walk, a riddle. None of it needs a server of your own.
Steal the idea, not the code: if a visitor's answer can drive something on screen, it can drive anything — a game, a wall, a tally, a toy.
Fish pond
Submit a line and a fish swims into the pond. Click a fish to read who said it.
liveMaze builder
The form is the editor: raise walls, walk your own route, publish it. Everyone else has to walk it too — and the server checks their steps.
liveRiddles
Two fields instead of one: a riddle and its answer become a game everyone can play. Guesses are checked on the server.
liveYours
A scoreboard that updates as people vote. A story that reads itself out field by field. A queue number. A birthday card. The form only has to deliver the answer — the rest is your page.
What the same endpoint can drive
- Live tallies. Ask one question, render the bars from the answers already stored.
- Queues and counters. Show the visitor their place, not just a thank-you page.
- Slow reveals. A daily prompt where yesterday's answers are revealed as cards.
- Team dashboards. A wall mounted in an office that reflects the last N submissions.
- Games with rules. Submit a guess, get told how far off you were, keep a running score.
Every demo on this page is the same form and the same database. Everything you see is read back from real rows — nothing is mocked. They all post to /f/demo; the panels are filled from /demo/feed. The maze one goes further: its fields are a grid and a route, so the server can judge what a visitor did, not just store what they typed.