Multiple fields on the same Resource

[bbs-smuller]

Hello,

I have a question for the version 3.0
I have multiple "Mason::make()" on the same resource.

But using the iframe it seems that only the last field is handled.

It is link to the <iframe> in

mason/resources/views/mason.blade.php

Line 81 in 1db6ea0

x-ref="previewIframe"

and the related JS in

mason/resources/js/mason.js

Line 43 in 1db6ea0

iframe = this.$refs.previewIframe

I cannot fix it by myself but I think it will be a great level up to allow multiple fields in the same resources.

Thanks for all your work !

[muyaedward]

Hi @bbs-smuller,

Thanks for raising this! I understand the request, but I wanted to share some perspective on Mason's design philosophy.

The core purpose of Mason builder is to build a page - it's designed as a comprehensive page builder where you construct
the entire page content through a single, unified editing experience. Having multiple Mason editors on the same resource would
somewhat defeat this purpose, as it fragments the page-building experience and creates potential conflicts with the iframe
preview system (as you've already discovered).

Mason is meant to give you one powerful canvas where you assemble all your content blocks in a cohesive way, rather than
having multiple disconnected editors scattered across different fields. This keeps the editing experience intuitive and
prevents confusion about which editor controls which part of the page.

That said, I'd love to hear @awcodes' take on this - there might be use cases or architectural approaches I'm not considering.
Adam, what are your thoughts on supporting multiple Mason instances on a single resource?

Best regards

[bbs-smuller]

Hello @muyaedward ; thanks for your feedback.

I think there's a lot of examples to allow multiple Mason bricks fields on the same page.
For example if you want to handle summary and body of the page and use same bricks.
Or like in my screenshot a field for EN locale bricks and another for other locales (if you dont want to use a i18n library).
Or simply to handle the content of a slider without generating all page content from bricks.

But sure ; interested in how @awcodes see the purpose of the library.

[awcodes]

I agree with what @muyaedward said.

But v3.0.4 supports them.

[bbs-smuller]

Whaou ! Thanks !