Commit b84fa9d h

Pat Ambrosio · 26-08-26 15:31

Drop the post breadcrumb

Changes: 2 files +20 -63

Changes (Side-by-Side)

Raw

commit b84fa9d9f3753e9038ff864afc8a7fd973495478
Author: Pat Ambrosio <cp.ambrosio@gmail.com>
Date:   Wed Aug 26 15:31:31 2026 +0800

    Drop the post breadcrumb
    
    Added one commit ago and wrong. A post's own segment is its slug, which
    usually restates the title sitting directly beneath it -- the header read
    "DEAD KEY -> ON PLAIN TEXT" above a title saying "On Plain Text".
    
    Worse than the redundancy: making it read well would mean choosing titles
    that differ from their slugs, so the layout would be dictating what a post
    may be called. A theme should not constrain the writing that way.
    
    A page keeps its trail, which earns its place: the path has segments --
    study, notes/method -- that the title does not repeat, and a page has no
    date line to identify it either.
    
    The tests become the rule they replaced: a post's header is the site title
    alone, and a page's still has its trail, so the two differ on purpose
    rather than by omission. Checked by mutation.
    
    Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
    Claude-Session: https://claude.ai/code/session_01WnSAstgnDYdKPwLGv1YZE5

diff --git a/share/jenny/layout/post.sh b/share/jenny/layout/post.sh
index f22979c..396c355 100755
--- a/share/jenny/layout/post.sh
+++ b/share/jenny/layout/post.sh
@@ -90,35 +90,6 @@ render_footer_nav() {
   printf '</footer>\n'
 }
 
-# post_crumb
-# The post's own segment of the breadcrumb, matching what a page renders: an
-# arrow, then the slug with dashes read as spaces.
-#
-# The slug rather than the title because the breadcrumb is a picture of the
-# URL -- it says where you are, and the address is what the reader can act on.
-# A long title would also wrap the header, which the trail is meant to survive.
-#
-# Marked current the way a page's last segment is, so the same rule underlines
-# it and the two headers behave identically.
-post_crumb() {
-  [ -z "${IS_PAGE:-}" ] || return 0
-  local url=${POST_URL:-} slug
-  [ -n "$url" ] || return 0
-  slug=${url##*/}
-  # Under URL_STYLE=html the URL carries the extension, which is part of the
-  # address but not of the post's name -- without this the crumb read
-  # "hello world.html".
-  slug=${slug%.html}
-  [ -n "$slug" ] || return 0
-  # Built from URL_PREFIX rather than POST_URL, which is site-absolute: the
-  # site title beside it is relative, and a header that mixes the two breaks
-  # the moment the site is served from a subdirectory.
-  # The href keeps the URL's own ending; only the label drops it.
-  printf ' &#x2192;&#xFE0E; <a href="%s/post/%s" class="current">%s</a>' \
-    "$URL_PREFIX" "$(html_escape "${url##*/}")" \
-    "$(html_escape "$(printf '%s' "$slug" | tr '-' ' ')")"
-}
-
 html_escape() {
   local s=$1
   # The replacement text must escape &, because bash >= 5.2 expands a bare &
@@ -607,7 +578,13 @@ cat << _EOF_
     </head>
     <body>
       <a href="#" class="theme-toggle" aria-label="Toggle dark mode">&#x263C;&#xFE0E;</a>
-      <header><a href="$URL_PREFIX/"$([ -n "${IS_PAGE:-}" ] && echo ' class="current"')>$(html_escape "${BLOG_TITLE:-}")</a>$(post_crumb)</header>
+      <!-- No breadcrumb on a post. Its own segment would be the slug, which
+           usually restates the title sitting directly beneath it -- and making
+           that read well would mean choosing titles that differ from their
+           slugs, which is the layout dictating what a post may be called. A
+           page's trail earns its place because the path has segments the title
+           does not repeat. -->
+      <header><a href="$URL_PREFIX/">$(html_escape "${BLOG_TITLE:-}")</a></header>
       <article>
       <div class="heading$([ -n "${IS_PAGE:-}" ] && echo ' heading-page')"><a href="${POST_URL:-}">$([ -z "${IS_PAGE:-}" ] && printf '<span class="stamp" data-iso="%s"><span class="stamp-slide"><span class="stamp-abs">%s</span><span class="stamp-rel" aria-hidden="true"></span></span></span>' "$(html_escape "${POST_DATE_RFC822:-}")" "$("$DATE" -d "${POST_DATE_RFC822:-}" +%m/%d/%Y 2>/dev/null || printf '%s' "${POST_DATE:-}")")<h1 class="title">$(html_escape "${POST_TITLE:-}")</h1></a></div>
       <div class="body-row">
diff --git a/test/regressions.sh b/test/regressions.sh
index 31d059e..98cc3ab 100755
--- a/test/regressions.sh
+++ b/test/regressions.sh
@@ -913,48 +913,28 @@ assert_file_contains "$tl_post" '.citations ol { padding-left: 1.4em; margin-top
 it "the build is clean"
 assert_eq "$stderr_output" ""
 
-suite "a post names itself in the breadcrumb"
+suite "a post has no breadcrumb"
 
-# A page's header shows the trail to where you are; a post's showed only the
-# site title, so the two headers disagreed about what a header is for.
+# A post's own segment would be its slug, which usually restates the title
+# directly beneath it. Making that read well would mean choosing titles that
+# differ from their slugs -- the layout dictating what a post may be called.
+# A page's trail earns its place because the path has segments the title does
+# not repeat.
 
 bc="$TMPROOT/breadcrumb"
 make_blog_min "$bc" 1 10
+mkdir -p "$bc/pages"
+printf '# Plain\n\nBody.\n' > "$bc/pages/plain.md"
 run_jenny_split "$bc"
 bc_post=$(find "$bc/.dist/post" -name '*.html' | head -1)
 
-it "the post's own segment follows the site title"
-assert_file_contains "$bc_post" '&#x2192;&#xFE0E; <a href='
-
-it "the segment reads the slug with dashes as spaces"
-# The slug rather than the title: the breadcrumb is a picture of the URL, it
-# says where you are, and a long title would wrap the header.
-assert_file_contains "$bc_post" 'class="current">post 01</a>'
-
-it "the segment is marked current, like a page's last one"
-# So the same rule underlines it and the two headers behave identically.
-assert_file_contains "$bc_post" 'class="current">'
-
-it "the crumb link is relative, like the site title beside it"
-# POST_URL is site-absolute; a header mixing the two breaks the moment the
-# site is served from a subdirectory. Scoped to the header: the heading's own
-# link is absolute and was so before this, which is a separate question.
+it "a post's header is the site title alone"
 bc_header=$("$GREP" -o '<header>.*</header>' "$bc_post" | head -1)
-assert_contains "$bc_header" 'href="../post/'
-assert_not_contains "$bc_header" 'href="/post/'
+assert_not_contains "$bc_header" 'class="current"'
+assert_not_contains "$bc_header" '&#x2192;&#xFE0E;'
 
-it "the label drops the extension the href keeps"
-# Under URL_STYLE=html the URL carries .html, which is part of the address but
-# not of the post's name -- the crumb read "hello world.html".
-printf 'URL_STYLE=html\n' >> "$bc/.blogrc"
-run_jenny_split "$bc"
-assert_file_contains "$bc_post" 'class="current">post 01</a>'
-assert_file_contains "$bc_post" 'href="../post/post-01.html"'
-
-it "a page's breadcrumb is unchanged"
-mkdir -p "$bc/pages"
-printf '# Plain\n\nBody.\n' > "$bc/pages/plain.md"
-run_jenny_split "$bc"
+it "a page still has its trail"
+# The two headers differ on purpose, not by omission.
 assert_file_contains "$bc/.dist/plain.html" 'class="current">plain</a>'
 
 it "the build is clean"