src/pages/

Responsibility

Implements the file-based routing layer for the Astro 6 static site. Each .astro file or subdirectory maps to a URL path segment, producing fully static HTML at build time via getStaticPaths for dynamic routes and direct rendering for static ones. trailingSlash: "always" is enforced at the framework level.

Design

Routes are grouped by feature into subdirectories, each containing index.astro for the listing page and, where applicable, [slug].astro for detail pages. Three content-driven dynamic routes use getStaticPaths to pre-render all entries from content collections. One API endpoint (robots.txt.ts) returns a plain-text response.

Route inventory (15 files, 16 routes):

Dynamic route patterns:

• produktionen/[slug].astro — Uses getCollection("productions"), filters out hidden entries (t.data.hidden !== true), and renders each through the MDX Content component with ProductionsLayout injected as a named component. Also loads getCollection("people") to build a peopleById lookup map passed via props.
• news/[slug].astro — Uses getPublishedNewsEntries() (which wraps getCollection("news") with draft filtering), serves entries in reverse chronological order, and passes previousEntry/nextEntry for pagination links. Renders MDX content with a suite of custom components (NewsImage, NewsSeparator, NewsSplitLayout, NewsText, NewsMaxWidth, NewsButtonLink, ButtonGroup).
• mitwirkende/[slug].astro — Uses getCollection("people") and getCollection("productions"), derives each person’s participations via buildParticipationsByPerson(), renders MDX with PeopleLayout injected.

Flow

1. Static pages — Astro reads the .astro file frontmatter at build time, executes the script block (importing layouts, components, and inline data), and renders the template to a static HTML file at the corresponding directory path (e.g., /produktionen/index.html → served at /produktionen/).
2. Dynamic pages — getStaticPaths is invoked at build time. It queries content collections via getCollection() / getPublishedNewsEntries(), maps each entry to { params: { slug }, props }, and Astro generates one HTML file per entry. The page script receives Astro.props, renders the MDX Content via await render(entry), and wraps it in a layout.
3. API route — robots.txt.ts exports a GET function that returns a Response with Content-Type: text/plain, dynamically inserting the sitemap URL from the site config.
4. Layout hierarchy — All routes wrap in BaseLayout (provides HTML shell, SEO meta, JSON-LD, Google Fonts, analytics bootstrap, and dark-mode safeguard). Production detail routes additionally inject ProductionsLayout as an MDX wrapper component; contributor detail routes inject PeopleLayout. Legal-content pages (impressum, datenschutz) use ContentPageShell for prose spacing.
5. React islands — Two pages hydrate client-side React components:
   • /tickets/ → <TicketShopIframe client:load /> (oeticket iframe embed)
   • /news/abo/ → <NewsletterFormBlock client:load /> with <Toaster client:idle /> Both use client:load / client:idle directives; no SSR ISR involved.

Integration

All routes depend on BaseLayout (@/layouts/BaseLayout.astro) for the outer HTML document. Feature-specific layouts/components are imported per route as shown below.

Content collections (defined in src/content.config.ts):

• productions — MDX, schema includes title, hidden, promotion, dates (discriminated union: hidden/range/multiRange/distinct), duration, logo, summary, images, participants (with people references), sponsors (references), songlist, legacyShowId, pressFiles, pressImages.
• news — MDX, schema includes title, description, date, heroImage, heroImageAlt, draft.
• people — MDX, schema includes firstName, lastName, profileImage. Used by productions via reference("people").
• sponsors — YAML, schema includes title, url, logoType, logo. Referenced by productions.