Skip to content

feat: contact-form - Store enquiries with accessible acknowledgement #210

Open

Description

@ashleyshaw

Feature Summary

Provide stored contact enquiries, confirmation emails, an About contact section and a dedicated contact thank-you page. This expands the earlier inline-only scope. The existing M estimate remains unchanged and has not been revalidated.

Linked Stories/Tasks

Parent: #16. Project: This One Time on Acid — book. Shared capture, deployment, operations and verification separate.

Milestones & Timeline

No milestone, cycle, due date or release date requested.

Proposed Solution

Update src/app/components/pages/book-site/ContactPage.tsx: remove alert; name name/email/organisation/enquiry-type/message controls; associate labels with IDs. Organisation optional, preserve other existing requirements and media/speaking/events/publisher/general values. Add contact identity, source-route /contact, hidden form-name/honeypot. Shared pending/duplicate guard/status/explicit retry; reset only after accepted success. Autocomplete/keyboard hints, mobile/theme styling, centralised copy.

Linked Stories/Tasks

No PR linked. Operator notifications are distinct from required customer confirmation emails; neither implies newsletter enrolment. Do not claim email delivery without evidence or promise a response time.

Milestones & Timeline

Release timing remains unset.

Acceptance Criteria

  • Stored contact record includes all fields and source-route /contact.
  • Optional organisation and every enquiry type preserved; required controls validate.
  • Pending prevents duplicates; failure retains all values with explicit retry.
  • The dedicated contact thank-you page acknowledges evidenced receipt; confirmation-email status remains distinct and truthful. Reset only after accepted receipt.
  • About includes the contact section.
  • Label associations, keyboard/focus/mobile/themes verified.
  • No marketing enrolment, legacy Typeform activation or unsupported email-delivery claim.
  • All acceptance criteria met
  • Documentation/changelog updated
  • Tests added/updated
  • PR uses correct branch prefix (feat/)
  • Labels/types match org standards
  • PR description updated with relevant details
  • Changelog entry prepared for PR (if applicable)
  • Labels/types match org standards

Designs / References

Contact component, setup, project Figma Make/repository guidance. Historical ranges 23–26,91–134 belong to original 76b1528 audit.

Dependencies

Provider, destinations, access, retention/deletion and confirmation behaviour require approval before implementation. Netlify capture is not an approved confirmation-email solution; manuscript-entry retention does not automatically govern contact. Trace to REQ-011–012 and AC-012–013.

Testing Approach

Each enquiry value, organisation present/absent, Unicode/multiline messages, invalid/pending/slow/offline/rejected requests, retry/reset timing and real dashboard records.

Additional Context

No personal-data logs/browser persistence. React/Vite repository rules; LightSpeed Feature defaults retained with approved Backlog/status:needs-triage conflict.


Definition of Ready (DoR)

  • Problem statement and outcome defined
  • Acceptance criteria written (Given/When/Then)
  • Designs/specs/references attached (if relevant)
  • Dependencies mapped
  • Estimate added
  • Stakeholders/approvers listed
  • Milestone/iteration assigned (if applicable)

Definition of Done (DoD)

  • All acceptance criteria met
  • Feature implemented and tested
  • Tests added/updated; CI green
  • Accessibility: WCAG 2.2 AA compliance verified (semantic HTML, keyboard support, colour contrast)
  • Security: input validated, output escaped, no OWASP Top 10 vulnerabilities
  • Performance: no measurable regression introduced
  • Documentation/changelog updated if needed
  • Feature toggles/rollout considered
  • QA verified/UAT approved (if applicable)
  • Release notes prepared; monitoring/alerts set
  • Branch prefix is correct (feat/)
  • Branch deleted after merge
  • Linked issue(s) updated with latest status and closed after merge,
  • The related epic should not be closed, instead updated with a comment to reflect the closed issue

Related project document: Book website — Contact thank-you: content and author questions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Fields

Priority

None yet

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions