"let this be the 'footnote pattern' as it also highlights in red, and it picks out highlight bold for particular words or phrases."
The problem
A long-read accretes reader questions and replies in the margins. Dumped inline they swamp the spine of the piece; given long descriptive titles they turn the footer into a wall of competing headlines. You want the appendix dense and scannable when closed, and fully self-announcing when opened — without the collapsed list shouting over the article above it.
The conventional footnote solves one half: it gets the annotation out of the body. It fails the other half: the collapsed list has no hierarchy, so the eye can't scan it, and the opened body leads with a number rather than a title, so you're already back in the spine before the note has announced itself.
The element, in-page
The live copy below runs in a sandboxed iframe (the pattern-preview primitive). Superscript markers link to the footnote list; clicking any marker scrolls to the matching note and highlights it via CSS :target. The back-link returns to the reference point in the body. Flip the tabs to read the source.
The most important insight in any long-read rarely sits in the spine of the
argument — it hides in the qualification, the concession threaded into a
subordinate clause.1
Great editors know this: the footnote is where the writer
lets their guard down and says what they actually mean.
A single-word handle gives each note its own address in the reader's
memory. Hold glance or keystone in mind and you can
find it again; a half-sentence title evaporates before the page
scrolls back.2
Two type signatures carry distinct weights: red italic for the
through-line of emphasis, bold for the term under the lens. Nest
them where a word sits at both intersections — the argument's spine
and the note's specimen: keystone.3
The margin is where the guard drops — qualification
Why do the best insights hide in subordinate clauses?
Because the main argument is being watched. In the margin, the
writer answers the question they actually
asked themselves — too uncomfortable to carry in the spine.
↩ back
One word is a memory hook; a phrase is noise — address
What makes a single keyword memorable?
Working memory holds roughly seven items. A word costs one slot;
a phrase crowds out three. The note's handle
must cost nothing to hold.
↩ back
Bold-red marks the pivot of the argument — intersection
When should both signatures apply to the same word?
When the word is both the argument's through-line emphasis and
the note's examined term — simultaneously the argument's
spine and the note's specimen.
↩ back
*{box-sizing:border-box;margin:0;padding:0}
body{font-family:'Newsreader',Georgia,serif;background:#f7f3ec;color:#1a1816;
font-size:18px;line-height:1.7;padding:28px 24px;max-width:660px}
em{font-style:italic;color:#2c4a3a}
strong{font-weight:700;color:#1a1816}
em strong,strong em{color:#2c4a3a;font-weight:700;font-style:italic}
/* Body text */
.body-text p{margin:0 0 1.1em}
.body-text p:last-child{margin-bottom:0}
sup{font-size:0.68em;line-height:1;vertical-align:super}
sup a{color:#2c4a3a;text-decoration:none;
font-family:ui-monospace,'SF Mono',monospace;font-size:11px;
padding:1px 4px;border-radius:2px;
border-bottom:1px solid rgba(44,74,58,0.35);font-style:normal}
sup a:hover{background:rgba(44,74,58,0.09);border-bottom-color:#2c4a3a}
/* Footnotes list */
.footnotes{list-style:none;padding:0;margin:36px 0 0;
border-top:1px solid rgba(26,24,22,0.18);padding-top:4px}
.footnotes li{padding:18px 0;border-bottom:1px solid rgba(26,24,22,0.08);
scroll-margin-top:12px;transition:background 0.35s,padding 0.2s}
.footnotes li:last-child{border-bottom:none}
.footnotes li p{margin:0 0 8px;font-size:15px;line-height:1.6}
.footnotes li p:last-child{margin-bottom:0}
/* Carried-in headline — full title appears at top of opened note */
.fn-headline{font-size:17px;font-weight:600;color:#1a1816;
padding-bottom:12px;margin-bottom:14px!important;
border-bottom:1px solid rgba(26,24,22,0.12)}
.fn-headline em{font-style:italic;color:#2c4a3a}
/* :target — the linked-to footnote gets a warm cream flush */
.footnotes li:target{background:#e8dfd0;border-radius:4px;
padding-left:14px;padding-right:14px;margin:0 -14px}
.footnotes li:target .fn-headline{border-bottom-color:rgba(44,74,58,0.22)}
/* Back-link */
.fn-back{font-family:ui-monospace,'SF Mono',monospace;font-size:12px;
color:#5a544d;text-decoration:none;
border-bottom:1px solid rgba(26,24,22,0.22);margin-left:6px;
font-style:normal}
.fn-back:hover{color:#2c4a3a;border-bottom-color:#2c4a3a}
// Smooth-scroll to footnote on marker click; update hash so :target CSS fires.
document.querySelectorAll('sup a[href^="#fn"]').forEach(function(a) {
a.addEventListener('click', function(e) {
e.preventDefault();
var id = this.getAttribute('href').slice(1);
location.hash = id; // triggers :target highlight
var el = document.getElementById(id);
if (el) el.scrollIntoView({behavior: 'smooth', block: 'start'});
});
});
// Smooth-scroll back to inline reference on back-link click.
document.querySelectorAll('.fn-back').forEach(function(a) {
a.addEventListener('click', function(e) {
e.preventDefault();
var id = this.getAttribute('href').slice(1);
location.hash = id;
var el = document.getElementById(id);
if (el) el.scrollIntoView({behavior: 'smooth', block: 'center'});
});
});
The two-signature system
Two semantic signals do the emphasis work — each carries a distinct register, and they're meant to be rationed:
Red italic <em> carries the through-line: the accent colour (#2c4a3a) on a phrase that runs across the argument, and the one-word keyword in the collapsed summary. It's the note's identity.
Bold <strong> picks out the single term under the lens in a given paragraph — the word the reply is examining right now. It's the note's focus.
Nested <em><strong> for bold-red: a word that is simultaneously the through-line and the examined term — the pivot at which argument and annotation meet.
The discipline is one <strong> per paragraph maximum. If every third word is picked out, nothing is — the signal relies on scarcity.
When it breaks
Two-word creep. The discipline is one keyword per footnote. A tight two-word term (clean exits) is the ceiling, not the target. Let the handle grow and the collapsed list stops being an index.
Bold everywhere. If every other word is picked out in <strong>, nothing is. The pick-out only works rationed to the one term that matters in that paragraph.
Orphan keyword. If the summary word never appears in the carried-in headline, the closed and open states stop agreeing. The headline must land on the same word as the collapsed handle.
Dropped back-link. Without a .fn-back link, the reader who expands a note has no cheap route back to where they were in the body text — the footnote becomes a dead-end.
Where it applies
Use on long-form editorial pieces — happiness.gf.cx/behaviour/ articles are the canonical home — where the author wants to answer reader questions without pulling the reader out of the spine.
Use when annotations have a single identifiable keyword: the note is answering a question, defining a term, or examining a phrase the body uses without explaining.
Skip when every paragraph has three markers: at that density you need a sidebar or a separate page, not a foot-anchored list.
Skip when the notes are pure citations with no prose body — a standard numbered reference list is simpler and more familiar for that job.
Reusable elements
The named, copyable pieces — lift any one without the others:
Superscript marker pair — <sup><a href="#fnN" id="fnrefN">N</a></sup> in the body; id="fnN" on the list item. Bidirectional: the id on the ref is the back-link's target.
Carried-in headline — <p class="fn-headline"> as the first element of each footnote body; carries the full title that was too long for the collapsed summary. Must end on the same keyword as the summary word.
One-keyword summary — the collapsed row is just the muted label + a single italic keyword. Every keyword on the page is unique — it is the footnote's handle and memory hook.
:target highlight — scroll-margin-top + background transition on li:target; no JS required for the visual state, only for smooth scrolling.
Two-signature emphasis — red <em> for through-line, bold <strong> for the examined term, nested <em><strong> for bold-red pivot. All three copy cleanly to any editorial surface.
Back-link — <a href="#fnrefN" class="fn-back">↩ back</a> at the close of each note body; monospace, muted, right of the last sentence.
Reference
Source
Dan, 2026-06-22 — named and formalised while converting behaviour/scorched-earth-game-plays-out/ to the pattern.