⚠ THE INFORMATION RECORDED ON THESE PAGES IS NOT PRESENT IN THIS WORLD ⚠

The Liminal Archives

An artificial database of liminal spaces, anomalous entities, and the people who never made it back.

Reference

Getting Started

Help is organized like a Landscape family — use the sidebar on the left to jump between topics instead of scrolling one long page. Every block on every topic page is copy-paste ready: hit "Copy" to grab the exact markup, then paste it into an entry's MDX body and edit the text. Everything here works with just the global stylesheet linked — sliders, collapsibles, and censor bars need no JavaScript at all (beyond the one shared site.js already linked on every page).

Registering a New Entry

A class listing page (Landscapes, Entities, Groups, Phenomena) never needs hand-written cards. It calls getPrimaryEntries() (see src/lib/entries.ts), which queries every file in that collection's src/content/<class>/ folder — filtered to exclude Variants/POIs — and the page maps the results straight into cards. Add one new file and the entry appears on its listing page and joins the "Random Entry" rotation, both automatically. To create one:

  1. Copy templates/entry-template.mdx (repo root) into src/content/landscapes/, entities/, groups/, or phenomena/.
  2. Rename it to the entry's slug, e.g. the-wanderers-guild.mdx.
  3. Fill in its frontmatter and write the body in Markdown/MDX below the ---.
---
title: "The Wanderers' Guild"
tag: "Group · Faction"
description: "One-sentence teaser shown on its card."
featured: false                # true also hand-picks it for the homepage
dangerLevel: 2                 # every infobox field below is optional —
dangerLabel: "Uncertain"       # only the ones you set actually render
---

Regular Markdown/MDX body goes here.

Variants and POIs never go in as their own listing-page entry — seeRelated-Entries Sidebar for how those work instead.

Classification Badges

The badge at the top of every entry is driven by which collection folder the file lives in — the page template for that collection sets the right type-* modifier automatically. These are the five:

Class: LandscapeClass: EntityClass: Object
Class: GroupClass: Phenomenon
<span class="article-classification type-landscape">Class: Landscape</span>
<span class="article-classification type-entity">Class: Entity</span>
<span class="article-classification type-object">Class: Object</span>
<span class="article-classification type-group">Class: Group</span>
<span class="article-classification type-phenomenon">Class: Phenomenon</span>