Replace all marketing placeholder content with real MYeasyCMS content

- Logo: Replace generic Makerkit SVG with MYeasyCMS branded logo (grid icon + styled text)
- Blog: Replace 3 SaaS placeholder posts with 5 real articles (Vereinsverwaltung, SEPA, Website, DSGVO, Mitglieder-Tipps)
- Changelog: Replace 6 generic entries with real feature announcements (Verbandsverwaltung, Fischerei, Dateien, Kurse, Einladungen, i18n)
- Documentation: Rewrite all 20 docs from Makerkit references to MYeasyCMS content
- FAQ: Replace 6 generic SaaS questions with 10 real MYeasyCMS questions
- Navigation: Replace Changelog link with Contact in main nav
- Footer: Reorganize into Product/Company/Legal sections
- Translations: Update all EN marketing strings to match real Com.BISS content

apps/web/content/documentation/authentication/configuration.mdoc

@@ -1,55 +1,28 @@
 ---
-title: "Configuration"
-description: "Learn how authentication works in MakerKit and how to configure it."
+title: "Anmeldung konfigurieren"
+description: "Login-Optionen und Sicherheitseinstellungen in MYeasyCMS konfigurieren."
 publishedAt: 2024-04-11
 order: 1
 status: "published"
 ---
 
-The way you want your users to authenticate can be driven via configuration.
+MYeasyCMS bietet verschiedene Anmeldemethoden, die vom Administrator konfiguriert werden können.
 
-If you open the global configuration at `src/configuration.ts`, you'll find
-the `auth` object:
+## E-Mail und Passwort
 
-```tsx title="configuration.ts"
-import type { Provider } from '@supabase/gotrue-js/src/lib/types';
+Die Standard-Anmeldung erfolgt mit E-Mail-Adresse und Passwort. Passwörter müssen eine Mindestlänge von 8 Zeichen haben und sollten Groß- und Kleinbuchstaben sowie Zahlen enthalten.
 
-auth: {
-  requireEmailConfirmation: false,
-  providers: {
-    emailPassword: true,
-    phoneNumber: false,
-    emailLink: false,
-    oAuth: ['google'] as Provider[],
-  },
-}
-```
+## Passwort zurücksetzen
 
-As you can see, the `providers` object can be configured to only display the
-auth methods we want to use.
+Benutzer können ihr Passwort über die "Passwort vergessen"-Funktion zurücksetzen. Ein Link zur Passworterstellung wird per E-Mail zugesandt.
 
-1. For example, by setting both `phoneNumber` and `emailLink` to `true`, the
-authentication pages will display the `Email Link` authentication
-and the `Phone Number` authentication forms.
-2. Instead, by setting `emailPassword` to `false`, we will remove the
-`email/password` form from the authentication and user profile pages.
+## Multi-Faktor-Authentifizierung
 
-## Requiring Email Verification
+Für zusätzliche Sicherheit kann MFA aktiviert werden. Unterstützt werden:
 
-This setting needs to match what you have set up in Supabase. If you require email confirmation before your users can sign in, you will have to flip the following flag in your configuration:
+- **Authenticator-Apps** — Google Authenticator, Authy oder vergleichbare TOTP-Apps
+- **Passkeys** — Biometrische Anmeldung über Fingerabdruck oder Gesichtserkennung
 
-```ts
-auth: {
-  requireEmailConfirmation: false,
-}
-```
+## Sitzungsdauer
 
-When the flag is set to `true`, the user will not be redirected to the onboarding flow, but will instead see a successful alert asking them to confirm their email. After confirmation, they will be able to sign in.
-
-When the flag is set to `false`, the application will redirect them directly to the onboarding flow.
-
-## Emails sent by Supabase
-
-Supabase spins up an [InBucket](http://localhost:54324/) instance where all the emails are sent: this is where you can find emails related to password reset, sign-in links, and email verifications.
-
-To access the InBucket instance, you can go to the following URL: [http://localhost:54324/](http://localhost:54324/). Save this URL, you will use it very often.
+Anmeldesitzungen laufen nach einer konfigurierbaren Zeitspanne ab. Benutzer werden automatisch abgemeldet, wenn sie längere Zeit inaktiv sind.