We are exploring other options for getting the outstanding issues resolved as Alex Hammerschmied 's team are not able to do this in time. Jozsef Keller is speaking with some Mautic developers in Hungary who might be able to help. Worst case, we can have this go out with the 3.3 Release Candidate and aim to fix the bugs in the week between the Release Candidate and General Availability.
We need to update the readme to give information about how to install it for testing - there are broken links and incorrect information on the readme currently
We need to write the documentation on how to enable the plugin, how to disable it and go back to the legacy builder (and any steps you have to take like rebuilding assets, clearing cache). Alex Hammerschmied will update the readme and start the documentation
We talked about the 2.x branch and we will not be supporting the 2.x branch. We will put a note in the repo Readme file to say we will be removing that branch when the 3.3 General Availability release is made.
We need to test and get merged the PR’s from Alan:
https://github.com/mautic/mautic/pull/9654
https://github.com/mautic/plugin-grapesjs-builder/pull/42
https://github.com/mautic/developer-documentation/pull/185
We need to make the PR to include this plugin in Mautic Core. Alex Hammerschmied is going to look into this on Fri/Sat but may need some guidance on how to do this in Github. Zdeno Kuzmany would you be able to assist?
We talked about existing emails and landing pages which, once you turn on the new builder, will no longer be able to ‘see’ the old templates. We need to test this behaviour. We will have to inform folk that they will need to add into their theme config file a line to be able to work with the themes in the new builder:
Go to the config.json file of the theme and add "builder": "grapesjsbuilder" to the json object
Alan Hartless found that it looks like when you edit an existing resource, you can make changes and save them, however the wrong template will show in the dropdown because the one that was used originally is not available (assuming they did not add the line in the config file for the template). We need to document this if that is the case and make sure that people are aware, before they start working with the builder. We should also test what happens if you edit with GrapeJS and then go back to the default builder. This will only be relevant until 4.0 but we should still make sure that it does not break the world.
We have been asked to support Jozsef Keller with the release marketing materials for 3.3 - we should make a big splash about this being available for beta testing and make sure that we are up front about anything they need to consider before enabling it (e.g. the point above).
Alex Hammerschmied asked how best to share the changes he has made using the GrapesJS builder in production. We suggested making one PR for each feature or fix, so that we can decide on a case by case basis what is needed.
Alex Hammerschmied asked if we should have the root JS file and the minified files in the repo - currently we have the minified file which makes it difficult to work with when making changes. We think we should for now have both, and PR’s should affect both files, but going forward we should maybe find a way to only have the root file and not commit the minified files as it leaves it open to making mistakes which could break the builder.
Jozsef Keller is going to submit some new themes which will be compatible with the new builder and will be optimised for best practice.
Alex Hammerschmied is making some resources on the new builder but it is in German, however he may be able to create the basic videos and share them with us in English. We can add any fancy visuals if needed post-production.