Specific experience
HTMX qualification journey and accessible payment
Guide individuals, companies and other audiences through HTMX cards before sending each situation to the appropriate form or final payment state.
The journey is a decision questionnaire, not merely a payment screen. HTMX cards load the next step from a Drupal taxonomy, update the URL and selection trail, then direct the visitor to the relevant content, form or payment method. At the final state, a Webform/CiviCRM bridge adds accessible waiting messages, failure recovery and a fallback redirect.
Context
Supporting a nonprofit does not begin at the payment provider. The journey must first qualify the audience, request and type of engagement without losing context between steps.
Role
Takeover of the existing Drupal questionnaire, design of taxonomy-driven HTMX navigation, accessibility improvements for the cards and a resilient Webform/CiviCRM handoff to payment.
Deliverables
HTMX qualification cards; selection trail and URL history; keyboard navigation; parameter persistence; form or HelloAsso exits; aria-live states; fallback continuation link; AJAX failure recovery.
Verification
HTMX fragment and journey-parameter checks; Kernel test for Webform integration; bounded settings; iframe-origin checks; maximum-level PHPCS and PHPStan checks for the payment bridge.
Maintenance and follow-up
Takeover of existing Drupal deliverables, isolated updates in maintainable modules, regression checks on critical journeys, documented limitations and incident follow-up after commissioning.
Outcome