Forms and integrations: clear responsibilities

Drupal can retain Form API, validation and processing; the frontend must integrate the complete lifecycle.

What lupus_decoupled_form provides

It wraps Form API HTML in drupal-form--* elements. Drupal keeps validation and processing. The frontend integration must forward POST, cookies and tokens and present the response or redirect and messages.

What works here

Login and recovery are Canvas screens with custom React components and direct POST to Drupal. They are not a generic CE Form API adapter. Next.js has no authenticated proxy or general session forwarding.

Webform and widgets

lupus_decoupled_webform exists, but Webform is not installed in this POC. CSS and JS libraries are not delivered automatically: AJAX, widgets and confirmations need testing and adaptation.

Before expanding or publishing

Define authentication, CSRF, error handling, messages and redirects; verify permissions, accessibility, translations and caching. One compatible route or block does not prove that every Drupal module works unchanged.

Explore the explanation and real example