Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
» Clarify how this differs from similar modules (or join forces)
One of the 7 principles of the Drupal project is collaboration. Would you consider merging your project into embed widgets and collaborating with it's authors?
Otherwise, it would be great if you could document on the project page what makes this module different and also link to that module so that people can make a good decision about which one to use.
Hey, thanks for the question, indeed, at first glance it seems as though the modules do the same thing. However as you will see in the first release of the module, we are different enough to require a separate module. A couple of reasons are:
* Embed method allows for interaction with third party site DOM.
* Works out of the box with the Panels module (you can embed any page without extra steps required, just by placing an url prefix to the page path).
* Provides control over your embed (you can blacklist sites).
* Allows for extra settings of the Panel Page / Variant.
* It is actively maintained.
The last one is not a reason for a new module, it's a reason to co-maintain the under-maintained module.
The rest seem pretty valid to me. I suggest adding them (along with a link to embed) to the project page to help end users know whether or not they should use this module or embed.
Yes, it's not an iframe, it uses JavaScript (document.write) to embed your content into the third party site and when the content is evaluated, the site will load your JS and CSS files. The documentation is still a work in progress, but I hope this sheds some light.
Comments
Comment #1
gregglesOne of the 7 principles of the Drupal project is collaboration. Would you consider merging your project into embed widgets and collaborating with it's authors?
Otherwise, it would be great if you could document on the project page what makes this module different and also link to that module so that people can make a good decision about which one to use.
Comment #2
tudor.sitaru commentedHey, thanks for the question, indeed, at first glance it seems as though the modules do the same thing. However as you will see in the first release of the module, we are different enough to require a separate module. A couple of reasons are:
* Embed method allows for interaction with third party site DOM.
* Works out of the box with the Panels module (you can embed any page without extra steps required, just by placing an url prefix to the page path).
* Provides control over your embed (you can blacklist sites).
* Allows for extra settings of the Panel Page / Variant.
* It is actively maintained.
Comment #3
gregglesThe last one is not a reason for a new module, it's a reason to co-maintain the under-maintained module.
The rest seem pretty valid to me. I suggest adding them (along with a link to embed) to the project page to help end users know whether or not they should use this module or embed.
Comment #4
Flying Drupalist commentedHow are you embedding this? This is not an iframe? You can load JS and CSS files directly onto the external site?
Comment #5
tudor.sitaru commentedYes, it's not an iframe, it uses JavaScript (document.write) to embed your content into the third party site and when the content is evaluated, the site will load your JS and CSS files. The documentation is still a work in progress, but I hope this sheds some light.
Comment #6
tudor.sitaru commentedComment #7
gregglesCould you add this documentation to the project page to explain how it differs from similar modules and link to those similar modules?
Comment #8
tudor.sitaru commentedUpdated the module's description page, please reopen the ticket if you think more details are required.