External CSS file for Form styles

[Indy-rbo]

Description

We frequently need to apply custom CSS to our forms. At the moment, this CSS is stored as an escaped string within the styles key of the form’s .json file. To make future changes easier, we also keep a separate .css file alongside the JSON. However, this approach requires manual effort to keep both files in sync, especially when pulling changes.

It would be helpful if the contents of the styles field were written out to an external .css file on pull and read from that file when pushing changes. Ideally, this file would follow the same naming convention as the form’s .json file (for example, *_FormData.json). This would greatly improve the authoring and maintenance experience for custom styles.

Alternatives

Continue working with escaped CSS strings in JSON, or build custom local tooling to extract and generate a .css file from the styles key.