diff --git a/.cursor/rules/prompts/update-project-structure-documentation.md b/.cursor/rules/prompts/update-project-structure-documentation.md
new file mode 100644
index 0000000..1b24032
--- /dev/null
+++ b/.cursor/rules/prompts/update-project-structure-documentation.md
@@ -0,0 +1,563 @@
+# Update Project Structure Documentation
+
+## Purpose
+
+This prompt provides comprehensive instructions for updating the complete Project Structure Documentation of the DyingStar repository. Use this when the repository structure has changed significantly or when documentation needs to be refreshed.
+
+## Target Files
+
+The following files must be updated:
+
+1. `Documentation/Guidelines/architecture/FolderStructure.md` - High-level architecture overview
+2. `Documentation/Guidelines/architecture/ProjectTreeFolder.md` - Complete file tree documentation
+3. `Documentation/Guidelines/architecture/FileTypes.md` - File naming conventions (update if new patterns emerge)
+4. `Documentation/Guidelines/architecture/Architecture.md` - Reference links (usually no changes needed)
+
+---
+
+## Prerequisites
+
+Before starting, ensure you have:
+
+- Full context of the repository structure
+- Access to all directories and files
+- Understanding of Next.js 15 App Router architecture
+- Knowledge of the project's tech stack
+
+---
+
+## Step-by-Step Instructions
+
+### Phase 1: Reconnaissance - Explore the Repository
+
+#### 1.1 Scan Root Directory
+
+```
+List and document:
+- Configuration files (.nvmrc, .prettierrc, eslint.config.mjs, etc.)
+- Package management files (package.json, pnpm-lock.yaml)
+- Build & deployment files (Makefile, middleware.ts, docker/, etc.)
+- Documentation files (README.md, LICENSE)
+```
+
+#### 1.2 Scan app/ Directory (Next.js App Router)
+
+```
+Recursively explore:
+- app/ root level files (layout.tsx, error.tsx, sitemap.tsx, etc.)
+- app/[locale]/ structure
+  - Route groups: (landing), (layout), (logged-in)
+  - Parallel routes: @modal
+  - Dynamic routes: docs/[slug]
+  - Special files: globals.css, providers.tsx, manifest.ts
+- For each route segment, document:
+  - page.tsx
+  - layout.tsx
+  - loading.tsx
+  - error.tsx
+  - not-found.tsx
+  - _components/ folders
+```
+
+#### 1.3 Scan src/ Directory (Application Code)
+
+```
+Explore and categorize:
+- src/components/
+  - DS/ (Design System components)
+  - ui/ (shadcn/ui primitives)
+  - svg/ (SVG components)
+  - utils/ (Component utilities)
+
+- src/features/ (Vertical slices)
+  - List each feature folder
+  - Document file patterns (*.tsx, *.type.ts, *.hook.ts, etc.)
+
+- src/hooks/ (Cross-cutting hooks)
+  - List all hook files
+
+- src/i18n/ (Internationalization)
+  - config.ts, routing.ts, navigation.ts, request.ts
+
+- src/lib/ (Libraries & utilities)
+  - actions/
+  - env/
+  - errors/
+  - format/
+  - Individual utility files
+
+- src/types/ (Global types)
+
+- Root level src/ files (middleware.ts, site-config.ts)
+```
+
+#### 1.4 Scan content/ Directory
+
+```
+Document:
+- content/news/en/ - English articles
+- content/news/fr/ - French articles
+- Any other content folders
+```
+
+#### 1.5 Scan public/ Directory
+
+```
+List:
+- public/images/
+- public/assets/
+- Root level SVG/PNG files
+```
+
+#### 1.6 Scan messages/ Directory
+
+```
+Document:
+- Translation files (en.json, fr.json, etc.)
+```
+
+#### 1.7 Scan docker/ & Documentation/ Directories
+
+```
+Docker:
+- Dockerfile.dev
+- Dockerfile.prod
+- docker-compose.yml
+
+Documentation:
+- Guidelines/architecture/
+- Guidelines/ (process docs)
+- Guidelines/pictures/
+```
+
+---
+
+### Phase 2: Update FolderStructure.md
+
+**File:** `Documentation/Guidelines/architecture/FolderStructure.md`
+
+**Structure:**
+
+```markdown
+# Folder Structure
+
+[Introduction paragraph about Next.js 15 App Router architecture]
+
+## Global Structure
+
+[ASCII tree showing top-level folders with brief descriptions]
+
+## 📁 `app/` - Next.js App Router
+
+[Description]
+[ASCII tree of app/ structure]
+[Key Concepts section]
+
+## 📁 `src/` - Application source code
+
+[Description]
+[ASCII tree of src/ structure]
+[Feature-based architecture explanation]
+
+## 📁 `content/` - Editorial content
+
+[Description and purpose]
+
+## 📁 `public/` - Static assets
+
+[Description and access pattern]
+
+## 📁 `messages/` - i18n translations
+
+[Description, structure, and usage example]
+
+## 📁 `docker/` - Containerization
+
+[Description and file listing]
+
+## 📁 `Documentation/` - Internal documentation
+
+[Description and structure]
+
+## TypeScript path aliases
+
+[Configuration from tsconfig.json with usage examples]
+
+## File naming conventions
+
+[Quick reference with links to FileTypes.md]
+
+## References
+
+[Links to Next.js docs and other internal docs]
+```
+
+**Key Requirements:**
+
+- Use emojis (📁) for main sections
+- Keep ASCII trees clean and aligned
+- Include brief but clear descriptions
+- Limit depth to 2-3 levels maximum
+- Focus on HIGH-LEVEL overview, not every file
+
+**Format Example:**
+
+```
+## 📁 `app/` - Next.js App Router
+
+Handles **routing**, **layouts**, and **entry points** of the application following Next.js 15 conventions.
+
+```
+
+app/
+├── 📁 [locale]/ # Internationalized routes (en, fr, etc.)
+│ ├── 📁 (layout)/ # Route group - Static pages
+│ │ └── 📁 pageName/ # Page folder
+│ ├── 📁 @modal/ # Parallel route - Modal system
+│ └── 📁 docs/ # User documentation
+
+```
+
+**Key Concepts:**
+- **Route Groups** `(name)`: Organize without affecting URL
+- **Parallel Routes** `@modal`: Display multiple pages simultaneously
+```
+
+---
+
+### Phase 3: Update ProjectTreeFolder.md
+
+**File:** `Documentation/Guidelines/architecture/ProjectTreeFolder.md`
+
+**Structure:**
+
+```markdown
+# Project Tree - Complete File Structure
+
+[Introduction and link to FolderStructure.md]
+
+---
+
+## 📂 Root Directory
+
+### Configuration Files
+
+[Bullet list of ALL config files with descriptions]
+
+### Package Management
+
+[package.json, pnpm-lock.yaml with descriptions]
+
+### Build & Development
+
+[Makefile, middleware.ts with descriptions]
+
+### Documentation & Legal
+
+[README.md, LICENSE with descriptions]
+
+---
+
+## 📂 app/ — Next.js App Router
+
+[Detailed explanation of routing layer]
+
+### Root Level (app/)
+
+[ASCII tree with ALL files and descriptions]
+
+### Internationalized Routes (app/[locale]/)
+
+[Complete ASCII tree showing EVERY route segment and file]
+
+**Key Concepts:**
+[Explanations of route groups, parallel routes, etc.]
+
+---
+
+## 📂 src/ — Application Source Code
+
+[Introduction]
+
+### src/components/ — Reusable UI Components
+
+[Complete tree showing DS/, ui/, svg/, utils/ with ALL files]
+
+### src/features/ — Business Features
+
+[Complete tree showing each feature folder with its files]
+
+### src/hooks/ — Cross-cutting React Hooks
+
+[List all hook files]
+
+### src/i18n/ — Internationalization Configuration
+
+[List all i18n files]
+
+### src/lib/ — Libraries and Utilities
+
+[Complete tree with all subdirectories and files]
+
+### src/types/ — Global TypeScript Types
+
+[List type files]
+
+### Other src/ Files
+
+[middleware.ts, site-config.ts]
+
+---
+
+## 📂 content/ — Editorial Content
+
+[Structure and explanation of MDX organization]
+
+---
+
+## 📂 public/ — Static Assets
+
+[Complete listing with explanations]
+
+---
+
+## 📂 messages/ — i18n Translation Dictionaries
+
+[Structure, JSON format example, usage example]
+
+---
+
+## 📂 docker/ — Containerization
+
+[List all Docker files]
+
+---
+
+## 📂 Documentation/ — Internal Documentation
+
+[Complete tree of all documentation files]
+
+---
+
+## 🔄 Data Flow Examples
+
+### News Pipeline
+
+[Diagram showing data flow]
+
+### Component Import Flow
+
+[Diagram showing component hierarchy]
+
+### i18n Flow
+
+[Diagram showing internationalization flow]
+
+---
+
+## 📝 Notes
+
+[Important notes about path aliases, file types, auto-generated files]
+
+---
+
+## 🔗 References
+
+[Links to related documentation]
+```
+
+**Key Requirements:**
+
+- EXHAUSTIVE listing of ALL important files
+- Use emojis for major sections (📂, 🔄, 📝, 🔗)
+- Group files logically (config, package management, etc.)
+- Include clear descriptions for each file/folder
+- Add data flow diagrams
+- Keep ASCII trees properly formatted
+- List shadcn/ui components completely
+
+**Format Example:**
+
+```
+### src/components/ui/ — shadcn/ui primitives
+
+```
+
+src/components/ui/
+├── accordion.tsx
+├── alert.tsx
+├── alert-dialog.tsx
+├── button.tsx
+├── card.tsx
+├── dialog.tsx
+├── form.tsx
+├── input.tsx
+└── ...
+
+```
+
+[Continue with complete list]
+```
+
+---
+
+### Phase 4: Review and Update FileTypes.md (if needed)
+
+**File:** `Documentation/Guidelines/architecture/FileTypes.md`
+
+**When to Update:**
+
+Only update if you discover:
+
+- New file type patterns (e.g., `*.service.ts`, `*.util.ts`)
+- Changes to existing patterns
+- New conventions being used
+
+**What to Update:**
+
+1. File Type Reference table
+2. Add new detailed explanation section
+3. Update examples if patterns changed
+
+**What NOT to Change:**
+
+- Existing well-documented patterns
+- The overall structure of the document
+- Examples that are still valid
+
+---
+
+### Phase 5: Verify Architecture.md
+
+**File:** `Documentation/Guidelines/architecture/Architecture.md`
+
+**Check:**
+
+- Section "Project Structure Documentation" exists
+- Links to FolderStructure.md, ProjectTreeFolder.md, FileTypes.md are correct
+- No duplication of content
+
+**Expected Structure:**
+
+```markdown
+## Project Structure Documentation
+
+The project structure is documented in multiple files for better organization:
+
+- **[FolderStructure.md](./FolderStructure.md)** — High-level architecture overview, key concepts, and folder organization
+- **[ProjectTreeFolder.md](./ProjectTreeFolder.md)** — Complete file-by-file breakdown of the entire repository
+- **[FileTypes.md](./FileTypes.md)** — Detailed file naming conventions and patterns
+```
+
+---
+
+## Quality Checklist
+
+After completing all updates, verify:
+
+### Content Accuracy
+
+- [ ] All directories accurately documented
+- [ ] No missing important files
+- [ ] All paths are correct
+- [ ] File descriptions are accurate
+
+### Formatting
+
+- [ ] ASCII trees are properly aligned
+- [ ] Markdown rendering is correct
+- [ ] Code blocks use correct syntax highlighting
+- [ ] Emojis are used consistently
+
+### Completeness
+
+- [ ] FolderStructure.md covers all major folders
+- [ ] ProjectTreeFolder.md lists all important files
+- [ ] FileTypes.md documents all file patterns
+- [ ] Architecture.md links are correct
+
+### Readability
+
+- [ ] Human-friendly language
+- [ ] Clear hierarchical structure
+- [ ] Logical grouping of information
+- [ ] Not overly verbose
+
+### Cross-references
+
+- [ ] Links between documents work
+- [ ] References to Next.js docs are valid
+- [ ] Internal links are correct
+
+---
+
+## Common Pitfalls to Avoid
+
+1. **Too Much Detail in FolderStructure.md**
+   - Keep it high-level
+   - Don't list every single file
+   - Focus on architecture overview
+
+2. **Missing Files in ProjectTreeFolder.md**
+   - Be thorough
+   - Check all subdirectories
+   - Don't skip "boring" config files
+
+3. **Outdated Examples**
+   - Verify code examples actually exist in repo
+   - Update import paths if changed
+   - Check that patterns are still in use
+
+4. **Broken Links**
+   - Test all markdown links
+   - Verify file paths
+   - Check external links
+
+5. **Inconsistent Formatting**
+   - Use same emoji style throughout
+   - Keep ASCII tree alignment consistent
+   - Follow markdown conventions
+
+6. **Forgetting Data Flows**
+   - Update data flow diagrams in ProjectTreeFolder.md
+   - Ensure they reflect current architecture
+   - Add new flows if patterns emerged
+
+---
+
+## Tips for Efficiency
+
+1. **Use Tools**
+   - Use `list_dir` extensively
+   - Use `glob_file_search` for finding file patterns
+   - Read actual files to verify content
+
+2. **Work Systematically**
+   - Complete Phase 1 fully before moving to Phase 2
+   - Don't skip the reconnaissance phase
+   - Document as you explore
+
+3. **Maintain Context**
+   - Keep track of what you've documented
+   - Note any inconsistencies found
+   - Mark areas that need clarification
+
+4. **Stay Organized**
+   - Update one file at a time
+   - Complete each section before moving on
+   - Test your changes
+
+---
+
+## Final Notes
+
+- This is COMPREHENSIVE documentation work
+- Expect 100-200+ tool calls for complete update
+- Take your time to be thorough
+- The goal is to create documentation that truly reflects the repository
+- Humans should be able to understand the project structure just by reading these docs
+- When in doubt, BE MORE DETAILED rather than less
+
+**Remember:** This documentation is critical for onboarding, maintenance, and project understanding. Quality matters more than speed.
+
+---
diff --git a/.github/ISSUE_TEMPLATE/feat.yml b/.github/ISSUE_TEMPLATE/feat.yml
index ebba492..efce0e6 100644
--- a/.github/ISSUE_TEMPLATE/feat.yml
+++ b/.github/ISSUE_TEMPLATE/feat.yml
@@ -59,11 +59,10 @@ body:
     id: before
     attributes:
       label: Avant de vous jeter dans le code
+      placeholder: "Quelques conseils avant de vous jeter dans le code..."
       value: |
         Avant de vous jeter dans le code, assurez-vous de bien avoir compris ce qu'il faut faire et comment faire.  
         Au besoin, pingez le lead Web dans le salon Discord et posez vos questions.  
         Plusieurs personnes peuvent travailler ensemble sur cette issue.
-
-        [Post Discord]()
     validations:
       required: false
diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml
index 3836125..3ddfae2 100644
--- a/.github/workflows/build.yml
+++ b/.github/workflows/build.yml
@@ -60,7 +60,7 @@ jobs:
         uses: actions/cache@v4
         with:
           path: .next/cache
-          key: next-cache-${{ runner.os }}-${{ hashFiles('next.config.mjs') }}
+          key: next-cache-${{ runner.os }}-${{ hashFiles('next.config.ts') }}
           restore-keys: |
             next-cache-${{ runner.os }}-
 
diff --git a/.vscode/settings.json b/.vscode/settings.json
index 5cf7dac..1360f3e 100644
--- a/.vscode/settings.json
+++ b/.vscode/settings.json
@@ -7,7 +7,8 @@
     "Versions",
     "API",
     "Webhook",
-    "Internationalisation"
+    "Internationalisation",
+    "Documentation"
   ],
   "editor.defaultFormatter": "esbenp.prettier-vscode",
   "editor.tabSize": 2,
diff --git a/Documentation/Guidelines/CodeReviewProcess.md b/Documentation/Guidelines/CodeReviewProcess.md
new file mode 100644
index 0000000..b93e1d3
--- /dev/null
+++ b/Documentation/Guidelines/CodeReviewProcess.md
@@ -0,0 +1,394 @@
+# Code Review Process
+
+This document describes the complete code review process for the DyingStar project, from creating a feature to deploying to staging.
+
+## Table of Contents
+
+- [Introduction](#introduction)
+- [Prerequisites](#prerequisites)
+- [Development Process](#development-process)
+- [Before Creating the Pull Request](#before-creating-the-pull-request)
+- [Creating the Pull Request](#creating-the-pull-request)
+- [Automated CI/CD Pipeline](#automated-cicd-pipeline)
+- [Review Process](#review-process)
+- [Merge and Deployment](#merge-and-deployment)
+- [Quick Checklist](#quick-checklist)
+
+## Introduction
+
+The DyingStar project uses the **git-flow** model to manage development. All development is done in feature branches, which are then merged into `develop` via Pull Request after validation.
+
+The code review process ensures code quality, architectural consistency, and adherence to best practices before a change is integrated.
+
+> 📖 More information on git-flow: [DevelopmentProcess Documentation](./DevelopmentProcess.md)
+
+## Prerequisites
+
+Before starting development:
+
+1. **Get issue details** from GitHub Projects
+2. **Ask your questions** to the Website Lead on Discord in the post linked to the issue
+3. **Request assignment** of the issue from the Website Lead
+4. **Fully understand the requirements** listed in the issue (Design, Frontend, Backend, Integration)
+
+## Development Process
+
+### 1. Update the `develop` branch
+
+Make sure you have the latest version of `develop`:
+
+```bash
+git checkout develop
+git pull origin develop
+```
+
+### 2. Create the feature branch
+
+Create your branch following the naming convention:
+
+```bash
+git checkout -b feat/{issue-number}-{ShortIssueName}
+```
+
+**Examples:**
+
+- `feat/123-AddUserProfile`
+- `fix/456-FixLoginBug`
+
+### 3. Development
+
+Develop the features according to the issue requirements.
+
+**Best practices:**
+
+- Make regular commits with clear messages
+- Test your changes locally with `make up` then `make pnpm dev`
+- Follow the project's code conventions
+
+## Before Creating the Pull Request
+
+### 1. Synchronization with `develop`
+
+Before creating your PR, synchronize your branch with `develop` to avoid conflicts:
+
+```bash
+git pull origin develop
+```
+
+If conflicts appear, resolve them locally and test that everything works.
+
+### 2. Mandatory local checks
+
+Before pushing, run the following commands to ensure your code meets the standards:
+
+#### a) Clean (Lint + Typecheck + Prettier)
+
+```bash
+make pnpm clean
+```
+
+This command executes:
+
+- `eslint . --fix`: Analyzes and automatically fixes lint errors
+- `tsc --noEmit`: Checks TypeScript types without generating files
+- `prettier --write .`: Formats the code according to project rules
+
+#### b) Build
+
+```bash
+make pnpm build
+```
+
+This command compiles the Next.js application with Turbopack. The build must succeed without errors.
+
+> ⚠️ **Important**: These two steps are **mandatory** before creating a PR. If the build fails, do not create the PR.
+
+### 3. Commit and push
+
+Once all checks pass:
+
+```bash
+git add .
+git commit -m "feat: description of your feature"
+git push origin feat/{issue-number}-{ShortIssueName}
+```
+
+## Creating the Pull Request
+
+### 1. Open the Pull Request on GitHub
+
+- Go to the GitHub repository
+- Click on "Compare & pull request" or create a new PR
+- **Base branch**: `develop`
+- **Compare branch**: your feature branch
+
+### 2. Fill in the PR description
+
+A good description should contain:
+
+**Title:**
+
+- Format: `[#{issue-number}] Short feature title`
+- Example: `[#123] Add user profile page`
+
+**Description:**
+
+```markdown
+## Context
+
+Describe the context and objective of this PR.
+
+## Changes
+
+- List of main modifications
+- New features added
+- Bugs fixed
+
+## Screenshots (if applicable)
+
+Add screenshots for UI changes
+
+## Requirements Checklist
+
+- [ ] Design: [description if applicable]
+- [ ] Frontend: [description]
+- [ ] Backend: [description]
+- [ ] Integration: [description]
+
+## Tests Performed
+
+- [ ] Local tests OK
+- [ ] Build successful
+- [ ] Lint/Typecheck/Prettier OK
+```
+
+### 3. Link the GitHub issue
+
+In the PR description, add:
+
+```markdown
+Closes #123
+```
+
+This will automatically link the issue to the PR and close it upon merge.
+
+### 4. Verify the requirements
+
+Make sure you have addressed **all requirements** listed in the original issue:
+
+- ✅ Design
+- ✅ Frontend
+- ✅ Backend
+- ✅ Integration (CI/CD, observability, documentation)
+
+## Automated CI/CD Pipeline
+
+As soon as the PR is created, **GitHub Actions** automatically triggers to validate your code.
+
+### Pipeline steps
+
+The pipeline executes the following steps (defined in `.github/workflows/build.yml`):
+
+1. **Environment setup**
+   - Node.js 22
+   - pnpm (version from `package.json`)
+   - Dependency cache
+
+2. **Install dependencies**
+
+   ```bash
+   pnpm install --frozen-lockfile
+   ```
+
+3. **Type generation**
+
+   ```bash
+   pnpm type:generate
+   ```
+
+4. **Lint CI**
+
+   ```bash
+   pnpm lint:ci
+   ```
+
+   This command executes:
+   - `eslint . --max-warnings 0`: Lint with zero tolerance for warnings
+   - `tsc --noEmit`: Type checking
+   - `prettier --check .`: Format checking (without modification)
+
+5. **Build Next.js**
+
+   ```bash
+   pnpm build
+   ```
+
+6. **Build Docker Image** (without push for PRs)
+
+### Check the pipeline status
+
+- The pipeline status is displayed directly in the PR
+- ✅ **Checks passed**: All tests are OK, the PR can be reviewed
+- ❌ **Checks failed**: Errors have been detected, you must fix them
+
+> ⚠️ **Important**: A PR can only be merged if all checks are green.
+
+### In case of failure
+
+If the pipeline fails:
+
+1. Check the detailed logs in the "Checks" tab of the PR
+2. Fix the errors locally
+3. Re-run `make pnpm clean` and `make pnpm build`
+4. Commit and push the fixes
+5. The pipeline will rerun automatically
+
+## Review Process
+
+### 1. Notification
+
+Once the PR is created and checks have passed, **notify the team on Discord**:
+
+```
+🔔 PR ready for review: [PR Link]
+Issue: #123 - Issue title
+```
+
+### 2. Review by another developer (recommended)
+
+Another developer can perform a review for:
+
+**Review criteria:**
+
+- ✅ **Code quality**: Readability, variable/function naming
+- ✅ **Architecture**: Respect for project patterns
+- ✅ **Performance**: No unnecessary blocking code
+- ✅ **Security**: No obvious vulnerabilities
+- ✅ **Documentation**: Comments / Documentation.md if necessary
+
+The reviewer can:
+
+- ✅ **Approve** the PR if everything is OK
+- 💬 **Comment** to request clarifications
+- ❌ **Request changes** if corrections are needed
+
+### 3. Mandatory review by the Website Lead
+
+The **Website Lead** must review and approve the PR before merge.
+
+They verify:
+
+- Compliance with issue requirements
+- Consistency with overall architecture
+- Alignment with project vision
+
+### 4. Address review comments
+
+If changes are requested:
+
+1. Make the requested modifications
+2. Re-run `make pnpm clean` and `make pnpm build`
+3. Commit and push
+4. Respond to review comments
+5. Re-request review if necessary
+
+## Merge and Deployment
+
+### 1. Final approval
+
+Once all reviews are passed and approved:
+
+- ✅ All GitHub Actions checks are green
+- ✅ At least one approval from the Website Lead
+- ✅ All review comments are resolved
+
+### 2. Merge into `develop`
+
+**Only the Website Lead can merge the PR.**
+
+The merge is done via the GitHub interface:
+
+1. Click on "Merge pull request"
+2. Choose the merge type (usually "Squash and merge")
+3. Confirm the merge
+
+### 3. Automatic deployment to staging
+
+As soon as the code is merged into `develop`, **GitHub Actions automatically triggers** the staging deployment:
+
+**Deployment pipeline:**
+
+1. **Application build** (job `build`)
+2. **Docker image build** (job `docker-image`)
+   - Tag: `ghcr.io/dyingstar-game/website:staging`
+   - Tag: `ghcr.io/dyingstar-game/website:staging-{sha}`
+3. **Image push** to GitHub Container Registry (GHCR)
+4. **SSH deployment** (job `deploy`)
+   - Connection to staging server
+   - Pull of new Docker image
+   - Container restart via `docker-compose`
+
+**Estimated duration:** 5-10 minutes
+
+### 4. Staging verification
+
+After deployment:
+
+1. **Wait** for the deployment pipeline to finish (green checks)
+2. **Verify** that the application works on the staging environment
+3. **Test** your feature on staging
+4. **Report** any issues to the Website Lead
+
+## Quick Checklist
+
+Use this checklist to make sure you don't forget anything:
+
+### Before developing
+
+- [ ] Issue read and understood
+- [ ] Issue assignment obtained
+- [ ] `develop` branch up to date
+- [ ] Feature branch created with correct convention
+
+### During development
+
+- [ ] Code developed according to requirements
+- [ ] Local tests performed
+- [ ] Regular commits with clear messages
+
+### Before the PR
+
+- [ ] Merge of `develop` into my branch
+- [ ] Conflicts resolved (if applicable)
+- [ ] `make pnpm clean` executed successfully ✅
+- [ ] `make pnpm build` executed successfully ✅
+- [ ] Code committed and pushed
+
+### Creating the PR
+
+- [ ] PR created with complete description
+- [ ] Issue linked with `Closes #xxx`
+- [ ] All issue requirements addressed
+- [ ] Screenshots added (if UI)
+- [ ] Team notified on Discord
+
+### After the PR
+
+- [ ] GitHub Actions pipeline green ✅
+- [ ] Review comments addressed
+- [ ] Website Lead approval obtained
+- [ ] PR merged by Website Lead
+- [ ] Staging deployment verified
+
+---
+
+## Useful Resources
+
+- [Git-flow model](https://nvie.com/posts/a-successful-git-branching-model/)
+- [Development Process Documentation](./DevelopmentProcess.md)
+- [Architecture Documentation](./architecture/Architecture.md)
+- [Makefile commands](../../Makefile)
+
+---
+
+**Questions?** Contact the Website Lead on Discord 💬
diff --git a/Documentation/Guidelines/DevelopmentProcess.md b/Documentation/Guidelines/DevelopmentProcess.md
new file mode 100644
index 0000000..d58c3c3
--- /dev/null
+++ b/Documentation/Guidelines/DevelopmentProcess.md
@@ -0,0 +1,142 @@
+# Development Process
+
+The application is developed using the git-flow model. Developers cannot commit to **master** and **develop** branches. All features are developed in feature branches. A feature can then be merged into develop using Pull/merge request.
+
+You can find more information about the git-flow model [here](https://nvie.com/posts/a-successful-git-branching-model/).
+
+Here is a screenshot of the git-flow model : ![Git-flow Model](./pictures/git-flow-model.png)
+
+All branches must be named using the following conventions :
+
+- `feat/{issue-number}-{ShortIssueName}` : use for application new features
+- `fix/{issue-number}-{ShortIssueName}` : use for fixing application bugs / issues
+- `release/release-{semantic-version-number}` : use for release tasks
+
+examples :
+
+- feat/15469-AddNewFeature
+- fix/15469-FixBug
+- release/release-1.2.3
+
+## Merging process
+
+### Merging process for `feat` or `fix` branch into `develop` branch
+
+_Only the Website Lead can merge the `feat` or `fix` branch into the `develop` branch_
+
+- Get all details from the issue on github projects
+- Ask the Website Lead for any questions about the issue on discord post related to the issue
+- Ask the Website Lead to be assigned to the issue
+- Updated the `develop` : `git pull origin develop`
+- Create feature branch : `git checkout -b feat/15469-AddNewFeature`
+- Develop the specified requirements
+- Run the formater, linter, tests, build and make sure they are passing
+- Commit and Push the code
+- Create a Pull request to merge the feature branch into the `develop` branch
+- Indicate on discord post that the PR is ready for review
+- Address the required review comments (if any)
+- Approve the PR when the code is ready to be merged by the Website Lead
+- Website Lead merge the PR into the `develop` branch
+
+### Creating hotfix process :
+
+#### 1. Creating the hotfix branch
+
+Create the branch from `main` (not from `develop`):
+
+```bash
+git checkout main
+git pull origin main
+git checkout -b hotfix/hotfix-1.2.4
+```
+
+> 📝 **Note**: The hotfix increments the PATCH number (1.2.3 → 1.2.4)
+
+#### 2. Fixing the critical bug
+
+- Fix **only** the critical bug
+- Do **not** make other changes
+- Test locally
+
+```bash
+make pnpm clean
+make pnpm build
+```
+
+#### 3. Updating the version
+
+Edit `package.json`:
+
+```json
+{
+  "version": "1.2.4"
+}
+```
+
+#### 4. Commit and push
+
+```bash
+git add .
+git commit -m "hotfix(Build Process): fix critical bug in production"
+git push origin hotfix/hotfix-1.2.4
+```
+
+#### 5. Pull Request to `main`
+
+- Create a PR from `hotfix/hotfix-1.2.4` to `main`
+- **Title**: `[HOTFIX] v1.2.4 - Description of the critical bug`
+- Mark the PR as urgent
+- Immediately notify the Website Lead
+
+#### 6. Express review and merge
+
+- Quick but thorough review by the Website Lead
+- Merge into `main`
+
+#### 7. Tag creation
+
+```bash
+git checkout main
+git pull origin main
+git tag -a v1.2.4 -m "Hotfix 1.2.4"
+git push origin v1.2.4
+```
+
+Production deployment is triggered automatically.
+
+#### 8. Merge-back to `develop`
+
+**IMPORTANT**: The hotfix must also be integrated into `develop`:
+
+```bash
+git checkout develop
+git pull origin develop
+git merge main
+git push origin develop
+```
+
+This triggers a staging deployment with the fix.
+
+#### 9. Creating the GitHub Release
+
+Create a release on GitHub documenting the hotfix.
+
+### Creating release process :
+
+_Only the Website Lead can create a release_
+
+- Updated the `develop` : `git pull origin develop`
+- Create release branch : `git checkout -b release/release-1.2.3`
+- Update the version number in the `package.json` file
+- _On this branch: small fixes and preparation of metadata (changelog, dates, etc.). No big features_
+- Update changelog, version notes, build numbers...
+- Commit and Push the code
+- Create a Pull request to merge the release branch into the `master` branch
+- Indicate on discord post that the PR is ready for review
+- Address the required review comments (if any)
+- Approve the PR when the code is ready to be merged by the Website Lead
+- Merge the PR into the `master` branch
+- Create tag with the new version number : `git tag -a v1.2.3 -m "Release 1.2.3"`
+- Push the tag : `git push origin v1.2.3`
+- Merge the `master` branch into the `develop` branch
+- Create a new release on github with the new version number
diff --git a/Documentation/Guidelines/Onboarding.md b/Documentation/Guidelines/Onboarding.md
new file mode 100644
index 0000000..b8a126b
--- /dev/null
+++ b/Documentation/Guidelines/Onboarding.md
@@ -0,0 +1,49 @@
+# [DyingStar - Webapp] Tools
+
+Please install following tools
+
+| Tool                                               | Version           | Required |
+| -------------------------------------------------- | ----------------- | -------- |
+| [Node.js](https://nodejs.org/en)                   | 22.20.0 or higher | Yes      |
+| [Docker](https://www.docker.com/)                  | 24.0.0 or higher  | Yes      |
+| [Docker Compose](https://docs.docker.com/compose/) | 2.20.0 or higher  | Yes      |
+| [Make](https://www.gnu.org/software/make/)         | 3.81 or higher    | Yes      |
+| [Git](https://git-scm.com/)                        | 2.50.0 or higher  | Yes      |
+| [pnpm](https://pnpm.io/)                           | 10.17.1 or higher | Yes      |
+
+# Git command-line configuration
+
+Make sure you have configured your user with Git. This information will be used by Git.
+
+```
+git config --global user.name "Your Fullname"
+git config --global user.email "Your Email"
+```
+
+Windows users should use Git bash for better command-line experience. If you are not well-versed with Git then you can read the [tutorial](https://github.com/shekhargulati/git-the-missing-tutorial).
+
+# Connecting to Github using SSH
+
+Refer to this [link](https://docs.github.com/en/free-pro-team@latest/github/authenticating-to-github/connecting-to-github-with-ssh) to setup SSH for your Github account.
+
+# Get your access to the repository
+
+Ask to the Website Lead on this [discord channel](https://discord.com/channels/1399325839665004554/1417133740810833940) to get push permissions to the repository.
+
+# Clone the application
+
+Clone the application using the following command.
+
+```
+git clone git@github.com:DyingStar-game/website.git
+```
+
+# Local Development
+
+## Setup
+
+1. Copy `.env.sample` to `.env.local` and fill in the required environment variables
+2. Run `make up` to start the development environment (MeiliSearch service)
+3. Run `make pnpm dev` to start the Next.js development server
+4. Open your browser and navigate to `http://localhost:3000` to see the website.
+5. To stop the development server, press `Ctrl+C` in the terminal where `make pnpm dev` was run.
diff --git a/Documentation/Guidelines/ReleaseAndDeployment.md b/Documentation/Guidelines/ReleaseAndDeployment.md
new file mode 100644
index 0000000..22e2bf9
--- /dev/null
+++ b/Documentation/Guidelines/ReleaseAndDeployment.md
@@ -0,0 +1,711 @@
+# Release and Deployment Process
+
+This document describes the complete release creation and deployment process for the DyingStar project, based on the git-flow model and the GitHub Actions CI/CD pipeline.
+
+## Table of Contents
+
+- [Introduction](#introduction)
+- [Environments](#environments)
+- [Release Process](#release-process)
+- [Detailed CI/CD Pipeline](#detailed-cicd-pipeline)
+- [Hotfix Process](#hotfix-process)
+- [Rollback and Recovery](#rollback-and-recovery)
+- [Verification and Tests](#verification-and-tests)
+- [Release Checklist](#release-checklist)
+
+## Introduction
+
+The DyingStar project uses the **git-flow** model for release and deployment management. The process is automated via GitHub Actions and ensures reliable deployments to staging and production.
+
+### Roles and Responsibilities
+
+**Only the Website Lead can:**
+
+- Create releases
+- Merge release branches to `main`
+- Create version tags
+- Trigger production deployments
+
+### Versioning
+
+The project uses **Semantic Versioning** (SemVer):
+
+- `vMAJOR.MINOR.PATCH` (e.g., `v1.2.3`)
+- **MAJOR**: Incompatible API changes
+- **MINOR**: New backwards-compatible features
+- **PATCH**: Backwards-compatible bug fixes
+
+> 📖 More information: [https://semver.org/](https://semver.org/)
+
+## Environments
+
+### Staging
+
+**Trigger:** Automatic on push to the `develop` branch
+
+**Characteristics:**
+
+- Docker tag: `ghcr.io/dyingstar-game/website:staging`
+- Secondary tag: `ghcr.io/dyingstar-game/website:staging-{sha}`
+- Architecture: `linux/amd64` only
+- Port: `8101` (according to `docker/staging.compose.yml`)
+
+**Usage:**
+
+- Testing new features
+- Pre-production validation
+- Demonstrations
+
+### Production
+
+**Trigger:** Automatic on creation of a `v*` tag (e.g., `v1.2.3`)
+
+**Characteristics:**
+
+- Primary Docker tag: `ghcr.io/dyingstar-game/website:v{version}`
+- Secondary tag: `ghcr.io/dyingstar-game/website:prod`
+- Architecture: Multi-platform (`linux/amd64`, `linux/arm64`)
+- Deployment via SSH to production server
+
+**Specifics:**
+
+- Multi-architecture build for maximum compatibility
+- Protected environment requiring approvals
+- Active monitoring and alerts
+
+## Release Process
+
+### Prerequisites
+
+Before creating a release, ensure that:
+
+- ✅ All features for the release are merged into `develop`
+- ✅ The staging environment is stable
+- ✅ Staging tests are conclusive
+- ✅ The changelog is ready
+
+### Release Creation Steps
+
+#### 1. Update `develop`
+
+```bash
+git checkout develop
+git pull origin develop
+```
+
+#### 2. Create the release branch
+
+Create a release branch following the naming convention:
+
+```bash
+git checkout -b release/release-1.2.3
+```
+
+> 📝 **Note**: Replace `1.2.3` with the appropriate version number according to SemVer
+
+#### 3. Update the version number
+
+Edit the `package.json` file and update the version:
+
+```json
+{
+  "name": "dying-star",
+  "version": "1.2.3",
+  ...
+}
+```
+
+#### 4. Prepare metadata
+
+On this branch, only perform:
+
+- ✅ CHANGELOG update
+- ✅ Version notes addition
+- ✅ Minor documentation fixes
+- ✅ Small critical bugfixes discovered
+
+❌ **No major new features**
+
+#### 5. Local verification
+
+Before creating the PR, run the verifications:
+
+```bash
+make pnpm clean
+make pnpm build
+```
+
+#### 6. Commit and push
+
+```bash
+git add .
+git commit -m "chore: prepare release 1.2.3"
+git push origin release/release-1.2.3
+```
+
+#### 7. Pull Request creation
+
+- Create a PR from `release/release-1.2.3` to `main`
+- **Title**: `[Release] v1.2.3`
+- **Description**:
+
+```markdown
+## Release v1.2.3
+
+### New features
+
+- Feature 1
+- Feature 2
+
+### Bug fixes
+
+- Fix 1
+- Fix 2
+
+### Improvements
+
+- Improvement 1
+
+### Breaking Changes (if applicable)
+
+- Breaking change 1
+
+### Migration notes (if applicable)
+
+Instructions for users/developers
+```
+
+- Notify the team on Discord
+
+#### 8. Review and Approval
+
+- The Website Lead reviews the PR
+- Other developers can review (recommended)
+- Address comments if necessary
+- Final approval by the Website Lead
+
+#### 9. PR Merge
+
+**The Website Lead merges the PR into `main`:**
+
+```
+1. Merge pull request
+2. Merge type: usually "Squash and merge"
+3. Confirm the merge
+```
+
+#### 10. Version tag creation
+
+Once the PR is merged into `main`:
+
+```bash
+git checkout main
+git pull origin main
+git tag -a v1.2.3 -m "Release 1.2.3"
+git push origin v1.2.3
+```
+
+> ⚡ **Important**: Pushing the tag automatically triggers production deployment
+
+#### 11. Merge-back to `develop`
+
+After production deployment, merge changes back into `develop`:
+
+```bash
+git checkout develop
+git pull origin develop
+git merge main
+git push origin develop
+```
+
+#### 12. GitHub Release creation
+
+1. Go to GitHub → Releases → Draft a new release
+2. Choose the tag `v1.2.3`
+3. Title: `Release v1.2.3`
+4. Description: Copy the release notes from the PR
+5. Add binaries/assets if necessary
+6. Publish the release
+
+## Detailed CI/CD Pipeline
+
+The pipeline is defined in `.github/workflows/build.yml` and consists of 3 main jobs.
+
+### Job 1: Build Next.js
+
+**Trigger:**
+
+- Push to `develop`
+- Push of `v*` tags
+- Pull Requests to `main` or `develop`
+- Manual workflow (workflow_dispatch)
+
+**Steps:**
+
+1. **Code checkout**
+
+   ```yaml
+   uses: actions/checkout@v4
+   ```
+
+2. **Environment setup**
+   - Container: `node:22-alpine`
+   - Installation of tar and jq
+   - CPU: 2 cores
+
+3. **pnpm configuration**
+
+   ```bash
+   corepack enable
+   VERSION=$(jq -r '.packageManager|capture("pnpm@(?<v>.*)$").v' package.json)
+   corepack prepare pnpm@${VERSION} --activate
+   ```
+
+4. **Dependency caching**
+   - pnpm cache based on `pnpm-lock.yaml`
+   - Next.js cache based on `next.config.ts`
+
+5. **Dependency installation**
+
+   ```bash
+   pnpm fetch --silent
+   pnpm install --frozen-lockfile --prefer-offline
+   ```
+
+6. **Allowed scripts configuration**
+
+   ```bash
+   pnpm config set allow-scripts "@parcel/watcher,@tailwindcss/oxide,esbuild,sharp"
+   ```
+
+7. **Environment files recreation**
+   - `.env` from the `WEBSITE_ENV_FILE` secret
+   - `.env.production` from the same secret
+
+8. **Type generation**
+
+   ```bash
+   pnpm type:generate
+   ```
+
+9. **Lint CI**
+
+   ```bash
+   pnpm lint:ci
+   ```
+
+   This command executes:
+   - `eslint . --max-warnings 0`
+   - `tsc --noEmit`
+   - `prettier --check .`
+
+10. **Next.js Build**
+
+    ```bash
+    NODE_OPTIONS=--max-old-space-size=4096 pnpm build
+    ```
+
+11. **Dev dependencies cleanup**
+
+    ```bash
+    pnpm prune --prod
+    ```
+
+12. **Runtime artifact creation**
+
+    ```bash
+    tar -czf runtime.tar.gz \
+      .next/standalone \
+      .next/static \
+      public \
+      package.json \
+      pnpm-lock.yaml
+    ```
+
+13. **Artifact upload**
+    - Name: `next-runtime`
+    - Retention: 1 day
+
+### Job 2: Docker Image
+
+**Dependencies:** Requires the `build` job
+
+**Steps:**
+
+1. **Download runtime artifact**
+
+2. **Artifact extraction**
+
+   ```bash
+   tar -xzf artifact/runtime.tar.gz
+   ```
+
+3. **Target decision (prod/staging/none)**
+   - **Production**: if `v*` tag
+     - Platforms: `linux/amd64,linux/arm64`
+   - **Staging**: if `develop` branch or manual workflow
+     - Platforms: `linux/amd64`
+   - **None**: for PRs (build only, no push)
+
+4. **Docker tags calculation**
+
+   **For staging:**
+
+   ```
+   Primary tag: ghcr.io/dyingstar-game/website:staging
+   Secondary tag: ghcr.io/dyingstar-game/website:staging-{sha}
+   ```
+
+   **For production:**
+
+   ```
+   Primary tag: ghcr.io/dyingstar-game/website:v1.2.3
+   Secondary tag: ghcr.io/dyingstar-game/website:prod
+   ```
+
+5. **Docker Buildx & QEMU Setup**
+   - Buildx for multi-platform
+   - QEMU if ARM64 architecture needed
+
+6. **Push and cache policy**
+   - **PR**: No push, GitHub Actions cache
+   - **Staging/Prod**: Push to GHCR, registry cache
+
+7. **GitHub Container Registry login**
+
+   ```bash
+   docker login ghcr.io -u ${{ github.actor }}
+   ```
+
+8. **Build & Push image**
+   - Dockerfile: `docker/Dockerfile.prod`
+   - Cache from: `ghcr.io/dyingstar-game/website:buildcache`
+   - Cache to: same reference
+
+### Job 3: Deploy
+
+**Dependencies:** Requires the `docker-image` job
+
+**Condition:** Only if target = `staging` or `prod`
+
+**Environment:**
+
+- `staging`: if `develop` branch
+- `prod`: if `v*` tag
+
+**Steps:**
+
+1. **Checkout compose files**
+
+2. **Compose file selection**
+   - Production: `${{ secrets.COMPOSE_FILE_PROD }}`
+   - Staging: `${{ secrets.COMPOSE_FILE_STAGING }}`
+
+3. **SSH deployment**
+
+   Connection to server via SSH with:
+   - Host: `${{ secrets.SSH_HOST }}`
+   - User: `${{ secrets.SSH_USER }}`
+   - Key: `${{ secrets.SSH_KEY }}`
+   - Port: `${{ secrets.SSH_PORT || 22 }}`
+
+   Executed script:
+
+   ```bash
+   # Registry login
+   echo "${{ secrets.GHCR_PAT }}" | docker login ghcr.io -u "${{ secrets.GHCR_USERNAME }}" --password-stdin
+
+   # Pull new image
+   cd docker
+   docker compose -f {compose-file} pull --ignore-pull-failures
+
+   # Container restart
+   docker compose -f {compose-file} up -d --no-deps
+
+   # Verification
+   docker compose -f {compose-file} ps
+   ```
+
+**Total estimated duration:** 5-10 minutes
+
+## Hotfix Process
+
+Hotfixes are used to fix critical bugs in production that cannot wait for the next release.
+
+### When to create a hotfix?
+
+- ❌ Critical bug in production
+- ❌ Security vulnerability
+- ❌ Data loss
+- ❌ Service unavailable
+
+❌ **Do not use for:**
+
+- Minor non-critical bugs
+- New features
+- Non-urgent performance improvements
+
+## Rollback and Recovery
+
+### Rollback Scenarios
+
+A rollback may be necessary if:
+
+- The deployment causes critical errors
+- Features don't work as expected
+- Severe performance issues appear
+
+### Rollback Procedure
+
+#### Option 1: Docker Rollback (Fast)
+
+**On production/staging server:**
+
+1. **Identify the previous stable version**
+
+   Available Docker tags:
+   - `ghcr.io/dyingstar-game/website:v1.2.2` (previous version)
+   - `ghcr.io/dyingstar-game/website:v1.2.3` (current problematic version)
+
+2. **Modify the compose file**
+
+   SSH to the server:
+
+   ```bash
+   ssh user@server
+   cd docker
+   ```
+
+   Edit the compose file (staging.compose.yml or prod.compose.yml):
+
+   ```yaml
+   services:
+     app:
+       image: ghcr.io/dyingstar-game/website:v1.2.2 # Stable version
+   ```
+
+3. **Restart containers**
+
+   ```bash
+   docker compose -f {compose-file} pull
+   docker compose -f {compose-file} up -d --force-recreate
+   docker compose -f {compose-file} ps
+   ```
+
+4. **Verify rollback**
+   - Test the application
+   - Check logs: `docker compose -f {compose-file} logs -f app`
+
+**Estimated duration:** 2-5 minutes
+
+#### Option 2: Git Rollback (Complete)
+
+If the issue requires a complete code rollback:
+
+1. **Create a release revert**
+
+   ```bash
+   git checkout main
+   git pull origin main
+   git revert -m 1 <merge-commit-sha>
+   git push origin main
+   ```
+
+2. **Create a new patch tag**
+
+   ```bash
+   git tag -a v1.2.4 -m "Rollback to 1.2.2"
+   git push origin v1.2.4
+   ```
+
+3. **Wait for automatic deployment**
+
+### Recovery Procedure
+
+After a rollback, to recover and fix:
+
+1. **Identify the root cause**
+   - Analyze logs
+   - Reproduce the bug locally
+
+2. **Create a hotfix**
+   Follow the [Hotfix Process](#hotfix-process)
+
+3. **Test thoroughly**
+   - Local tests
+   - Staging tests
+   - Non-regression tests
+
+4. **Redeploy**
+   Create a new tag once the fix is validated
+
+## Verification and Tests
+
+### Pre-Release Tests
+
+Before creating a release, verify:
+
+#### Local Tests
+
+```bash
+# Start development environment
+make up
+make pnpm dev
+
+# In another terminal, test
+# - Navigation on all pages
+# - Main features
+# - Responsive design
+```
+
+#### Build Tests
+
+```bash
+# Clean and build
+make pnpm clean
+make pnpm build
+
+# Verify there are no errors
+```
+
+#### Staging Tests
+
+Once merged into `develop`:
+
+1. Wait for automatic staging deployment
+2. Test all new features
+3. Verify existing features (non-regression)
+4. Test on different browsers
+5. Test responsive (mobile/tablet/desktop)
+
+### Post-Deployment Verification
+
+After a production deployment:
+
+#### Immediate Verification (0-5 min)
+
+- [ ] Site is accessible
+- [ ] No 500 errors
+- [ ] Homepage loads correctly
+- [ ] Authentication works
+- [ ] Main navigation works
+
+#### In-Depth Verification (5-30 min)
+
+- [ ] All new features work
+- [ ] Existing critical features OK
+- [ ] External integrations OK (GitHub, Meilisearch)
+- [ ] Acceptable performance (loading times)
+- [ ] No JavaScript errors in console
+
+#### Continuous Monitoring (30 min - 24h)
+
+- [ ] Monitor error logs
+- [ ] Check performance metrics
+- [ ] Monitor user errors
+- [ ] Team and user feedback
+
+### Verification Commands
+
+#### Check Docker containers
+
+```bash
+# SSH to server
+ssh user@server
+cd docker
+
+# Container status
+docker compose -f {compose-file} ps
+
+# Application logs
+docker compose -f {compose-file} logs -f app
+
+# Meilisearch logs
+docker compose -f {compose-file} logs -f meilisearch
+```
+
+#### Check Docker images
+
+```bash
+# List images on server
+docker images | grep website
+
+# Check available tags on GHCR
+# Via GitHub UI: Packages → website → View all tagged versions
+```
+
+## Release Checklist
+
+Use this checklist to ensure a flawless release process.
+
+### Phase 1: Preparation
+
+- [ ] All planned features are merged into `develop`
+- [ ] CHANGELOG prepared with all modifications
+- [ ] Documentation updated if necessary
+- [ ] Team notified of upcoming release
+
+### Phase 2: Release Creation
+
+- [ ] Local `develop` branch up to date
+- [ ] `release/release-X.Y.Z` branch created
+- [ ] Version in `package.json` updated
+- [ ] CHANGELOG finalized
+- [ ] `make pnpm clean` executed successfully ✅
+- [ ] `make pnpm build` executed successfully ✅
+- [ ] Changes committed and pushed
+- [ ] PR created to `main` with complete description
+- [ ] Team notified on Discord
+
+### Phase 3: Review and Validation
+
+- [ ] Code reviewed by at least 1 developer
+- [ ] Website Lead approval obtained
+- [ ] All review comments addressed
+- [ ] GitHub Actions pipeline green ✅
+- [ ] Final deployment confirmation obtained
+
+### Phase 4: Merge and Tag
+
+- [ ] PR merged into `main` by Website Lead
+- [ ] Local `main` branch up to date
+- [ ] Tag `vX.Y.Z` created
+- [ ] Tag pushed to GitHub
+- [ ] Production deployment pipeline launched
+
+### Phase 5: Deployment
+
+- [ ] GitHub Actions pipeline completed successfully
+- [ ] Production deployment confirmed
+- [ ] Immediate post-deployment verifications OK
+- [ ] Site accessible and functional
+- [ ] No critical errors detected
+
+### Phase 6: Finalization
+
+- [ ] Changes merged from `main` to `develop`
+- [ ] GitHub Release created and published
+- [ ] 24h monitoring activated
+- [ ] Team notified of successful deployment
+- [ ] Communication to users (if necessary)
+
+### Phase 7: Follow-up (24h-48h)
+
+- [ ] Error monitoring: no critical errors
+- [ ] Stable performance
+- [ ] Positive team feedback
+- [ ] No rollback needed
+- [ ] Post-mortem documentation if incidents
+
+## Useful Resources
+
+- [Git-flow model](https://nvie.com/posts/a-successful-git-branching-model/)
+- [Semantic Versioning](https://semver.org/)
+- [Development Process Documentation](./DevelopmentProcess.md)
+- [Code Review Documentation](./CodeReviewProcess.md)
+- [GitHub Actions Workflow](.github/workflows/build.yml)
+- [Makefile](../../Makefile)
+
+---
+
+**Questions?** Contact the Website Lead on Discord 💬
diff --git a/Documentation/Guidelines/architecture/ADR/000-Template.md b/Documentation/Guidelines/architecture/ADR/000-Template.md
new file mode 100644
index 0000000..ae8f69d
--- /dev/null
+++ b/Documentation/Guidelines/architecture/ADR/000-Template.md
@@ -0,0 +1,72 @@
+# [short title of solved problem and solution]
+
+- Status: [proposed | rejected | accepted | deprecated | … | superseded by [ADR-0005](0005-example.md)] <!-- optional -->
+- Deciders: [list everyone involved in the decision] <!-- optional -->
+- Date: [YYYY-MM-DD when the decision was last updated] <!-- optional -->
+
+Technical Story: [description | ticket/issue URL] <!-- optional -->
+
+## Context and Problem Statement
+
+[Describe the context and problem statement, e.g., in free form using two to three sentences. You may want to articulate the problem in form of a question.]
+
+## Decision Drivers <!-- optional -->
+
+- [driver 1, e.g., a force, facing concern, …]
+- [driver 2, e.g., a force, facing concern, …]
+- … <!-- numbers of drivers can vary -->
+
+## Considered Options
+
+- [option 1]
+- [option 2]
+- [option 3]
+- … <!-- numbers of options can vary -->
+
+## Decision Outcome
+
+Chosen option: "[option 1]", because [justification. e.g., only option, which meets k.o. criterion decision driver | which resolves force force | … | comes out best (see below)].
+
+### Positive Consequences <!-- optional -->
+
+- [e.g., improvement of quality attribute satisfaction, follow-up decisions required, …]
+- …
+
+### Negative Consequences <!-- optional -->
+
+- [e.g., compromising quality attribute, follow-up decisions required, …]
+- …
+
+## Pros and Cons of the Options <!-- optional -->
+
+### [option 1]
+
+[example | description | pointer to more information | …] <!-- optional -->
+
+- Good, because [argument a]
+- Good, because [argument b]
+- Bad, because [argument c]
+- … <!-- numbers of pros and cons can vary -->
+
+### [option 2]
+
+[example | description | pointer to more information | …] <!-- optional -->
+
+- Good, because [argument a]
+- Good, because [argument b]
+- Bad, because [argument c]
+- … <!-- numbers of pros and cons can vary -->
+
+### [option 3]
+
+[example | description | pointer to more information | …] <!-- optional -->
+
+- Good, because [argument a]
+- Good, because [argument b]
+- Bad, because [argument c]
+- … <!-- numbers of pros and cons can vary -->
+
+## Links <!-- optional -->
+
+- [Link type] [Link to ADR] <!-- example: Refined by [ADR-0005](0005-example.md) -->
+- … <!-- numbers of links can vary -->
diff --git a/Documentation/Guidelines/architecture/ADRs.md b/Documentation/Guidelines/architecture/ADRs.md
new file mode 100644
index 0000000..c12bccd
--- /dev/null
+++ b/Documentation/Guidelines/architecture/ADRs.md
@@ -0,0 +1,5 @@
+<!-- adrlog -->
+
+- [ADR-000](ADR/000-Template.md) - [short title of solved problem and solution]
+
+<!-- adrlogstop -->
diff --git a/Documentation/Guidelines/architecture/Architecture.md b/Documentation/Guidelines/architecture/Architecture.md
new file mode 100644
index 0000000..025187e
--- /dev/null
+++ b/Documentation/Guidelines/architecture/Architecture.md
@@ -0,0 +1,89 @@
+# [DyingStar - Webapp] Webapp Architecture
+
+## Architecture Decision Records
+
+All ADRs are stored in the [ADR](./ADR) folder and referenced in the [ADRs.md](./ADRs.md) file.
+
+## Technologies
+
+The list of technologies we will use to build the application are as follows:
+
+| Technology                       | Description               | Version  |
+| -------------------------------- | ------------------------- | -------- |
+| [Next.js]                        | Base framework            | 15.5.6   |
+| [React]                          | UI library                | 19.1.1   |
+| [TypeScript]                     | Type safety               | 5.9.2    |
+| [pnpm]                           | Package manager           | 10.17.1  |
+| [@t3-oss/env-nextjs]             | Environment variables     | 0.13.8   |
+| [Tailwind CSS]                   | Styling                   | 4.1.13   |
+| [tailwind-merge]                 | Merge Tailwind classes    | 3.3.1    |
+| [class-variance-authority]       | Component variants        | 0.7.1    |
+| [clsx]                           | Conditional classnames    | 2.1.1    |
+| [Radix UI]                       | Headless UI components    | Various  |
+| [lucide-react]                   | Icon library              | 0.542.0  |
+| [cmdk]                           | Command menu              | 1.1.1    |
+| [better-auth]                    | Authentication            | 1.3.8    |
+| [next-intl]                      | Internationalization      | 4.3.9    |
+| [@tanstack/react-query]          | Server state management   | 5.87.1   |
+| [@tanstack/react-query-devtools] | React Query DevTools      | 5.87.1   |
+| [Zustand]                        | Client state management   | 5.0.8    |
+| [Zod]                            | Schema validation         | 4.1.5    |
+| [react-hook-form]                | Form management           | 7.62.0   |
+| [@hookform/resolvers]            | Form validation resolvers | 5.2.1    |
+| [Framer Motion]                  | Animations                | 12.23.15 |
+| [motion]                         | Animation library         | 12.23.12 |
+| [next-safe-action]               | Type-safe server actions  | 8.0.11   |
+| [next-themes]                    | Theme management          | 0.4.6    |
+| [next-zod-route]                 | Zod route validation      | 1.0.0    |
+| [next-mdx-remote-client]         | MDX rendering             | 2.1.3    |
+| [Shiki]                          | Syntax highlighting       | 3.12.2   |
+| [recharts]                       | Data visualization        | 3.1.2    |
+| [tslog]                          | Logging                   | 4.9.3    |
+| [sonner]                         | Toast notifications       | 2.0.7    |
+| [nprogress]                      | Progress bar              | 0.2.0    |
+| [nuqs]                           | URL state management      | 2.6.0    |
+| [date-fns]                       | Date utilities            | 4.1.0    |
+| [nanoid]                         | Unique ID generation      | 5.1.5    |
+| [up-fetch]                       | HTTP client               | 2.4.0    |
+| [react-hotkeys-hook]             | Keyboard shortcuts        | 5.1.0    |
+| [react-use]                      | React hooks collection    | 17.6.0   |
+| [markdown-to-jsx]                | Markdown to JSX           | 7.7.13   |
+| [front-matter]                   | Front matter parser       | 4.0.2    |
+| [rehype-autolink-headings]       | Auto-link headings        | 7.1.0    |
+| [rehype-slug]                    | Add slugs to headings     | 6.0.0    |
+| [remark-gfm]                     | GitHub Flavored Markdown  | 4.0.1    |
+| [sass]                           | CSS preprocessor          | 1.92.1   |
+| [styled-jsx]                     | CSS-in-JS                 | 5.1.7    |
+| [ESLint]                         | Linting                   | 9.35.0   |
+| [Prettier]                       | Code formatting           | 3.6.2    |
+
+## Non-functional Requirements
+
+Non-functional requirement for the project are:
+
+| Quality Attribute | Description                                                                                                                                                                         | Target                                                     |
+| ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------- |
+| Performance       | Transaction Response Time                                                                                                                                                           | 2 seconds                                                  |
+| Availability      | System Uptime                                                                                                                                                                       | 99.9                                                       |
+| Throughput        | Number of requests/transactions per second at peak time                                                                                                                             | 1000 RPS                                                   |
+| Auditability      | Ability of the application to show what has happened to it, who did it and when                                                                                                     | A log file that captures the event with the timestamp      |
+| Reliability       | Mean time to recovery                                                                                                                                                               | System should be able to recover from failure under 5 mins |
+| Usability         | Usability can be described as the capacity of a system to provide a condition for its users to perform the tasks safely, effectively, and efficiently while enjoying the experience | Browsers: Chrome, IE, Firefox                              |
+
+## Services
+
+The list of services we will use to build the application are as follows:
+
+| Service       | Description   | Version |
+| ------------- | ------------- | ------- |
+| [Meilisearch] | Search engine | 1.22.3  |
+
+HLD for the services is available in the [web excalidraw](https://excalidraw.com/#room=605670133765d25f7dad,ilvMr8eaNTosJ5krQmHY9A) file.
+
+## Project Structure Documentation
+
+The project structure is documented in multiple files for better organization:
+
+- **[FolderStructure.md](./FolderStructure.md)** — High-level architecture overview, key concepts, and folder organization
+- **[ProjectTreeFolder.md](./ProjectTreeFolder.md)** — Complete file-by-file breakdown of the entire repository
+- **[FileTypes.md](./FileTypes.md)** — Detailed file naming conventions and patterns
diff --git a/Documentation/Guidelines/architecture/FileTypes.md b/Documentation/Guidelines/architecture/FileTypes.md
new file mode 100644
index 0000000..866e0bd
--- /dev/null
+++ b/Documentation/Guidelines/architecture/FileTypes.md
@@ -0,0 +1,974 @@
+# File Types and Naming Conventions
+
+## Overview
+
+This document provides a comprehensive guide to the file naming conventions and architectural patterns used throughout the DyingStar codebase. Each file type serves a specific purpose and follows strict conventions to maintain code organization, readability, and maintainability.
+
+---
+
+## Table of Contents
+
+1. [File Type Reference](#file-type-reference)
+2. [Detailed Explanations](#detailed-explanations)
+3. [Directory Structure Patterns](#directory-structure-patterns)
+4. [Path Aliases](#path-aliases)
+5. [Best Practices](#best-practices)
+
+---
+
+## File Type Reference
+
+Quick reference table for all file types:
+
+| Extension/Pattern    | Purpose                                             | Location                                                       | Example                            |
+| -------------------- | --------------------------------------------------- | -------------------------------------------------------------- | ---------------------------------- |
+| `*.tsx`              | React components with JSX                           | `src/components/`, `src/features/`, `app/`                     | `button.tsx`, `header.tsx`         |
+| `*.ts`               | Pure TypeScript logic (utilities, configs, helpers) | `src/lib/`, `src/hooks/`, `src/i18n/`, `src/features/`, `app/` | `utils.ts`, `logger.ts`            |
+| `*.model.ts`         | Type definitions and Zod schemas                    | Any `src/` subdirectory                                        | `navigation.model.ts`              |
+| `*.hook.ts`          | Custom React hooks (outside `src/hooks/`)           | `src/features/*/`                                              | `use-news-filter.hook.ts`          |
+| `*.link.ts`          | Navigation link logic and definitions               | `src/features/navigation/`                                     | `footer.link.tsx`, `Links.ts`      |
+| `*.query.ts`         | Prisma database queries                             | `src/lib/queries/`                                             | `user.query.ts`                    |
+| `*.query.hook.ts`    | TanStack Query (React Query) queries                | `src/features/*/`                                              | `news.query.hook.ts`               |
+| `*.mutation.hook.ts` | TanStack Query mutations                            | `src/features/*/`                                              | `create-user.mutation.hook.ts`     |
+| `*.action.ts`        | Server actions (Next.js Server Actions)             | `src/lib/actions/`                                             | `newsletter.action.ts`             |
+| `*.mdx`              | Markdown with JSX for content-driven pages          | `content/news/`, `app/`                                        | `demo.mdx`                         |
+| `*.config.ts`        | Configuration files                                 | Root, `src/i18n/`                                              | `next.config.ts`, `site-config.ts` |
+| `middleware.ts`      | Next.js middleware (routing, i18n, auth)            | Root, `src/`                                                   | `middleware.ts`                    |
+| `layout.tsx`         | Next.js layouts                                     | `app/` segments                                                | `layout.tsx`                       |
+| `page.tsx`           | Next.js pages/routes                                | `app/` segments                                                | `page.tsx`                         |
+| `loading.tsx`        | Next.js loading UI                                  | `app/` segments                                                | `loading.tsx`                      |
+| `error.tsx`          | Next.js error boundaries                            | `app/` segments                                                | `error.tsx`, `global-error.tsx`    |
+| `not-found.tsx`      | Next.js 404 pages                                   | `app/` segments                                                | `not-found.tsx`                    |
+| `route.ts`           | Next.js API routes                                  | `app/api/`                                                     | `route.ts`                         |
+
+---
+
+## Detailed Explanations
+
+### 1. `*.tsx` - React Components
+
+**Purpose**: Files containing React components that use JSX syntax.
+
+**Location**:
+
+- `src/components/` - Reusable UI components
+- `src/features/` - Feature-specific components
+- `app/` - Next.js App Router pages and layouts
+
+**Conventions**:
+
+- Use PascalCase for component names
+- Use camelCase for file names
+- One primary component per file
+- Export component and related types
+
+**Example**:
+
+```tsx
+// src/components/ui/button.tsx
+import * as React from "react";
+
+import { cn } from "@lib/utils";
+import { Slot } from "@radix-ui/react-slot";
+import { type VariantProps, cva } from "class-variance-authority";
+
+const buttonVariants = cva("justify-center... inline-flex items-center", {
+  variants: {
+    variant: {
+      default: "text-primary-foreground... bg-primary",
+      destructive: "text-white... bg-destructive",
+    },
+    size: {
+      default: "px-6 py-2",
+      sm: "px-5 py-2",
+    },
+  },
+});
+
+export type ButtonProps = React.ComponentProps<"button"> &
+  VariantProps<typeof buttonVariants> & {
+    asChild?: boolean;
+  };
+
+function Button({
+  className,
+  variant,
+  size,
+  asChild = false,
+  ...props
+}: ButtonProps) {
+  const Comp = asChild ? Slot : "button";
+  return (
+    <Comp
+      className={cn(buttonVariants({ variant, size, className }))}
+      {...props}
+    />
+  );
+}
+
+export { Button, buttonVariants };
+```
+
+**Usage Scenarios**:
+
+- UI components (buttons, inputs, cards)
+- Layout components (headers, footers, sidebars)
+- Feature components (news items, forms, dialogs)
+- Page components in the App Router
+
+---
+
+### 2. `*.ts` - Pure TypeScript Logic
+
+**Purpose**: Pure TypeScript files without JSX, containing business logic, utilities, configurations, or helper functions.
+
+**Location**:
+
+- `src/lib/` - Core utilities and libraries
+- `src/hooks/` - React hooks
+- `src/i18n/` - Internationalization logic
+- Root directory - Configuration files
+
+**Conventions**:
+
+- Use camelCase for file names (except configs)
+- Pure functions without side effects (when possible)
+- No React or JSX imports
+- Thoroughly documented with JSDoc
+
+**Example**:
+
+```ts
+// src/lib/utils.ts
+import { type ClassValue, clsx } from "clsx";
+import { twMerge } from "tailwind-merge";
+
+/**
+ * Combines class names using clsx and merges Tailwind classes
+ */
+export function cn(...inputs: ClassValue[]) {
+  return twMerge(clsx(inputs));
+}
+```
+
+**Usage Scenarios**:
+
+- Utility functions (`utils.ts`, `format.ts`)
+- Configuration (`site-config.ts`, `routing.ts`)
+- Non-React helpers (`logger.ts`, `server-url.ts`)
+
+---
+
+### 3. `*.model.ts` - Type Definitions and Schemas
+
+**Purpose**: Dedicated files for TypeScript type definitions and Zod validation schemas. This pattern centralizes type safety and runtime validation.
+
+**Location**: Any `src/` subdirectory, typically alongside related logic
+
+**Conventions**:
+
+- Define both Zod schemas and TypeScript types
+- Export schemas and infer types from them
+- Group related types logically
+- Use clear, descriptive region comments
+
+**Example**:
+
+```ts
+// src/features/issue/get/IssuesCount.model.ts
+import type { FacetHit } from "meilisearch";
+import { z } from "zod";
+
+export const IssuesCountSchema = z.object({
+  openIssueCount: z.number(),
+  openIssueWithAssigneeCount: z.number(),
+  countByProject: z.array(z.custom<FacetHit>()),
+});
+
+export type IssuesCountType = z.infer<typeof IssuesCountSchema>;
+```
+
+**Why This Pattern**:
+
+- **Type Safety**: Compile-time type checking via TypeScript
+- **Runtime Validation**: Zod schemas validate data at runtime
+- **Single Source of Truth**: Types are inferred from schemas
+- **Documentation**: Schemas serve as self-documenting contracts
+
+**Usage Scenarios**:
+
+- API response/request types
+- Component prop types
+- Database model types
+- Form validation schemas
+
+---
+
+### 4. `*.hook.ts` - Custom React Hooks (Feature-Specific)
+
+**Purpose**: Custom React hooks that are specific to a feature and not general enough to belong in `src/hooks/`.
+
+**Location**: Within feature directories (`src/features/*/`)
+
+**Conventions**:
+
+- File name should match hook name
+- Use `use` prefix for hook functions
+- Export one primary hook per file
+- Include TypeScript types for parameters and return values
+
+**Example**:
+
+```ts
+// src/features/news/use-news-filter.hook.ts
+import { useMemo, useState } from "react";
+
+import type { NewsItem } from "./news.type";
+
+export function useNewsFilter(items: NewsItem[]) {
+  const [searchTerm, setSearchTerm] = useState("");
+  const [category, setCategory] = useState<string | null>(null);
+
+  const filteredItems = useMemo(() => {
+    return items.filter((item) => {
+      const matchesSearch = item.title
+        .toLowerCase()
+        .includes(searchTerm.toLowerCase());
+      const matchesCategory = !category || item.category === category;
+      return matchesSearch && matchesCategory;
+    });
+  }, [items, searchTerm, category]);
+
+  return {
+    filteredItems,
+    searchTerm,
+    setSearchTerm,
+    category,
+    setCategory,
+  };
+}
+```
+
+**Difference from `src/hooks/`**:
+
+- `src/hooks/*.ts` - General-purpose, reusable across features
+- `*.hook.ts` - Feature-specific, co-located with feature code
+
+**Usage Scenarios**:
+
+- Feature-specific state management
+- Complex component logic extraction
+- Business logic hooks tied to a feature
+
+---
+
+### 5. `*.link.ts` / `*.link.tsx` - Navigation Link Definitions
+
+**Purpose**: Centralized navigation link definitions and logic, providing type-safe routing throughout the application.
+
+**Location**: `src/features/navigation/`
+
+**Conventions**:
+
+- Define link structure with params
+- Use link generator functions for dynamic routes
+- Export typed link objects
+- Support both static and parameterized links
+
+**Example**:
+
+```ts
+// src/features/navigation/Links.ts
+import { z } from "zod";
+
+import type { NavigationLink } from "./navigation.type";
+
+const PATHS = {
+  NEWS: `/news/:newsSlug`,
+};
+
+export const EmptyLinkParamsSchema = z.object({}).strict();
+
+export const NewsLinkParamsSchema = EmptyLinkParamsSchema.extend({
+  newsSlug: z.string(),
+}).strict();
+
+// Utility to create link generators
+const createLinkGenerator = (path: string, needsParams = false) => {
+  if (!needsParams) {
+    return () => path;
+  }
+
+  return (params: Record<string, string> = {}) => {
+    let result = path;
+    Object.entries(params).forEach(([key, value]) => {
+      result = result.replace(`:${key}`, value);
+    });
+    return result;
+  };
+};
+
+const createLink = (
+  href: string,
+  label: string,
+  options: Partial<Omit<NavigationLink, "href" | "label">> = {},
+  needsParams = false,
+): NavigationLink => ({
+  href: createLinkGenerator(href, needsParams),
+  label,
+  ...options,
+});
+
+export const LINKS = {
+  Landing: {
+    Landing: createLink("/", "Project", undefined, false),
+  },
+  News: {
+    All: createLink("/news", "All News", undefined, false),
+    News: createLink(`${PATHS.NEWS}`, "News", { Icon: Info }, true),
+  },
+};
+```
+
+**Benefits**:
+
+- Type-safe navigation
+- Centralized route definitions
+- Easy refactoring (change route in one place)
+- Auto-complete for links throughout the app
+
+**Usage Scenarios**:
+
+- Navigation menus
+- Footer links
+- Programmatic navigation
+- Link generation with parameters
+
+---
+
+### 6. `*.query.ts` - Prisma Database Queries
+
+**Purpose**: Encapsulates Prisma database queries in reusable, testable functions.
+
+**Location**: `src/lib/queries/` or within feature directories
+
+**Conventions**:
+
+- One query function per operation
+- Use descriptive function names
+- Include error handling
+- Return typed results
+
+**Example**:
+
+```ts
+// src/lib/queries/user.query.ts
+import { prisma } from "@lib/prisma";
+import type { User } from "@prisma/client";
+
+export async function getUserById(userId: string): Promise<User | null> {
+  return prisma.user.findUnique({
+    where: { id: userId },
+    include: {
+      profile: true,
+    },
+  });
+}
+
+export async function getUsersByRole(role: string): Promise<User[]> {
+  return prisma.user.findMany({
+    where: { role },
+    orderBy: { createdAt: "desc" },
+  });
+}
+```
+
+**Why Separate Query Files**:
+
+- **Testability**: Easy to mock in tests
+- **Reusability**: Share queries across features
+- **Maintainability**: Database logic in one place
+- **Performance**: Optimize queries independently
+
+---
+
+### 7. `*.query.hook.ts` - TanStack Query (React Query)
+
+**Purpose**: React hooks that use TanStack Query for server state management, caching, and synchronization.
+
+**Location**: Within feature directories
+
+**Conventions**:
+
+- Use `useQuery` from TanStack Query
+- Define query keys at the top
+- Include proper TypeScript types
+- Handle loading and error states
+
+**Example**:
+
+```ts
+// src/features/news/news.query.hook.ts
+import { useQuery } from "@tanstack/react-query";
+
+import type { NewsItem } from "./news.type";
+
+// Query keys
+export const newsKeys = {
+  all: ["news"] as const,
+  lists: () => [...newsKeys.all, "list"] as const,
+  list: (filters: string) => [...newsKeys.lists(), { filters }] as const,
+  details: () => [...newsKeys.all, "detail"] as const,
+  detail: (slug: string) => [...newsKeys.details(), slug] as const,
+};
+
+// Fetch function
+async function fetchNewsItem(slug: string): Promise<NewsItem> {
+  const res = await fetch(`/api/news/${slug}`);
+  if (!res.ok) throw new Error("Failed to fetch news");
+  return res.json();
+}
+
+// React Query hook
+export function useNewsItem(slug: string) {
+  return useQuery({
+    queryKey: newsKeys.detail(slug),
+    queryFn: () => fetchNewsItem(slug),
+    staleTime: 5 * 60 * 1000, // 5 minutes
+  });
+}
+```
+
+**Benefits**:
+
+- Automatic caching
+- Background refetching
+- Optimistic updates
+- Request deduplication
+
+---
+
+### 8. `*.mutation.hook.ts` - TanStack Query Mutations
+
+**Purpose**: React hooks for data mutations (create, update, delete) using TanStack Query.
+
+**Location**: Within feature directories
+
+**Conventions**:
+
+- Use `useMutation` from TanStack Query
+- Include optimistic updates
+- Invalidate relevant queries
+- Handle success/error callbacks
+
+**Example**:
+
+```ts
+// src/features/news/create-news.mutation.hook.ts
+import { useMutation, useQueryClient } from "@tanstack/react-query";
+
+import { newsKeys } from "./news.query.hook";
+import type { CreateNewsInput, NewsItem } from "./news.type";
+
+async function createNews(data: CreateNewsInput): Promise<NewsItem> {
+  const res = await fetch("/api/news", {
+    method: "POST",
+    headers: { "Content-Type": "application/json" },
+    body: JSON.stringify(data),
+  });
+  if (!res.ok) throw new Error("Failed to create news");
+  return res.json();
+}
+
+export function useCreateNews() {
+  const queryClient = useQueryClient();
+
+  return useMutation({
+    mutationFn: createNews,
+    onSuccess: () => {
+      // Invalidate and refetch news list
+      queryClient.invalidateQueries({ queryKey: newsKeys.lists() });
+    },
+  });
+}
+```
+
+**Usage**:
+
+```tsx
+function CreateNewsForm() {
+  const createNews = useCreateNews();
+
+  const handleSubmit = (data: CreateNewsInput) => {
+    createNews.mutate(data, {
+      onSuccess: () => {
+        toast.success("News created!");
+      },
+    });
+  };
+
+  return <form onSubmit={handleSubmit}>...</form>;
+}
+```
+
+---
+
+### 9. `*.action.ts` - Next.js Server Actions
+
+**Purpose**: Server-side functions that can be called from client components, providing type-safe RPC-style endpoints.
+
+**Location**: `src/lib/actions/` or within feature directories
+
+**Conventions**:
+
+- Use `"use server"` directive
+- Use `next-safe-action` for validation
+- Define input schemas with Zod
+- Handle errors gracefully
+
+**Example**:
+
+```ts
+// src/lib/actions/newsletter.action.ts
+"use server";
+
+import { action } from "@lib/actions/safe-actions";
+import { z } from "zod";
+
+// src/lib/actions/newsletter.action.ts
+
+const subscribeNewsletterSchema = z.object({
+  email: z.string().email(),
+  name: z.string().optional(),
+});
+
+export const subscribeNewsletter = action
+  .inputSchema(subscribeNewsletterSchema)
+  .action(async ({ parsedInput: { email, name } }) => {
+    // Add to newsletter service
+    await addToMailingList(email, name);
+
+    return { success: true, message: "Successfully subscribed!" };
+  });
+```
+
+**Usage in Client Component**:
+
+```tsx
+"use client";
+
+import { subscribeNewsletter } from "@lib/actions/newsletter.action";
+
+export function NewsletterForm() {
+  const [, execute, isPending] = useAction(subscribeNewsletter);
+
+  const handleSubmit = async (formData: FormData) => {
+    const result = await execute({
+      email: formData.get("email") as string,
+    });
+
+    if (result.data?.success) {
+      toast.success(result.data.message);
+    }
+  };
+
+  return <form action={handleSubmit}>...</form>;
+}
+```
+
+**Benefits**:
+
+- Type-safe client-server communication
+- Automatic validation
+- No need for API routes for simple operations
+- Direct database access from actions
+
+---
+
+### 10. `*.mdx` - Markdown with JSX
+
+**Purpose**: Content-driven pages that combine Markdown for text content with React components for interactive elements.
+
+**Location**:
+
+- `content/news/` - Editorial content (articles, blog posts)
+- `app/` - Static/semi-static pages
+
+**Conventions**:
+
+- Frontmatter for metadata
+- Localized content (separate files per language)
+- Use JSX components when needed
+
+**Example**:
+
+````mdx
+---
+title: Introducing Our New Feature
+titleIcon: 🎉
+category: announcement
+description: We're excited to announce a new feature that will change how you work
+keywords:
+  - feature
+  - announcement
+  - update
+tags:
+  - product
+  - release
+coverUrl: https://example.com/cover.jpg
+date: 2025-01-15T10:00:00
+author: Team DyingStar
+authorRoles:
+  - Product Manager
+---
+
+# Introducing Our New Feature
+
+We're thrilled to announce our latest feature!
+
+## What's New
+
+Here's what you can expect:
+
+- **Feature 1**: Description
+- **Feature 2**: Description
+
+```ts
+// Code example
+const example = "You can include code blocks";
+```
+````
+
+<CustomComponent prop="value" />
+
+## Get Started
+
+Try it out today!
+
+````
+
+**Processing Pipeline**:
+1. MDX file stored in `content/`
+2. Parsed by `features/markdown/`
+3. Managed by feature-specific manager (e.g., `news-manager.ts`)
+4. Rendered in App Router pages
+5. Metadata extracted for SEO
+
+**Benefits**:
+- Easy content authoring
+- Mix static content with dynamic components
+- Type-safe component usage
+- Great for non-technical content editors
+
+---
+
+### 11. Configuration Files
+
+#### `site-config.ts`
+
+**Purpose**: Central configuration for site-wide settings.
+
+**Example**:
+
+```ts
+// src/site-config.ts
+export const SiteConfig = {
+  title: "Dying Star",
+  description: "Collect and showcase powerful video and text testimonials",
+  prodUrl: "https://demo.dyingstar.app",
+  appId: "dyingstar",
+  domain: "demo.dyingstar.app",
+  appIcon: "/images/icon.png",
+};
+````
+
+#### `middleware.ts`
+
+**Purpose**: Next.js middleware for request interception and modification.
+
+**Example**:
+
+```ts
+// middleware.ts
+import { routing } from "i18n/routing";
+import createMiddleware from "next-intl/middleware";
+
+export default createMiddleware(routing);
+
+export const config = {
+  matcher: [
+    "/((?!api|_next/static|_next/image|favicon.ico|sitemap.xml|robots.txt).*)",
+  ],
+  runtime: "nodejs",
+};
+```
+
+---
+
+### 12. Next.js App Router Special Files
+
+#### `layout.tsx`
+
+**Purpose**: Shared UI that wraps pages within a route segment.
+
+**Key Features**:
+
+- Persists across navigation
+- Can fetch data
+- Can be nested
+
+**Example**:
+
+```tsx
+// app/[locale]/layout.tsx
+export default function LocaleLayout({
+  children,
+  params: { locale },
+}: {
+  children: React.ReactNode;
+  params: { locale: string };
+}) {
+  return (
+    <html lang={locale}>
+      <body>
+        <Header />
+        {children}
+        <Footer />
+      </body>
+    </html>
+  );
+}
+```
+
+#### `page.tsx`
+
+**Purpose**: Unique UI for a route.
+
+**Example**:
+
+```tsx
+// app/[locale]/(landing)/page.tsx
+export default function LandingPage() {
+  return (
+    <main>
+      <Hero />
+      <Features />
+      <CTA />
+    </main>
+  );
+}
+```
+
+#### `loading.tsx`
+
+**Purpose**: Loading UI shown during Suspense boundaries.
+
+**Example**:
+
+```tsx
+// app/[locale]/news/loading.tsx
+export default function NewsLoading() {
+  return <Skeleton className="h-screen" />;
+}
+```
+
+#### `error.tsx`
+
+**Purpose**: Error UI for error boundaries.
+
+**Example**:
+
+```tsx
+// app/[locale]/news/error.tsx
+"use client";
+
+export default function NewsError({
+  error,
+  reset,
+}: {
+  error: Error;
+  reset: () => void;
+}) {
+  return (
+    <div>
+      <h2>Something went wrong!</h2>
+      <button onClick={reset}>Try again</button>
+    </div>
+  );
+}
+```
+
+#### `not-found.tsx`
+
+**Purpose**: 404 UI for when `notFound()` is called.
+
+**Example**:
+
+```tsx
+// app/[locale]/not-found.tsx
+export default function NotFound() {
+  return (
+    <div>
+      <h2>404 - Page Not Found</h2>
+      <Link href="/">Go home</Link>
+    </div>
+  );
+}
+```
+
+---
+
+## Directory Structure Patterns
+
+### Feature-Based Organization
+
+The codebase follows a feature-based architecture where related files are co-located:
+
+```
+src/features/news/
+├── news.model.ts              # Types and schemas
+├── news-manager.ts           # Core business logic
+├── news.query.hook.ts        # Data fetching
+├── NewsItem.tsx              # Component
+├── NewsItemLight.tsx         # Variant component
+└── use-news-filter.hook.ts   # Feature-specific hook
+```
+
+### Component Organization
+
+```
+src/components/
+├── DS/                       # Design System
+│   ├── layout/
+│   │   ├── header.tsx
+│   │   ├── footer.tsx
+│   │   └── footer.link.tsx
+│   ├── CTA/
+│   └── typography.tsx
+├── ui/                       # shadcn/ui components
+│   ├── button.tsx
+│   ├── input.tsx
+│   └── dialog.tsx
+└── utils/                    # Component utilities
+```
+
+### Library Organization
+
+```
+src/lib/
+├── actions/
+│   ├── safe-actions.ts       # Action client setup
+│   └── actions-utils.ts      # Action utilities
+├── errors/
+│   ├── application-error.ts
+│   └── action-error.ts
+├── format/
+│   ├── date.ts
+│   └── display-name.ts
+└── utils.ts                  # General utilities
+```
+
+---
+
+## Path Aliases
+
+The project uses TypeScript path aliases for clean imports:
+
+```json
+{
+  "paths": {
+    "@components/*": ["components/*"],
+    "@feat/*": ["features/*"],
+    "@hooks/*": ["hooks/*"],
+    "@i18n/*": ["i18n/*"],
+    "@lib/*": ["lib/*"],
+    "@type/*": ["types/*"],
+    "@ui/*": ["components/ui/*"]
+  }
+}
+```
+
+**Usage**:
+
+```tsx
+// Instead of:
+import { Button } from "../../../components/ui/button";
+
+// Use:
+import { Button } from "@ui/button";
+```
+
+---
+
+## Best Practices
+
+### 1. **Single Responsibility**
+
+- One file, one purpose
+- Keep files focused and small
+- Extract complex logic into separate files
+
+### 2. **Type Safety**
+
+- Always use TypeScript
+- Define types in `*.model.ts` files
+- Use Zod for runtime validation
+
+### 3. **Co-location**
+
+- Keep related files together
+- Feature files in feature directories
+- Types next to their implementation
+
+### 4. **Naming Consistency**
+
+- Follow file naming conventions strictly
+- Use descriptive names
+- Match file name to primary export
+
+### 5. **Documentation**
+
+- Add JSDoc comments to public APIs
+- Document complex logic
+- Include usage examples
+
+### 6. **Separation of Concerns**
+
+- UI components separate from business logic
+- Data fetching separate from presentation
+- Server code separate from client code
+
+### 7. **Import Organization**
+
+- External imports first
+- Internal imports second
+- Use path aliases
+- Group imports logically
+
+### 8. **Avoid Circular Dependencies**
+
+- Be mindful of import chains
+- Use dependency injection when needed
+- Extract shared code to common locations
+
+---
+
+## Summary
+
+This file type system creates a highly organized, scalable, and maintainable codebase:
+
+- **Clear Separation**: Each file type has a distinct purpose
+- **Type Safety**: TypeScript and Zod ensure correctness
+- **Co-location**: Related code lives together
+- **Discoverability**: Naming conventions make files easy to find
+- **Scalability**: Pattern supports growth without chaos
+
+By following these conventions, developers can:
+
+- Quickly understand code structure
+- Locate relevant files instantly
+- Maintain consistency across the codebase
+- Onboard new team members efficiently
+- Scale the application confidently
+
+---
diff --git a/Documentation/Guidelines/architecture/FolderStructure.md b/Documentation/Guidelines/architecture/FolderStructure.md
new file mode 100644
index 0000000..c48fdb3
--- /dev/null
+++ b/Documentation/Guidelines/architecture/FolderStructure.md
@@ -0,0 +1,111 @@
+# Folder Structure
+
+The project follows the Next.js 15 **App Router** architecture with a clear separation between routing (`app/`), business logic (`src/`), and content (`content/`).
+
+## Global Structure
+
+```
+dying-star/
+├── 📁 app/                    # Next.js App Router - Routing and layouts
+├── 📁 src/                    # Source code - Business logic
+├── 📁 content/                # Editorial content (MDX)
+├── 📁 public/                 # Static assets
+├── 📁 messages/               # i18n translations
+├── 📁 docker/                 # Docker configuration
+├── 📁 Documentation/          # Internal documentation
+├── 📄 middleware.ts           # Next.js global middleware
+├── 📄 next.config.ts          # Next.js configuration
+├── 📄 tsconfig.json           # TypeScript configuration
+└── 📄 package.json            # Dependencies
+```
+
+## 📁 `app/` - Next.js App Router
+
+Handles **routing**, **layouts**, and **entry points** of the application following Next.js 15 conventions.
+
+```
+app/
+├── 📁 [locale]/               # Internationalized routes (en, fr, etc.)
+│   ├── 📁 (layout)/           # Route group - Static pages
+│   │   └── 📁 pageName/       # Page folder
+│   |       └── 📁 _components/ # Components folder
+│   ├── 📁 @modal/             # Parallel route - Modal system with intercepting routes
+│   └── 📁 docs/               # User documentation with dynamic pages
+```
+
+**Key Concepts:**
+
+- **Route Groups** `(name)`: Organize without affecting URL
+- **Parallel Routes** `@modal`: Display multiple pages simultaneously
+- **Intercepting Routes**: Modals that preserve history
+- **Dynamic Routes** `[slug]`: Parameterized routes
+
+## 📁 `src/` - Application source code
+
+Contains all **business logic**, **components**, and **utilities** following a feature-based architecture.
+
+```
+src/
+├── 📁 components/             # Reusable UI components
+├── 📁 features/               # Business features (vertical slices)
+├── 📁 hooks/                  # Cross-cutting React hooks
+├── 📁 i18n/                   # i18n configuration (config, routing, navigation, request)
+├── 📁 lib/                    # Libraries and utilities
+└── 📁 types/                  # Global TypeScript types
+```
+
+**Feature-based architecture:**
+
+- Each feature in `features/` is **autonomous** and contains its logic, components, types
+- Clear separation between **UI** (`components/`), **logic** (`features/`), **utilities** (`lib/`, `hooks/`)
+
+## 📁 `content/` - Editorial content
+
+MDX files (Markdown + JSX) for dynamic content organized by locale.
+
+## 📁 `public/` - Static assets
+
+Static files served directly by Next.js.
+
+**Access:** `/images/logo.png` → `public/images/logo.png`
+
+## 📁 `messages/` - i18n translations
+
+Translation dictionaries for internationalization.
+
+```
+messages/                      # JSON translation files per locale (en.json, fr.json)
+```
+
+**Usage:**
+
+```tsx
+import { useTranslations } from "next-intl";
+
+const t = useTranslations("namespace");
+```
+
+## 📁 `docker/` - Containerization
+
+Docker configuration for development and production environments.
+
+```
+docker/                        # Dockerfile.dev, Dockerfile.prod, docker-compose.yml
+```
+
+## 📁 `Documentation/` - Internal documentation
+
+Project documentation, guidelines, and ADRs.
+
+```
+Documentation/
+└── 📁 Guidelines/
+    ├── 📁 architecture/       # Architecture docs and ADRs
+    └── 📁 pictures/           # Documentation images
+```
+
+## References
+
+- [Next.js App Router](https://nextjs.org/docs/app)
+- [Next.js Project Structure](https://nextjs.org/docs/getting-started/project-structure)
+- [Complete structure details](./projectTreeFolder.md)
diff --git a/Documentation/Guidelines/architecture/ProjectTreeFolder.md b/Documentation/Guidelines/architecture/ProjectTreeFolder.md
new file mode 100644
index 0000000..ae2901a
--- /dev/null
+++ b/Documentation/Guidelines/architecture/ProjectTreeFolder.md
@@ -0,0 +1,495 @@
+# Project Tree - Complete File Structure
+
+This document provides a detailed file-by-file breakdown of the entire repository structure.
+
+For a high-level overview, see [FolderStructure.md](./FolderStructure.md).
+
+---
+
+## 📂 Root Directory
+
+### Configuration Files
+
+- **`.nvmrc`** — Node.js version specification (ensures consistency across environments)
+- **`.prettierrc`** — Code formatting rules for Prettier
+- **`components.json`** — Configuration for shadcn/ui component generator
+- **`eslint.config.mjs`** — ESLint rules (TypeScript, React, Next.js)
+- **`next.config.ts`** — Next.js framework configuration
+- **`next-env.d.ts`** — Next.js TypeScript declarations (auto-generated)
+- **`postcss.config.mjs`** — Tailwind CSS / PostCSS pipeline configuration
+- **`tsconfig.json`** — TypeScript configuration (path aliases, strict mode, compiler options)
+- **`tsconfig.tsbuildinfo`** — TypeScript build cache (auto-generated)
+
+### Package Management
+
+- **`package.json`** — Project dependencies and npm scripts
+- **`pnpm-lock.yaml`** — Lock file for pnpm (ensures reproducible installs)
+
+### Build & Development
+
+- **`Makefile`** — Development shortcuts and build commands (e.g., `make dev`, `make build`)
+- **`middleware.ts`** — Global Next.js middleware (runs before routing: i18n, auth, redirects)
+
+### Documentation & Legal
+
+- **`README.md`** — Project overview, quickstart guide, and useful links
+- **`LICENSE`** — Project license file
+
+---
+
+## 📂 app/ — Next.js App Router
+
+The routing layer of the application. Handles layouts, error boundaries, and entry points.
+
+### Root Level (app/)
+
+```
+app/
+├── layout.tsx              # Root HTML layout (html, body, theme provider, fonts)
+├── error.tsx               # Root error boundary
+├── global-error.tsx        # Global error fallback
+├── unauthorized.tsx        # Generic 401 unauthorized page
+├── sitemap.tsx             # Dynamic sitemap generation for SEO
+├── favicon.ico             # Browser favicon
+├── icon.png                # PWA icon
+└── apple-icon.png          # Apple touch icon
+```
+
+### Internationalized Routes (app/[locale]/)
+
+```
+app/[locale]/
+├── layout.tsx              # Locale-specific layout wrapper
+├── providers.tsx           # React context providers (theme, i18n, query client)
+├── not-found.tsx           # Locale-specific 404 page
+├── globals.css             # Global CSS styles (reset, design tokens, Tailwind imports)
+├── manifest.ts             # PWA manifest generator
+│
+├── (landing)/              # Route group: Landing page
+│   └── page.tsx            # Home/landing page
+│
+├── (layout)/               # Route group: Public static pages
+│   ├── about/
+│   │   └── page.tsx        # About page
+│   │
+│   ├── legal/
+│   │   ├── privacy/
+│   │   │   └── page.tsx    # Privacy policy page
+│   │   └── terms/
+│   │       └── page.tsx    # Terms & conditions page
+│   │
+│   ├── news/
+│   │   ├── page.tsx        # News listing page
+│   │   ├── loading.tsx     # Loading state for news pages
+│   │   └── [slug]/
+│   │       ├── page.tsx    # Individual news article page
+│   │       ├── error.tsx   # Error boundary for article pages
+│   │       ├── not-found.tsx  # 404 for missing articles
+│   │       └── newsSlugMetadataImage.tsx  # Dynamic OG image generator
+│   │
+│   └── not-found/
+│       └── page.tsx        # Custom 404 page in layout segment
+│
+├── (logged-in)/            # Route group: Protected pages (requires auth)
+│   ├── error.tsx           # Error boundary for authenticated pages
+│   ├── not-found.tsx       # 404 for authenticated section
+│   └── unauthorized.tsx    # 401 for logged-in section
+│
+├── @modal/                 # Parallel route: Modal system
+│   ├── [...catchAll]/
+│   │   └── page.tsx        # Catch-all for intercepted routes
+│   └── default.tsx         # Default empty slot when no modal active
+│
+└── docs/                   # Documentation section
+    ├── layout.tsx          # Docs layout with sidebar
+    ├── page.tsx            # Docs home page
+    ├── doc-manager.ts      # Logic for loading and parsing docs
+    ├── [slug]/
+    │   └── page.tsx        # Dynamic doc pages
+    └── _components/
+        └── doc-sidebar.tsx # Documentation sidebar component
+```
+
+**Key Concepts:**
+
+- **Route Groups** `(name)`: Organize routes without affecting URL structure
+- **Parallel Routes** `@modal`: Render multiple pages simultaneously (modal overlays)
+- **Intercepting Routes**: Modals that preserve navigation history
+- **Dynamic Routes** `[slug]`: Parameterized routes for dynamic content
+
+---
+
+## 📂 src/ — Application Source Code
+
+All business logic, components, features, and utilities.
+
+### src/components/ — Reusable UI Components
+
+```
+src/components/
+├── DS/                     # DyingStar Design System (project-specific components)
+│   ├── automatic-pagination.tsx
+│   ├── divider.tsx
+│   ├── grid-background.tsx
+│   ├── keyboard-shortcut.tsx
+│   ├── loader.tsx
+│   ├── logo.tsx
+│   ├── typography.tsx
+│   │
+│   ├── CTA/                # Call-to-action components
+│   │   └── ...
+│   │
+│   ├── layout/             # Layout components
+│   │   ├── base-layout.tsx
+│   │   ├── header.tsx
+│   │   ├── header-base.tsx
+│   │   ├── footer.tsx
+│   │   └── footer.link.tsx
+│   │
+│   ├── legal/              # Legal components (floating footer, etc.)
+│   │   └── ...
+│   │
+│   └── TODO/               # Work-in-progress components
+│       └── ...
+│
+├── ui/                     # shadcn/ui components (primitive UI elements)
+│   ├── accordion.tsx
+│   ├── alert.tsx
+│   ├── alert-dialog.tsx
+│   ├── aspect-ratio.tsx
+│   ├── avatar.tsx
+│   ├── badge.tsx
+│   ├── breadcrumb.tsx
+│   ├── button.tsx
+│   ├── card.tsx
+│   ├── chart.tsx
+│   ├── checkbox.tsx
+│   ├── collapsible.tsx
+│   ├── command.tsx
+│   ├── dialog.tsx
+│   ├── dropdown-menu.tsx
+│   ├── form.tsx
+│   ├── input.tsx
+│   ├── input-otp.tsx
+│   ├── label.tsx
+│   ├── pagination.tsx
+│   ├── popover.tsx
+│   ├── progress.tsx
+│   ├── radio-group.tsx
+│   ├── select.tsx
+│   ├── separator.tsx
+│   ├── sheet.tsx
+│   ├── sidebar.tsx
+│   ├── skeleton.tsx
+│   ├── sonner.tsx
+│   ├── switch.tsx
+│   ├── table.tsx
+│   ├── tabs.tsx
+│   ├── textarea.tsx
+│   ├── toggle.tsx
+│   └── tooltip.tsx
+│
+├── svg/                    # SVG React components
+│   └── ...
+│
+└── utils/                  # Visual utility components
+    ├── intercept-dialog/   # Intercepting route dialog utilities
+    └── tailwind-indicator/ # Dev mode visual indicator for responsive breakpoints
+```
+
+### src/features/ — Business Features (Vertical Slices)
+
+Each feature is self-contained with its own logic, components, and types.
+
+```
+src/features/
+├── dialog-manager/         # Global dialog system
+│   ├── dialog-factory.tsx  # Dialog component factory
+│   ├── dialog-renderer.tsx # Dialog rendering logic
+│   ├── dialog-store.ts     # Zustand store for dialog state
+│   └── dialog.type.ts      # Dialog type definitions
+│
+├── form/                   # Form utilities
+│   ├── auto-save-form.tsx  # Auto-save form wrapper
+│   └── submit-button.tsx   # Enhanced submit button with loading states
+│
+├── global-dialog/          # Pre-configured global dialogs
+│   └── ...
+│
+├── i18n/                   # Internationalization UI
+│   └── LocaleSwitcher.tsx  # Language switcher component
+│
+├── landing/                # Landing page features
+│   ├── landing-CTA.tsx     # Landing page CTAs
+│   └── landing-layout.tsx  # Landing page layout wrapper
+│
+├── markdown/               # Markdown/MDX rendering
+│   ├── client-markdown.tsx # Client-side markdown renderer
+│   ├── server-mdx.tsx      # Server-side MDX renderer
+│   └── markdown.config.ts  # Markdown processing configuration
+│
+├── navigation/             # Navigation system
+│   ├── Links.ts            # Link definitions
+│   ├── navigation.type.ts  # Navigation type definitions
+│   ├── navigation-wrapper.tsx
+│   └── navigationLinks.tsx # Navigation link components
+│
+├── news/                   # News feature
+│   ├── NewsItem.tsx        # Full news item component
+│   ├── NewsItemLight.tsx   # Lightweight news item
+│   ├── news-manager.ts     # News loading and management
+│   └── calculate-reading-time.ts  # Reading time calculation
+│
+├── page/                   # Page utilities
+│   ├── error-page.tsx      # Error page templates
+│   ├── not-found-page.tsx  # 404 page template
+│   └── top-loader.tsx      # Top loading progress bar
+│
+└── server-sonner/          # Server-to-client toast notifications
+    └── ...
+```
+
+### src/hooks/ — Cross-cutting React Hooks
+
+```
+src/hooks/
+├── use-debounce-fn.ts              # Debounce function execution
+├── use-is-client.ts                # Client-side rendering detection
+├── use-mobile.ts                   # Mobile device detection
+├── use-warn-if-unsaved-changes.ts  # Prompt before leaving with unsaved changes
+└── useCurrentPath.ts               # Current pathname hook
+```
+
+### src/i18n/ — Internationalization Configuration
+
+```
+src/i18n/
+├── config.ts               # i18n configuration (locales, default locale)
+├── routing.ts              # Localized routing utilities
+├── navigation.ts           # i18n-aware navigation utilities
+└── request.ts              # Server-side locale detection
+```
+
+### src/lib/ — Libraries and Utilities
+
+```
+src/lib/
+├── actions/                # Server Actions utilities
+│   ├── safe-actions.ts     # Type-safe server action wrapper
+│   └── ...
+│
+├── env/                    # Environment variable validation
+│   ├── client.ts           # Client-side env vars (Zod validation)
+│   └── server.ts           # Server-side env vars (Zod validation)
+│
+├── errors/                 # Error types and handling
+│   ├── ActionError.ts      # Server action error type
+│   ├── ApplicationError.ts # Application error type
+│   └── ZodRouteError.ts    # Route validation error type
+│
+├── format/                 # Formatting utilities
+│   ├── date.ts             # Date formatting
+│   ├── display-name.ts     # Display name utilities
+│   └── id.ts               # ID generation and formatting
+│
+├── logger.ts               # Logging utility (tslog)
+├── metadata.ts             # Page metadata generator (SEO/OG tags)
+├── server-toast.tsx        # Server-to-client toast bridge
+├── server-url.ts           # Server-side URL generation
+├── utils.ts                # General utility functions (cn, etc.)
+└── zod-route.ts            # Route parameter validation with Zod
+```
+
+### src/types/ — Global TypeScript Types
+
+```
+src/types/
+└── next.ts                 # Next.js custom/extended type definitions
+```
+
+### Other src/ Files
+
+```
+src/
+├── middleware.ts           # Additional middleware (if needed beyond root)
+└── site-config.ts          # Central site configuration (name, links, social, feature flags)
+```
+
+---
+
+## 📂 content/ — Editorial Content
+
+MDX files for dynamic content, organized by locale.
+
+```
+content/
+└── news/                   # News articles
+    ├── en/                 # English articles
+    │   └── *.mdx           # Individual news articles (frontmatter + MDX)
+    └── fr/                 # French articles
+        └── *.mdx           # Individual news articles (frontmatter + MDX)
+```
+
+**MDX Structure:**
+
+- Frontmatter with metadata (title, date, author, category, etc.)
+- Markdown body with JSX components support
+- Parsed by `features/news/news-manager.ts`
+- Rendered by `features/markdown/`
+
+---
+
+## 📂 public/ — Static Assets
+
+Files served directly by Next.js without processing.
+
+```
+public/
+├── images/                 # Static images
+│   └── ...                 # Logos, backgrounds, illustrations
+│
+├── assets/                 # Other static assets
+│   └── ...
+│
+└── *.svg                   # Category icons for news
+    ├── immersion-landscape.svg
+    ├── news-architectes.svg
+    ├── news-archives.svg
+    ├── news-colonisation.svg
+    ├── news-expedition.svg
+    └── news-observatoire.svg
+```
+
+**Access:** Files in `public/` are served from root path  
+Example: `public/images/logo.png` → `/images/logo.png`
+
+---
+
+## 📂 messages/ — i18n Translation Dictionaries
+
+JSON translation files for internationalization (used by next-intl).
+
+```
+messages/
+├── en.json                 # English translations
+└── fr.json                 # French translations
+```
+
+**Structure:**
+
+```json
+{
+  "namespace": {
+    "key": "Translation value"
+  }
+}
+```
+
+**Usage:**
+
+```tsx
+import { useTranslations } from "next-intl";
+
+const t = useTranslations("namespace");
+```
+
+---
+
+## 📂 docker/ — Containerization
+
+Docker configuration for development and production environments.
+
+```
+docker/
+├── Dockerfile.dev          # Development Docker image
+├── Dockerfile.prod         # Production Docker image
+└── docker-compose.yml      # Local/preview orchestration
+```
+
+---
+
+## 📂 Documentation/ — Internal Documentation
+
+Project documentation, guidelines, processes, and Architecture Decision Records (ADRs).
+
+```
+Documentation/
+└── Guidelines/
+    ├── architecture/       # Architecture documentation
+    │   ├── Architecture.md         # Main architecture overview
+    │   ├── FolderStructure.md      # High-level folder structure
+    │   ├── ProjectTreeFolder.md    # This file (detailed file tree)
+    │   ├── FileTypes.md            # File naming conventions and patterns
+    │   ├── ADRs.md                 # ADR index
+    │   └── ADR/                    # Individual ADR documents
+    │       └── ...
+    │
+    ├── pictures/           # Documentation images and diagrams
+    │   └── ...
+    │
+    ├── CodeReviewProcess.md       # Code review guidelines
+    ├── DevelopmentProcess.md      # Development workflow
+    ├── Onboarding.md              # Onboarding guide for new developers
+    └── ReleaseAndDeployment.md    # Release and deployment procedures
+```
+
+---
+
+## 🔄 Data Flow Examples
+
+### News Pipeline
+
+```
+content/news/{locale}/*.mdx
+    ↓
+features/markdown/server-mdx.tsx (parsing)
+    ↓
+features/news/news-manager.ts (loading, metadata, reading time)
+    ↓
+app/[locale]/(layout)/news/page.tsx (listing)
+app/[locale]/(layout)/news/[slug]/page.tsx (detail)
+```
+
+### Component Import Flow
+
+```
+src/components/ui/button.tsx (primitive)
+    ↓
+src/components/DS/CTA/... (design system)
+    ↓
+src/features/landing/landing-CTA.tsx (feature)
+    ↓
+app/[locale]/(landing)/page.tsx (page)
+```
+
+### i18n Flow
+
+```
+messages/{locale}.json (translations)
+    ↓
+src/i18n/config.ts (configuration)
+    ↓
+middleware.ts (locale detection)
+    ↓
+app/[locale]/layout.tsx (provider)
+    ↓
+components (useTranslations hook)
+```
+
+---
+
+## 📝 Notes
+
+- **Path Aliases**: See [FolderStructure.md](./FolderStructure.md) for TypeScript path alias configuration
+- **File Types**: See [FileTypes.md](./FileTypes.md) for detailed file naming conventions
+- **Architecture**: See [Architecture.md](./Architecture.md) for tech stack and non-functional requirements
+- **Auto-generated files**: `.next/`, `node_modules/`, `*.tsbuildinfo` are not included in this tree
+
+---
+
+## 🔗 References
+
+- [Next.js App Router Documentation](https://nextjs.org/docs/app)
+- [Next.js Project Structure](https://nextjs.org/docs/getting-started/project-structure)
+- [FolderStructure.md](./FolderStructure.md) - High-level architecture overview
+- [FileTypes.md](./FileTypes.md) - File naming patterns and conventions
diff --git a/Documentation/Guidelines/pictures/git-flow-model.png b/Documentation/Guidelines/pictures/git-flow-model.png
new file mode 100644
index 0000000..5b96426
Binary files /dev/null and b/Documentation/Guidelines/pictures/git-flow-model.png differ
diff --git a/Documentation/Guidelines/workflows/TeamWorkflow.md b/Documentation/Guidelines/workflows/TeamWorkflow.md
new file mode 100644
index 0000000..3dc7d88
--- /dev/null
+++ b/Documentation/Guidelines/workflows/TeamWorkflow.md
@@ -0,0 +1,454 @@
+# Team Workflow - Complete Feature Lifecycle
+
+This document describes the complete workflow for developing a feature, from the initial idea to production deployment.
+
+## Table of Contents
+
+- [Introduction](#introduction)
+- [Roles and Responsibilities](#roles-and-responsibilities)
+- [Workflow Overview](#workflow-overview)
+- [Phase 1: Feature Request](#phase-1-feature-request)
+- [Phase 2: Requirements Definition](#phase-2-requirements-definition)
+- [Phase 3: Create Epic/Issue](#phase-3-create-epicissue)
+- [Phase 4: Development Preparation](#phase-4-development-preparation)
+- [Phase 5: UX/UI Design (Optional)](#phase-5-uxui-design-optional)
+- [Phase 6: Development](#phase-6-development)
+- [Phase 7: Pull Request & Review](#phase-7-pull-request--review)
+- [Phase 8: Staging Deployment](#phase-8-staging-deployment)
+- [Phase 9: Production Release](#phase-9-production-release)
+- [Discord Sync Points](#discord-sync-points)
+- [Quick Checklist](#quick-checklist)
+- [References](#references)
+
+---
+
+## Introduction
+
+The development of a feature follows a structured lifecycle involving multiple actors and validation steps. This workflow ensures that:
+
+- ✅ Requirements are well understood before development
+- ✅ Code quality is ensured through reviews and CI/CD
+- ✅ Deployments are controlled and traceable
+- ✅ Communication is fluid among all stakeholders
+
+**Average feature duration:** 1-3 weeks (depending on complexity)
+
+---
+
+## Roles and Responsibilities
+
+| Role                       | Responsibilities                                                                                |
+| -------------------------- | ----------------------------------------------------------------------------------------------- |
+| **Community / Teams**      | Suggests features, participates in discussions                                                  |
+| **Website Lead**           | Validates needs, creates issues, assigns developers, final review, merges PRs, manages releases |
+| **UX/UI Team**             | Creates designs and mockups (if visual impact)                                                  |
+| **Developer**              | Develops the feature, creates PR, responds to reviews                                           |
+| **Reviewer**               | Reviews the code (optional but recommended)                                                     |
+| **CI/CD (GitHub Actions)** | Automated tests, build, deployment                                                              |
+
+---
+
+## Workflow Overview
+
+```mermaid
+graph TD
+    A[Phase 1: Feature Request on Discord] -->|Anyone| B[Phase 2: Requirements Definition on Discord]
+    B -->|Discussion & Validation| C{Requirements validated?}
+    C -->|No| Z[Rejected/Pending]
+    Z -->|Redefine requirements| B
+    C -->|Yes| D[Phase 3: Create Epic/Issue GitHub]
+    D -->|Website Lead| E[Phase 4: Dev Preparation]
+    E -->|Assignment| F{Visual impact?}
+
+    F -->|Yes| G[Phase 5: UX/UI Design]
+    F -->|No| H[Phase 6: Development]
+    G -->|Design validated| H
+
+    H -->|Code + Local Tests| I[Phase 7: Pull Request & Review]
+    I -->|CI/CD checks| J{Checks OK?}
+    J -->|No| H
+    J -->|Yes| K{Review OK?}
+    K -->|Changes required| H
+    K -->|Approved| L[Phase 8: Merge & Deploy Staging]
+
+    L -->|Auto-deploy| M{Staging tests OK?}
+    M -->|No| N[Debug & Fix]
+    N --> H
+    M -->|Yes| O[Phase 9: Production Release]
+    O -->|Tag + Deploy| P[Feature in Production ✅]
+
+    style A fill:#e1f5ff
+    style D fill:#fff4e1
+    style G fill:#ffe1f5
+    style H fill:#e1ffe1
+    style L fill:#f5e1ff
+    style O fill:#ffe1e1
+    style P fill:#90EE90
+```
+
+---
+
+## Phase 1: Feature Request
+
+**🎯 Goal:** Propose a new feature or improvement  
+**👥 Actors:** Anyone (community, players, team)  
+**📍 Where:** Discord, Channel: [ #w-feature-requests](https://discord.com/channels/1399325839665004554/1431251363924545546)
+
+### Actions
+
+1. **Create a Discord post** with:
+   - Clear title of the feature
+   - Description of the need
+   - Usage context
+   - Expected benefits
+   - Examples or references (if applicable)
+
+2. **Use appropriate tags** to categorize the request
+
+### Exit Criteria
+
+- ✅ Discord post created and published
+- ✅ Team notified of the new request
+
+### Example
+
+```
+📝 Feature Request: RSS Feed for News
+
+Description:
+Add an RSS/Atom feed to allow users to follow project news via their preferred RSS reader.
+
+Context:
+Many players use RSS aggregators (Feedly, Inoreader, etc.) to centralize their information sources. Currently, they need to visit the website regularly to check for news.
+
+Benefits:
+- Allow users to stay updated with news without visiting the website
+- Increase the reach of announcements
+- Widely supported web standard
+- Improves community engagement
+
+References:
+- RSS 2.0 format: https://www.rssboard.org/rss-specification
+- Example: The Next.js blog offers an RSS feed
+- See attached screenshot from an RSS reader
+```
+
+---
+
+## Phase 2: Requirements Definition
+
+**🎯 Goal:** Clarify, refine, and validate the requirements before development  
+**👥 Actors:** Community + Website Lead + Tech Team  
+**📍 Where:** Discord (on the feature request post)
+
+### Actions
+
+1. **Discussions and exchanges:**
+   - Clarification questions
+   - Use case exploration
+   - Identification of technical constraints
+   - Feasibility assessment
+
+2. **Assessment by Website Lead:**
+   - Alignment with project vision
+   - Prioritization (urgent, important, nice-to-have)
+   - Complexity estimation
+   - Identification of dependencies
+
+3. **Decision:**
+   - ✅ Accepted → Move to Phase 3
+   - ⏸️ Pending → Backlog
+   - ❌ Rejected → Reason provided
+
+### Exit Criteria
+
+- ✅ Clearly defined and documented requirements
+- ✅ Website Lead validation obtained
+- ✅ Consensus on added value
+
+### Discord Sync Point
+
+💬 **Website Lead announces the decision** in the Discord thread
+
+---
+
+## Phase 3: Create Epic/Issue
+
+**🎯 Goal:** Formalize the feature in GitHub Projects for tracking  
+**👥 Actors:** Website Lead  
+**📍 Where:** GitHub Projects
+
+### Actions
+
+1. **Create an Epic** (if the feature is complex and spans multiple issues):
+   - Descriptive title
+   - Complete description
+   - Link to Discord discussion
+   - Global acceptance criteria
+
+2. **Create one or more Issues:**
+   - Clear title with issue number
+   - Detailed description and context
+   - **Detailed requirements:**
+     - ✅ Design: Mockups, wireframes (if applicable)
+     - ✅ Frontend: UI components, interactions, responsiveness
+     - ✅ Backend: APIs, business logic, database
+     - ✅ Integration: Tests, CI/CD, documentation
+   - Appropriate labels (feature, enhancement, bug, etc.)
+   - Priority and estimation
+
+3. **Link to project:**
+   - Add to GitHub Projects board
+   - Set initial status (Backlog, To Do, etc.)
+
+### Exit Criteria
+
+- ✅ Issue(s) created with all requirements
+- ✅ Issue visible in GitHub Projects
+- ✅ Discord ↔ GitHub link established
+
+### Example Issue
+
+The issue will be created via the GitHub template `.github/ISSUE_TEMPLATE/feat.yml`:
+
+**Title:** `[#123] Add RSS Feed for News`
+
+**Context**
+
+```
+Users requested an RSS feed to follow project news via their preferred RSS readers.
+Currently, they have to visit the site regularly to check for news.
+
+Discord discussion: [link to the Discord post]
+```
+
+**Design**
+
+```
+No major UI changes required (mainly a backend feature)
+```
+
+**Frontend**
+
+```
+- [ ] Add a link to the RSS feed in the footer
+- [ ] Add an RSS icon/button in the news listing page
+- [ ] Add `<link rel="alternate">` tag in the HTML head for autodiscovery
+- [ ] Style for RSS icon in the news page
+```
+
+**Backend**
+
+```
+- [ ] Generate an RSS 2.0 XML feed at `/rss.xml` or `/feed.xml`
+- [ ] Include the latest 50 news items
+- [ ] Support localized feeds (`/en/rss.xml`, `/fr/rss.xml`)
+- [ ] Include full metadata (title, description, pubDate, author, category)
+- [ ] Include full content or an excerpt
+- [ ] Add a unique GUID for each item
+- [ ] Implement caching for feed generation (1 hour)
+- [ ] Handle UTF-8 encoding and special characters
+```
+
+**Integration**
+
+```
+- [ ] Test the feed with W3C Feed Validator
+- [ ] Test with popular RSS readers (Feedly, Inoreader, NetNewsWire)
+- [ ] Add the RSS feed to sitemap.xml
+- [ ] Update documentation (README, user docs)
+- [ ] Add RSS autodiscovery meta tags
+- [ ] Automated tests for feed generation
+```
+
+**Before You Start Coding**
+
+```
+Before you start coding, make sure you fully understand what needs to be done and how.
+If needed, ping the Web Lead in the Discord channel and ask your questions.
+Several people can work together on this issue.
+
+Useful resources:
+- RSS 2.0 specification: https://www.rssboard.org/rss-specification
+- W3C Feed Validator: https://validator.w3.org/feed/
+```
+
+---
+
+## Phase 4: Development Preparation
+
+**🎯 Goal:** Ensure the developer fully understands the requirements before coding  
+**👥 Actors:** Developer + Website Lead  
+**📍 Where:** Discord (thread linked to the issue) + GitHub
+
+### Actions
+
+1. **Request assignment:**
+   - Contact the Website Lead on Discord
+   - Indicate your availability and interest
+
+2. **Read and understand the issue:**
+   - Read all requirements (Design, Frontend, Backend, Integration)
+   - Identify unclear points
+
+3. **Ask questions:**
+   - Use the Discord thread linked to the issue
+   - Ask for technical clarifications
+   - Validate implementation choices
+   - Identify external dependencies
+
+4. **Wait for official assignment:**
+   - Website Lead assigns the issue on GitHub
+   - Confirmation on Discord
+
+5. **Prepare the environment:**
+   - Make sure `develop` is up to date
+   - Verify that local environment is working
+
+### Exit Criteria
+
+- ✅ Developer officially assigned
+- ✅ All questions clarified
+- ✅ Requirements 100% understood
+- ✅ Dev environment ready
+
+### Discord Sync Point
+
+💬 **Website Lead confirms assignment** and answers questions
+
+---
+
+## Phase 5: UX/UI Design (Optional)
+
+**🎯 Goal:** Create designs and mockups for features with visual impact  
+**👥 Actors:** UX/UI Team + Website Lead + Developer  
+**📍 Where:** Discord + Figma/other design tool  
+**⚠️ Note:** This phase is **optional** and concerns only features with significant visual impact.
+
+### Trigger Conditions
+
+This phase is required if the feature involves:
+
+- ✅ New UI components
+- ✅ Major interface changes
+- ✅ New pages or layouts
+- ✅ Complex interactions
+
+Not required for:
+
+- ❌ Backend bugs
+- ❌ Performance optimizations
+- ❌ Refactoring with no visual impact
+- ❌ Small minor UI tweaks
+
+### Actions
+
+1. **Design creation** (UX/UI Team):
+   - Wireframes / Mockups
+   - Interaction definition
+   - Responsive design (mobile, tablet, desktop)
+   - Design system alignment
+
+2. **Design review:**
+   - Presentation to the team on Discord
+   - Feedback from Website Lead
+   - Feedback from developer (technical feasibility)
+
+3. **Iterations** (if needed):
+   - Adjustments based on feedback
+   - Final validation
+
+4. **Delivery to developer:**
+   - Exported assets (images, icons, etc.)
+   - Specifications (spacing, colors, fonts, etc.)
+   - Link to Figma/other mockups
+
+### Exit Criteria
+
+- ✅ Designs validated by Website Lead
+- ✅ Assets available for developer
+- ✅ Clear documented specifications
+
+### Parallel Workflow
+
+💡 **Important:** This phase can be done **in parallel** with backend development if the feature allows. The developer can start with:
+
+- Backend logic
+- Data structures
+- APIs
+
+Then integrate frontend design when ready.
+
+---
+
+## Phase 6: Development
+
+**🎯 Goal:** Implement the feature according to requirements  
+**👥 Actors:** Developer  
+**📍 Where:** Local + GitHub
+
+### Documentation
+
+> 📖 See [DevelopmentProcess.md](../DevelopmentProcess.md) for naming conventions and feature branch creation  
+> 📖 See [CodeReviewProcess.md](../CodeReviewProcess.md) for commit conventions and PR creation
+
+## Phase 7: Pull Request & Review
+
+**🎯 Goal:** Submit code for automated and human validation  
+**👥 Actors:** Developer → CI/CD → Reviewers → Website Lead  
+**📍 Where:** GitHub
+
+### Documentation
+
+> 📖 See [CodeReviewProcess.md](../CodeReviewProcess.md) for PR creation
+
+## Phase 8: Staging Deployment
+
+**🎯 Goal:** Auto-deploy to staging environment for tests  
+**👥 Actors:** Website Lead (merge) → CI/CD (auto-deploy)  
+**📍 Where:** GitHub + Staging Server
+
+### Documentation
+
+> 📖 See [ReleaseAndDeployment.md](../ReleaseAndDeployment.md) for staging deployment
+
+## Phase 9: Production Release
+
+**🎯 Goal:** Deploy feature to production and communicate the release  
+**👥 Actors:** Website Lead (only authorized)  
+**📍 Where:** GitHub + Production Server + Discord  
+**⚠️ Important:** Only the **Website Lead** can create releases.
+
+### Documentation
+
+> 📖 See [ReleaseAndDeployment.md](../ReleaseAndDeployment.md) for production deployment
+
+## Discord Sync Points
+
+Summary of key moments to communicate on Discord:
+
+| Phase             | Who            | Message                        | Importance       |
+| ----------------- | -------------- | ------------------------------ | ---------------- |
+| **End Phase 2**   | Website Lead   | Need validated/rejected        | 🔴 Critical      |
+| **Start Phase 4** | Website Lead   | Assignment confirmation        | 🟠 Important     |
+| **End Phase 5**   | UX/UI Team     | Design validated and delivered | 🟡 If applicable |
+| **End Phase 7**   | Developer      | PR ready for review            | 🔴 Critical      |
+| **End Phase 8**   | Developer/Lead | Feature validated on staging   | 🟢 Info          |
+| **End Phase 9**   | Website Lead   | Release in production          | 🔴 Critical      |
+
+## References
+
+Detailed documents for further information:
+
+| Document                                                     | Content                                                       |
+| ------------------------------------------------------------ | ------------------------------------------------------------- |
+| **[DevelopmentProcess.md](../DevelopmentProcess.md)**        | Git-flow conventions, branch naming, detailed git commands    |
+| **[CodeReviewProcess.md](../CodeReviewProcess.md)**          | PR process, complete CI/CD pipeline, review criteria          |
+| **[ReleaseAndDeployment.md](../ReleaseAndDeployment.md)**    | Detailed release process, hotfix, rollback, production checks |
+| **[Onboarding.md](../Onboarding.md)**                        | Initial setup, required tools, environment configuration      |
+| **[Architecture.md](../architecture/Architecture.md)**       | Tech stack, architecture, non-functional requirements         |
+| **[FolderStructure.md](../architecture/FolderStructure.md)** | Code organization, file naming conventions                    |
+
+---
+
+**Questions?** Contact the Website Lead on Discord 💬
diff --git a/DOC_SITEMAP.md b/Documentation/Tech/DOC_SITEMAP.md
similarity index 100%
rename from DOC_SITEMAP.md
rename to Documentation/Tech/DOC_SITEMAP.md
diff --git a/Documentation/Tech/index.md b/Documentation/Tech/index.md
new file mode 100644
index 0000000..b03fa02
--- /dev/null
+++ b/Documentation/Tech/index.md
@@ -0,0 +1 @@
+- [DOC_SITEMAP.md](DOC_SITEMAP.md) : Guide for updating the sitemap when modifying pages or URLs
diff --git a/README.md b/README.md
index 1b43f77..2cd0f8b 100644
--- a/README.md
+++ b/README.md
@@ -1,34 +1,18 @@
-# DyingStar Website
+# [DyingStar - Webapp] Collaboration Guideline's wiki
 
-## Local Development
+Here you'll find all the documents you need to collaborate on the project.
 
-### Requirements
+| Topic                                                                      | Description                                                        |
+| -------------------------------------------------------------------------- | ------------------------------------------------------------------ |
+| [Onboarding](Documentation/Guidelines/Onboarding.md)                       | Documents related to new developer onboarding                      |
+| [Development Process](Documentation/Guidelines/DevelopmentProcess.md)      | Documents related to development process                           |
+| [Architecture](Documentation/Guidelines/architecture/Architecture.md)      | Documents related to architecture and Technical choices            |
+| [Code Review Process](Documentation/Guidelines/CodeReviewProcess.md)       | Documents related to code review process, definition of ready/done |
+| [Release and Deployment](Documentation/Guidelines/ReleaseAndDeployment.md) | Documents related to release and deployment                        |
+| [Workflows](Documentation/Guidelines/workflows/TeamWorkflow.md)            | Documents related to workflows                                     |
 
-- [Docker](https://www.docker.com/get-started)
-- [Docker Compose](https://docs.docker.com/compose/install/)
-- [Make](https://www.gnu.org/software/make/) to use the provided Makefile (optional but recommended)
+# Technical Documentation
 
-### Setup
+You'll find the technical documentation in the [Tech](Documentation/Tech/index.md) folder.
 
-1. Copy `.env.example` to `.env.local` and fill in the required environment variables
-2. Run `make dev` to start the development server. This will install dependencies and start the server.
-3. Open your browser and navigate to `http://localhost:3000` to see the website.
-4. To stop the development server, stop the Docker container with `Ctrl+C` in the terminal where `make dev` was run.
-
-### Notes
-
-- The development server supports hot-reloading, so any changes you make to the code will automatically be reflected in the browser.
-- If you need to install new dependencies, you can do so by running `make add-dependency <package-name>` or `make add-dev-dependency <package-name>` for dev dependencies.
-
-## CI/CD Pipeline
-
-The project uses GitHub Actions for continuous integration and deployment. The workflow is defined in `.github/workflows/build.yml`.
-
-### Stages
-
-1. **Next.js Build**: This stage installs dependencies, lints the code, and builds the Next.js application.
-2. **Docker Build and Push**: This stage builds a Docker image of the application and pushes it to the registry. The push is triggered only on the `main` branch with a tag starting with `v`.
-
-### Environment Variables
-
-- The workflow expects a secret named `WEBSITE_ENV_PRODUCTION_FILE` containing the contents of the `.env.production` file. This file is created during the CI process to ensure that sensitive information is not hardcoded in the repository
+**NB** : Got an idea ? Or a suggestion ? Feel free to open an issue or contact one of our developers.
diff --git a/content/en/news/20250727-project-creation.mdx b/content/en/news/20250727-project-creation.mdx
index c977131..436effc 100644
--- a/content/en/news/20250727-project-creation.mdx
+++ b/content/en/news/20250727-project-creation.mdx
@@ -33,7 +33,7 @@ A few project features:
 
 - Making an immersive space MMO
 - Making it open source, using the [Godot](https://godotengine.org/) engine
-- ​​Game name: **StarDeception**
+- Game name: **StarDeception**
 - No instances, everyone in the same unique universe
 - Very few piew piew (weapons)
 
diff --git a/package.json b/package.json
index 8bd1d6c..46f477f 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "dying-star",
-  "version": "0.3.1",
+  "version": "0.3.2",
   "private": true,
   "scripts": {
     "build": "next build --turbo",
@@ -11,7 +11,8 @@
     "prettier": "prettier --write .",
     "typecheck": "tsc --noEmit",
     "clean": "eslint . --fix && tsc --noEmit && prettier --write .",
-    "lint:ci": "eslint . --max-warnings 0 && tsc --noEmit && prettier --check ."
+    "lint:ci": "eslint . --max-warnings 0 && tsc --noEmit && prettier --check .",
+    "adr:generate": "adr-log -d ./Documentation/Guidelines/architecture/ADR -i ./Documentation/Guidelines/architecture/ADRs.md"
   },
   "dependencies": {
     "@hookform/resolvers": "^5.2.1",
@@ -107,6 +108,7 @@
     "@typescript-eslint/eslint-plugin": "^8.42.0",
     "@typescript-eslint/parser": "^8.42.0",
     "@vitejs/plugin-react": "^5.0.2",
+    "adr-log": "^2.2.0",
     "cross-fetch": "^4.1.0",
     "dotenv": "^17.2.2",
     "eslint": "^9.35.0",
diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml
index eec5b34..1ff8810 100644
--- a/pnpm-lock.yaml
+++ b/pnpm-lock.yaml
@@ -282,6 +282,9 @@ importers:
       '@vitejs/plugin-react':
         specifier: ^5.0.2
         version: 5.0.4(vite@7.1.9(@types/node@24.6.2)(jiti@2.6.1)(lightningcss@1.30.1)(sass@1.93.2)(tsx@4.20.6)(yaml@2.8.1))
+      adr-log:
+        specifier: ^2.2.0
+        version: 2.2.0
       cross-fetch:
         specifier: ^4.1.0
         version: 4.1.0
@@ -2221,6 +2224,10 @@ packages:
     engines: {node: '>=0.4.0'}
     hasBin: true
 
+  adr-log@2.2.0:
+    resolution: {integrity: sha512-+J6SUdITpd+N4tvptSPu672zckVITj9ux7xClpfVoB1W148X4KGCOIj82ONIzK2acUMNN4OUYvIG1hLZ+fGy5g==}
+    hasBin: true
+
   agent-base@7.1.4:
     resolution: {integrity: sha512-MnA+YT8fwfJPgBx3m60MNqakm30XOkyIoH1y6huTQvC0PwZG7ki8NacLBcrPbNoo8vEZy7Jpuk7+jMO+CUovTQ==}
     engines: {node: '>= 14'}
@@ -2228,10 +2235,22 @@ packages:
   ajv@6.12.6:
     resolution: {integrity: sha512-j3fVLgvTo527anyYyJOGTYJbG+vnnQYvE0m5mmkc1TK+nxAppkCLMIL0aZ4dblVCNoGShhm+kzE4ZUykBoMg4g==}
 
+  ansi-red@0.1.1:
+    resolution: {integrity: sha512-ewaIr5y+9CUTGFwZfpECUbFlGcC0GCw1oqR9RI6h1gQCd9Aj2GxSckCnPsVJnmfMZbwFYE+leZGASgkWl06Jow==}
+    engines: {node: '>=0.10.0'}
+
+  ansi-regex@2.1.1:
+    resolution: {integrity: sha512-TIGnTpdo+E3+pCyAluZvtED5p5wCqLdezCyhPZzKPcxvFplEt4i+W7OONCKgeZFT3+y5NZZfOOS/Bdcanm1MYA==}
+    engines: {node: '>=0.10.0'}
+
   ansi-regex@5.0.1:
     resolution: {integrity: sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ==}
     engines: {node: '>=8'}
 
+  ansi-styles@2.2.1:
+    resolution: {integrity: sha512-kmCevFghRiWM7HB5zTPULl4r9bVFSWjz62MhqizDGUrq2NWuNMQyuv4tHHoKJHs69M/MF64lEcHdYIocrdWQYA==}
+    engines: {node: '>=0.10.0'}
+
   ansi-styles@4.3.0:
     resolution: {integrity: sha512-zbB9rCJAT1rbjiVDb2hqKFHNYLxgtk8NURxZ3IZwD3F6NtxbXZQCnnSi1Lkx+IDohdPlFp222wVALIheZJQSEg==}
     engines: {node: '>=8'}
@@ -2240,6 +2259,10 @@ packages:
     resolution: {integrity: sha512-Cxwpt2SfTzTtXcfOlzGEee8O+c+MmUgGrNiBcXnuWxuFJHe6a5Hz7qwhwe5OgaSYI0IJvkLqWX1ASG+cJOkEiA==}
     engines: {node: '>=10'}
 
+  ansi-wrap@0.1.0:
+    resolution: {integrity: sha512-ZyznvL8k/FZeQHr2T6LzcJ/+vBApDnMNZvfVFy3At0knswWd6rJ3/0Hhmpu8oqa6C92npmozs890sX9Dl6q+Qw==}
+    engines: {node: '>=0.10.0'}
+
   arg@4.1.3:
     resolution: {integrity: sha512-58S9QDqG0Xx27YwPSt9fJxivjYl432YCwfDMfZ+71RAqUrZef7LrKQZ3LHLOwCS4FLNBplP533Zx895SeOCHvA==}
 
@@ -2304,6 +2327,9 @@ packages:
     resolution: {integrity: sha512-hsU18Ae8CDTR6Kgu9DYf0EbCr/a5iGL0rytQDobUcdpYOKokk8LEjVphnXkDkgpi0wYVsqrXuP0bZxJaTqdgoA==}
     engines: {node: '>= 0.4'}
 
+  autolinker@0.28.1:
+    resolution: {integrity: sha512-zQAFO1Dlsn69eXaO6+7YZc+v84aquQKbwpzCE3L0stj56ERn9hutFxPopViLjo9G+rWwjozRhgS5KJ25Xy19cQ==}
+
   available-typed-arrays@1.0.7:
     resolution: {integrity: sha512-wvUjBtSGN7+7SjNpq/9M2Tg350UZD3q62IFZLbRAR1bSMlCo1ZaeW+BJ+D090e4hIIZLBcTDWe4Mh4jvUDajzQ==}
     engines: {node: '>= 0.4'}
@@ -2404,6 +2430,10 @@ packages:
     peerDependencies:
       react: '>=17.0.0'
 
+  chalk@1.1.3:
+    resolution: {integrity: sha512-U3lRVLMSlsCfjqYPbLyVv11M9CPW4I728d6TCKMAOJueEeB9/8o+eSsMnxPJD+Q+K909sdESg7C+tIkoH6on1A==}
+    engines: {node: '>=0.10.0'}
+
   chalk@4.1.2:
     resolution: {integrity: sha512-oKnbhFyRIXpUuez8iBMmyEa4nbj4IOQyuhc/wy9kY7/WVPcwIO9VA668Pu8RkO7+0G76SLROeyw9CpQ061i4mA==}
     engines: {node: '>=10'}
@@ -2450,6 +2480,12 @@ packages:
   codem-isoboxer@0.3.10:
     resolution: {integrity: sha512-eNk3TRV+xQMJ1PEj0FQGY8KD4m0GPxT487XJ+Iftm7mVa9WpPFDMWqPt+46buiP5j5Wzqe5oMIhqBcAeKfygSA==}
 
+  coffee-script@1.12.7:
+    resolution: {integrity: sha512-fLeEhqwymYat/MpTPUjSKHVYYl0ec2mOyALEMLmzr5i1isuG+6jfI2j2d5oBO3VIzgUXgBVIcOT9uH1TFxBckw==}
+    engines: {node: '>=0.8.0'}
+    deprecated: CoffeeScript on NPM has moved to "coffeescript" (no hyphen)
+    hasBin: true
+
   collapse-white-space@2.1.0:
     resolution: {integrity: sha512-loKTxY1zCOuG4j9f6EPnuyyYkf58RnhhWTvRoZEokgB+WbdXehfjFviyOVYkqzEWz1Q5kRiZdBYS5SwxbQYwzw==}
 
@@ -2466,12 +2502,21 @@ packages:
   concat-map@0.0.1:
     resolution: {integrity: sha512-/Srv4dswyQNBfohGpz9o6Yb3Gz3SrUDqBH5rTuhGR7ahtlbYKnVxw2bCFMRljaA7EXHaXZ8wsHdodFvbkhKmqg==}
 
+  concat-with-sourcemaps@1.1.0:
+    resolution: {integrity: sha512-4gEjHJFT9e+2W/77h/DS5SGUgwDaOwprX8L/gl5+3ixnzkVJJsZWDSelmN3Oilw3LNDZjZV0yqH1hLG3k6nghg==}
+
+  console-stamp@0.2.10:
+    resolution: {integrity: sha512-HjPHHsUGj5xcwkcwolgBg9SxhVqLzktH16GmvGsdZJ+FJPNq+xr+wSdYh8744JEAbCkJ0pNJuDN+34Bx14vERg==}
+
   convert-source-map@2.0.0:
     resolution: {integrity: sha512-Kvp459HrV2FEJ1CAsi1Ku+MY3kasH19TFykTz2xWmMeq6bk2NU3XXvfJ+Q61m0xktWwt+1HSYf3JZsTms3aRJg==}
 
   copy-to-clipboard@3.3.3:
     resolution: {integrity: sha512-2KV8NhB5JqC3ky0r9PMCAZKbUHSwtEo4CwCs0KXgruG43gX5PMqDEBbVU4OUzw2MuAWUfsuFmWvEKG5QRfSnJA==}
 
+  core-util-is@1.0.3:
+    resolution: {integrity: sha512-ZQBvi1DcpJ4GDqanjucZ2Hj3wEO5pZDS89BWbkcrvdxksJorwUDDZamX9ldFkp9aw2lmBDLgkObEA4DWNJ9FYQ==}
+
   create-require@1.1.1:
     resolution: {integrity: sha512-dcKFX3jn0MpIaXjisoRvexIJVEKzaq7z2rZKxf+MSr9TkdmHmsU4m2lcLojrj/FHl8mk5VxMmYA+ftRkP/3oKQ==}
 
@@ -2576,6 +2621,10 @@ packages:
   date-fns@4.1.0:
     resolution: {integrity: sha512-Ukq0owbQXxa/U3EGtsdVBkR1w7KOQ5gIBqdH2hkvknzZPYvBxb/aa6E8L7tmjFtkwZBu3UXBbjIgPo/Ez4xaNg==}
 
+  dateformat@1.0.11:
+    resolution: {integrity: sha512-5zcI+Qoul0QgiCcjzsobs9G1c+vHCNaYB2NGa57ZbVnP7bZeKJJgoM/K+I/obaHAmyEL0J8hJafbQ+HFSZnzZA==}
+    hasBin: true
+
   debug@3.2.7:
     resolution: {integrity: sha512-CFjzYYAi4ThfiQvizrFQevTTXHtnCqWfe7x1AhgEscTz6ZbLbfoLRLPugTQyBth6f8ZERVUSyWHFD/7Wu4t1XQ==}
     peerDependencies:
@@ -2721,6 +2770,10 @@ packages:
     resolution: {integrity: sha512-WUj2qlxaQtO4g6Pq5c29GTcWGDyd8itL8zTlipgECz3JesAiiOKotd8JU6otB3PACgG6xkJUyVhboMS+bje/jA==}
     engines: {node: '>=6'}
 
+  escape-string-regexp@1.0.5:
+    resolution: {integrity: sha512-vbRorB5FUQWvla16U8R/qgaFIya2qGzwDrNmCZuYKrbdSUMG6I1ZCGQRefkRVhuOkIGVne7BQ35DSfo1qvJqFg==}
+    engines: {node: '>=0.8.0'}
+
   escape-string-regexp@4.0.0:
     resolution: {integrity: sha512-TtpcNJ3XAzx3Gq8sWRzJaVajRs0uVxA2YAkdb1jm2YkPz4G6egUFAyA3n5vtEIZefPk5Wa4UXbKuS5fKkJWdgA==}
     engines: {node: '>=10'}
@@ -2851,6 +2904,10 @@ packages:
   eventemitter3@5.0.1:
     resolution: {integrity: sha512-GWkBvjiSZK87ELrYOSESUYeVIc9mvLLf/nXalMOS5dYrgZq9o5OVkbZAVM06CVxYsCwH9BDZFPlQTlPA1j4ahA==}
 
+  extend-shallow@2.0.1:
+    resolution: {integrity: sha512-zCnTtlxNoAiDc3gqY2aYAWFx7XWWiasuF2K8Me5WbN8otHKTUKBwjPtNpRs/rbUZm7KxWAaNj7P1a/p52GbVug==}
+    engines: {node: '>=0.10.0'}
+
   extend@3.0.2:
     resolution: {integrity: sha512-fjquC59cD7CyW6urNXK0FBufkZcoiGG80wTuPujX590cB5Ttln20E2UB4S/WARVqhXffZl2LNgS+gQdPIIim/g==}
 
@@ -2936,6 +2993,9 @@ packages:
   front-matter@4.0.2:
     resolution: {integrity: sha512-I8ZuJ/qG92NWX8i5x1Y8qyj3vizhXS31OxjKDu3LKP+7/qBgfIKValiZIEwoVoJKUHlhWtYrktkxV1XsX+pPlg==}
 
+  fs.realpath@1.0.0:
+    resolution: {integrity: sha512-OO0pH2lK6a0hZnAdau5ItzHPI6pUlvI7jMVnxUQRtw4owF2wk8lOSabtGDCTP4Ggrg2MbGnWO9X8K1t4+fGMDw==}
+
   fsevents@2.3.3:
     resolution: {integrity: sha512-5xoDfX+fL7faATnagmWPpbFtwh/R77WmMMqqHGS65C3vvB0YHrgF+B1YmZ3441tMj5n63k0212XNoJwzlhffQw==}
     engines: {node: ^8.16.0 || ^10.6.0 || >=11.0.0}
@@ -2971,6 +3031,10 @@ packages:
     resolution: {integrity: sha512-sTSfBjoXBp89JvIKIefqw7U2CCebsc74kiY6awiGogKtoSGbgjYE/G/+l9sF3MWFPNc9IcoOC4ODfKHfxFmp0g==}
     engines: {node: '>= 0.4'}
 
+  get-stdin@9.0.0:
+    resolution: {integrity: sha512-dVKBjfWisLAicarI2Sf+JuBE/DghV4UzNAVe9yhEJuzeREd3JhOTE9cUaJTeSa77fsbQUK3pcOpJfM59+VKZaA==}
+    engines: {node: '>=12'}
+
   get-symbol-description@1.1.0:
     resolution: {integrity: sha512-w9UMqWwJxHNOvoNzSJ2oPF5wvYcvP7jUvYzhp67yEhTi17ZDBBC1z9pTdGuzjD+EFIqLSYRweZjqfiPzQ06Ebg==}
     engines: {node: '>= 0.4'}
@@ -2989,6 +3053,10 @@ packages:
     resolution: {integrity: sha512-XxwI8EOhVQgWp6iDL+3b0r86f4d6AX6zSU55HfB4ydCEuXLXc5FcYeOu+nnGftS4TEju/11rt4KJPTMgbfmv4A==}
     engines: {node: '>=10.13.0'}
 
+  glob@7.2.3:
+    resolution: {integrity: sha512-nFR0zLpU2YCaRxwoCJvL6UvCH2JFyFVIvwTLsIf21AuHlMskA1hhTdk+LlYJtOlYt9v6dvszD2BGRqBL+iQK9Q==}
+    deprecated: Glob versions prior to v9 are no longer supported
+
   globals@14.0.0:
     resolution: {integrity: sha512-oahGvuMGQlPw/ivIYBjVSrWAfWLBeku5tpPE2fOPLi+WHffIWbuh2tCjhyQhTBPMf5E9jDEH4FOmTYgYwbKwtQ==}
     engines: {node: '>=18'}
@@ -3011,6 +3079,18 @@ packages:
   graphemer@1.4.0:
     resolution: {integrity: sha512-EtKwoO6kxCL9WO5xipiHTZlSzBm7WLT627TqC/uVRd0HKmq8NXyebnNYxDoBi7wt8eTWrUrKXCOVaFq9x1kgag==}
 
+  gray-matter@2.1.1:
+    resolution: {integrity: sha512-vbmvP1Fe/fxuT2QuLVcqb2BfK7upGhhbLIt9/owWEvPYrZZEkelLcq2HqzxosV+PQ67dUFLaAeNpH7C4hhICAA==}
+    engines: {node: '>=0.10.0'}
+
+  gulp-header@1.8.12:
+    resolution: {integrity: sha512-lh9HLdb53sC7XIZOYzTXM4lFuXElv3EVkSDhsd7DoJBj7hm+Ni7D3qYbb+Rr8DuM8nRanBvkVO9d7askreXGnQ==}
+    deprecated: Removed event-stream from gulp-header
+
+  has-ansi@2.0.0:
+    resolution: {integrity: sha512-C8vBJ8DwUCx19vhm7urhTuUsr4/IyP6l4VzNQDv+ryHQObW3TTTp9yB68WpYgRe2bbaGuZ/se74IqFeVnMnLZg==}
+    engines: {node: '>=0.10.0'}
+
   has-bigints@1.1.0:
     resolution: {integrity: sha512-R3pbpkcIqv2Pm3dUwgjclDRVmWpTJW2DcMzcIhEXEx1oh/CEMObMm3KLmRJOdvhM7o4uQBnwr8pzRK2sJWIqfg==}
     engines: {node: '>= 0.4'}
@@ -3122,6 +3202,16 @@ packages:
     resolution: {integrity: sha512-EdDDZu4A2OyIK7Lr/2zG+w5jmbuk1DVBnEwREQvBzspBJkCEbRa8GxU1lghYcaGJCnRWibjDXlq779X1/y5xwg==}
     engines: {node: '>=8'}
 
+  inflight@1.0.6:
+    resolution: {integrity: sha512-k92I/b08q4wvFscXCLvqfsHCrjrF7yiXsQuIVvVE7N82W3+aqpzuUdBbfhWcy/FZR3/4IgflMgKLOsvPDrGCJA==}
+    deprecated: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
+
+  inherits@2.0.3:
+    resolution: {integrity: sha512-x00IRNXNy63jwGkJmzPigoySHbaqpNuzKbBOmzK+g2OdZpQ9w+sxCN+VSB3ja7IAge2OP2qpfxTjeNcyjmW1uw==}
+
+  inherits@2.0.4:
+    resolution: {integrity: sha512-k/vGaX4/Yla3WzyMCvTQOXYeIHvqOKtnqBduzTHpzpQZzAskKMhZ2K+EnBiSM9zGSoIFeMpXKxa4dYeZIQqewQ==}
+
   inline-style-parser@0.2.4:
     resolution: {integrity: sha512-0aO8FkhNZlj/ZIbNi7Lxxr12obT7cL1moPfE4tg1LkX7LlLfC6DeX4l2ZEud1ukP9jNQyNnfzQVqwbwmAATY4Q==}
 
@@ -3167,6 +3257,9 @@ packages:
     resolution: {integrity: sha512-wa56o2/ElJMYqjCjGkXri7it5FbebW5usLw/nPmCMs5DeZ7eziSYZhSmPRn0txqeW4LnAmQQU7FgqLpsEFKM4A==}
     engines: {node: '>= 0.4'}
 
+  is-buffer@1.1.6:
+    resolution: {integrity: sha512-NcdALwpXkTm5Zvvbk7owOUSvVvBKDgKP5/ewfXEznmQFfs4ZRmanOeKBTjRVjka3QFoN6XJ+9F3USqfHqTaU5w==}
+
   is-callable@1.2.7:
     resolution: {integrity: sha512-1BC0BVFhS/p0qtw6enp8e+8OD0UrK0oFLztSjNzhcKA3WDuJxxAPXzPuPtKkjEY9UUoEWlX/8fgKeu2S8i9JTA==}
     engines: {node: '>= 0.4'}
@@ -3186,6 +3279,10 @@ packages:
   is-decimal@2.0.1:
     resolution: {integrity: sha512-AAB9hiomQs5DXWcRB1rqsxGUstbRroFOPPVAomNk/3XHR5JyEZChOyTWe2oayKnsSsr/kcGqF+z6yuH6HHpN0A==}
 
+  is-extendable@0.1.1:
+    resolution: {integrity: sha512-5BMULNob1vgFX6EjQw5izWDxrecWK9AM72rugNr0TFldMOi0fj6Jk+zeKIt0xGj4cEfQIJth4w3OKWOJ4f+AFw==}
+    engines: {node: '>=0.10.0'}
+
   is-extglob@2.1.1:
     resolution: {integrity: sha512-SbKbANkN603Vi4jEZv49LeVJMn4yGwsbzZworEoyEiutsN3nJYdbO36zfhGJ6QEDpOZIFkDtnq5JRxmvl3jsoQ==}
     engines: {node: '>=0.10.0'}
@@ -3264,6 +3361,9 @@ packages:
     resolution: {integrity: sha512-mfcwb6IzQyOKTs84CQMrOwW4gQcaTOAWJ0zzJCl2WSPDrWk/OzDaImWFH3djXhb24g4eudZfLRozAvPGw4d9hQ==}
     engines: {node: '>= 0.4'}
 
+  isarray@1.0.0:
+    resolution: {integrity: sha512-VLghIWNM6ELQzo7zwmcg0NmTVyWKYjvIeM83yjp0wRDTmUnrM678fQbcKBo6n2CJEF0szoG//ytg+TKla89ALQ==}
+
   isarray@2.0.5:
     resolution: {integrity: sha512-xHjhDr3cNBK0BzdUJSPXZntQUx/mwMS5Rw4A7lPJ90XGAO6ISP/ePDNuo0vhqOZU+UD5JoodwCAAoZQd3FeAKw==}
 
@@ -3337,10 +3437,18 @@ packages:
   keyv@4.5.4:
     resolution: {integrity: sha512-oxVHkHR/EJf2CNXnWxRLW6mg7JyCCUcG0DtEGmL2ctUo1PNTin1PUil+r/+4r5MpVgC/fn1kjsx7mjSujKqIpw==}
 
+  kind-of@3.2.2:
+    resolution: {integrity: sha512-NOW9QQXMoZGg/oqnVNoNTTIFEIid1627WCffUBJEdMxYApq7mNE7CpzucIPc+ZQg25Phej7IJSmX3hO+oblOtQ==}
+    engines: {node: '>=0.10.0'}
+
   kysely@0.28.7:
     resolution: {integrity: sha512-u/cAuTL4DRIiO2/g4vNGRgklEKNIj5Q3CG7RoUB5DV5SfEC2hMvPxKi0GWPmnzwL2ryIeud2VTcEEmqzTzEPNw==}
     engines: {node: '>=20.0.0'}
 
+  lazy-cache@2.0.2:
+    resolution: {integrity: sha512-7vp2Acd2+Kz4XkzxGxaB1FWOi8KjWIWsgdfD5MCb86DWvlLqhRPM+d6Pro3iNEL5VT9mstz5hKAlcd+QR6H3aA==}
+    engines: {node: '>=0.10.0'}
+
   levn@0.4.1:
     resolution: {integrity: sha512-+bT2uH4E5LGE7h/n3evcS/sQlJXCpIp6ym8OWJ5eV6+67Dsql/LaaT7qJBAt2rzfoa/5QBGBhxDix1dMt2kQKQ==}
     engines: {node: '>= 0.8.0'}
@@ -3419,9 +3527,19 @@ packages:
     resolution: {integrity: sha512-iPZK6eYjbxRu3uB4/WZ3EsEIMJFMqAoopl3R+zuq0UjcAm/MO6KCweDgPfP3elTztoKP3KtnVHxTn2NHBSDVUw==}
     engines: {node: '>=10'}
 
+  lodash._reinterpolate@3.0.0:
+    resolution: {integrity: sha512-xYHt68QRoYGjeeM/XOE1uJtvXQAgvszfBhjV4yvsQH0u2i9I6cI6c6/eG4Hh3UAOVn0y/xAXwmTzEay49Q//HA==}
+
   lodash.merge@4.6.2:
     resolution: {integrity: sha512-0KpjqXRVvrYyCsX1swR/XTK0va6VQkQM6MNo7PqW77ByjAhoARA8EfrP1N4+KlKj8YS0ZUCtRT/YUuhyYDujIQ==}
 
+  lodash.template@4.5.0:
+    resolution: {integrity: sha512-84vYFxIkmidUiFxidA/KjjH9pAycqW+h980j7Fuz5qxRtO9pgB7MDFTdys1N7A5mcucRiDyEq4fusljItR1T/A==}
+    deprecated: This package is deprecated. Use https://socket.dev/npm/package/eta instead.
+
+  lodash.templatesettings@4.2.0:
+    resolution: {integrity: sha512-stgLz+i3Aa9mZgnjr/O+v9ruKZsPsndy7qPZOchbqk2cnTU1ZaldKK+v7m54WoKIyxiuMZTKT2H81F8BeAc3ZQ==}
+
   lodash@4.17.21:
     resolution: {integrity: sha512-v2kDEe57lecTulaDIuNTPy3Ry4gLGJ6Z1O3vE1krgXZNrsQ+LFTGHVxVjcXPs17LhbZVGedAJv8XZ1tvj5FvSg==}
 
@@ -3533,6 +3651,10 @@ packages:
   meilisearch@0.53.0:
     resolution: {integrity: sha512-nG4VXbEOSzUmtbfsgOo+t6yX1ECEgXaT4hC0ap9MBpQGK5xwT+NWYDENYsKWR75cVaWaAqva+ok4zHlgtdXlLw==}
 
+  meow@14.0.0:
+    resolution: {integrity: sha512-JhC3R1f6dbspVtmF3vKjAWz1EVIvwFrGGPLSdU6rK79xBwHWTuHoLnRX/t1/zHS1Ch1Y2UtIrih7DAHuH9JFJA==}
+    engines: {node: '>=20'}
+
   merge2@1.4.1:
     resolution: {integrity: sha512-8q7VEgMJW4J8tcfVPy8g09NcQwZdbwFEqhe/WZkoIzjn/3TGDwtOCYtXGxA3O8tPzpczCCDgv+P2P5y00ZJOOg==}
     engines: {node: '>= 8'}
@@ -3857,6 +3979,9 @@ packages:
     resolution: {integrity: sha512-gXah6aZrcUxjWg2zR2MwouP2eHlCBzdV4pygudehaKXSGW4v2AsRQUK+lwwXhii6KFZcunEnmSUoYp5CXibxtA==}
     engines: {node: '>= 0.4'}
 
+  once@1.4.0:
+    resolution: {integrity: sha512-lNaJgI+2Q5URQBkccEKHTQOPaXdUxnZZElQTZY0MFUAuaEqe1E+Nyvgdz/aIyNi6Z9MzO5dv1H8n58/GELp3+w==}
+
   oniguruma-parser@0.12.1:
     resolution: {integrity: sha512-8Unqkvk1RYc6yq2WBYRj4hdnsAxVze8i7iPfQr8e4uSP3tRv0rpZcbGUDvxfQQcdwHt/e9PrMvGCsa8OqG9X3w==}
 
@@ -3896,6 +4021,10 @@ packages:
     resolution: {integrity: sha512-ak9Qy5Q7jYb2Wwcey5Fpvg2KoAc/ZIhLSLOSBmRmygPsGwkVVt0fZa0qrtMz+m6tJTAHfZQ8FnmB4MG4LWy7/w==}
     engines: {node: '>=8'}
 
+  path-is-absolute@1.0.1:
+    resolution: {integrity: sha512-AVbw3UJ2e9bq64vSaS9Am0fje1Pa8pbGqTTsmXfaIiMpnr5DlDhfJOuLj9Sf95ZPVDAUerDfEk88MPmPe7UCQg==}
+    engines: {node: '>=0.10.0'}
+
   path-key@3.1.1:
     resolution: {integrity: sha512-ojmeN0qd+y0jszEtoY48r0Peq5dwMEkIlCOu6Q5f41lfkswXuKtYrhgoTpLnyIcHm24Uhqx+5Tqm2InSwLhE6Q==}
     engines: {node: '>=8'}
@@ -3903,6 +4032,9 @@ packages:
   path-parse@1.0.7:
     resolution: {integrity: sha512-LDJzPVEEEPR+y48z93A0Ed0yXb8pAByGWo/k5YYdYgpY2/2EsOsksJrq7lOHxryrVOn1ejG6oAp8ahvOIQD8sw==}
 
+  path@0.12.7:
+    resolution: {integrity: sha512-aXXC6s+1w7otVF9UletFkFcDsJeO7lSZBPUQhtb5O0xJe8LtYhj/GxldoL09bBj9+ZmE2hNoHqQSFMN5fikh4Q==}
+
   picocolors@1.1.1:
     resolution: {integrity: sha512-xceH2snhtb5M9liqDsmEw56le376mTZkEX/jEb/RxNFyegNul7eNslCXP9FDj/Lcu0X8KEyMceP2ntpaHrDEVA==}
 
@@ -4007,6 +4139,13 @@ packages:
     resolution: {integrity: sha512-Qb1gy5OrP5+zDf2Bvnzdl3jsTf1qXVMazbvCoKhtKqVs4/YK4ozX4gKQJJVyNe+cajNPn0KoC0MC3FUmaHWEmQ==}
     engines: {node: ^10.13.0 || ^12.13.0 || ^14.15.0 || >=15.0.0}
 
+  process-nextick-args@2.0.1:
+    resolution: {integrity: sha512-3ouUOpQhtgrbOa17J7+uxOTpITYWaGP7/AhoR3+A+/1e9skrzelGi/dXzEYyvbxubEF6Wn2ypscTKiKJFFn1ag==}
+
+  process@0.11.10:
+    resolution: {integrity: sha512-cdGef/drWFoydD1JsMzuFf8100nZl+GT+yacc2bEced5f9Rjk4z+WtFUTBu9PhOi9j/jfmBPu0mMEY4wIdAF8A==}
+    engines: {node: '>= 0.6.0'}
+
   prop-types@15.8.1:
     resolution: {integrity: sha512-oj87CgZICdulUohogVAR7AjlC0327U4el4L6eAvOqCeudMDVU0NThNaV+b9Df4dXgSP1gXMTnPdhfe/2qDH5cg==}
 
@@ -4119,6 +4258,9 @@ packages:
     resolution: {integrity: sha512-w8nqGImo45dmMIfljjMwOGtbmC/mk4CMYhWIicdSflH91J9TyCyczcPFXJzrZ/ZXcgGRFeP6BU0BEJTw6tZdfQ==}
     engines: {node: '>=0.10.0'}
 
+  readable-stream@2.3.8:
+    resolution: {integrity: sha512-8p0AUk4XODgIewSi0l8Epjs+EVnWiK7NoDIEGU0HhE7+ZyY8D1IMY7odu5lRrFXGg71L15KG8QrPmum45RTtdA==}
+
   readdirp@4.1.2:
     resolution: {integrity: sha512-GDhwkLfywWL2s6vEjyhri+eXmfH6j1L7JE27WhqLeYzoh/A3DBaYGEj2H/HFZCn/kMfim73FXxEJTw06WtxQwg==}
     engines: {node: '>= 14.18.0'}
@@ -4206,6 +4348,11 @@ packages:
   remark-stringify@11.0.0:
     resolution: {integrity: sha512-1OSmLd3awB/t8qdoEOMazZkNsfVTeY4fTsgzcQFdXNq8ToTN4ZGwrMnlda4K6smTFKD+GRV6O48i6Z4iKgPPpw==}
 
+  remarkable@1.7.4:
+    resolution: {integrity: sha512-e6NKUXgX95whv7IgddywbeN/ItCkWbISmc2DiqHJb0wTrqZIexqdco5b8Z3XZoo/48IdNVKM9ZCvTPJ4F5uvhg==}
+    engines: {node: '>= 0.10.0'}
+    hasBin: true
+
   reselect@5.1.1:
     resolution: {integrity: sha512-K/BG6eIky/SBpzfHZv/dd+9JBFiS4SWV7FIujVyJRux6e45+73RaUHXLmIR1f7WOMaQ0U1km6qwklRQxpJJY0w==}
 
@@ -4253,6 +4400,9 @@ packages:
     resolution: {integrity: sha512-AURm5f0jYEOydBj7VQlVvDrjeFgthDdEF5H1dP+6mNpoXOMo1quQqJ4wvJDyRZ9+pO3kGWoOdmV08cSv2aJV6Q==}
     engines: {node: '>=0.4'}
 
+  safe-buffer@5.1.2:
+    resolution: {integrity: sha512-Gd2UZBJDkXlY7GbJxfsE8/nvKkUEU1G38c1siN6QP6a9PT9MmHB8GnpscSmMJSoF8LOIrt8ud/wPtojys4G6+g==}
+
   safe-push-apply@1.0.0:
     resolution: {integrity: sha512-iKE9w/Z7xCzUMIZqdBsp6pEQvwuEebH4vdpjcDWnyzaI6yl6O9FHvVpmGelvEHNsoY6wGblkxR6Zty/h00WiSA==}
     engines: {node: '>= 0.4'}
@@ -4313,6 +4463,10 @@ packages:
     resolution: {integrity: sha512-7PGFlmtwsEADb0WYyvCMa1t+yke6daIG4Wirafur5kcf+MhUnPms1UeR0CKQdTZD81yESwMHbtn+TR+dMviakQ==}
     engines: {node: '>= 0.4'}
 
+  set-getter@0.1.1:
+    resolution: {integrity: sha512-9sVWOy+gthr+0G9DzqqLaYNA7+5OKkSmcqjL9cBpDEaZrr3ShQlyX2cZ/O/ozE41oxn/Tt0LGEM/w4Rub3A3gw==}
+    engines: {node: '>=0.10.0'}
+
   set-harmonic-interval@1.0.1:
     resolution: {integrity: sha512-AhICkFV84tBP1aWqPwLZqFvAwqEoVA9kxNMniGEUvzOlm4vLmOFLiTT3UZ6bziJTy4bOVpzWGTfSCbmaayGx8g==}
     engines: {node: '>=6.9'}
@@ -4352,6 +4506,10 @@ packages:
     resolution: {integrity: sha512-ZX99e6tRweoUXqR+VBrslhda51Nh5MTQwou5tnUDgbtyM0dBgmhEDtWGP/xbKn6hqfPRHujUNwz5fy/wbbhnpw==}
     engines: {node: '>= 0.4'}
 
+  slash@3.0.0:
+    resolution: {integrity: sha512-g9Q1haeby36OSStwb4ntCGGGaKsaVSjQ68fBxoQcutl5fS1vuY18H3wSt3jFyFtrkx+Kz0V1G85A4MyAdDMi2Q==}
+    engines: {node: '>=8'}
+
   sonner@2.0.7:
     resolution: {integrity: sha512-W6ZN4p58k8aDKA4XPcx2hpIQXBRAgyiWVkYhT7CvK6D3iAu7xjvVyhQHg2/iaKJZ1XVJ4r7XuwGL+WGEK37i9w==}
     peerDependencies:
@@ -4418,9 +4576,16 @@ packages:
     resolution: {integrity: sha512-UXSH262CSZY1tfu3G3Secr6uGLCFVPMhIqHjlgCUtCCcgihYc/xKs9djMTMUOb2j1mVSeU8EU6NWc/iQKU6Gfg==}
     engines: {node: '>= 0.4'}
 
+  string_decoder@1.1.1:
+    resolution: {integrity: sha512-n/ShnvDi6FHbbVfviro+WojiFzv+s8MPMHBczVePfUpDJLwoLT0ht1l4YwBCbi8pJAveEEdnkHyPyTP/mzRfwg==}
+
   stringify-entities@4.0.4:
     resolution: {integrity: sha512-IwfBptatlO+QCJUo19AqvrPNqlVMpW9YEL2LIVY+Rpv2qsjCGxaDLNRgeGsQWJhfItebuJhsGSLjaBbNSQ+ieg==}
 
+  strip-ansi@3.0.1:
+    resolution: {integrity: sha512-VhumSSbBqDTP8p2ZLKj40UjBCV4+v8bUSEpUb4KjRgWk9pbqGF4REFj6KEagidb2f/M6AzC0EmFyDNGaw9OCzg==}
+    engines: {node: '>=0.10.0'}
+
   strip-bom@3.0.0:
     resolution: {integrity: sha512-vavAMRXOgBVNF6nyEEmL3DBK19iRpDcoIwW+swQ+CbGiu7lju6t+JklA1MHweoWtadgt4ISVUsXLyDq34ddcwA==}
     engines: {node: '>=4'}
@@ -4471,6 +4636,10 @@ packages:
   super-media-element@1.4.2:
     resolution: {integrity: sha512-9pP/CVNp4NF2MNlRzLwQkjiTgKKe9WYXrLh9+8QokWmMxz+zt2mf1utkWLco26IuA3AfVcTb//qtlTIjY3VHxA==}
 
+  supports-color@2.0.0:
+    resolution: {integrity: sha512-KKNVtd6pCYgPIKU4cp2733HWYCpplQhddZLBUryaAHou723x+FRzQ5Df824Fj+IyyuiQTRoub4SnIFfIcrp70g==}
+    engines: {node: '>=0.8.0'}
+
   supports-color@7.2.0:
     resolution: {integrity: sha512-qpCAvRl9stuOHveKsn7HncJRvv501qIacKzQlO/+Lwxc9+0q2wLyv4Dfvt80/DPn2pqOBsJdDiogXGR9+OvwRw==}
     engines: {node: '>=8'}
@@ -4505,6 +4674,9 @@ packages:
     resolution: {integrity: sha512-dTEWWNu6JmeVXY0ZYoPuH5cRIwc0MeGbJwah9KUNYSJwommQpCzTySTpEe8Gs1J23aeWEuAobe4Ag7EHVt/LOg==}
     engines: {node: '>=10'}
 
+  through2@2.0.5:
+    resolution: {integrity: sha512-/mrRod8xqpA+IHSLyGCQ2s8SPHiCDEeQJSep1jqLYeEUClOFG2Qsh+4FU6G9VeqpZnGW/Su8LQGc4YKni5rYSQ==}
+
   tiktok-video-element@0.1.1:
     resolution: {integrity: sha512-BaiVzvNz2UXDKTdSrXzrNf4q6Ecc+/utYUh7zdEu2jzYcJVDoqYbVfUl0bCfMoOeeAqg28vD/yN63Y3E9jOrlA==}
 
@@ -4522,6 +4694,10 @@ packages:
     resolution: {integrity: sha512-WMi/OQ2axVTf/ykqCQgXiIct+mSQDFdH2fkwhPwgEwvJ1kSzZRiinb0zF2Xb8u4+OqPChmyI6MEu4EezNJz+FQ==}
     hasBin: true
 
+  to-object-path@0.3.0:
+    resolution: {integrity: sha512-9mWHdnGRuh3onocaHzukyvCZhzvr6tiflAy/JRFXcJX0TjgfWA9pk9t8CMbzmBE4Jfw58pXbkngtBtqYxzNEyg==}
+    engines: {node: '>=0.10.0'}
+
   to-regex-range@5.0.1:
     resolution: {integrity: sha512-65P7iz6X5yEr1cwcgvQxbbIw7Uk3gOy5dIdtZ4rDveLqhrdJP+Li/Hx6tyK0NEb+2GCyneCMJiGqrADCSNk8sQ==}
     engines: {node: '>=8.0'}
@@ -4529,6 +4705,9 @@ packages:
   toggle-selection@1.0.6:
     resolution: {integrity: sha512-BiZS+C1OS8g/q2RRbJmy59xpyghNBqrr6k5L/uKBGRsTfxmu3ffiRnd8mlGPUVayg8pvfi5urfnu8TU7DVOkLQ==}
 
+  toml@2.3.6:
+    resolution: {integrity: sha512-gVweAectJU3ebq//Ferr2JUY4WKSDe5N+z0FvjDncLGyHmIDoxgY/2Ie4qfEIDm4IS7OA6Rmdm7pdEEdMcV/xQ==}
+
   tough-cookie@5.1.2:
     resolution: {integrity: sha512-FVDYdxtnj0G6Qm/DhNPSb8Ju59ULcup3tuJxkFb5K8Bv2pUXILbf0xZWU8PX8Ov19OXljbUyveOFwRMwkXzO+A==}
     engines: {node: '>=16'}
@@ -4723,6 +4902,9 @@ packages:
   util-deprecate@1.0.2:
     resolution: {integrity: sha512-EPD5q1uXyFxJpCrLnCc1nHnq3gOa6DZBocAIiI2TaSCA7VCJ1UJDMagCzIkXNsUYfD1daK//LTEQ8xiIbrHtcw==}
 
+  util@0.10.4:
+    resolution: {integrity: sha512-0Pm9hTQ3se5ll1XihRic3FDIku70C+iHUdT/W926rSgHV5QgXsYbKZN8MSC3tJtSkhuROzvsQjAaFENRXr+19A==}
+
   v8-compile-cache-lib@3.0.1:
     resolution: {integrity: sha512-wa7YjyUGfNZngI/vtK0UHAN+lgDCxBPCylVXGp0zu59Fz5aiGtNXaq3DhIov063MorB+VfufLh3JlF2KdTK3xg==}
 
@@ -4839,6 +5021,9 @@ packages:
     resolution: {integrity: sha512-BN22B5eaMMI9UMtjrGd5g5eCYPpCPDUy0FJXbYsaT5zYxjFOckS53SQDE3pWkVoWpHXVb3BrYcEN4Twa55B5cA==}
     engines: {node: '>=0.10.0'}
 
+  wrappy@1.0.2:
+    resolution: {integrity: sha512-l4Sp/DRseor9wL6EvV2+TuQn63dMkPjZ/sp9XkghTEbV9KlPS1xUsZ3u7/IQO4wxtcFB4bgpQPRcR3QCvezPcQ==}
+
   ws@8.18.3:
     resolution: {integrity: sha512-PEIGCY5tSlUt50cqyMXfCzX+oOPqN0vuGqWzbcJ2xvnkzkq46oOpz7dQaTDBdfICb4N14+GARUDw2XV2N4tvzg==}
     engines: {node: '>=10.0.0'}
@@ -4862,6 +5047,10 @@ packages:
   xmlchars@2.2.0:
     resolution: {integrity: sha512-JZnDKK8B0RCDw84FNdDAIpZK+JuJw+s7Lz8nksI7SIuU3UXJJslUthsi+uWBUYOwPFwW7W7PRLRfUKpxjtjFCw==}
 
+  xtend@4.0.2:
+    resolution: {integrity: sha512-LKYU1iAXJXUgAXn9URjiu+MWhyUXHsvfp7mcuYm9dSUKK0/CjtrUwFAxD82/mCWbtLsGjFIad0wIsod4zrTAEQ==}
+    engines: {node: '>=0.4'}
+
   yallist@3.1.1:
     resolution: {integrity: sha512-a4UGQaWPH59mOXUYnAG2ewncQS4i4F43Tv3JoAM+s2VDAmS9NsK8GpDMLrCHPksFT7h3K6TOoUNn2pb7RoXx4g==}
 
@@ -6754,6 +6943,17 @@ snapshots:
 
   acorn@8.15.0: {}
 
+  adr-log@2.2.0:
+    dependencies:
+      console-stamp: 0.2.10
+      glob: 7.2.3
+      gray-matter: 2.1.1
+      lazy-cache: 2.0.2
+      minimist: 1.2.8
+      path: 0.12.7
+      remarkable: 1.7.4
+      slash: 3.0.0
+
   agent-base@7.1.4: {}
 
   ajv@6.12.6:
@@ -6763,14 +6963,24 @@ snapshots:
       json-schema-traverse: 0.4.1
       uri-js: 4.4.1
 
+  ansi-red@0.1.1:
+    dependencies:
+      ansi-wrap: 0.1.0
+
+  ansi-regex@2.1.1: {}
+
   ansi-regex@5.0.1: {}
 
+  ansi-styles@2.2.1: {}
+
   ansi-styles@4.3.0:
     dependencies:
       color-convert: 2.0.1
 
   ansi-styles@5.2.0: {}
 
+  ansi-wrap@0.1.0: {}
+
   arg@4.1.3: {}
 
   argparse@1.0.10:
@@ -6866,6 +7076,10 @@ snapshots:
 
   async-function@1.0.0: {}
 
+  autolinker@0.28.1:
+    dependencies:
+      gulp-header: 1.8.12
+
   available-typed-arrays@1.0.7:
     dependencies:
       possible-typed-array-names: 1.1.0
@@ -6969,6 +7183,14 @@ snapshots:
     dependencies:
       react: 19.1.1
 
+  chalk@1.1.3:
+    dependencies:
+      ansi-styles: 2.2.1
+      escape-string-regexp: 1.0.5
+      has-ansi: 2.0.0
+      strip-ansi: 3.0.1
+      supports-color: 2.0.0
+
   chalk@4.1.2:
     dependencies:
       ansi-styles: 4.3.0
@@ -7012,6 +7234,8 @@ snapshots:
 
   codem-isoboxer@0.3.10: {}
 
+  coffee-script@1.12.7: {}
+
   collapse-white-space@2.1.0: {}
 
   color-convert@2.0.1:
@@ -7024,12 +7248,23 @@ snapshots:
 
   concat-map@0.0.1: {}
 
+  concat-with-sourcemaps@1.1.0:
+    dependencies:
+      source-map: 0.6.1
+
+  console-stamp@0.2.10:
+    dependencies:
+      chalk: 1.1.3
+      dateformat: 1.0.11
+
   convert-source-map@2.0.0: {}
 
   copy-to-clipboard@3.3.3:
     dependencies:
       toggle-selection: 1.0.6
 
+  core-util-is@1.0.3: {}
+
   create-require@1.1.1: {}
 
   cross-fetch@4.1.0:
@@ -7148,6 +7383,11 @@ snapshots:
 
   date-fns@4.1.0: {}
 
+  dateformat@1.0.11:
+    dependencies:
+      get-stdin: 9.0.0
+      meow: 14.0.0
+
   debug@3.2.7:
     dependencies:
       ms: 2.1.3
@@ -7372,6 +7612,8 @@ snapshots:
 
   escalade@3.2.0: {}
 
+  escape-string-regexp@1.0.5: {}
+
   escape-string-regexp@4.0.0: {}
 
   escape-string-regexp@5.0.0: {}
@@ -7559,6 +7801,10 @@ snapshots:
 
   eventemitter3@5.0.1: {}
 
+  extend-shallow@2.0.1:
+    dependencies:
+      is-extendable: 0.1.1
+
   extend@3.0.2: {}
 
   fast-content-type-parse@3.0.0: {}
@@ -7638,6 +7884,8 @@ snapshots:
     dependencies:
       js-yaml: 3.14.1
 
+  fs.realpath@1.0.0: {}
+
   fsevents@2.3.3:
     optional: true
 
@@ -7678,6 +7926,8 @@ snapshots:
       dunder-proto: 1.0.1
       es-object-atoms: 1.1.1
 
+  get-stdin@9.0.0: {}
+
   get-symbol-description@1.1.0:
     dependencies:
       call-bound: 1.0.4
@@ -7698,6 +7948,15 @@ snapshots:
     dependencies:
       is-glob: 4.0.3
 
+  glob@7.2.3:
+    dependencies:
+      fs.realpath: 1.0.0
+      inflight: 1.0.6
+      inherits: 2.0.4
+      minimatch: 3.1.2
+      once: 1.4.0
+      path-is-absolute: 1.0.1
+
   globals@14.0.0: {}
 
   globals@16.4.0: {}
@@ -7713,6 +7972,24 @@ snapshots:
 
   graphemer@1.4.0: {}
 
+  gray-matter@2.1.1:
+    dependencies:
+      ansi-red: 0.1.1
+      coffee-script: 1.12.7
+      extend-shallow: 2.0.1
+      js-yaml: 3.14.1
+      toml: 2.3.6
+
+  gulp-header@1.8.12:
+    dependencies:
+      concat-with-sourcemaps: 1.1.0
+      lodash.template: 4.5.0
+      through2: 2.0.5
+
+  has-ansi@2.0.0:
+    dependencies:
+      ansi-regex: 2.1.1
+
   has-bigints@1.1.0: {}
 
   has-flag@4.0.0: {}
@@ -7865,6 +8142,15 @@ snapshots:
 
   indent-string@4.0.0: {}
 
+  inflight@1.0.6:
+    dependencies:
+      once: 1.4.0
+      wrappy: 1.0.2
+
+  inherits@2.0.3: {}
+
+  inherits@2.0.4: {}
+
   inline-style-parser@0.2.4: {}
 
   inline-style-prefixer@7.0.1:
@@ -7921,6 +8207,8 @@ snapshots:
       call-bound: 1.0.4
       has-tostringtag: 1.0.2
 
+  is-buffer@1.1.6: {}
+
   is-callable@1.2.7: {}
 
   is-core-module@2.16.1:
@@ -7940,6 +8228,8 @@ snapshots:
 
   is-decimal@2.0.1: {}
 
+  is-extendable@0.1.1: {}
+
   is-extglob@2.1.1: {}
 
   is-finalizationregistry@1.1.1:
@@ -8014,6 +8304,8 @@ snapshots:
       call-bound: 1.0.4
       get-intrinsic: 1.3.0
 
+  isarray@1.0.0: {}
+
   isarray@2.0.5: {}
 
   isexe@2.0.0: {}
@@ -8098,8 +8390,16 @@ snapshots:
     dependencies:
       json-buffer: 3.0.1
 
+  kind-of@3.2.2:
+    dependencies:
+      is-buffer: 1.1.6
+
   kysely@0.28.7: {}
 
+  lazy-cache@2.0.2:
+    dependencies:
+      set-getter: 0.1.1
+
   levn@0.4.1:
     dependencies:
       prelude-ls: 1.2.1
@@ -8162,8 +8462,19 @@ snapshots:
     dependencies:
       p-locate: 5.0.0
 
+  lodash._reinterpolate@3.0.0: {}
+
   lodash.merge@4.6.2: {}
 
+  lodash.template@4.5.0:
+    dependencies:
+      lodash._reinterpolate: 3.0.0
+      lodash.templatesettings: 4.2.0
+
+  lodash.templatesettings@4.2.0:
+    dependencies:
+      lodash._reinterpolate: 3.0.0
+
   lodash@4.17.21: {}
 
   longest-streak@3.1.0: {}
@@ -8381,6 +8692,8 @@ snapshots:
 
   meilisearch@0.53.0: {}
 
+  meow@14.0.0: {}
+
   merge2@1.4.1: {}
 
   micromark-core-commonmark@2.0.3:
@@ -8842,6 +9155,10 @@ snapshots:
       define-properties: 1.2.1
       es-object-atoms: 1.1.1
 
+  once@1.4.0:
+    dependencies:
+      wrappy: 1.0.2
+
   oniguruma-parser@0.12.1: {}
 
   oniguruma-to-es@4.3.3:
@@ -8895,10 +9212,17 @@ snapshots:
 
   path-exists@4.0.0: {}
 
+  path-is-absolute@1.0.1: {}
+
   path-key@3.1.1: {}
 
   path-parse@1.0.7: {}
 
+  path@0.12.7:
+    dependencies:
+      process: 0.11.10
+      util: 0.10.4
+
   picocolors@1.1.1: {}
 
   picomatch@2.3.1: {}
@@ -8950,6 +9274,10 @@ snapshots:
       ansi-styles: 5.2.0
       react-is: 17.0.2
 
+  process-nextick-args@2.0.1: {}
+
+  process@0.11.10: {}
+
   prop-types@15.8.1:
     dependencies:
       loose-envify: 1.4.0
@@ -9068,6 +9396,16 @@ snapshots:
 
   react@19.1.1: {}
 
+  readable-stream@2.3.8:
+    dependencies:
+      core-util-is: 1.0.3
+      inherits: 2.0.4
+      isarray: 1.0.0
+      process-nextick-args: 2.0.1
+      safe-buffer: 5.1.2
+      string_decoder: 1.1.1
+      util-deprecate: 1.0.2
+
   readdirp@4.1.2: {}
 
   recharts@3.2.1(react-dom@19.1.1(react@19.1.1))(react-is@17.0.2)(react@19.1.1)(redux@5.0.1)(types-react@19.0.0-rc.1):
@@ -9237,6 +9575,11 @@ snapshots:
       mdast-util-to-markdown: 2.1.2
       unified: 11.0.5
 
+  remarkable@1.7.4:
+    dependencies:
+      argparse: 1.0.10
+      autolinker: 0.28.1
+
   reselect@5.1.1: {}
 
   resize-observer-polyfill@1.5.1: {}
@@ -9307,6 +9650,8 @@ snapshots:
       has-symbols: 1.1.0
       isarray: 2.0.5
 
+  safe-buffer@5.1.2: {}
+
   safe-push-apply@1.0.0:
     dependencies:
       es-errors: 1.3.0
@@ -9368,6 +9713,10 @@ snapshots:
       functions-have-names: 1.2.3
       has-property-descriptors: 1.0.2
 
+  set-getter@0.1.1:
+    dependencies:
+      to-object-path: 0.3.0
+
   set-harmonic-interval@1.0.1: {}
 
   set-proto@1.0.0:
@@ -9450,6 +9799,8 @@ snapshots:
       side-channel-map: 1.0.1
       side-channel-weakmap: 1.0.2
 
+  slash@3.0.0: {}
+
   sonner@2.0.7(react-dom@19.1.1(react@19.1.1))(react@19.1.1):
     dependencies:
       react: 19.1.1
@@ -9535,11 +9886,19 @@ snapshots:
       define-properties: 1.2.1
       es-object-atoms: 1.1.1
 
+  string_decoder@1.1.1:
+    dependencies:
+      safe-buffer: 5.1.2
+
   stringify-entities@4.0.4:
     dependencies:
       character-entities-html4: 2.1.0
       character-entities-legacy: 3.0.0
 
+  strip-ansi@3.0.1:
+    dependencies:
+      ansi-regex: 2.1.1
+
   strip-bom@3.0.0: {}
 
   strip-indent@3.0.0:
@@ -9574,6 +9933,8 @@ snapshots:
 
   super-media-element@1.4.2: {}
 
+  supports-color@2.0.0: {}
+
   supports-color@7.2.0:
     dependencies:
       has-flag: 4.0.0
@@ -9602,6 +9963,11 @@ snapshots:
 
   throttle-debounce@3.0.1: {}
 
+  through2@2.0.5:
+    dependencies:
+      readable-stream: 2.3.8
+      xtend: 4.0.2
+
   tiktok-video-element@0.1.1: {}
 
   tiny-invariant@1.3.3: {}
@@ -9617,12 +9983,18 @@ snapshots:
     dependencies:
       tldts-core: 6.1.86
 
+  to-object-path@0.3.0:
+    dependencies:
+      kind-of: 3.2.2
+
   to-regex-range@5.0.1:
     dependencies:
       is-number: 7.0.0
 
   toggle-selection@1.0.6: {}
 
+  toml@2.3.6: {}
+
   tough-cookie@5.1.2:
     dependencies:
       tldts: 6.1.86
@@ -9845,6 +10217,10 @@ snapshots:
 
   util-deprecate@1.0.2: {}
 
+  util@0.10.4:
+    dependencies:
+      inherits: 2.0.3
+
   v8-compile-cache-lib@3.0.1: {}
 
   vfile-matter@5.0.1:
@@ -9977,6 +10353,8 @@ snapshots:
 
   word-wrap@1.2.5: {}
 
+  wrappy@1.0.2: {}
+
   ws@8.18.3: {}
 
   xml-js@1.6.11:
@@ -9987,6 +10365,8 @@ snapshots:
 
   xmlchars@2.2.0: {}
 
+  xtend@4.0.2: {}
+
   yallist@3.1.1: {}
 
   yallist@5.0.0: {}