From e344988c6e057bf2d21aeec8c063d45039f6d291 Mon Sep 17 00:00:00 2001 From: Ted Goas Date: Fri, 11 Feb 2022 19:39:08 -0500 Subject: [PATCH] MIssed read as HTML and caused a typo Fixes #279 --- docs/content/templates.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/templates.md b/docs/content/templates.md index 3b7f227..1654d39 100644 --- a/docs/content/templates.md +++ b/docs/content/templates.md @@ -64,7 +64,7 @@ Not necessarily bugs with the code in this repo, but a few things that could tri I recommend against using a CSS inliner with Cerberus. Here’s why: - Cerberus is supposed to be simple and should not require a dependency like a CSS inliner. -- The placement of Cerberus’s CSS is already optimized. The CSS in the is meant only for email clients that parse CSS in this location. It doesn’t need to be inlined. +- The placement of Cerberus’s CSS is already optimized. The CSS in the <head> is meant only for email clients that parse CSS in this location. It doesn’t need to be inlined. - There are some CSS selectors like :hover that don’t inline so well and cause errors in some CSS inliners. - Inlining leads to code bloat. Not only does this impact download speeds, but some email clients like Gmail and iOS Outlook truncate messages after they exceed a certain file size.