Documentation update for nginx and IIS

Author: codehippie1

docs-website/docs/getting-started.md

@@ -116,17 +116,27 @@ export class AppComponent {
 
 ### Production Issues?
 
-**PDF viewer stuck at loading screen in production (nginx)**
+**PDF viewer stuck at loading screen in production**
 
-This is caused by incorrect MIME types for `.mjs` files. Add to your nginx configuration:
+This is caused by incorrect MIME types for `.mjs` and `.ftl` files.
 
+**Nginx configuration:**
 ```nginx
 types {
     application/javascript  js mjs;
+    text/plain             ftl;
 }
 ```
 
-**Why**: PDF.js v5+ uses ES modules (`.mjs` files) that need proper MIME type configuration.
+**IIS configuration (web.config):**
+```xml
+<staticContent>
+  <mimeMap fileExtension=".mjs" mimeType="application/javascript" />
+  <mimeMap fileExtension=".ftl" mimeType="text/plain" />
+</staticContent>
+```
+
+**Why**: PDF.js v5+ uses ES modules (`.mjs`) and localization files (`.ftl`) that need proper MIME type configuration.
 
 ## What's Next?
 

docs-website/docs/installation.md

@@ -28,16 +28,32 @@ your-app@1.0.0 /path/to/your-app
 
 ### Nginx Configuration
 
-For production deployments using nginx, you may need to configure MIME types for PDF.js ES modules (`.mjs` files):
+For production deployments using nginx, configure MIME types for PDF.js ES modules:
 
 ```nginx
 # Add to your nginx.conf or site configuration
 types {
     application/javascript  js mjs;
+    text/plain             ftl;
 }
 ```
 
-**Why this is needed**: PDF.js v5+ uses `.mjs` files (ES modules). Without proper MIME type configuration, nginx serves these files with incorrect content-type headers, causing the PDF viewer to crash during loading in production environments.
+### IIS Configuration (Windows Server)
+
+For production deployments using IIS, add to your `web.config`:
+
+```xml
+<configuration>
+  <system.webServer>
+    <staticContent>
+      <mimeMap fileExtension=".mjs" mimeType="application/javascript" />
+      <mimeMap fileExtension=".ftl" mimeType="text/plain" />
+    </staticContent>
+  </system.webServer>
+</configuration>
+```
+
+**Why this is needed**: PDF.js v5+ uses `.mjs` files (ES modules) and `.ftl` files (localization). Without proper MIME type configuration, web servers serve these files with incorrect content-type headers, causing the PDF viewer to crash during loading in production environments.
 
 **Symptoms**: Everything works locally but the viewer gets stuck at the loading screen in production.
 

lib/README.md

@@ -219,16 +219,32 @@ Add PDF.js assets to your `angular.json`:
 
 #### Nginx Configuration
 
-For production deployments using nginx, you may need to configure MIME types for PDF.js ES modules (`.mjs` files):
+For production deployments using nginx, configure MIME types for PDF.js ES modules:
 
 ```nginx
 # Add to your nginx.conf or site configuration
 types {
     application/javascript  js mjs;
+    text/plain             ftl;
 }
 ```
 
-**Why this is needed**: PDF.js v5+ uses `.mjs` files (ES modules). Without proper MIME type configuration, nginx serves these files with incorrect content-type headers, causing the PDF viewer to crash during loading in production environments.
+#### IIS Configuration (Windows Server)
+
+For production deployments using IIS, add to your `web.config`:
+
+```xml
+<configuration>
+  <system.webServer>
+    <staticContent>
+      <mimeMap fileExtension=".mjs" mimeType="application/javascript" />
+      <mimeMap fileExtension=".ftl" mimeType="text/plain" />
+    </staticContent>
+  </system.webServer>
+</configuration>
+```
+
+**Why this is needed**: PDF.js v5+ uses `.mjs` files (ES modules) and `.ftl` files (localization). Without proper MIME type configuration, web servers serve these files with incorrect content-type headers, causing the PDF viewer to crash during loading in production environments.
 
 ### Angular Version Support