...
- Update the Readme file Alex Hammerschmied as soon as possible (Friday at the latest for the testing sprint please!)
- Start on documentation - please create a Google Doc in the community Drive and share the link - Alex Hammerschmied will make a start on this and we can all contribute. Must include what is needed to make templates support this builder If you can write it in markdown it makes it much quicker to port over to the docs.
- Test the behaviour with emails and landing pages when GrapesJS builder is enabled and an existing resource is edited and saved. Also test what happens if you edit and save, and then go back to the Legacy builder and open/edit the resource again - Alan Hartless has done some testing but we need to test it much more widely
- Work on resources for the Marketing Team to tell the world about the Email and Landing Page builder and how they can test it. Also include tutorials / reviews etc. Maybe work with other language communities to get them translated into other languages.
- Alex Hammerschmied will push over separate PR’s for each feature or enhancement/fix that they have created while in use in production so that they can be reviewed and merged as appropriate.
- Alex Hammerschmied to submit a PR to include the root files in addition to the minified files
- Jozsef Keller is going to make some PR’s this weekend to add the new templates that will ship with Mautic Core and support the GrapeJS builder.
- Test and merge the PR’s
- Make a PR to include the builder in the 3.3 release
Decisions
- We will add a note on the Readme to say that we are NOT supporting 2.x and we will remove that branch when we launch 3.3 General Availability