Merger

[BayBreezy]

Feature request

Summary

Hey,

I was able to use the new plugin SDK that Strapi provides to create a version that is compatible with Strapi5. We were having a discussion over here: BayBreezy/strapi-plugin-email-designer-5#10 about merging both plugins so that there is no confusion when users want to use the email designer.

We would love to hear what you think about this. Feel free to check the thread to see what we discussed over there.

Why is it needed?

To cause less confusion among Strapi users.

Suggested solution(s)

Find some way to merge the new plugin into this one.

Related issue(s)/PR(s)

N/A

[alexzaganelli]

Hi @BayBreezy , thank you for your work on the forked repository and for addressing this issue. I truly appreciate the effort. To be transparent, I’ve stepped back a bit from the development of this project due to the increasing number of feature requests without much contribution to the actual development. It’s encouraging to see the community take initiative, and I hope more developers will continue to get involved.

I’d be happy to review a pull request if you decide to submit one to the main repo. However, before publishing any updates, it would be necessary to involve a few testers (besides myself) to ensure everything runs smoothly considering that this plugin is downloaded thousand and thousand times per weeks ( NPM Link ) .

[boazpoolman]

I would like to help testing when a beta is ready!

[begservice]

if i get it running i will help as well

[boazpoolman]

In terms of next steps; @BayBreezy can you draw up a PR with your changes?

[BayBreezy]

Ehhhh.. I am not even sure where to start.
Do i just for this repo and put my changes on a new branch?

[boazpoolman]

Yep, that's about it!

[BayBreezy]

Cool cool.
The plugin just got placed on the marketplace btw.
Do we still move forward with this?