When users choose a custom HTML block, it usually means standard blocks cannot solve their use case.

In many cases, this becomes a blocker. Here is a real example from practice:

– The current menu block does not work properly on mobile devices in responsive, multi-column layouts.

– A user needs a very simple footer structure: logo in the left column and a menu in the right column (stacking on mobile). This cannot be achieved with standard Stripo blocks.

– As a result, the user switches to a custom HTML block with custom CSS.

– The footer is required in every email, so the user saves it as a module.

– However, when saved as a module, the CSS breaks and the element no longer works as intended.

This creates a hard limitation. Users cannot solve the problem with standard blocks, and at the same time, Stripo prevents them from implementing a custom solution.

Please allow saving and reusing CSS for custom HTML blocks inside modules so custom solutions remain functional and reusable across emails.

For custom HTML blocks, CSS is a critical part of the solution. Without preserving the associated CSS, the custom code cannot work as intended. It would be much better if Stripo saved and reused custom HTML together with its CSS as a single, intact module.