AstralPass Docs

Documentation site for AstralPass, built with Astro Starlight and intended for deployment on Cloudflare Pages.

Domain

Production domain:

• https://docs.astralpass.com

Stack

• Astro
• Starlight
• static output for Cloudflare Pages

Project structure

.
├── public/
│   ├── brand/                 # public favicon, background, and brand assets
│   └── fonts/                 # website font files reused by the docs theme
├── src/
│   ├── assets/                # Astro-managed images (used by Starlight config)
│   ├── content/
│   │   └── docs/              # documentation content
│   │       ├── core/
│   │       ├── star-atlas/
│   │       └── index.mdx
│   ├── pages/
│   │   └── 404.astro          # custom 404 page
│   └── styles/
│       └── custom.css         # brand-level Starlight overrides
├── astro.config.mjs
└── package.json

Main sections

Core

• About AstralPass
• Getting Started
• Linking Wallets
• Hardware Wallets
• Discord Roles
• Solo Players
• Troubleshooting
• FAQ

Star Atlas

• Why AstralPass for Star Atlas
• Player Profiles
• What Is a DAC?
• Joining a DAC On-Chain
• DAC Membership and Discord Roles
• Glossary

Commands

npm install
npm run dev
npm run build
npm run preview

Notes

• The site URL is configured as https://docs.astralpass.com in astro.config.mjs.
• Starlight's site logo uses an Astro-managed asset from src/assets/.
• Public brand files remain in public/brand/ for direct URL use on pages like the home hero and the custom 404.
• Website font files are mirrored into public/fonts/ so the docs theme can reuse the same MicrogrammaExt and Orbitron faces as the main AstralPass site.
• The logo currently exists in both src/assets/ and public/brand/ on purpose because Starlight config needs an Astro-managed image while page-level direct URLs are simpler from public/.
• Copy should stay practical and user-facing. Avoid turning end-user docs into internal architecture notes.