docs: update ESLint configuration references and improve i18n import paths

Author: JeremyDolle

documentation/docs/03-Project Structure.md

@@ -31,7 +31,7 @@ To achieve this, the project structure is thoughtfully organized into distinct s
 | `jest.config.js`   | Configuration file for Jest testing.                |
 | `tsconfig.json`    | TypeScript configuration (for TypeScript projects). |
 | `src/app.tsx`      | Main component of the application.                  |
-| `eslint.config.js` | ESLint configuration with project structure rules.  |
+| `eslint.config.mjs` | ESLint configuration with project structure rules.  |
 
 ## Atomic Design
 

documentation/docs/04-Guides/09-ESLint.md

@@ -12,9 +12,9 @@ These rules help maintain consistency and prevent common architectural issues as
 :::tip Optional Strict Rules
 The project structure enforcement rules are **intentionally strict** to maintain architectural consistency. However, they are:
 - **Evolutionary**: These rules will be refined and updated over time as best practices emerge
-- **Optional**: If you find them too restrictive for your use case, you can disable them by commenting out the project-structure configuration in `eslint.config.js`:
+- **Optional**: If you find them too restrictive for your use case, you can disable them by commenting out the project-structure configuration in `eslint.config.mjs`:
 
-```js title="eslint.config.js"
+```js title="eslint.config.mjs"
 export default defineConfig([
   // {
   //   files: ['**/*.{js,jsx,ts,tsx}'],
@@ -40,7 +40,7 @@ You can also selectively disable specific rules (e.g., only keep `folder-structu
 
 The boilerplate now uses a modern ESLint flat config with several powerful plugins:
 
-```js title="eslint.config.js"
+```js title="eslint.config.mjs"
 import { defineConfig } from 'eslint/config';
 import tseslint from 'typescript-eslint';
 import eslint from '@eslint/js';
@@ -64,7 +64,7 @@ export default defineConfig([
 
 The ESLint configuration works seamlessly with both TypeScript and JavaScript projects:
 
-```js title="eslint.config.js"
+```js title="eslint.config.mjs"
 export default defineConfig([
   // ... TypeScript configs
 
@@ -543,7 +543,7 @@ npm run lint
 
 If TypeScript type checking is slow:
 
-```js title="eslint.config.js"
+```js title="eslint.config.mjs"
 {
   languageOptions: {
     parserOptions: {

documentation/docs/10-FAQ.md

@@ -89,7 +89,7 @@ This means you get the same architectural enforcement and code quality rules reg
 
 ### Can I disable the strict project structure rules?
 
-Yes! The project structure enforcement rules are optional. You can disable them by commenting out the configuration in `eslint.config.js`:
+Yes! The project structure enforcement rules are optional. You can disable them by commenting out the configuration in `eslint.config.mjs`:
 
 ```js
 // Comment out this section to disable project structure enforcement

template/eslint.config.js template/eslint.config.mjstemplate/eslint.config.js renamed to template/eslint.config.mjs

@@ -4,8 +4,8 @@ import i18n from 'i18next';
 import { initReactI18next } from 'react-i18next';
 import * as z from 'zod';
 
-import en from '../../translations/en-EN.json';
-import fr from '../../translations/fr-FR.json';
+import en from '@/translations/en-en.json';
+import fr from '@/translations/fr-fr.json';
 
 export const enum SupportedLanguages {
   EN_EN = 'en-EN',