Skip to content

Update Email Builder overview image for the Mautic 6.0 UI - #902

Open
promptless-for-oss wants to merge 2 commits into
mautic:6.0from
Promptless:promptless/issue-473-update-email-landing-page-images
Open

Update Email Builder overview image for the Mautic 6.0 UI#902
promptless-for-oss wants to merge 2 commits into
mautic:6.0from
Promptless:promptless/issue-473-update-email-landing-page-images

Conversation

@promptless-for-oss

@promptless-for-oss promptless-for-oss commented Aug 1, 2026

Copy link
Copy Markdown
Contributor

Open in Promptless

Refreshes editoroverview.png with a freshly captured Mautic 6.0.9 GrapesJS builder screenshot, with the five red numbered callouts redrawn to match the numbered list in the prose. No prose or image directives change.

Scope note: editorfonts.jpg is intentionally left unchanged — it shows an expanded native browser font dropdown (OS-rendered select popup) that cannot be authentically re-captured in a headless browser.

Closes #473

Trigger Events


Update — addressing @RCheesley's review: recaptured editoroverview.png using the Brienz theme (matching the original) instead of the blank theme. The builder canvas now shows the richer Brienz newsletter (logo, hero image, headline, and a call-to-action button); the five red numbered callouts (1 device-size toggles, 2 undo/redo, 3 editor tool cluster, 4 Sections panel, 5 Blocks panel) are redrawn to match the prose. Captured on a local Mautic 6.0.9 instance at 2x.

Refresh editoroverview.png with a freshly captured Mautic 6.0.9 GrapesJS
builder screenshot, with the five red numbered callouts redrawn.

editorfonts.jpg is intentionally left unchanged: it shows an open native
browser font dropdown that can't be captured in a headless browser.

Refs mautic#473
@promptless-for-oss
promptless-for-oss requested a review from a team as a code owner August 1, 2026 04:04
@promptless-for-oss
promptless-for-oss requested review from adiati98 and favour-chibueze and removed request for a team August 1, 2026 04:04

@RCheesley RCheesley left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Small suggestion - the theme used in the original is called Brienz.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is a worse screenshot as it's just using the blank theme. Let's use a nicer theme?

@promptless-for-oss

Copy link
Copy Markdown
Contributor Author

Thanks @RCheesley — good call. I'll recapture the Email Builder overview using the Brienz theme (as in the original) instead of the blank theme, redraw the five numbered callouts, and follow up here once done.

@promptless-for-oss

Copy link
Copy Markdown
Contributor Author

Confirmed — the current image is the blank "Hello World" theme, while the original used the richer Brienz newsletter template. Standing up a local Mautic 6.0.9 instance to recapture the Email Builder overview with the Brienz theme, then redrawing the five numbered callouts (device-size toggles, undo/redo, editor toolbar, Sections panel, Blocks panel) to match the prose.

Per maintainer review on PR mautic#902: recapture editoroverview.png in the
GrapesJS Email Builder using the Brienz theme (matching the original)
instead of the blank theme. The five red numbered callouts are redrawn
to match the numbered list in the prose. Captured at Mautic 6.0.9, 2x.
@promptless-for-oss

Copy link
Copy Markdown
Contributor Author

Thanks @RCheesley — good catch. I've recaptured the Email Builder overview using the Brienz theme so it matches the original instead of the blank/default theme. The builder canvas now shows the richer Brienz newsletter (logo, hero image, headline, and the "MORE UPDATES" button), and the five numbered callouts have been redrawn to line up with the numbered list in the prose. Captured on a local Mautic 6.0.9 instance at 2x, pushed as SHA 43fd136. Could you take another look when you have a moment?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants