Orbitope — orbitope.com

The Orbitope landing page. A single self-contained index.html — all styles, scripts, the logo (inline SVG), and the favicon are embedded. Fonts load from Google Fonts. No build step, no dependencies.

Deploy to GitHub Pages

1. Create a new repository named orbitope.github.io (replace orbitope with your GitHub username/org — for the org account it's literally orbitope.github.io).
2. Upload index.html and .nojekyll to the repo root.
3. Repo → Settings → Pages → Source: Deploy from a branch → Branch: main / folder: / (root) → Save.
4. Live at https://orbitope.github.io within ~60 seconds.
5. Custom domain: the CNAME file in this repo points Pages at orbitope.com (also set under Settings → Pages → Custom domain). That is the canonical host — orbitope.github.io still resolves and redirects there, but every in-page link, the og:url, and the footer use orbitope.com. Project sites live beneath it as orbitope.com/<repo>/.

Editing

• Links — search index.html for github.com and the mailto: to update destinations. The YouTube, X, and Instagram buttons were removed while those accounts are empty; the .link-btn styling still supports them, so adding one back is a matter of pasting the anchor into .links.
• Tagline / description — the .tagline and .desc elements near the bottom of the <body>.
• Projects — two section.projects blocks split by read-vs-do: Interactive Explorations (things you read, that happen to run in the browser — the interactive articles and explainers, including Leyline, Signal, and Simulacrum) and Projects (things you play or use — Parlance headlined, then the tools and games). Each owns its own .project-grid; copy a .project block into whichever grid fits. A project can list its own writeup as an entry (Parlance links its validation article that way, Leyline links its map article).
• Colors — the :root block at the top of the <style> (Palette B: charcoal + amber + steel).

Project list layout

.project-grid owns the layout; .project makes no assumptions about its own width. To go from a two-column grid to a single-column list, change one line:

grid-template-columns: repeat(auto-fill, minmax(min(360px, 100%), 1fr));  /* grid */
grid-template-columns: 1fr;                                              /* list */

Keep the min(360px, 100%) wrapper. A bare minmax(360px, 1fr) outweighs the container on narrow screens and scrolls the page sideways on a phone.

Project pages live in their own repos

Each project's article/site is served from its own repo via GitHub Pages, not from here — see Orbitope/pushman (main:/docs) and Orbitope/RLevator (main:/docs). This repo only holds the landing page that links to them.

Articles hosted directly here: leyline/, parlance-validation/, and codenames-clue-generator/ are full articles hosted in this repo (served at orbitope.com/leyline/, orbitope.com/parlance-validation/, etc.). They carry their own index.html + og.png and the same GA tag, meta/OG block, and shared a11y/engagement scripts as the sibling articles.

GitHub Pages project paths are case-sensitive. The path segment must match the repo name exactly: /RLevator/ resolves, /rlevator/ returns a 404 with no redirect attempt. (Confusingly, repo URLs on github.com are case-insensitive.) The rlevator/ directory here is a redirect stub that catches the lowercase spelling; /RLevator/ stays canonical.

Discoverability

Every article lives in its own repo under this one domain, so nothing crawls from the landing page to all of them unaided and there is no generator here to emit a sitemap. Both files are hand-maintained:

• sitemap.xml — one <url> block per published page. Paths are case-sensitive: /RLevator/ is canonical and /rlevator/ is only a redirect stub, so the stub is deliberately not listed.
• robots.txt — allow all, and points at the sitemap.

Adding an article means a <url> block here and an entry in tools/og-card/articles.json.

Each article page carries an absolute og:image, og:url, rel=canonical, twitter:card, and JSON-LD Article schema. Social scrapers reject relative image URLs — that is not a style preference.

Files

File	Purpose
index.html	The landing page — the entire site.
sitemap.xml	Hand-maintained; every published page.
robots.txt	Allow-all, points at the sitemap.
og.png	The landing page's own social card.
tools/og-card/	Generates every article's social card.
rlevator/index.html	Lowercase redirect to canonical /RLevator/.
.nojekyll	Tells GitHub Pages to serve files as-is.