Merge branch 'development' into 990970-AI-FAIL

Author: saravanangn

blazor-toc.html

@@ -386,6 +386,9 @@
 					<li>
 						<a href="/blazor/common/deployment/deployment-azure">Deploy a Blazor Web App to Azure App Service</a>
 					</li>
+					<li>
+						<a href="/blazor/common/deployment/deployment-linux-nginx">Deploy a Blazor Web App to Linux with NGINX</a>
+					</li>
 				</ul>
 			</li>
 			<li>
@@ -3143,7 +3146,8 @@
 			<li> <a href="/blazor/gantt-chart/excel-export">Excel Export</a></li>
 			<li> <a href="/blazor/gantt-chart/pdf-export">PDF Export</a>
 				<ul>
-					<li> <a href="/blazor/gantt-chart/template-pdf-export">PDF Exporting with Templates</a> </li>
+					<li> <a href="/blazor/gantt-chart/header-and-footer">Header and Footer</a> </li>
+					<li> <a href="/blazor/gantt-chart/customize-pdf-export">Customize PDF Export</a> </li>
 				</ul>
 			</li>
 			<li> <a href="/blazor/gantt-chart/timezone">Timezone</a></li>

blazor/common/deployment/deployment-linux-nginx.md

@@ -0,0 +1,110 @@
+---
+layout: post
+title: Deploy a Blazor Web App to Linux with NGINX | Syncfusion
+description: Learn here all about deploying the Blazor Web App with Syncfusion Blazor Components to Linux server using NGINX.
+platform: Blazor
+component: Common
+documentation: ug
+---
+
+# Deploy Blazor Web App to Linux with NGINX
+
+This section provides information about deploying a Blazor Web applications with the Syncfusion Blazor components to Linux server using NGINX as a reverse proxy.
+
+Refer to [Host ASP.NET Core on Linux with NGINX](https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/linux-nginx?view=aspnetcore-9.0&tabs=linux-ubuntu) topic for more information.
+
+## Prerequisites
+
+* Linux Server – Ubuntu 20.04, Red Hat Enterprise (RHEL) 8.0 and SUSE Linux Enterprise Server 12.
+* [.NET runtime](https://blazor.syncfusion.com/documentation/system-requirements#net-sdk) installed on the server.
+* An existing Blazor Web App with Syncfusion components or create a new one.
+
+## Install and Start NGINX
+
+Install NGINX on your Linux system and enable it to start automatically:
+
+```bash
+sudo dnf install nginx
+sudo systemctl start nginx
+sudo systemctl enable nginx
+sudo systemctl status nginx
+```
+
+**Verification**: Open `http://your-server-ip` in a browser — you should see the NGINX welcome page.
+
+## Create and publish Your Blazor Web App with Syncfusion Components
+
+* You can create a Blazor Web App using the .NET CLI commands with Syncfusion components by referring [here](https://blazor.syncfusion.com/documentation/getting-started/blazor-web-app?tabcontent=.net-cli).
+
+* Publish your Blazor Web application in Release configuration using the following command and run it:
+
+```bash
+dotnet publish -c Release -o publish
+cd publish
+dotnet SfBlazorApp.dll --urls "http://0.0.0.0:5000"
+```
+
+![Publish Blazor Web App](../images/publish-blazor-app.png)
+
+## Configure NGINX to Proxy Requests
+
+Create a new NGINX configuration file for your Blazor application:
+
+```bash
+sudo nano /etc/nginx/conf.d/blazorapp.conf
+```
+
+Add the following configuration to enable NGINX to act as a reverse proxy:
+
+```nginx
+server {
+    listen 80;
+    server_name _;
+    location / {
+        proxy_pass http://localhost:5000;
+        proxy_http_version 1.1;
+        proxy_set_header Host $host;
+        proxy_set_header X-Real-IP $remote_addr;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header X-Forwarded-Proto $scheme;
+        proxy_set_header Upgrade $http_upgrade;
+        proxy_set_header Connection "upgrade";
+    }
+}
+```
+
+Save and exit the file (Ctrl+O, Enter, then Ctrl+X).
+
+## Validate and Restart NGINX
+
+Test the NGINX configuration and restart the service:
+
+```bash
+sudo nginx -t
+sudo systemctl restart nginx
+```
+
+## Configure SELinux (For Red Hat-based Systems)
+
+On Red Hat-based systems, SELinux may block NGINX from accessing your Blazor app. Allow NGINX to connect to network services:
+
+```bash
+sudo setsebool -P httpd_can_network_connect 1
+```
+
+## Access the Application
+
+From your Windows machine or any other device, open a browser and navigate to:
+
+```
+http://<your-vm-ip>/
+```
+
+You should now see your Blazor Web app running successfully with Syncfusion components!
+
+![Output-Linux](../images/output-linux.png)
+
+## See also
+
+* [Host ASP.NET Core on Linux with NGINX](https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/linux-nginx?view=aspnetcore-9.0)
+* [Configure NGINX for ASP.NET Core](https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/linux-nginx?view=aspnetcore-9.0#configure-nginx)

blazor/common/images/output-linux.png

@@ -1,19 +1,45 @@
 ---
 layout: post
 title: Critical Path in Blazor Gantt Chart Component | Syncfusion
-description: Checkout and learn here all about critical path in Syncfusion Blazor Gantt Chart component and much more details.
+description: Learn here all about Critical path in Syncfusion Blazor Gantt Chart component and much more details.
 platform: Blazor
-component: Gantt Chart
+component: Critical path
 documentation: ug
 ---
 
 # Critical Path in Blazor Gantt Chart component
 
-The critical path in a project is indicated by a single task or a series of tasks. If a task in critical path is delayed, the entire project will be delayed. A task is considered to be critical if any delay to this task would affect the project end date.
+The critical path represents the longest sequence of dependent tasks that determines the minimum project duration. Tasks on the critical path have zero or negative [SlackValue](https://help.syncfusion.com/cr/blazor/Syncfusion.Blazor.Gantt.GanttCriticalPathSettings.html#Syncfusion_Blazor_Gantt_GanttCriticalPathSettings_SlackValue) (float), meaning any delay in these tasks directly impacts the overall project completion date. The Blazor Gantt Chart component automatically calculates and highlights critical tasks in red with emphasized dependency connector lines when the [EnableCriticalPath](https://help.syncfusion.com/cr/blazor/Syncfusion.Blazor.Gantt.SfGantt-1.html#Syncfusion_Blazor_Gantt_SfGantt_1_EnableCriticalPath) property is enabled. Critical path analysis helps identify which tasks require immediate attention and cannot be delayed without affecting project deadlines.
 
-The critical path can be enabled in the Gantt Chart by using the built-in toolbar button or by setting the [EnableCriticalPath](https://help.syncfusion.com/cr/blazor/Syncfusion.Blazor.Gantt.SfGantt-1.html#Syncfusion_Blazor_Gantt_SfGantt_1_EnableCriticalPath) property to true in the [SfGantt](https://help.syncfusion.com/cr/blazor/Syncfusion.Blazor.Gantt.SfGantt-1.html) component.
+## Understanding critical path calculation
 
-The following code example shows how to display the critical path in the Gantt control:
+The component uses Critical Path Method (CPM) principles to identify critical tasks through a comprehensive calculation process that analyzes task dependencies, timing relationships, and slack values to determine which tasks have no scheduling flexibility. A task becomes critical when it has zero or negative slack, meaning any delay (even by a minute) shifts the entire project end date. This occurs because critical tasks are linked through dependencies, creating a chain reaction where delays propagate across the dependency network, ultimately affecting the project completion date.
+
+**Project end date determination**: The calculation begins by determining the overall project end date. If the [ProjectEndDate](https://help.syncfusion.com/cr/blazor/Syncfusion.Blazor.Gantt.SfGantt-1.html#Syncfusion_Blazor_Gantt_SfGantt_1_ProjectEndDate) property is provided, it uses that value as the project completion reference. If `ProjectEndDate` is not specified, the component automatically calculates the project end date by examining all task end dates in the data source to find the latest completion point. This reference point determines how much delay each task can tolerate without affecting project completion.
+
+**Slack value calculation**: For each task, the component calculates slack by measuring the time difference between the task's end date and the project end date. Slack represents how much time a task can be delayed without affecting the project completion:
+- **Zero slack**: The task must finish exactly on time. Any delay will push back the project end date, making it critical
+- **Negative slack**: The task is already behind schedule or creates scheduling conflicts. This occurs when a task's end date is beyond the project end date, or when dependency relationships create impossible timing constraints.
+
+**Parent-Child task relationships**: In projects with hierarchical tasks, the critical path calculation focuses on dependencies rather than the parent-child structure used for task organization. For example, if Task 1.1 (a child task) depends on Task 2 (a parent task), only the tasks directly linked by the dependency are evaluated for criticality based on their timing. A parent task like Task 2 being critical does not automatically make its child tasks (e.g., Task 2.1, Task 2.2) critical, nor does a critical child task imply a critical parent. The component evaluates each task’s slack independently, ensuring that only tasks with zero or negative slack, driven by their dependency constraints, are marked as critical. This distinction allows precise identification of critical tasks without conflating organizational hierarchy with scheduling dependencies.
+
+**Dependency-based analysis**: The component analyzes different dependency relationship types to determine slack impacts:
+- **Finish-to-Start**: When a predecessor task ends after its successor should start, negative slack results from the timing conflict
+- **Start-to-Start**: When a predecessor starts after its successor should start, the component calculates negative slack based on scheduling impossibility  
+- **Finish-to-Finish** and **Start-to-Finish**: These relationships can also produce negative slack when timing conflicts exist between connected tasks
+- **Offset and scheduling mode handling**: When dependencies include time offsets (e.g., "+2 days" or "-1 hour"), the component adjusts slack calculations by factoring in the offset duration. The calculation differs for automatically scheduled versus manually scheduled tasks: automatic tasks use forward and backward pass algorithms to compute slack, while manual tasks compare their end dates directly against the project completion date.
+
+**Progress consideration**: The component considers task completion progress. Only tasks with less than 100% progress can be marked as critical, since completed tasks cannot cause future delays. Tasks that end on or beyond the project end date automatically become critical regardless of their dependency relationships, as they directly determine the project completion timing.
+
+## Critical path setup and configuration
+
+The Critical Path feature in the Blazor Gantt component highlights tasks that directly impact the overall project completion date. To enable this functionality, ensure that the data source must contain tasks with valid start dates, end dates, and task dependencies properly mapped through the [Dependency](https://help.syncfusion.com/cr/blazor/Syncfusion.Blazor.Gantt.GanttTaskFields.html#Syncfusion_Blazor_Gantt_GanttTaskFields_Dependency) field in [TaskFields](https://help.syncfusion.com/cr/blazor/Syncfusion.Blazor.Gantt.GanttTaskFields.html).
+
+Enable critical path display by setting [EnableCriticalPath](https://help.syncfusion.com/cr/blazor/Syncfusion.Blazor.Gantt.SfGantt-1.html#Syncfusion_Blazor_Gantt_SfGantt_1_EnableCriticalPath) to **true**, or add the `CriticalPath` option to the [Toolbar](https://help.syncfusion.com/cr/blazor/Syncfusion.Blazor.Gantt.SfGantt-1.html#Syncfusion_Blazor_Gantt_SfGantt_1_Toolbar) array to allow interactive toggling. The [GetCriticalTasks](https://help.syncfusion.com/cr/blazor/Syncfusion.Blazor.Gantt.SfGantt-1.html#Syncfusion_Blazor_Gantt_SfGantt_1_Toolbar) method retrieves all tasks identified as critical at runtime.
+
+The critical path recalculates automatically when task properties change, including start and end dates, duration modifications, dependency updates, or progress adjustments. This ensures the visualization remains accurate throughout project management workflows.
+
+The following example demonstrates enabling critical path analysis:
 
 {% tabs %}
 {% highlight razor tabtitle="Index.razor" %}