diff --git a/docs/angular/src/content/en/components/angular-reactive-form-validation.mdx b/docs/angular/src/content/en/components/angular-reactive-form-validation.mdx
index 749ac30399..6dd2d66a84 100644
--- a/docs/angular/src/content/en/components/angular-reactive-form-validation.mdx
+++ b/docs/angular/src/content/en/components/angular-reactive-form-validation.mdx
@@ -182,7 +182,7 @@ export class MyComponent implements OnInit {
Related topics:
-- [Combo](/combo)
+- [Combo](/inputs/combo/overview)
- [Select](/select)
- [Input Group](/input-group)
- [Date Picker](/date-picker)
diff --git a/docs/angular/src/content/en/components/combo-features.mdx b/docs/angular/src/content/en/components/combo-features.mdx
index a1d9570546..098878c5da 100644
--- a/docs/angular/src/content/en/components/combo-features.mdx
+++ b/docs/angular/src/content/en/components/combo-features.mdx
@@ -227,12 +227,12 @@ Additional components and/or directives with relative APIs that were used:
-- [ComboBox Component](/combo)
+- [ComboBox Component](/inputs/combo/overview)
- [ComboBox Remote Binding](/combo-remote)
-- [ComboBox Templates](/combo-templates)
+- [ComboBox Templates](/inputs/combo/templates)
- [Template Driven Forms Integration](/input-group)
- [Reactive Forms Integration](/angular-reactive-form-validation)
-- [Single Select ComboBox](/simple-combo)
+- [Single Select ComboBox](/inputs/combo/single-selection)
Our community is active and always welcoming to new ideas.
diff --git a/docs/angular/src/content/en/components/combo-remote.mdx b/docs/angular/src/content/en/components/combo-remote.mdx
index 401d31c32e..dd38953068 100644
--- a/docs/angular/src/content/en/components/combo-remote.mdx
+++ b/docs/angular/src/content/en/components/combo-remote.mdx
@@ -227,7 +227,7 @@ A service needs to be included as a provider.
### Handling Selection
-When using a combobox bound to remote data loaded in chunks and dealing with a more complex data type (e.g. objects), it is necessary to define a `valueKey`. As stated in the [combobox topic](/combo#data-value-and-display-properties), when no `valueKey` is specified, the combobox will try to handle selection by `equality (===)`. Since the objects that will be marked as selected will not be the same as the object that are continuously loaded, the selection will fail.
+When using a combobox bound to remote data loaded in chunks and dealing with a more complex data type (e.g. objects), it is necessary to define a `valueKey`. As stated in the [combobox topic](/inputs/combo/overview#data-binding), when no `valueKey` is specified, the combobox will try to handle selection by `equality (===)`. Since the objects that will be marked as selected will not be the same as the object that are continuously loaded, the selection will fail.
When binding a combobox to remote data, make sure to specify a `valueKey`, representing a property that is unique to each item.
@@ -243,12 +243,12 @@ When the combobox is bound to remote data, setting value/selected items through
-- [ComboBox Component](/combo)
+- [ComboBox Component](/inputs/combo/overview)
- [ComboBox Features](/combo-features)
-- [ComboBox Templates](/combo-templates)
+- [ComboBox Templates](/inputs/combo/templates)
- [Template Driven Forms Integration](/input-group)
- [Reactive Forms Integration](/angular-reactive-form-validation)
-- [Single Select ComboBox](/simple-combo)
+- [Single Select ComboBox](/inputs/combo/single-selection)
Our community is active and always welcoming to new ideas.
diff --git a/docs/angular/src/content/en/components/combo-templates.mdx b/docs/angular/src/content/en/components/combo-templates.mdx
deleted file mode 100644
index 6bbf09f852..0000000000
--- a/docs/angular/src/content/en/components/combo-templates.mdx
+++ /dev/null
@@ -1,190 +0,0 @@
----
-title: ComboBox Templates - MIT license
-description: Custom templates for different areas of the igx-combo component can be defined, including items, header, footer, empty list and adding button.
-keywords: Ignite UI for Angular, UI controls, Angular widgets, web widgets, UI widgets, Angular, Native Angular Components Suite, Native Angular Controls, Native Angular Components Library, Angular Combo components, Angular Templates, Angular Combo Templates
-license: MIT
-llms:
- description: "The Ignite UI for Angular ComboBox Component allows defining custom templates for different areas such as header, footer, items, empty list and adding button."
----
-
-import DocsAside from 'igniteui-astro-components/components/mdx/DocsAside.astro';
-import Sample from 'igniteui-astro-components/components/mdx/Sample.astro';
-import ApiLink from 'igniteui-astro-components/components/mdx/ApiLink.astro';
-
-# ComboBox Templates
-
-
-
-The Ignite UI for Angular ComboBox Component allows defining custom templates for different areas such as header, footer, items, empty list and adding button.
-
-
-## Angular ComboBox Templates Example
-
-
-
-## Usage
-
-To get started with the ComboBox component, first you need to import the `IgxComboModule` in your **app.module.ts** file:
-
-```typescript
-import { IgxComboModule } from 'igniteui-angular/combo';
-// import { IgxComboModule } from '@infragistics/igniteui-angular'; for licensed package
-
-@NgModule({
- imports: [
- ...
- IgxComboModule,
- ...
- ]
-})
-export class AppModule {}
-```
-
-## Template Types
-
-When defining combobox templates, you need to reference them using the following predefined reference names:
-
-### Item template
-
-Use selector `[igxComboItem]`:
-
-```html
-
-
-
-
-
-```
-
-### Footer template
-
-Use selector `[igxComboFooter]`:
-
-```html
-
-
-
-
-
-```
-
-### Empty template
-
-Use selector `[igxComboEmpty]`:
-
-```html
-
-
- No available states
-
-
-```
-
-### Add template
-
-Use selector `[igxComboAddItem]`:
-
-```html
-
-
-
-
-
-```
-
-### Toggle Icon Template
-
-Use selector `[igxComboToggleIcon]`:
-
-```html
-
-
- {{ collapsed ? 'expand_more' : 'expand_less'}}
-
-
-```
-
-
-This component uses Material Icons. Add the following link to your `index.html`: ``
-
-
-### Clear Icon Template
-
-Use selector `[igxComboClearIcon]`:
-
-```html
-
-
- cancel
-
-
-```
-
-## Templating ComboBox Input
-
-When used with templates, the `igxComboClearIcon` and the `igxComboToggleIcon` selectors, change how the respective buttons appear in the combobox input. Passing content inside of the `igx-combo` also allows templating of the combobox input similar to the way an `igx-input-group` can be templated (using `igx-prefix`, `igx-suffix` and `igxLabel`). The code snippet below illustrates how to add an appropriate label and prefix to the combobox input:
-
-```html
-
-
- pin_drop
-
-```
-
-## API References
-
--
--
-## Additional Resources
-
-
-
-- [ComboBox Component](/combo)
-- [ComboBox Features](/combo-features)
-- [ComboBox Remote Binding](/combo-remote)
-- [Template Driven Forms Integration](/input-group)
-- [Reactive Forms Integration](/angular-reactive-form-validation)
-- [Single Select ComboBox](/simple-combo)
-
-Our community is active and always welcoming to new ideas.
-
-- [Ignite UI for Angular **Forums**](https://www.infragistics.com/community/forums/f/ignite-ui-for-angular)
-- [Ignite UI for Angular **GitHub**](https://github.com/IgniteUI/igniteui-angular)
diff --git a/docs/angular/src/content/en/components/combo.mdx b/docs/angular/src/content/en/components/combo.mdx
deleted file mode 100644
index 7f127f9b65..0000000000
--- a/docs/angular/src/content/en/components/combo.mdx
+++ /dev/null
@@ -1,464 +0,0 @@
----
-title: Angular Combobox Component | Data binding combobox | Infragistics | MIT license
-description: The Ignite UI for Angular ComboBox provides a powerful input, combining features of the basic HTML input, select, filtering and custom drop-down lists. Try it for FREE
-keywords: angular combobox, angular combo component, angular combobox component, Angular UI Components, ignite ui for angular, infragistics
-license: MIT
-llms:
- description: "The Angular ComboBox component represents a drop-down list that provides editable functionalities, allowing users to choose multiple options from a predefined list."
----
-
-import DocsAside from 'igniteui-astro-components/components/mdx/DocsAside.astro';
-import Sample from 'igniteui-astro-components/components/mdx/Sample.astro';
-import ApiLink from 'igniteui-astro-components/components/mdx/ApiLink.astro';
-
-# Angular ComboBox Component Overview
-
-The Angular ComboBox component represents a drop-down list that provides editable functionalities, allowing users to choose multiple options from a predefined list. The Ignite UI for Angular ComboBox Component also provides filtering capabilities, grouping and adding custom values to a dropdown list. It can be used as an alternative to the HTML select tag and has several out-of-the-box features such as data binding (local and remote), filtering, grouping, custom templates for items, header, and footer, custom values, and more.
-
-## Angular ComboBox Example
-
-In this Angular ComboBox example, you can see how users can filter items and perform selection with the provided data. In addition, the ComboBox exposes keyboard navigation and custom styling capabilities.
-
-
-
-
-
-## Angular ComboBox Features
-
-The combobox control exposes the following features:
-
-- Data Binding - local data and [remote data](/combo-remote)
-- [Value Binding](/combo-features#data-binding)
-- [Filtering](/combo-features#filtering)
-- [Grouping](/combo-features#grouping)
-- [Custom Values](/combo-features#custom-values)
-- [Templates](/combo-templates)
-- Integration with [Template Driven Forms](/input-group) and [Reactive Forms](/angular-reactive-form-validation)
-
-## Getting Started with Ignite UI for Angular ComboBox
-
-To get started with the Ignite UI for Angular ComboBox component, first you need to install Ignite UI for Angular. In an existing Angular application, type the following command:
-
-```cmd
-ng add igniteui-angular
-```
-
-For a complete introduction to the Ignite UI for Angular, read the [_getting started_](/general/getting-started) topic.
-
-The next step is to import the `IgxComboModule` in your **app.module.ts** file.
-
-```typescript
-import { IgxComboModule } from 'igniteui-angular/combo';
-// import { IgxComboModule } from '@infragistics/igniteui-angular'; for licensed package
-
-@NgModule({
- imports: [
- ...
- IgxComboModule,
- ...
- ]
-})
-export class AppModule {}
-```
-
-Alternatively, as of `16.0.0` you can import the `IgxComboComponent` as a standalone dependency, or use the [`IGX_COMBO_DIRECTIVES`](https://github.com/IgniteUI/igniteui-angular/blob/master/projects/igniteui-angular/combo/src/combo/public_api.ts) token to import the component and all of its supporting components and directives.
-
-```typescript
-// home.component.ts
-
-import { IGX_COMBO_DIRECTIVES } from 'igniteui-angular/combo';
-// import { IGX_COMBO_DIRECTIVES } from '@infragistics/igniteui-angular'; for licensed package
-
-@Component({
- selector: 'app-home',
- template: '',
- styleUrls: ['home.component.scss'],
- standalone: true,
- imports: [IGX_COMBO_DIRECTIVES]
- /* or imports: [IgxComboComponent] */
-})
-export class HomeComponent {}
-```
-
-Now that you have the Ignite UI for Angular Combo module or directives imported, you can start using the `igx-combo` component.
-
-## Using the Angular ComboBox Component
-
-After the initial setup, you can bind the to data.
-
-```typescript
-@Component({
- selector: 'app-combo-demo',
- template: '',
- styleUrls: ['combo-demo.component.scss'],
- standalone: true,
- imports: [IGX_COMBO_DIRECTIVES]
-})
-export class ComboDemo implements OnInit {
- public cities: { name: string, id: string }[] = [];
-
- public ngOnInit() {
- this.cities = [{ name: 'London', id: 'UK01' }, { name: 'Sofia', id: 'BG01'}, ...];
- }
-}
-```
-
-Our combobox is now bound to the array of cities, but we still haven't told the component which property to use for the items' text and which to use for the value. Let's do that now.
-
-### Data value and display properties
-
-Since the combobox is bound to an array of complex data (i.e. objects), we need to specify a property that the control will use to handle the selected items. The control exposes two `@Input` properties - and :
-
-- `valueKey` - _Optional, recommended for object arrays_ - Specifies which property of the data entries will be stored for the combobox's selection. If `valueKey` is omitted, the combobox value will use references to the data entries (i.e. the selection will be an array of entries from `igxCombo.data`).
-- `displayKey` - _Required for object arrays_ - Specifies which property will be used for the items' text. If no value is specified for `displayKey`, the combobox will use the specified `valueKey` (if any).
-
-In our case, we want the combobox to display the `name` of each city and the combobox value to store the `id` of each city. Therefore, we are providing these properties to the combobox's `displayKey` and `valueKey`, respectively:
-
-```html
-
-```
-
-
-When the data source is an array of primitives (e.g. `string[]`, `number[]`), **do not** specify a `valueKey` and `displayKey`. Primitive values will be used for both value and text.
-
-
-### Two-Way Binding
-
-The combobox component fully supports two-way data-binding with `[(ngModel)]` as well as usage in [template driven](https://angular.io/guide/forms) and [reactive](https://angular.io/guide/reactive-forms) forms. The combobox selection can be accessed either through two-way binding or through the [selection API](#selection-api). We can pass an array of items of the same type as the ones in the combobox's selection (based on `valueKey`) and any time one changes, the other is updated accordingly.
-
-In the following example, the cities Sofia and London will initially be selected. Any further changes in the combobox's selection will reflect on the `selectedCities` array.
-
-```html
-
-```
-
-```typescript
-export class MyCombo {
- public cities: { name: string, id: string }[] = [
- { name: 'Sofia', id: 'BG01' }, { name: 'London', id: 'UK01' }, ...];
- public selectedCities: string[] = ['BG01', 'UK01'];
-}
-```
-
-
-
-Two-way binding can also be achieved without a specified `valueKey`. For example, if `valueKey` is omitted, the bound model will look like this:
-
-```typescript
-export class MyCombo {
- public cities: { name: string, id: string } [] = [
- { name: 'Sofia', id: 'BG01' }, { name: 'London', id: 'UK01' }, ...];
- public selectedCities: { name: string, id: string } [] = [this.cities[0], this.cities[1]];
-}
-```
-
-
-
-### Selection API
-
-The combobox component exposes API that allows getting and manipulating the current selection state of the control.
-
-One way to get the combobox's selection is via the property. It returns an array of values which correspond to the selected items, depending on the specified [valueKey](#data-value-and-display-properties) (if any).
-
-In our example, `selection` will return an array of the selected cities' `id`s:
-
-```typescript
-export class MyCombo {
- ...
- public selection: string[] = this.combo.selection;
-}
-```
-
-Using the selection API, you can also change the combobox's selected items without user interaction with the control - via a button click, as a response to an Observable changing, etc. For example, we can implement a button that selects a set of cities, using the method:
-
-```html
-
-
-```
-
-When clicking the button, the cities London and Sofia will be added to the combobox's selection:
-
-```typescript
-export class MyExampleCombo {
- @ViewChild(IgxComboComponent, { read: IgxComboComponent, static: true })
- public combo: IgxComboComponent;
- ...
- selectFavorites(): void {
- this.combo.select(['UK01', 'BG01']);
- }
-}
-```
-
-The combobox also fires an event every time its selection changes - . The emitted event arguments, , contain information about the selection prior to the change, the current selection and the items that were added or removed. The event can also be cancelled, preventing the selection update with the new array of items.
-
-Binding to the event can be done through the proper `@Output` property on the `igx-combo` tag:
-
-```html
-
-
-```
-
-In the following example, when a city is added or removed from the selection, a handler that updates the statistic visualization is fired:
-
-```typescript
-export class MyExampleCombo {
- ...
- handleCityChange(event: IComboSelectionChangingEventArgs): void {
- for (const item of event.added) {
- this.addToVisualization(item);
- }
- for (const item of event.removed) {
- this.removeFromVisualization(item);
- }
- }
-}
-```
-
-Additionally, the combobox fires a event after the selection is committed and the component state has been updated. The emitted event arguments, , contain information about the previous selection, the current selection and the items that were added or removed. Unlike `selectionChanging`, this event is not cancellable and is guaranteed to reflect the final committed selection state. When the combobox is used with `ngModel` or Angular forms, `selectionChanged` is emitted after the value change callback is invoked.
-
-Binding to the event can be done through the proper `@Output` property on the `igx-combo` tag:
-
-```html
-
-
-```
-
-In the following example, when the selection changes, the handler updates a short summary and tracks how many items were added and removed:
-
-```typescript
-export class MyExampleCombo {
- ...
- handleCitySelectionChanged(event: IComboSelectionChangedEventArgs): void {
- this.updateSelectionSummary(event.displayText, event.newSelection.length);
-
- for (const item of event.added) {
- this.highlightAddedCity(item);
- }
-
- for (const item of event.removed) {
- this.dimRemovedCity(item);
- }
-
- this.logSelectionTransition(event.oldSelection, event.newSelection);
- }
-}
-```
-
-## Single Selection
-
-By default, the combo control provides multiple selection. The snippet below demonstrates how to achieve single selection in the component by attaching a handler to the `selectionChanging` event:
-
-```html
-
-```
-
-```typescript
-public singleSelection(event: IComboSelectionChangingEventArgs) {
- if (event.added.length) {
- event.newValue = event.added;
- }
-}
-```
-
-> Note: It is recommended to use the [igxSimpleCombo](/simple-combo) instead of modifying the igxCombo like it is shown above.
-
-
-
-## Keyboard Navigation
-
-When combobox is closed and focused:
-
-- `ArrowDown` or `Alt` + `ArrowDown` will open the combobox's drop down and will move focus to the search input.
-
-- `Esc` will clear the selected value(s) while keeping focus on the combobox.
-
-- `Tab` will move the focus to the next focusable element outside the combobox.
-
-When combobox is opened:
-
-- `Esc` will close the list and keep the focus on the combobox.
-
-- `Tab` will close the list and move focus to the next focusable element.
-
-When combobox is opened and search input is focused:
-
-- `ArrowUp` or `Alt` + `ArrowUp` will close the combobox's drop down and will move focus to the closed combobox.
-
-- `ArrowDown` will move focus from the search input to the first list item. If the list is empty and custom values are enabled will move it to the Add new item button.
-
-
-Any other key stroke will be handled by the input.
-
-
-When combobox is opened and list item is focused:
-
-- `ArrowDown` will move to the next list item. If the active item is the last one in the list and custom values are enabled, the focus will be moved to the Add item button.
-
-- `ArrowUp` will move to the previous list item. If the active item is the first one in the list, the focus will be moved back to the search input.
-
-- `End` will move to the last list item.
-
-- `Home` will move to the first list item.
-
-- `Space` will select/deselect the active list item.
-
-- `Enter` will confirm the already selected items and will close the list.
-
-When combobox is opened, allow custom values are enabled and add item button is focused:
-
-- `Enter` will add a new item with `valueKey` and `displayKey` equal to the text in the search input and will select the new item.
-
-- `ArrowUp` focus will be moved back to the last list item or if the list is empty, will be moved to the search input.
-
-## Styling
-
-### Combo Theme Property Map
-
-When you modify a primary property, all related dependent properties are updated automatically:
-
-| Primary Property | Dependent Property | Description |
-| --- | --- | --- |
-| **$empty-list-background** | $empty-list-placeholder-color | The combo placeholder text color. |
-| **$toggle-button-background** | $toggle-button-foreground | The combo toggle button foreground color. |
-| | $toggle-button-background-focus | The combo toggle button background color when focused. |
-| | $toggle-button-background-focus--border | The combo toggle button background color when focused (border variant). |
-| | $toggle-button-foreground-filled | The combo toggle button foreground color when filled. |
-| | $toggle-button-background-disabled | The combo toggle button background color when disabled. |
-| | $toggle-button-foreground-disabled | The combo toggle button foreground color when disabled. |
-| **$toggle-button-background-focus** | $toggle-button-foreground-focus | The combo toggle button foreground color when focused. |
-| **$clear-button-background-focus** | $clear-button-foreground-focus | The combo clear button foreground color when focused. |
-
-Using the [`Ignite UI for Angular Theming`](/themes), we can greatly alter the combobox appearance. First, in order for us to use the functions exposed by the theme engine, we need to import the `index` file in our style file:
-
-```scss
-@use "igniteui-angular/theming" as *;
-
-// IMPORTANT: Prior to Ignite UI for Angular version 13 use:
-// @import '~igniteui-angular/lib/core/styles/themes/index';
-```
-
-Following the simplest approach, we create a new theme that extends the . By setting the `$toggle-button-background`, the theme automatically determines suitable state colors and contrast foregrounds for the button. You can also specify additional parameters, such as `$search-separator-border-color`:
-
-```scss
-$custom-combo-theme: combo-theme(
- $search-separator-border-color: #1d3743,
- $toggle-button-background: #57a5cd,
-);
-```
-
-The uses the internally as an item container. It also includes the and the components. Creating new themes, that extend these components' themes, and scoping them under the respective classes will let you change the combobox styles:
-
-```scss
-$custom-drop-down-theme: drop-down-theme(
- $background-color: #57a5cd,
-);
-
-$custom-checkbox-theme: checkbox-theme(
- $border-radius: 10px,
- $fill-color: #1d3743,
- $empty-color: #1d3743,
-);
-```
-
-The last step is to include the component's theme.
-
-```scss
-:host {
- @include tokens($custom-combo-theme);
- @include tokens($custom-drop-down-theme);
- @include tokens($custom-checkbox-theme);
-}
-```
-
-
-The uses the [`IgxOverlay`](/overlay) service to display its list. Depending on View Encapsulation and where the generated selectors must match, the local theme include may still require `::ng-deep`. A list attached to the default detached outlet also cannot inherit from the combo's host; configure the beneath the themed container or emit the theme from a selector that can match the outlet. See the [`IgxOverlay Styling Guide`](/overlay-styling).
-[!Note]
-The default `type` of the `IgxCombo` is `box` unlike the [`IgxSelect`](/select) where it is `line`.
-
-
-### Demo
-
-
-
-
-
-### Styling with Tailwind
-
-You can style the `combo` using our custom Tailwind utility classes. Make sure to [set up Tailwind](/themes/misc/tailwind-classes) first.
-
-Along with the tailwind import in your global stylesheet, you can apply the desired theme utilities as follows:
-
-```scss
-@import "tailwindcss";
-...
-@use 'igniteui-theming/tailwind/utilities/material.css';
-```
-
-The utility file includes both `light` and `dark` theme variants.
-
-- Use `light-*` classes for the light theme.
-- Use `dark-*` classes for the dark theme.
-- Append the component name after the prefix, e.g., `light-combo`, `dark-combo`.
-
-Once applied, these classes enable dynamic theme calculations. From there, you can override the generated CSS variables using `arbitrary properties`. After the colon, provide any valid CSS color format (HEX, CSS variable, RGB, etc.).
-
-You can find the full list of properties in the . The syntax is as follows:
-
-```html
-
-```
-
-
-The exclamation mark(`!`) is required to ensure the utility class takes precedence. Tailwind applies styles in layers, and without marking these styles as important, they will get overridden by the component’s default theme.
-
-
-At the end your combo should look like this:
-
-
-
-## Known Issues
-
-- The combobox input that displays the selected items is not editable. However, due to browser specifics in FireFox, the cursor is visible.
-- When the combobox is bound to an array of primitive data which contains `undefined` (i.e. `[ undefined, ...]`), `undefined` is not displayed in the dropdown. When it is bound to an array of complex data (i.e. objects) and the value used for `valueKey` is `undefined`, the item will be displayed in the dropdown, but cannot be selected.
-- When the combobox is bound to a remote service and there is a predefined selection, its input will remain blank until the requested data is loaded.
-
-
-The combobox uses the [Virtual Scroll](./layouts/virtual-scroll.mdx) component internally to virtualize its list, hence all Virtual Scroll limitations are valid for the combobox. For more details see the [Virtual Scroll Known Limitations](./layouts/virtual-scroll.mdx#known-limitations) section.
-
-
-## API References
-
--
--
-Additional [angular components](https://www.infragistics.com/products/ignite-ui-angular) and/or directives with relative APIs that were used:
--
--
--
-## Theming Dependencies
-
--
--
--
--
-
-## Additional Resources
-
-
-
-- [ComboBox Features](/combo-features)
-- [ComboBox Remote Binding](/combo-remote)
-- [ComboBox Templates](/combo-templates)
-- [Template Driven Forms Integration](/input-group)
-- [Reactive Forms Integration](/angular-reactive-form-validation)
-- [Single Select ComboBox](/simple-combo)
-
-Our community is active and always welcoming to new ideas.
-
-- [Ignite UI for Angular **Forums**](https://www.infragistics.com/community/forums/f/ignite-ui-for-angular)
-- [Ignite UI for Angular **GitHub**](https://github.com/IgniteUI/igniteui-angular)
diff --git a/docs/angular/src/content/en/components/expansion-panel.mdx b/docs/angular/src/content/en/components/expansion-panel.mdx
index 4d49687e13..7f24299da8 100644
--- a/docs/angular/src/content/en/components/expansion-panel.mdx
+++ b/docs/angular/src/content/en/components/expansion-panel.mdx
@@ -194,7 +194,7 @@ We can do that by passing content in an `igx-expansion-panel-icon` tag:
Our Angular Expansion Panel will now render "Show More" when the panel is collapsed and "Show Less" once it's fully expanded.
-The `IgxExpansionPanel` control allows all sorts of content to be added inside of the `igx-expansion-panel-body`. It can render [`IgxGrid`](/grid/grid)s, [`IgxCombo`](/combo), charts and even other expansion panels!
+The `IgxExpansionPanel` control allows all sorts of content to be added inside of the `igx-expansion-panel-body`. It can render [`IgxGrid`](/grid/grid)s, [`IgxCombo`](/inputs/combo/overview), charts and even other expansion panels!
For the sake of simplicity let's add some basic markup to the body of our expansion panel.
diff --git a/docs/angular/src/content/en/components/general/cli/component-templates.mdx b/docs/angular/src/content/en/components/general/cli/component-templates.mdx
index d073cce00c..8d49904cf4 100644
--- a/docs/angular/src/content/en/components/general/cli/component-templates.mdx
+++ b/docs/angular/src/content/en/components/general/cli/component-templates.mdx
@@ -59,8 +59,8 @@ These templates generate components into an existing Angular workspace only. The
| snackbar | Ignite UI Schematics collection: ng g @igniteui/angular-schematics:c snackbar newSnackbar Ignite UI CLI: ig add snackbar newSnackbarBasic IgxSnackbar sample. | [IgxSnackbar](../../snackbar.mdx) showing a brief message with an optional action. |
| toast | Ignite UI Schematics collection: ng g @igniteui/angular-schematics:c toast newToast Ignite UI CLI: ig add toast newToastBasic IgxToast sample. | [IgxToast](../../toast.mdx) showing a non-interactive notification. |
| Data Entry & Display | | |
-| combo | Ignite UI Schematics collection: ng g @igniteui/angular-schematics:c combo newCombo Ignite UI CLI: ig add combo newComboBasic IgxCombo with templating. | [IgxCombo](../../combo.mdx) with custom [templating](../../combo-templates.mdx). |
-| simple-combo | Ignite UI Schematics collection: ng g @igniteui/angular-schematics:c simple-combo newSimpleCombo Ignite UI CLI: ig add simple-combo newSimpleComboBasic IgxSimpleCombo sample. | [IgxSimpleCombo](../../simple-combo.mdx) with single selection. |
+| combo | Ignite UI Schematics collection: ng g @igniteui/angular-schematics:c combo newCombo Ignite UI CLI: ig add combo newComboBasic IgxCombo with templating. | [IgxCombo](../../inputs/combo/overview.mdx) with custom [templating](../../inputs/combo/templates.mdx). |
+| simple-combo | Ignite UI Schematics collection: ng g @igniteui/angular-schematics:c simple-combo newSimpleCombo Ignite UI CLI: ig add simple-combo newSimpleComboBasic IgxSimpleCombo sample. | [IgxSimpleCombo](../../inputs/combo/single-selection.mdx) with single selection. |
| badge | Ignite UI Schematics collection: ng g @igniteui/angular-schematics:c badge newBadge Ignite UI CLI: ig add badge newBadgeBasic IgxBadge sample. | [IgxBadge](../../inputs/badge.mdx) displaying a status indicator. |
| button-group | Ignite UI Schematics collection: ng g @igniteui/angular-schematics:c button-group newButtonGroup Ignite UI CLI: ig add button-group newButtonGroupBasic IgxButtonGroup sample. | [IgxButtonGroup](../../inputs/button-group.mdx) with a set of toggle buttons. |
| checkbox | Ignite UI Schematics collection: ng g @igniteui/angular-schematics:c checkbox newCheckbox Ignite UI CLI: ig add checkbox newCheckboxBasic IgxCheckbox sample. | [IgxCheckbox](../../inputs/checkbox.mdx) for binary choices. |
diff --git a/docs/angular/src/content/en/components/general/update-guide.mdx b/docs/angular/src/content/en/components/general/update-guide.mdx
index ccaa6d9315..26840a30a5 100644
--- a/docs/angular/src/content/en/components/general/update-guide.mdx
+++ b/docs/angular/src/content/en/components/general/update-guide.mdx
@@ -1525,7 +1525,7 @@ The `ng update` process will update all enumeration names, like `AvatarType`, `T
```
- IgxCombo
- - The way that the [`igx-combo`](/combo) handles selection and data binding is changed.
+ - The way that the [`igx-combo`](/inputs/combo/overview) handles selection and data binding is changed.
- If the combo's [`valueKey`] input is defined, the control will look for that specific property in the passed array of data items when performing selection.
**All** selection events are handled with the value of the data items' `valueKey` property.
@@ -1564,7 +1564,7 @@ The `ng update` process will update all enumeration names, like `AvatarType`, `T
}
```
- You can read more about setting up the combo in the [readme](https://github.com/IgniteUI/igniteui-angular/blob/master/projects/igniteui-angular/src/lib/combo/README.md#value-binding) and in the [official documentation](/combo#selection-api).
+ You can read more about setting up the combo in the [readme](https://github.com/IgniteUI/igniteui-angular/blob/master/projects/igniteui-angular/src/lib/combo/README.md#value-binding) and in the [official documentation](/inputs/combo/overview#value-and-selection).
## From 8.0.x to 8.1.x
diff --git a/docs/angular/src/content/en/components/grids-and-lists.mdx b/docs/angular/src/content/en/components/grids-and-lists.mdx
index 7618ee456a..22ff06eaf5 100644
--- a/docs/angular/src/content/en/components/grids-and-lists.mdx
+++ b/docs/angular/src/content/en/components/grids-and-lists.mdx
@@ -149,7 +149,7 @@ Full support for exporting data grids to XLSX, XLS, TSV or CSV. The Ignite UI fo
- [Grid-level Searching](/grid/search)
- [Export to Excel, CSV, TSV](/exporter-excel)
- [Multi-Column Headers](/grid/multi-column-headers)
-- [Combo Box/Dropdown](/combo)
+- [Combo Box/Dropdown](/inputs/combo/overview)
- [Virtualization and Performance](/grid/virtualization)
- [Remote Data Load on Demand](/grid/virtualization#remote-virtualization)
- [Cell Templates](/grid/grid#cell-template)
diff --git a/docs/angular/src/content/en/components/overlay-styling.mdx b/docs/angular/src/content/en/components/overlay-styling.mdx
index a418b0766a..092ca739d9 100644
--- a/docs/angular/src/content/en/components/overlay-styling.mdx
+++ b/docs/angular/src/content/en/components/overlay-styling.mdx
@@ -18,7 +18,7 @@ import Sample from 'igniteui-astro-components/components/mdx/Sample.astro';
-[`IgxOverlayService`](/overlay) is used to display content above the page content. A lot of Ignite UI for Angular components use the overlay - [Drop Down](/drop-down), [Combo](/combo), [Date Picker](/date-picker) and more - so it is important to understand how the overlay displays content.
+[`IgxOverlayService`](/overlay) is used to display content above the page content. A lot of Ignite UI for Angular components use the overlay - [Drop Down](/drop-down), [Combo](/inputs/combo/overview), [Date Picker](/date-picker) and more - so it is important to understand how the overlay displays content.
To display the content above other elements, the service moves it into a special outlet container (attached at the end of the document's body, by default). This behavior can affect styles [scoped to specific container](#scoped-overlay-styles).