Remove decisions/ section; absorb language note into index

docs/decisions/content-location.md

@@ -1,42 +0,0 @@
-# Content Location (resolved)
-
-!!! success "Resolved"
-    Option A was implemented. Content lives in `pages/` and `blog/` at the container repo root. Astro loads them via glob loaders with `base: '../pages'` and `base: '../blog'`. Vite is configured with `server.fs.allow: ['..']`.
-
----
-
-This document records the design question that was open during early development and the options considered.
-
-## The question
-
-Where should wiki content (the `.md` files the community edits) live, and how should Astro load them?
-
-The constraint: Astro's rendering engine lives in the `site/` submodule (`brutsalvadi/astro-bloomz`). Content is wiki-specific and should not be committed to the engine's history.
-
-## Why symlinks failed
-
-Symlinking `bincio_wiki/pages/` → `site/src/content/entries/` was tried and abandoned. macOS's `fsevents` (used by Vite's file watcher) does not follow symlinks reliably, causing Astro's hot-reload and content layer to miss changes or crash in dev mode.
-
-## Options considered
-
-**Option A — Astro glob `base` pointing outside `site/`** ✓ *chosen*
-
-```ts
-loader: glob({ pattern: '**/*.md', base: '../pages' })
-```
-
-`../pages` relative to `site/` resolves to `bincio_wiki/pages/`. No symlinks. Content stays in the container repo. Vite's `server.fs.allow: ['..']` is required to permit serving files outside the project root in dev.
-
-**Option B — Copy/sync at dev time**
-
-Keep source at `bincio_wiki/pages/`. Add a watcher step to `dev.sh` that syncs changes to `site/src/content/entries/` (gitignored there). Edit server already uses `WIKI_PAGES_DIR`.
-
-Downside: two-directory sync is extra moving parts; a crash means stale content.
-
-**Option C — Absorb Astro into `bincio_wiki`**
-
-Remove the submodule. Move Astro source into `bincio_wiki/src/`. Cleanest at runtime but loses the reusable engine submodule.
-
-## Outcome
-
-Option A works correctly. Both Vite's file watcher and Astro's content layer see changes to `pages/` and `blog/` in dev. The `contentDeleteWatcher` plugin handles the edge case of deleted files (which require clearing the data store to prevent stale entries).

docs/decisions/lingua.md

@@ -1,31 +0,0 @@
----
-title: Lingua e Internazionalizzazione
----
-
-# Lingua e Internazionalizzazione
-
-Questo wiki è principalmente in italiano. Di seguito le opzioni valutate e la decisione presa.
-
-## Opzioni considerate
-
-### A — Solo italiano (1–2 ore)
-Sostituire le ~8 stringhe di interfaccia in inglese con italiano. Tutto il contenuto viene scritto in italiano. Nessun cambiamento strutturale.
-
-### B — Italiano di default, lingue miste tolerate (zero effort)
-Il wiki è una raccolta piatta di pagine: chi scrive in italiano lo fa, chi vuole contribuire in inglese può farlo. I `[[WikiLink]]` funzionano per nome file indipendentemente dalla lingua del contenuto. Opzione adottata per ora.
-
-### C — Bilingue completo `/it/` e `/en/` (1–2 giorni di sviluppo)
-Astro 6 supporta l'i18n routing nativo. Richiederebbe:
-- Dividere `pages/` in `pages/it/` e `pages/en/`
-- Aggiornare la content collection e la generazione degli URL
-- Aggiungere un selettore di lingua nella nav
-- Decidere come i `[[WikiLink]]` attraversano i confini linguistici
-- Un indice semtree per lingua o condiviso
-
-Il punto 4 è quello genuinamente complesso: il sistema wikibonsai non ha una risposta standard per i link cross-language.
-
-## Decisione attuale
-
-**Opzione B.** Si scrive in italiano. Se il wiki cresce e serve un mirror curato in inglese, si migra a C. La migrazione da B a C è breaking (gli URL cambiano), ma gestibile quando ci sarà abbastanza contenuto da motivarla.
-
-Le stringhe dell'interfaccia possono essere tradotte in italiano in 30 minuti, indipendentemente dal resto.

docs/index.md

@@ -7,6 +7,7 @@ BincioWiki is a private, invite-only wiki for the Bincio group of friends. It is
 - **Shared identity.** Authentication is shared with `bincio_activity` via a single SQLite database. One account, two apps, one session cookie.
 - **Client-side auth enforcement.** The HTML is publicly served by nginx; JavaScript redirects unauthenticated users to `/login/`. This is an intentional tradeoff — the content is community memories, not financial data, and the goal is keeping crawlers and casual visitors out, not resisting determined attackers.
 - **Self-hosted on a cheap VPS.** Everything runs on a single Hetzner Debian 12 VPS.
+- **Italian by default.** Content is written in Italian. Mixed-language pages are tolerated; there is no i18n routing.
 
 ## Repository structure
 

mkdocs.yml

@@ -15,9 +15,6 @@ nav:
     - Daily operations: deployment/operations.md
   - Development:
     - Getting started: development/getting-started.md
-  - Design decisions:
-    - Language / i18n: decisions/lingua.md
-    - Content location: decisions/content-location.md
 
 theme:
   name: material