Choose a Forms guide to start. These guides now lean on real Demo Projects HQ pages such as task_add.ejs, task_edit.ejs, login.ejs, and files.ejs so the patterns stay tied to concrete fields, buttons, and feedback states instead of floating as generic advice.
Forms guides
Section titled “Forms guides”Start here
Quick Overview
Get a quick overview of Forms: what it is, where to find it, and how it fits in your workflow.
Validation
Validate forms with good UX: required fields, feedback states, and clear error messages for users.
Multi-Step
Build multi-step forms: split inputs into steps, add navigation, and validate before moving forward.
Multi-Column
Design multi-column forms with Bootstrap grids: align fields cleanly, keep validation readable, and stay responsive.
Field patterns
Text, email, and contact fields
Use the Demo Projects HQ client form to choose plain text-style fields that match names, email addresses, phone numbers, and short supporting details.
Select fields and relationships
Use the Demo Projects HQ task form to separate simple status choices from relationship fields that point at live project and contact records.
Numbers, dates, and richer inputs
Use the Demo Projects HQ task form to see where number fields, scheduling inputs, and richer widgets each belong in a practical form.
Submission flow
Form to Server Action handoff
Use the Demo Projects HQ task form to connect page fields, the Server Connect form action, and the success/error states that come back after submit.
Login redirects and error states
Use the Demo Projects HQ login form to see how one submit flow can redirect on success, stay put on failure, and still keep the user oriented.