Architecture
Starlight on Astro
Section titled “Starlight on Astro”The site is a Starlight project built with
Astro 6 and deployed as a Cloudflare Worker (adapter: cloudflare(...) in
astro.config.mts; wrangler.jsonc serves the built ./dist via the ASSETS
binding). Content is authored in MDX under src/content/docs/.
Plugins
Section titled “Plugins”Configured in astro.config.mts:
starlight-sidebar-topics— the top-level topic switcher (Technology / Business). Each topic defines its own sidebar tree.starlight-theme-rapide— the visual theme.starlight-llms-txt— generates anllms.txtso the docs are LLM-friendly.astro-mermaid— Mermaid diagrams in fenced```mermaidblocks (theme: "forest",autoTheme: true— follows light/dark).- Tailwind CSS v4 via
@tailwindcss/vite+@astrojs/starlight-tailwind; theme tokens (Inter / IBM Plex Mono, indigo accent, zinc gray) are set insrc/styles/global.css.
Content structure
Section titled “Content structure”Two topics, defined in the starlightSidebarTopics([...]) call:
| Topic | Sidebar built from |
|---|---|
| Technology | Services (autogenerated per directory) + Infrastructure (explicit) |
| Business | Standups + autogenerated sprint-plans / business-development |
The Services groups use autogenerate: { directory: "technology/services/<svc>" },
so Starlight builds each service’s sidebar automatically from the .mdx files in
its folder — ordered by the sidebar.order frontmatter.
Custom components
Section titled “Custom components”src/components/:
ServiceInfo.astro— the header block at the top of each service Overview. Props:repo(GitHuborg/name), optionalurl, andtools(an array of slugs rendered as icons fromdevicons.railway.com).StandupTable.astro— renders a standup table from a{ date, note, summary }[]prop.