Skip to content

PMM-15031: Host the PMM email logo on the docs site - #5829

Open
mattiasimonato wants to merge 4 commits into
mainfrom
PMM-15031-email-logo-asset
Open

PMM-15031: Host the PMM email logo on the docs site#5829
mattiasimonato wants to merge 4 commits into
mainfrom
PMM-15031-email-logo-asset

Conversation

@mattiasimonato

@mattiasimonato mattiasimonato commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

Ticket number: PMM-15031

Feature build: SUBMODULES-4543

PMM emails showed a broken logo because the old percona.com logo URL was deleted during the rebranding. Emails need an image on a public URL we control, so this PR adds the new PMM logo to the docs site assets. The docs site then serves it at https://docs.percona.com/percona-monitoring-and-management/assets/pmm-logo-email.png, which is the URL the Grafana email templates point to.

The file goes in documentation/docs/assets/ and not in documentation/docs/images/ on purpose: documentation/resources/bin/check-images.sh only scans documentation/docs/images/, so make doc-remove-images would delete an image that no docs page uses. Nothing else changes, this PR is one PNG.

The companion change lives in the percona/grafana percona/grafana#921 and must merge after this one, so the URL already works when the templates start using it.

The logo in Grafana's email templates was fetched from a percona.com
product-logo URL that the rebranding removed. The templates need a
public host we control, so the asset ships with the docs site and they
point at /assets/pmm-logo-email.png there.

It lives in docs/assets rather than docs/images because
documentation/resources/bin/check-images.sh only sweeps docs/images:
under docs/images, make doc-remove-images would delete an asset that no
page references.

The file is 432x193 and is rendered at half that width for 2x displays.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Documentation changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants