Document use cases where XB's field widgets don't 1:1 match how they would work in a twig theme

Created on 6 May 2025, 6 days ago

Overview

As suggested in 📌 Support props that can use wysiwyg widgets Active we should expand the Redux integrated field widgets README to summarize ways in which the Render Array -> React pipeline doesn't necessarily provide a 1:1 replacement for a Twig-based alternative. This should include

Complex widgets such as ones using CKEditor5.
The additional complexity introduced by using Radix since the attributes do not map exactly and in some cases native elements aren't directly accessible even as refs.
Distinguish theme-related complexities from those that have more to do with autosaving and real time preview updates - something that would be an issue regardless of theme.

And probably more - it's a big topic.

Proposed resolution

User interface changes

📌 Task

Status

Active

Version

0.0

Component

Documentation

Created by

🇺🇸United States bnjmnm Ann Arbor, MI

Live updates comments and jobs are added and updated live.

Merge Requests

!1010Document use cases where XB's field widgets don't 1:1 match how they would work in a twig theme
Open
🇺🇸United States bnjmnm
updated about 15 hours ago

Comments & Activities

Issue created by @bnjmnm
Comment 5 days ago →
🇺🇸United States bnjmnm Ann Arbor, MI
Note: include a mention of function xb_stark_preprocess_field_multiple_value_form which should be there after 📌 Add e2e tests for multi-value textfield widget in page data form Active as that is some extra lifting that wouldn't be needed without Radix & the templates were more analagous to our Twig ones.
Comment 4 days ago →
🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
Let's document this while it's still fresh in your head 😊
Comment 4 days ago →
🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
📌 Support props that can use wysiwyg widgets Active is in!
Merge request !1010#3522999 writeup on theme limitations → (Open) created by bnjmnm

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024