Yes, my goal is having interactive components that come from the CMS via html π . For example I want to build articles that not only have image and text, but also could have a simple calculator to complement the content, with each cms page having a different calculator.
If a list of blocks is returned from cms you can render it in webstudio with collection and show prop. When block is "calculator" render html embed with calculator script.
your html from cms just needs to contain some placeholder container and potentially attributes if you need to configure it from the cms, its basically all client-side scripting otherwise