With your own modules it would be practical to have the rich_text editor available in the content preview instead of just in the left column of the fields.json output. Similar to the @hubspot/rich_text module, where the contentEditable = “true” attribute is passed to the DIV tag.
The same would be practicable for the headers at module @hubspot/header.
For the @ hubspot / header module, it would make sense to pass on the “class” attribute. then you could reuse this module instead of writing your own modules for headers (h1, h2, etc.)
Inline editing doesn’t work for custom modules in the HubSpot CMS.
Inline editing works well for HubSpot’s default modules, but not for custom modules. We can use inline editing with HubSpot’s default text/richtext/header module, but as soon as we copy it, without making any changes, to our theme, inline editing stops working.
In our experience, this feature is critical to productivity and convenience for users and editors.
Enabling inline editing and dynamic attribute handling for custom and default modules in HubSpot CMS would greatly enhance usability, productivity, and module reusability for developers and content editors.