Bundle mage-os/module-pagebuilder-template-import-export

[dadolun95]

I propose adding mage-os-lab/module-pagebuilder-template-import-export as a bundled module. https://github.com/mage-os-lab/module-pagebuilder-template-import-export

• It provides import/export functionality for PageBuilder templates across instances.
• It supports both local .zip template transfer and synchronization with Dropbox repositories.
• It is maintained and has practical utility for agencies and merchants working with distributed content.

Implications

• Merchants and agencies can standardize PageBuilder content across multiple stores without manually recreating it.
• Admins will be able to pull and sync reusable templates from Dropbox repositories (with multi-repository support).
• Shops leveraging PageBuilder for rapid content development can speed up their workflows and reduce errors.

Risks

• Dependency on Dropbox for remote sync, requiring proper API configuration.
• Admins may incorrectly configure Dropbox apps, leading to sync errors until setup is corrected.

Benefits

• Simplifies migration and reuse of PageBuilder templates across environments and projects.
• Enables remote content repository workflows via Dropbox.
• Reduces time-to-market for merchants using PageBuilder at scale.

PR

This PR results in the module being added as a pinned require of mage-os/product-community-edition like:

"mage-os/module-pagebuilder-template-import-export": "1.0.0",

Composer will then require it via Packagist. The latest published version will be pinned at the time of each release.

[rhoerr]

I code reviewed the Page Builder Template Import/Export module. I would like to see issues 3-7 addressed if possible, but I'm in favor of it being included in the next release.

I still need to review the CMS widget module.

I still need to try out both.

[rhoerr]

I reviewed the CMS widget preview module. I would like to see issues 2, 5, 6, 7, 8 addressed if possible before merge and release. I like what it adds, and I'm in favor of it being included in the next release.

[rhoerr]

To this actual PR: Please

• Split one module off into a separate PR, so each one can be considered and discussed separately
• Add some analysis of implications and risks of bundling it, based on the template I used in other bundle PRs (Perplexity can do most of the work for you)
• Sort the added modules alphabetically in the dependency list
  Handled

[rhoerr]

See last comment

[rhoerr]

I split page-builder-widget into a separate PR #243

[rhoerr]

• Code was reviewed, patched, and released. None of the open issues/suggestions are blockers.
• It adds a valuable and easy to use feature for managing page builder templates across environments.
• I haven't heard any voices of concern.
• I think it's simple enough and adds value enough to justify bundling it.

Merging.