feat: hidden pages

GEMINI.md

@@ -1,11 +1,11 @@
 # Project Context: Schreifuchs.ch
 
 ## Overview
+
 This project is a personal portfolio website for "Schreifuchs", featuring sections for Photography (Fotos), Informatics (Informatik), Music (Musig), and Video. It is currently being transitioned from a static site to a dynamic Node.js site powered by Nextcloud via WebDAV.
 
-- [Nextcloud Integration Plan](./TODO_NEXTCLOUD.md)
-
 ## Tech Stack
+
 - **Framework:** Svelte 5 (using Runes) & SvelteKit
 - **Language:** TypeScript
 - **Styling:** Tailwind CSS (with custom text-shadow plugin)
@@ -14,6 +14,7 @@ This project is a personal portfolio website for "Schreifuchs", featuring sectio
 - **Markdown:** `@ts-stack/markdown` for content rendering
 
 ## Directory Structure
+
 - `src/routes/`: File-based routing.
   - `src/routes/fotos`, `informatik`, `musig`, `video`: Feature-specific pages.
 - `src/lib/`: Shared utilities and components.
@@ -23,12 +24,13 @@ This project is a personal portfolio website for "Schreifuchs", featuring sectio
   - Contains Markdown content files (`Fotos.md`, etc.) and their associated attachments.
 
 ## Key Conventions
+
 - **Svelte 5:** Use Runes (`$state`, `$derived`, `$props`, etc.) for reactivity.
 - **Styling:** Use Tailwind utility classes. The font family is configured to 'Outfit'.
-- **Content:** Content is largely driven by Markdown files located in `static/` which are fetched and parsed.
-- **Static Generation:** The site is built as a static site outputting to the `build/` directory.
+- **Content:** Content is largely driven by Markdown files located on Nextcloud which are fetched and parsed.
 
 ## Development Scripts
+
 - `npm run dev`: Start development server.
 - `npm run build`: Build for production.
 - `npm run check`: Run Svelte and TypeScript checks.
@@ -59,4 +61,5 @@ You MUST use this tool whenever writing Svelte code before sending it to the use
 ### 4. playground-link
 
 Generates a Svelte Playground link with the provided code.
-After completing the code, ask the user if they want a playground link. Only call this tool after user confirmation and NEVER if code was written to files in their project.
+After completing the code, ask the user if they want a playground link. Only call this tool after user confirmation and NEVER if code was written to files in their project.
+