Merge branch 'vnext' into sstoychev/improve-gtm-implementation

Author: ChronosSF

docs/angular/src/content/en/components/button.mdx

@@ -294,7 +294,7 @@ $my-dialog-theme: dialog-theme(
 ```
 
 <DocsAside type="info">
-In order to style any additional components that are used as part of the dialog window's content (such as the [`IgxButton`](/button)), an additional theme should be created that is specific to the respective component and is placed under the dialog window's scope only (so it does not affect the rest of the application).
+In order to style any additional components that are used as part of the dialog window's content (such as the [`IgxButton`](./inputs/button.mdx)), an additional theme should be created that is specific to the respective component and is placed under the dialog window's scope only (so it does not affect the rest of the application).
 </DocsAside>
 
 ```scss

docs/angular/src/content/en/components/dialog.mdx

@@ -300,7 +300,7 @@ toggleFavorite(item: IgxListItem) {
 }
 ```
 
-Let's also allow the user to choose the size of the list by using the `--ig-size` CSS custom property. We will do this by importing the `IgxButtonGroupModule` and using the [**IgxButtonGroup**](/components/inputs/button-group) to display all size values. This way whenever one gets selected, we will update the **size** of the list.
+Let's also allow the user to choose the size of the list by using the `--ig-size` CSS custom property. We will do this by importing the `IgxButtonGroupModule` and using the [**IgxButtonGroup**](/inputs/button-group) to display all size values. This way whenever one gets selected, we will update the **size** of the list.
 
 ```typescript
 // app.module.ts

docs/angular/src/content/en/components/list.mdx

@@ -415,7 +415,7 @@ Related topics:
 - [Component Themes](../sass/component-themes.mdx)
 - [Typography](../sass/typography.mdx)
 - [Avatar Component](../../layouts/avatar.mdx)
-- [Button Component](../../button.mdx)
+- [Button Component](inputs/button)
 - [Dialog Component](../../dialog.mdx)
 - [Icon Component](../../icon.mdx)
 - [Expansion Panel Component](../../expansion-panel.mdx)

docs/angular/src/content/en/components/themes/misc/angular-material-theming.mdx

@@ -368,7 +368,7 @@ Ignite UI for Angular exposes four default type scales for each of its themes, w
 - [Component Themes](/themes/sass/component-themes)
 - [Typography](/themes/sass/typography)
 - [Avatar Component](../../layouts/avatar.mdx)
-- [Button Component](/button)
+- [Button Component](inputs/button)
 - [Dialog Component](/dialog)
 - [Icon Component](/icon)
 - [List Component](/list)

docs/angular/src/content/en/components/themes/misc/bootstrap-theming.mdx

@@ -20,7 +20,7 @@ Many Ignite UI components have predefined minimum and maximum border-radius valu
 When you set `--ig-radius-factor` to 0, the component uses its minimum border-radius and will appear more block-like with sharp corners. When set to 1, the component uses its maximum predefined border-radius and will appear rounded.
 
 Here is a list of the components that have predefined minimum and maximum border-radius values and can be modified using the `--ig-radius-factor` variable: <br/>
-• [Action Strip](/action-strip) • [Button](/button) • [Button Group](/components/inputs/button-group) • [Calendar](/calendar) • [Card](/card) • [Carousel](/carousel) • [Checkbox](/checkbox) • [Chip](/chip) • [Combo](/combo) • [Date Picker](/date-picker) • [Date Range Picker](/date-range-picker) • [Grid](/grid/grid) • [Input Group](/input-group) • [Linear Progress](/linear-progress) • [List](/list) • [Month Picker](/month-picker) • [Navigation Drawer](/navdrawer) • [Radio](/radio-button) • [Ripple](/ripple) • [Snackbar](/snackbar) • [Switch](/switch) • [Toast](/toast)
+• [Action Strip](/action-strip) • [Button](inputs/button) • [Button Group](/inputs/button-group) • [Calendar](/calendar) • [Card](/card) • [Carousel](/carousel) • [Checkbox](/checkbox) • [Chip](/chip) • [Combo](/combo) • [Date Picker](/date-picker) • [Date Range Picker](/date-range-picker) • [Grid](/grid/grid) • [Input Group](/input-group) • [Linear Progress](/linear-progress) • [List](/list) • [Month Picker](/month-picker) • [Navigation Drawer](/navdrawer) • [Radio](/radio-button) • [Ripple](/ripple) • [Snackbar](/snackbar) • [Switch](/switch) • [Toast](/toast)
 
 ## Usage
 

docs/angular/src/content/en/components/themes/roundness.mdx

@@ -408,7 +408,7 @@ $my-time-picker-theme: time-picker-theme(
 ```
 
 <DocsAside type="info">
-In order to style any additional components that are used as part of the time picker window's content (such as the [`IgxButton`](/button)), an additional theme should be created that is specific to the respective component and is placed under the dialog window's scope only (so it does not affect the rest of the application).
+In order to style any additional components that are used as part of the time picker window's content (such as the [`IgxButton`](./inputs/button.mdx)), an additional theme should be created that is specific to the respective component and is placed under the dialog window's scope only (so it does not affect the rest of the application).
 </DocsAside>
 
 Since the time picker window uses the [`IgxOverlayService`](/overlay), in order for our custom theme to reach down the time picker window that we want to style, we will provide a specific outlet where the dialog window will be placed in the DOM when it is visible.

docs/angular/src/content/en/components/time-picker.mdx

@@ -1979,7 +1979,7 @@
   },
   {
     "name": "Button",
-    "href": "button.mdx"
+    "href": "inputs/button.mdx"
   },
   {
     "name": "Button Group",

docs/angular/src/content/en/components/toc.json

@@ -486,7 +486,7 @@ $dark-tooltip: tooltip-theme(
 ```
 
 <DocsAside type="info">
-In order to style any additional components that are used as part of the tooltip's content (such as [`IgxButton`](/button), [`IgxSwitch`](/switch), etc.), an additional theme should be created that is specific to the respective component and placed under the tooltip's scope only (so it does not affect the rest of the application).
+In order to style any additional components that are used as part of the tooltip's content (such as [`IgxButton`](./inputs/button.mdx), [`IgxSwitch`](/switch), etc.), an additional theme should be created that is specific to the respective component and placed under the tooltip's scope only (so it does not affect the rest of the application).
 </DocsAside>
 
 Since the tooltip uses the [`IgxOverlayService`](/overlay), in order for our custom theme to reach down the tooltip that we want to style, we will provide a specific outlet where the tooltip will be placed in the DOM when it is visible.

docs/angular/src/content/en/components/tooltip.mdx

@@ -320,9 +320,9 @@ If you want the buttons to be part of the keyboard navigation, then each on of t
 Using the [Ignite UI for Angular Theme Library](/themes), we can greatly alter the Row Editing overlay.
 The Row Editing overlay is a composite element - its UI is comprised of a couple of other components:
     - [`igx-banner`](/banner) in order to render its contents
-    - [`igx-button`](/button)s are rendered in the default template (for the `Done` and `Cancel` buttons).
+    - [`igx-button`](inputs/button)s are rendered in the default template (for the `Done` and `Cancel` buttons).
 
-In the below example, we will make use of those two components' styling options, [`button styling`](/button#styling) & [`banner-styling`](/banner#styling), to customize the experience of our {ComponentName}'s Row Editing.
+In the below example, we will make use of those two components' styling options, [`button styling`](inputs/button#styling) & [`banner-styling`](/banner#styling), to customize the experience of our {ComponentName}'s Row Editing.
 We will also style the current cell's editor and background to make it more distinct.
 
 <ComponentBlock for="Grid, TreeGrid, HierarchicalGrid">