How this site is built

The rule

Every requirement on the page is copied from one of two public NASA documents, and each figure carries a tag saying which:

TagSourceUsed for
T1 to T4, §IIISCaN, Lunar Communications, PNT and Observability Industry Demand Signal, August 28, 2026Talk, Navigate, See, Build, the globe
UG + pageMoon Base User's Guide: Architecture Resources, April 2026Phase goals, Traffic, the Phase 1 comms targets, open problems, The base it serves, partnership areas

Where the two documents give different kinds of numbers for the same thing, the page shows both side by side and does not reconcile them. The clearest case: the guide's Phase 1 target of more than 500 Mbps is a capability target, while the SCaN table's 50 Mbps in 2028 is a demand forecast.

Where a lay reader needs a yardstick, the page offers one, but those are mine and are tagged mine in a dashed box: gigabit home fiber, an Olympic pool, how far light travels in a microsecond, and the illustrative rocks in the pixel demo. Nothing else is interpreted, projected or filled in.

One switch, every number

The paper is built around NASA's three Moon Base phases, and every table has the same three columns. The User's Guide uses the same three phases. So all of the data lives in a single file, assets/data.js: one object per phase from SCaN, and a second block for the guide. The phase switch at the bottom of the screen broadcasts the selected phase, and each section redraws itself from that object. If NASA revises the paper, one file changes.

Phase 2 is the one wrinkle. Table 2 splits it into 2030 and 2032 for throughput and user counts, so those values are stored as lists of milestones, and the page shows both.

The globe

The Moon is a three.js sphere with a texture from Solar System Scope (CC BY 4.0, based on NASA LRO data), using the same latitude and longitude convention as the companion GRAIL site. The camera circles below the South Pole.

ElementStatusWhy
Service region, latitude −84° to −90°To scaleTable 1. A spherical cap on the Moon's surface.
Region altitude, 125 km then 200 kmTo scaleTable 1. The cap is lifted to 1 + altitude ÷ 1,737.4 km lunar radii.
Number of surface sitesFrom the paperTable 1. Phase 3 says "3 to 5+", drawn as five.
Where the sites sitSchematicThe paper gives no coordinates.
Relay orbits and relay countSchematicThe paper sets coverage targets, not a constellation. It says early Phase 1 has fewer than the four relays navigation needs, so Phase 1 shows two.

The relay orbits are ellipses with their slow, high end over the southern hemisphere, and the satellites move by Kepler's equation, so they really do dawdle there. A link line is drawn only when a relay is above a site's horizon. The "To Earth" line points at the near side, since the Moon always keeps one face toward us.

The sharp close-up. Flat global Moon maps stretch badly at the poles, so the close-up swaps in the LRO camera team's South Pole mosaic (LROC Wide Angle Camera, NASA/GSFC/Arizona State University, Speyerer et al. 2020). It is published in polar stereographic projection at about 474 m per pixel. The site crops it to 20° from the pole, and each point of a cap over the pole gets its image position from the same projection formula, so craters land exactly where the global map puts them. The outer edge fades into the global map, and the image only downloads the first time someone opens the close-up.

Smaller pieces

Pixel demo. A 2 m patch of ground with two rocks is rendered at 1 cm, then each output pixel takes the average of its block, the way a real sensor sees. At 50 cm the whole 2 m patch is only sixteen pixels and even the 1 m boulder is a dark blur. At 25 cm it is sixty-four pixels and the boulder starts to hold its outline.

Revisit strips. One week, 168 hours, with a tick per pass. At a 3 hour revisit that is 56 ticks, at 1.5 hours 112, at 48 hours four, one pass every two days.

Traffic. Payload bars share one scale, so Phase 1's ~4,000 kg is a sliver next to Phase 3's ~150,000 kg. The "times Phase 1" figure in the callout is plain division of the guide's rounded numbers.

Navigation circles. Drawn in metres on one SVG coordinate system, so the 50, 25 and 10 m rings and the pool share a true scale.

Design

The site borrows NASA's design practice, not NASA's brand. The typefaces are the three nasa.gov uses: Inter for headlines, Public Sans for reading and DM Mono for numbers, so every figure reads like an instrument readout. The palette follows nasa.gov's carbon grays, with one red used only for the phase you are in and the surface sites, and blue for data and links. No NASA insignia, logotype or wordmark appears anywhere.

One element is allowed to be bold: the phase rail under the header, a real timeline whose segments are as wide as the years they cover. Everything else is separated by rules and space instead of boxes.

Accessibility follows the standard federal sites are held to, WCAG 2.1 AA: a skip link, header, main and footer landmarks, a phase switch you can drive with the arrow keys or the 1, 2 and 3 keys, 44 pixel touch targets, visible focus, text contrast checked in both themes, and no motion when your system asks for less.

Stack

The source is on GitHub under the MIT License. Built with Claude Code; the research design, verification and editorial decisions are mine, and every figure was checked against the source PDFs. Plain HTML, CSS and JavaScript. No framework, no build step, no tracking beyond Vercel Web Analytics. Fonts are self-hosted, so pages make no requests to Google, and three.js loads only when the globe comes into view. three.js is vendored locally. Dark and light themes, ?phase=2 deep-links a phase, keys 1 to 3 switch phases, and motion stops when your system asks for reduced motion.

What this is not

An independent explainer, not affiliated with, produced by, or endorsed by NASA. It summarizes only these two public documents, and it is not advice for anyone bidding on the work it describes.

For a longer, plain-language walk through the paper and this build, read the article.

Back to the site