docs: enhance installation and FAQ sections with Windows-specific troubleshooting tips

Author: JeremyDolle

documentation/docs/02-Installation.md

@@ -50,6 +50,12 @@ If you choose **No**, the boilerplate will automatically:
 
 The resulting project will be pure JavaScript while maintaining the same architecture and structure.
 
+:::tip Windows Users
+If you're on Windows, we recommend using **Git Bash** or **WSL** for the installation process. The JavaScript compilation uses POSIX shell commands that are not available in Command Prompt or PowerShell.
+
+If you encounter `spawnSync ENOENT` errors, ensure you're using Git Bash or check the [FAQ troubleshooting section](/docs/faq#installation--troubleshooting).
+:::
+
 :::note ESLint Configuration
 The ESLint configuration is designed to work with both TypeScript and JavaScript projects. When using JavaScript, TypeScript-specific rules are automatically disabled.
 :::

documentation/docs/10-FAQ.md

@@ -51,6 +51,20 @@ Yes, but it's not automated after initialization. You would need to:
 
 **Recommendation**: Make this choice during project initialization as it's much simpler.
 
+## Installation & Troubleshooting
+
+### Installation fails on Windows
+
+**Recommendation**: Use Git Bash or WSL (Windows Subsystem for Linux) for the best experience.
+
+The boilerplate uses POSIX shell commands (`cp`, `rm`, etc.) which are not available in Windows Command Prompt or PowerShell.
+
+**Options**:
+1. **Git Bash** (recommended for Windows): Comes with Git for Windows
+2. **WSL**: Full Linux environment on Windows
+3. **PowerShell with Unix commands**: Install [Git for Windows](https://gitforwindows.org/) which includes basic Unix utilities
+
+
 ## ESLint & Code Quality
 
 ### Are ESLint rules the same for JavaScript and TypeScript?