From cd8d8b495001be667ab994e46ec7e5dd50f4eb3b Mon Sep 17 00:00:00 2001 From: Philippe Granger <90652303+ppgranger@users.noreply.github.com> Date: Sun, 9 Aug 2026 21:25:09 +0200 Subject: [PATCH] fix: Liquid tags render even inside HTML comments, breaking the homepage MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The explanatory comment at the top of head.html was an HTML block, but it mentioned {% seo %} and {%- feed_meta -%} in prose. Liquid doesn't know those are 'just text in a comment' — it evaluates tags wherever they appear in the template, comment or not. {% seo %} renders its own '', and that tag's own '-->' closed the HTML comment early, leaking the rest of the explanation text plus a second, duplicate straight into the rendered page. Visible on the live site as raw comment prose above the real content. Fixed by switching to a Liquid {% comment %}...{% endcomment %} block: content inside is never parsed, so tags mentioned in the explanation stay inert regardless of what they render to elsewhere in the file. --- docs/_includes/head.html | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-) diff --git a/docs/_includes/head.html b/docs/_includes/head.html index 99dad67..855818b 100644 --- a/docs/_includes/head.html +++ b/docs/_includes/head.html @@ -1,4 +1,4 @@ - + (meta tags, seo tag, stylesheet, feed_meta, conditional Google Analytics) + so nothing else regresses; the JSON-LD block is the only addition. + + This has to be a Liquid {% comment %} block, not an HTML comment: + Liquid tags are evaluated wherever they appear, even inside HTML comments, + and {% seo %} below renders its own "" — whose + "-->" would close an HTML comment early and leak the rest of this text + (plus a duplicate ) straight into the rendered page. +{% endcomment %}