GDAM web

The public gdam.dev site: one static Astro page describing GDAM, the Godot Addon Manager.

This is the front door only. The registry application — sign-in, owner pages, addon pages, docs — is a separate app served from app.gdam.dev, and the registry API from api.gdam.dev. Nothing here talks to either: there is no authentication, no application state, no backend and no runtime environment configuration. The page ships no JavaScript, which is why there are no integrations in astro.config.mjs and why CI fails on a <script src> in the build output.

Commands

Command	Action
bun install	Install dependencies
bun dev	Start the Astro development server
bun run build	Generate the static site in dist/
bun preview	Preview the static build

What is on the page, and where it came from

Nothing on the page is invented. Everything traceable to the gdam and gdam-actions repositories is listed here so it can be re-checked when either changes.

The terminal frame is one real session, run end to end against the live registry — init, two adds, a link, then install — and reproduced verbatim. The session is internally consistent on purpose: gdam install prints two lines rather than three because the third addon is linked, and a linked addon has nothing to install.

The only edit is the path prefix. gdam init and gdam link print absolute paths, and the real ones were a scratch directory, so they were re-rooted at ~/code/roguelike/godot_client — consistently, so that ../gd-gesture still resolves to the ~/code/roguelike/gd-gesture the frame shows.

There is no colour in the frame beyond the prompt. That is not restraint, it is accuracy: gdam emits no ANSI codes at all — every line it prints is plain text through fmt.Printf. Syntax-highlighting the output would be drawing a tool that does not exist.

The two JSON files are the ones that session wrote, byte for byte apart from the same path re-rooting. They are the clearest statement of the split worth understanding: @aviorstudio/gd-gesture appears in gdam.json with an empty object because a linked addon has no published version to pin, and the path it actually resolves to appears only in gdam.link.json.

The command table is every command in printUsage in main.go, all nine, not the three that make a good demo. The three environment variables named in the prose — GDAM_SECRET_KEY, GDAM_API_URL, GITHUB_TOKEN — are from the same place.

The workflow snippet is the one in the gdam-actions README, including the reason it is two steps: publish needs the CLI, so it says so plainly rather than failing with gdam: command not found.

The install routes in the closing block are both of the ones the README documents. The hero shows go install rather than the shell installer only because the installer one-liner is 94 characters and would arrive as a horizontally scrolling box in the narrow hero column; the closing block gives it the full width and lists both.

Colour

The palette is the registry's own, taken from what app.gdam.dev already renders: #0f172b ink, #f1f5f9 paper, and #0284c7 for anything actionable. The front door and the thing behind it should look like one site rather than two designs sharing a domain. --sky-deep (#0369a1) is the darkened form for small text on paper, since the lighter blue is a button colour and does not carry body copy.

Fonts are the platform's own. No font is fetched, so no visitor's IP reaches a font CDN and no CSP exception is needed to render the page.

Domain

src/layouts/Full.astro, public/robots.txt and public/sitemap.xml assume https://gdam.dev, and the registry links point at https://app.gdam.dev. That split is the same one ormos uses — apex for the site, app. for the application — and it matches the existing api.gdam.dev.

It is not the layout in production today. gdam-be currently serves the registry application at the apex, so shipping this page to gdam.dev means moving that app to app.gdam.dev first. Until then every registry link here points somewhere that does not answer. The two hosts appear in one constant each (appUrl in src/pages/index.astro, the canonical base in src/layouts/Full.astro) plus robots.txt and sitemap.xml.