Dynamic Content Block data should be saved to mautic instance, not specific email

My idea is:

Currently dynamic content setup is saved individually in every email. This means, that it can’t be reused - even if its always the same configuration. It would be better to save it to the general dynamic content table and reuse it from different emails.

I think these groups of people would benefit from this idea:

People who make use of a lot of dynamic content in emails.

Why I think they would benefit from this idea:

Reducing effort, better managability of dynamic content blocks. Reuse existing logic.

Any code or resources to support this idea:

Dynamic content for other use is already using this approach.

Are you willing to work on this idea?:

No Coding, but support to form and shape this idea.

What skills and resources do you need to explore this further?

Dev knowledge - is it feasible to centralize dynamic content this way?

Well, this is what Twig Templates do:

Here is a video (from 2 years ago)

1 Like

Thanks @joeyk … will check. Regarding the reuse of configured dynamic content setup, would you agree that a centrally managed function (there is dynamic web content already) for dynamic email content would be efficient and user friendly as well?

I agree, and I think it should be super user friendly.
At the same time, the sculptors of Mautic are trying to keep the codebase super lean.
If a plugin and well documented and anone can easily add it, then why not.