47bd4bf53f
Astro's sitemap integration emits /sitemap-index.xml + /sitemap-0.xml. Bing Webmaster Tools and IndexNow probe /sitemap.xml literally, so a request for the canonical name was 404'ing. Two changes: - astro.config.mjs: add a 301 redirect /sitemap.xml → /sitemap-index.xml (alongside the existing / → /en/ redirect) - public/robots.txt: list both Sitemap URLs so any crawler that reads robots.txt finds an entry it can use directly After production redeploys (`docker compose up -d --build`), submit https://nibiru-framework.com/sitemap.xml in Bing Webmaster Tools — it'll follow the 301 and ingest the index. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Starlight Starter Kit: Basics
npm create astro@latest -- --template starlight
🧑🚀 Seasoned astronaut? Delete this file. Have fun!
🚀 Project Structure
Inside of your Astro + Starlight project, you'll see the following folders and files:
.
├── public/
├── src/
│ ├── assets/
│ ├── content/
│ │ └── docs/
│ └── content.config.ts
├── astro.config.mjs
├── package.json
└── tsconfig.json
Starlight looks for .md or .mdx files in the src/content/docs/ directory. Each file is exposed as a route based on its file name.
Images can be added to src/assets/ and embedded in Markdown with a relative link.
Static assets, like favicons, can be placed in the public/ directory.
🧞 Commands
All commands are run from the root of the project, from a terminal:
| Command | Action |
|---|---|
npm install |
Installs dependencies |
npm run dev |
Starts local dev server at localhost:4321 |
npm run build |
Build your production site to ./dist/ |
npm run preview |
Preview your build locally, before deploying |
npm run astro ... |
Run CLI commands like astro add, astro check |
npm run astro -- --help |
Get help using the Astro CLI |
👀 Want to learn more?
Check out Starlight’s docs, read the Astro documentation, or jump into the Astro Discord server.