Links

Every route on this site is a root-relative path (Astro handles the routing), built from where the entry's .mdx file actually sits under src/content/<class>/. A standalone entry with no file subfolder gets a clean single-segment URL, e.g./entities/furniture-crab; an entry that lives in its own subfolder (because it shares one with Variants/POIs, or just because you put it there) gets an extra segment from that folder, e.g. /landscapes/the-lobby/the-lobby. Check the entry's own frontmatter/file path if you're not sure which shape its URL takes — don't guess. Linking to a page in the same MDX file (a jump link) still just uses a #id hash.

Internal link (to another entry)

Swap in the real path for whichever entry you're linking to:

<a href="/landscapes/your-entry-slug">Entry Title</a>

<!-- or, in Markdown: -->
[Entry Title](/landscapes/your-entry-slug)

External link (opens in a new tab, safely)

<a href="https://example.com" target="_blank" rel="noopener noreferrer">External Source ↗</a>

Jump link (to a heading on the same page)

<a href="#help-internal-link">Jump to the Internal Link example above</a>

Footnotes

A numbered reference in the text that jumps down to a citation, with a "↩" link back up to where you came from. No JavaScript — just matching id attributes and anchor links, plus the smooth scroll every jump link on this site already gets from scroll-behavior: smooth in the global stylesheet. Put the <ol class="footnotes"> near the end of the article, after Addenda.

The lights are original 1973 fixtures<sup class="footnote-ref"><a href="#fn-1" id="fnref-1">[1]</a></sup>, though this has never been independently verified.

<!-- near the end of the article, after Addenda -->
## Footnotes
<ol class="footnotes">
  <li id="fn-1">Based on manufacturer stamps found on recovered ballasts. <a href="#fnref-1" class="footnote-back">↩</a></li>
</ol>