IgniteUI · dobromirts · Jul 2, 2026 · Jul 6, 2026 · Jul 7, 2026 · Jul 9, 2026
diff --git a/docs/angular/src/content/en/components/grids-and-lists.mdx b/docs/angular/src/content/en/components/grids-and-lists.mdx
@@ -188,8 +188,8 @@ Full support for exporting data grids to XLSX, XLS, TSV or CSV. The Ignite UI fo
 
         <ul>
             <li>Start at the Angular <a class="no-external-icon" href="{environment:infragisticsBaseUrl}/support/ignite-ui-angular-help">Support</a> home page</li>
-            <li>Read the Angular <a class="no-external-icon" href="{environment:infragisticsBaseUrl}/general/getting-started">Documentation</a> and experiment with Angular Samples</li>
-            <li>Read the<a class="no-external-icon" href="{environment:infragisticsBaseUrl}/community/blogs/tags/Ignite UI for Angular"> Angular Blogs</a> to stay up to date</li>
+            <li>Read the Angular <a class="no-external-icon" href="/general/getting-started">Documentation</a> and experiment with Angular Samples</li>
+            <li>Read the<a class="no-external-icon" href="{environment:infragisticsBaseUrl}/blogs/category/angular/"> Angular Blogs</a> to stay up to date</li>
             <li>Submit a <a class="no-external-icon" href="{environment:infragisticsBaseUrl}/products/ignite-ui-angular/grid-table"> Support Case</a></li>
             <li>Learn from the Angular <a class="no-external-icon" href="{environment:infragisticsBaseUrl}/resources/sample-applications">Reference Applications</a></li>
         </ul>

diff --git a/docs/xplat/docConfig.json b/docs/xplat/docConfig.json
@@ -32,6 +32,7 @@
             { "name": "{PackageMaps}",                "value": "igniteui-angular-maps"},
             { "name": "{PackageSpreadsheet}",         "value": "igniteui-angular-spreadsheet"},
             { "name": "{PackageDockManager}",         "value": "igniteui-dockmanager"},
+            { "name": "{DockManagerApiClass}",         "value": "IgxDockManagerComponent"},
             { "name": "{PackageInputs}",              "value": "igniteui-angular-inputs"},
             { "name": "{PackageLayouts}",             "value": "igniteui-angular-layouts"},
             { "name": "{PackageWebsite}",             "value": "https://www.npmjs.com/package/"},
@@ -159,6 +160,7 @@
             { "name": "{PackageMaps}",                 "value": "igniteui-react-maps"},
             { "name": "{PackageSpreadsheet}",          "value": "igniteui-react-spreadsheet"},
             { "name": "{PackageDockManager}",          "value": "igniteui-react-dockmanager"},
+            { "name": "{DockManagerApiClass}",          "value": "IgrDockManager"},
             { "name": "{PackageWebsite}",              "value": "https://www.npmjs.com/package/"},
             { "name": "{PackageVerChangedImports}",    "value": "16.11.7"},
             { "name": "{PackageVerRenamedGrid}",       "value": "16.12.2 (April 2020)"},
@@ -337,6 +339,7 @@
             { "name": "{PackageMaps}",                "value": "igniteui-webcomponents-maps"},
             { "name": "{PackageSpreadsheet}",         "value": "igniteui-webcomponents-spreadsheet"},
             { "name": "{PackageDockManager}",         "value": "igniteui-dockmanager"},
+            { "name": "{DockManagerApiClass}",         "value": "IgcDockManagerComponent"},
             { "name": "{PackageWebsite}",             "value": "https://www.npmjs.com/package/"},
             { "name": "{PackageVerChangedImports}",   "value": "1.0.6"},
             { "name": "{PackageVerRenamedGrid}",      "value": "1.1.2 (April 2020)"},
@@ -584,6 +587,7 @@
             { "name": "{PackageMaps}",              "value": "IgniteUI.Blazor"},
             { "name": "{PackageSpreadsheet}",       "value": "IgniteUI.Blazor"},
             { "name": "{PackageDockManager}",       "value": "IgniteUI.Blazor"},
+            { "name": "{DockManagerApiClass}",       "value": "IgbDockManager"},
             { "name": "{PackageWebsite}",           "value": "https://www.npmjs.com/package/"},
             { "name": "{PackageVerChangedImports}",  "value": "1.0.6"},
             { "name": "{PackageVerChanges-21-1}",    "value": "21.1.52 (April 2021)"},

diff --git a/docs/xplat/src/content/en/components/grids/grids-header.mdx b/docs/xplat/src/content/en/components/grids/grids-header.mdx
@@ -307,7 +307,7 @@ There are multiple options to get access to our award-winning support at Infragi
 
 - Start at the {Platform} <a class="no-external-icon" href="{environment:infragisticsBaseUrl}/support/ignite-ui-angular-help">Support</a> home page
 - Read the {Platform} [Documentation](../general-getting-started.md) and experiment with {Platform} Samples
-- Read the<a class="no-external-icon" href="{environment:infragisticsBaseUrl}/community/blogs/tags/Ignite%2bUI%2bfor%2b{Platform}"> {Platform} Blogs</a> to stay up to date
+- Read the<a class="no-external-icon" href="{environment:infragisticsBaseUrl}/blogs/category/{PlatformLower}/"> {Platform} Blogs</a> to stay up to date
 - Submit a <a class="no-external-icon" href="{environment:infragisticsBaseUrl}/products/ignite-ui-angular/grid-table"> Support Case</a>
 - Learn from the {Platform} <a class="no-external-icon" href="{environment:infragisticsBaseUrl}/resources/sample-applications">Reference Applications</a>
 

diff --git a/docs/xplat/src/content/en/components/grids/grids.mdx b/docs/xplat/src/content/en/components/grids/grids.mdx
@@ -973,7 +973,7 @@ There are multiple options to get access to our award-winning support at Infragi
         <ul>
             <li>Start at the {Platform} <a class="no-external-icon" href="{environment:infragisticsBaseUrl}/support/{ProductSpinal}-help">Support</a> home page</li>
             <li>Read the {Platform} [Documentation](..\general-getting-started.md) and experiment with {Platform} Samples</li>
-            <li>Read the<a class="no-external-icon" href="{environment:infragisticsBaseUrl}/community/blogs/tags/Ignite%2bUI%2bfor%2b{Platform}"> {Platform} Blogs</a> to stay up to date</li>
+            <li>Read the<a class="no-external-icon" href="{environment:infragisticsBaseUrl}/blogs/category/{PlatformLower}/"> {Platform} Blogs</a> to stay up to date</li>
             <li>Submit a <a class="no-external-icon" href="{environment:infragisticsBaseUrl}/my-account/support-activity"> Support Case</a> after signing into your account</li>
             <li>Learn from the {Platform} <a class="no-external-icon" href="{environment:infragisticsBaseUrl}/resources/sample-applications">Reference Applications</a></li>
         </ul>

diff --git a/docs/xplat/src/content/en/components/layouts/dock-manager-electron.mdx b/docs/xplat/src/content/en/components/layouts/dock-manager-electron.mdx
@@ -41,7 +41,7 @@ For the Dock Manager pane contents we have used **iframe** elements which host d
 
 ### Drag and drop
 
-In order to support dragging panes outside the application window we have replaced the built-in drag/drop which creates in-application floating panes with a custom implementation based on the [HTML Drag and Drop API](https://developer.mozilla.org/en-US/docs/Web/API/HTML_Drag_and_Drop_API). We have subscribed to the `PaneHeaderConnected` and `TabHeaderConnected` events which are fired when a header element is connected to the DOM. When a header element is connected we reset the built-in <ApiLink type="PaneHeaderElement" member="dragService" label="DragService" /> and attach `DragStart` and `DragEnd` event listeners.
+In order to support dragging panes outside the application window we have replaced the built-in drag/drop which creates in-application floating panes with a custom implementation based on the [HTML Drag and Drop API](https://developer.mozilla.org/en-US/docs/Web/API/HTML_Drag_and_Drop_API). We have subscribed to the `paneHeaderConnected` and `tabHeaderConnected` events which are fired when a header element is connected to the DOM. When a header element is connected we reset the built-in <ApiLink type="PaneHeaderElement" member="dragService" /> and attach `dragStart` and `dragEnd` event listeners.
 
 <PlatformBlock for="WebComponents">
 
@@ -65,7 +65,7 @@ dockManager.addEventListener('paneHeaderConnected', paneHeaderConnected);
 </PlatformBlock>
 
 
-In the `PaneHeaderDragStart` function we set the <ApiLink type="DockManager" member="draggedPane" label="DraggedPane" /> property of the Dock Manager component which will notify it that a drag operation has been started.
+In the `paneHeaderDragStart` function we set the <ApiLink type="DockManager" member="draggedPane" /> property of the Dock Manager component which will notify it that a drag operation has been started.
 
 <PlatformBlock for="WebComponents">
 
@@ -79,7 +79,7 @@ const paneHeaderDragStart = async (pane: IgcContentPane, event: DragEvent) => {
 
 </PlatformBlock>
 
-We have subscribed to the `DragOver` and `drop` events of the `document` element. In the `DragOver` listener we notify the Dock Manager that the mouse is dragged over it by setting its <ApiLink type="DockManager" member="dropPosition" label="DropPosition" /> property. This forces the Dock Manager to display its docking indicators.
+We have subscribed to the `dragover` and `drop` events of the `document` element. In the `dragover` listener we notify the Dock Manager that the mouse is dragged over it by setting its <ApiLink type="DockManager" member="dropPosition" /> property. This forces the Dock Manager to display its docking indicators.
 
 ```ts
 const handleDocumentDragOver = (event: DragEvent) => {
@@ -110,7 +110,7 @@ const paneHeaderDragEnd = async (event: DragEvent) => {
 }
 ```
 
-When the pane header is dropped inside a document we call the `DropPane` method which notifies the Dock Manager that the dragged pane was dropped. If the pane was dropped on a docking indicator the method returns **true**. If the pane was dropped in the same window it was dragged from, the pane will be docked to its new position automatically. However, if it was dropped in another window we call the `droppedInAnotherWindow` function which first removes the pane from the source Dock Manager and then adds it to the new one.
+When the pane header is dropped inside a document we call the `dropPane` method which notifies the Dock Manager that the dragged pane was dropped. If the pane was dropped on a docking indicator the method returns **true**. If the pane was dropped in the same window it was dragged from, the pane will be docked to its new position automatically. However, if it was dropped in another window we call the `droppedInAnotherWindow` function which first removes the pane from the source Dock Manager and then adds it to the new one.
 
 <PlatformBlock for="WebComponents">
 
@@ -133,7 +133,7 @@ const handleDocumentDrop = async (event: DragEvent) => {
 
 </PlatformBlock>
 
-When a pane is dropped out of its current window, we need to remove the <ApiLink type="DockManager" member="draggedPane" label="DraggedPane" /> from its Dock Manager component and update the layout.
+When a pane is dropped out of its current window, we need to remove the <ApiLink type="DockManager" member="draggedPane" /> from its Dock Manager component and update the layout.
 
 <PlatformBlock for="WebComponents">