I’m attempting to build my own form within the Form Content’s ‘Page Contents’ asset. At present, I can get some key information (ID, name, note, error, label), but other attributes of a Form Question (is required, placeholder, width, height, type, extras, etc) aren’t available for use in constructing the form.
Having individual keywords for everything would solve the issue, as long as there’s a keyword for each attribute. However it seems simpler if the pre-existing keyword format for attribute access were extended to work on these ‘shadow’ assets.
Either way, that requires both implementation on your side and then eventually an upgrade on ours – making lead time a long time away. In the meantime, the simplest solution is just to hard-code it all into the Page Contents asset. That’s not such an bad solution because I’m already having to hardcode the field order, asset IDs in keywords etc; but I’d still prefer just one location (eg the Form Questions) where an editor can make changes and avoid touching the HTML.