What really happens when someone clicks Submit
Follow one order from the moment a customer taps "Place order" to the moment it's saved, step by step, and understand forms and Server Actions well enough to direct the AI that builds them.
Why this matters
"The form doesn't work" is the most common message beginners send when they build a back end. It's also the hardest to fix, because a form isn't one thing. It's a chain of about eight small steps, in two different places, and any one of them can break.
If you can see the chain, you can find the broken link. "The browser sent it, but the server said no" is a problem you can fix in five minutes. "The form doesn't work" can take a whole evening.
This lesson follows one lunch order through every step. You'll meet two terms you'll use for the rest of Stage 2: form data (what the customer typed) and Server Action (the cook in the kitchen who receives it). You won't build anything yet. You'll build the dining room in Lesson 6.3 and connect the kitchen in Module 7. Today is about seeing the journey clearly, so that when you do build it, nothing feels like magic.
In the full lesson
- The idea in plain English
- Try it
- Check it worked
- Quick check
- What you can do now
The step-by-step, the prompt to copy, the video and the check-it-worked list, for every lesson in all 15 modules. GHS 399 ($40), paid once by mobile money or card, yours to keep.