Document external CSS/font URL requirements in email HTML guidelines (DOC-2315) - #463
Open
BrindaaRC wants to merge 1 commit into
Open
Document external CSS/font URL requirements in email HTML guidelines (DOC-2315)#463BrindaaRC wants to merge 1 commit into
BrindaaRC wants to merge 1 commit into
Conversation
Add a section explaining that invalid or non-directly-accessible external CSS/font URLs cause CSS inlining to fail and result in broken styling, while the campaign can still be sent. Notes that MoEngage does not validate these URLs and it is the client's responsibility to verify them before sending. Addresses SUP-6995 (recurring; also SUP-6383). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Adds an External CSS and Font URLs section to the email HTML guidelines page (best-practices-to-be-followed-within-an-email-body-html-guidelines.mdx).
The section:
<link href>must return the file directly, not a preview/share link (e.g. a Google Drive share link) or a URL that 404s.<Warning>) that MoEngage does not validate external CSS/font URLs, so verifying them before sending is the client's responsibility.Why
Support ticket SUP-6995 (recurring; also SUP-6383): invalid/inaccessible external CSS URLs caused broken styling while the campaign still sent, with no clear signal to the marketer. Engineering (Apurv Tiwari) confirmed MoEngage cannot validate arbitrary external CSS URLs.
Reviewer notes
🤖 Generated with Claude Code