Private Pro category · 8 compositions
Contact
Contact routing, office context, support triage, and inquiry forms. These records are manifest-derived and source-free; an implemented status does not imply manual verification, release readiness, entitlement protection, or availability for purchase.
Manifest items
All 8 records currently carry implemented status. A dedicated detail becomes internally discoverable only after release readiness and a reviewed public preview.
Support triage
Office constellation
Project brief form
Sales context form
Press contact
Partnership route
Availability notice
Category contract
- Purpose
- Contact routing, office context, support triage, and inquiry forms.
- Declared dependencies
- gummy-field, gummy-input, gummy-textarea, gummy-button
- Required review
- light, dark, responsive, keyboard-reviewed, rtl-reviewed, reduced-motion
How to evaluate Contact blocks
Choose a contact composition around how inquiries are genuinely routed: direct support, sales qualification, office information, or a structured request. Ask for only the information needed to respond, and explain which channel is appropriate before a visitor submits personal data.
Connect forms to an approved, monitored destination with server-side validation, abuse protection, retention rules, and an honest success state. Use correct autocomplete values and visible labels. Addresses, hours, phone numbers, and response targets must match the organisation’s maintained records.
Test validation, duplicate submission, offline recovery, provider failure, keyboard completion, and narrow screens. Confirm privacy language covers the collected fields and that sensitive security reports are redirected to the safer disclosure process rather than an ordinary contact form.
Handoff should pair every inquiry type with its monitored owner, required fields, retention period, response expectation, and provider failure route. Include the exact public address or endpoint only after it is active. Define what is recorded for abuse prevention without copying message bodies or unnecessary personal details into logs.
Boundary
Public pages contain only approved names, purposes, dependency aliases, requirements, status, and any future reviewed image preview. Editable paid source, test paths, release locations, and entitlement details remain private.