Fix links

rvsia · rvsia · commit 7ddbcd7d15bb · 2020-06-30T13:46:59.000+02:00
diff --git a/packages/react-renderer-demo/src/components/common/example-link.js b/packages/react-renderer-demo/src/components/common/example-link.js
@@ -15,8 +15,8 @@ const ExampleLink = ({ to, text = 'To example' }) => {
   return (
     <React.Fragment>
       <div style={{ float: 'right' }}>
-        <RouterLink href={`/component-example/${to}`}>
-          <a className={classes.toExampleLink} href={`/component-example/${to}`}>
+        <RouterLink href={`/mappers/${to}`}>
+          <a className={classes.toExampleLink} href={`/mappers/${to}`}>
             <Button color="primary">{text}</Button>
           </a>
         </RouterLink>
diff --git a/packages/react-renderer-demo/src/components/docsearch.js b/packages/react-renderer-demo/src/components/docsearch.js
@@ -56,7 +56,7 @@ const DocSearch = () => {
         const resultUrl = new URL(suggestion.url);
 
         let query = '';
-        if (resultUrl.pathname.startsWith('/component-example/')) {
+        if (resultUrl.pathname.startsWith('/mappper/')) {
           ['mui', 'pf4', 'pf3'].find((mapper) => {
             if (resultUrl.hash.includes(mapper)) {
               query = `?mapper=${mapper}`;
diff --git a/packages/react-renderer-demo/src/components/landing-page/landing-page-cards.js b/packages/react-renderer-demo/src/components/landing-page/landing-page-cards.js
@@ -89,22 +89,22 @@ const buildFeatures = [
   {
     text: 'Multiple provided libraries - MaterialUI included!',
     Icon: LocalLibraryIcon,
-    link: '/renderer/component-api'
+    link: '/mappers/component-api'
   },
   {
     text: 'Validation - basic types are provided, supports async validators!',
     Icon: VerifiedUserIcon,
-    link: '/renderer/validators'
+    link: '/schema/introduction#validate'
   },
   {
     text: 'Conditions - hide and modify fields according to values of other fields!',
     Icon: PlaylistAddCheckIcon,
-    link: '/renderer/condition'
+    link: '/schema/introduction#condition'
   },
   {
     text: 'Fully customizable - you can use any components you are using right now!',
     Icon: EditAttributesIcon,
-    link: '/renderer/component-mapping'
+    link: '/mappers/custom-mapper'
   },
   {
     text: 'Online editor - you can build your form using comfy DnD!',
diff --git a/packages/react-renderer-demo/src/components/navigation/examples-definitions.js b/packages/react-renderer-demo/src/components/navigation/examples-definitions.js
@@ -14,10 +14,6 @@ export const baseExamples = [
   {
     component: componentTypes.CHECKBOX,
     link: componentTypes.CHECKBOX,
-    prev: {
-      link: '/renderer/form-template',
-      label: 'Form Controls'
-    },
     linkText: 'Checkbox'
   },
   {
@@ -83,14 +79,6 @@ export const baseExamples = [
   {
     component: componentTypes.WIZARD,
     link: componentTypes.WIZARD,
-    linkText: 'Wizard',
-    next: {
-      link: '/releases',
-      label: 'Releases'
-    },
-    prev: {
-      link: '/component-example/time-picker',
-      label: 'Time Picker'
-    }
+    linkText: 'Wizard'
   }
 ];
diff --git a/packages/react-renderer-demo/src/doc-components/examples-texts/blueprint/blueprint-date-picker.md b/packages/react-renderer-demo/src/doc-components/examples-texts/blueprint/blueprint-date-picker.md
@@ -2,7 +2,7 @@ Please check the [original component](https://blueprintjs.com/docs/#datetime/dat
 
 **Props**
 
-DatePicker is wrapped in a form group, so it accepts all [form group props](/renderer/component-api#formgroupwrappedcomponents).
+DatePicker is wrapped in a form group, so it accepts all [form group props](/mappers/component-api#formgroupwrappedcomponents).
 
 |Props|Type|Description|
 |-----|----|-----------|
diff --git a/packages/react-renderer-demo/src/doc-components/examples-texts/blueprint/blueprint-dual-list-select.md b/packages/react-renderer-demo/src/doc-components/examples-texts/blueprint/blueprint-dual-list-select.md
@@ -2,7 +2,7 @@ This a custom component with a custom design.
 
 **Props**
 
-Dual list select is wrapped in a form group, so it accepts all [form group props](/renderer/component-api#formgroupwrappedcomponents).
+Dual list select is wrapped in a form group, so it accepts all [form group props](/mappers/component-api#formgroupwrappedcomponents).
 
 |Props|Type|Default|Description|
 |-----|----|-------|-----------|
diff --git a/packages/react-renderer-demo/src/doc-components/examples-texts/blueprint/blueprint-field-array.md b/packages/react-renderer-demo/src/doc-components/examples-texts/blueprint/blueprint-field-array.md
@@ -48,4 +48,4 @@ const fields = [
 
 **Custom component**
 
-To implement a custom component, please take a look [here](/renderer/dynamic-fields).
+To implement a custom component, please take a look [here](/components/field-array).
diff --git a/packages/react-renderer-demo/src/doc-components/examples-texts/mui/common.md b/packages/react-renderer-demo/src/doc-components/examples-texts/mui/common.md
@@ -2,4 +2,4 @@
 
 In order to fully leverage material UI styling, this component accepts a number of different props. These props are distributed to respective components.
 
-To avoid manually setting common styles and props to each field in schema, please use the [global components props](/renderer/global-component-props) in component mapper.
+To avoid manually setting common styles and props to each field in schema, please use the [global components props](/mappers/global-component-props) in component mapper.
diff --git a/packages/react-renderer-demo/src/doc-components/examples-texts/mui/mui-dual-list-select.md b/packages/react-renderer-demo/src/doc-components/examples-texts/mui/mui-dual-list-select.md
@@ -2,7 +2,7 @@ This a custom component with a custom design.
 
 **Props**
 
-Dual list select is wrapped in a form group, so it accepts all [form group props](/renderer/component-api#formgroupwrappedcomponents).
+Dual list select is wrapped in a form group, so it accepts all [form group props](/mappers/component-api#formgroupwrappedcomponents).
 
 |Props|Type|Default|Description|
 |-----|----|-------|-----------|
diff --git a/packages/react-renderer-demo/src/doc-components/examples-texts/mui/mui-field-array.md b/packages/react-renderer-demo/src/doc-components/examples-texts/mui/mui-field-array.md
@@ -46,4 +46,4 @@ const fields = [
 
 **Custom component**
 
-To implement a custom component, please take a look [here](/renderer/dynamic-fields).
+To implement a custom component, please take a look [here](/components/field-array).
diff --git a/packages/react-renderer-demo/src/doc-components/examples-texts/mui/mui-slider.md b/packages/react-renderer-demo/src/doc-components/examples-texts/mui/mui-slider.md
@@ -2,7 +2,7 @@ Please check the [original component](https://material-ui.com/components/slider/
 
 **Props**
 
-Slider is wrapped in a form group, so it accepts all [form group props](/renderer/component-api#formgroupwrappedcomponents).
+Slider is wrapped in a form group, so it accepts all [form group props](/mappers/component-api#formgroupwrappedcomponents).
 
 |Props|Type|Description|
 |-----|----|-----------|
diff --git a/packages/react-renderer-demo/src/doc-components/examples-texts/pf3/pf3-field-array.md b/packages/react-renderer-demo/src/doc-components/examples-texts/pf3/pf3-field-array.md
@@ -4,4 +4,4 @@ In case of need, please contact us or open a PR.
 
 **Custom component**
 
-To implement a custom component, please take a look [here](/renderer/dynamic-fields).
+To implement a custom component, please take a look [here](/components/field-array).
diff --git a/packages/react-renderer-demo/src/doc-components/examples-texts/pf3/pf3-slider.md b/packages/react-renderer-demo/src/doc-components/examples-texts/pf3/pf3-slider.md
@@ -2,7 +2,7 @@ Please check the [original component](https://patternfly-react-pf3.surge.sh/?pat
 
 **Props**
 
-Slider is wrapped in a form group, so it accepts all [form group props](/renderer/component-api#formgroupwrappedcomponents).
+Slider is wrapped in a form group, so it accepts all [form group props](/mappers/component-api#formgroupwrappedcomponents).
 
 |Props|Type|Description|
 |-----|----|-----------|
diff --git a/packages/react-renderer-demo/src/doc-components/examples-texts/pf4/pf4-dual-list.md b/packages/react-renderer-demo/src/doc-components/examples-texts/pf4/pf4-dual-list.md
@@ -2,7 +2,7 @@ This a custom component with a custom design. Things can be changed, after offic
 
 **Props**
 
-Dual list select is wrapped in a form group, so it accepts all [form group props](/renderer/component-api#formgroupwrappedcomponents).
+Dual list select is wrapped in a form group, so it accepts all [form group props](/mappers/component-api#formgroupwrappedcomponents).
 
 |Props|Type|Default|Description|
 |-----|----|-------|-----------|
diff --git a/packages/react-renderer-demo/src/doc-components/examples-texts/pf4/pf4-field-array.md b/packages/react-renderer-demo/src/doc-components/examples-texts/pf4/pf4-field-array.md
@@ -41,4 +41,4 @@ const fields = [
 
 **Custom component**
 
-To implement a custom component, please take a look [here](/renderer/dynamic-fields).
+To implement a custom component, please take a look [here](/components/field-array).
diff --git a/packages/react-renderer-demo/src/doc-components/examples-texts/suir/suir-field-array.md b/packages/react-renderer-demo/src/doc-components/examples-texts/suir/suir-field-array.md
@@ -46,7 +46,7 @@ const fields = [
 
 **Custom component**
 
-To implement a custom component, please take a look [here](/renderer/dynamic-fields).
+To implement a custom component, please take a look [here](/components/field-array).
 
 ### Sub components props
 
diff --git a/packages/react-renderer-demo/src/pages/components/field-array.md b/packages/react-renderer-demo/src/pages/components/field-array.md
@@ -13,7 +13,7 @@ import { FieldArray } from '@data-driven-forms/react-form-renderer';
 
 # Dynamic fields
 
-Dynamic fields allow you to add or remove field inputs in your forms. In Data Driven Forms, Field Array is used to provide this functionality. Simillarly to [FieldProvider](/renderer/field-provider) Data driven forms include [React Final Form Arrays](https://github.com/final-form/react-final-form-arrays). Please visit their documentation to learn more about the functionality and implementation.
+Dynamic fields allow you to add or remove field inputs in your forms. In Data Driven Forms, Field Array is used to provide this functionality. Simillarly to [FieldProvider](/components/field-provider) Data driven forms include [React Final Form Arrays](https://github.com/final-form/react-final-form-arrays). Please visit their documentation to learn more about the functionality and implementation.
 
 ## Using FieldArray
 
@@ -61,7 +61,7 @@ You don't need to name the nested components, then the values are saved as an ar
 
 # Validators
 
-You can use user a few provided validators (you can also use your [own](/renderer/validators).)
+You can use user a few provided validators (you can also use your [own](/mappers/validator-mapper).)
 
 ```jsx
 MIN_ITEMS_VALIDATOR: ({threshold})
@@ -74,9 +74,9 @@ EXACT_LENGTH: ({threshold})
 
 PF4 and MUI component mapper provides an experimental implementation of field arrays.
 
-[PF4 Field Array](/component-example/field-array?mapper=pf4)
+[PF4 Field Array](/mappers/field-array?mapper=pf4)
 
-[MUI Field Array](/component-example/field-array?mapper=mui)
+[MUI Field Array](/mappers/field-array?mapper=mui)
 
 <CodeExamples source="components/field-array/pf4-demo" mode="preview" />
 
diff --git a/packages/react-renderer-demo/src/pages/components/field-provider.md b/packages/react-renderer-demo/src/pages/components/field-provider.md
@@ -9,7 +9,7 @@ React form renderer is using [react-final-form](https://github.com/final-form/re
 Most of its features are not directly available for consistency and performance reasons. If you want to create any custom
 components, you can access these features via `FieldProvider` component or `useFieldApi` hook.
 
-`FieldProvider` is a wrapper using [useFieldApi](/hooks/use-field-api) to get the access to the form state. **It's recommended to use the hook.** You can read more about that in [Component mapping](/renderer/component-mapping).
+`FieldProvider` is a wrapper using [useFieldApi](/hooks/use-field-api) to get the access to the form state. **It's recommended to use the hook.** You can read more about that in [Component mapping](/mappers/custom-mapper).
 
 ## Props
 
diff --git a/packages/react-renderer-demo/src/pages/components/form-template.md b/packages/react-renderer-demo/src/pages/components/form-template.md
@@ -32,7 +32,7 @@ With using `useFormApi` hook you can get access to all form information and func
 
 ## Customize form buttons
 
-You can customize form buttons in your [FormTemplate](/renderer/renderer-api#requiredprops) component
+You can customize form buttons in your [FormTemplate](/components/renderer#requiredprops) component
 
 <CodeExample source="components/form-template/custom-buttons" mode="preview" />
 
diff --git a/packages/react-renderer-demo/src/pages/components/renderer.md b/packages/react-renderer-demo/src/pages/components/renderer.md
@@ -21,36 +21,30 @@ const App = () => (<FormRenderer
 
 |Prop|Type|Description|
 |----|:--:|----------:|
-|[componentMapper](/renderer/component-mapping)|object|Defines types of form field components. Field components can change the state of the form.|
-|[FormTemplate](/renderer/component-mapping)|Component|Components which defines a template of the form. This component receives two props from the renderer: `formFields` and `schema`. `formFields` is the content of the form. You should wrap this content into your `<form>` component and add form buttons.|
+|[componentMapper](/mappers/custom-mapper)|object|Defines types of form field components. Field components can change the state of the form.|
+|[FormTemplate](/components/form-template)|Component|Components which defines a template of the form. This component receives two props from the renderer: `formFields` and `schema`. `formFields` is the content of the form. You should wrap this content into your `<form>` component and add form buttons.|
 |onSubmit|func|A submit callback which receives two arguments: `values` and `formApi`.|
 |schema|object|A schema which defines structure of the form.|
 
 ## Optional props
 
 |Prop|Type|Description|Default|
 |----|:--:|----------:|------:|
-|[actionMapper](/renderer/action-mapper)|object|Action mapper allows to map props to functions.||
-|[clearOnUnmount](/renderer/unmounting)|bool|Will clear values of unmounted components. You can also set this to specific component in the form schema.|false|
-|[clearedValue](/renderer/cleared-value)|any|Value that will be set to field with **initialValue** after deleting it. Useful for forms while editing.|undefined|
+|[actionMapper](/mappers/action-mapper)|object|Action mapper allows to map props to functions.||
+|[clearOnUnmount](/schema/clear-on-unmount)|bool|Will clear values of unmounted components. You can also set this to specific component in the form schema.|false|
+|[clearedValue](/schema/cleared-value)|any|Value that will be set to field with **initialValue** after deleting it. Useful for forms while editing.|undefined|
 |onReset|func|A reset callback. You don't need to manually clear the form values!||
 |onCancel|func|A cancel callback, which receives `values` as the first argument.||
 |debug|func|A function which will be called with every form update, i.e. `({ values }) => setValues(values)`, please take a look [here](https://final-form.org/docs/react-final-form/types/FormProps#debug)||
 |initialValues|object|An object of fields names as keys and values as their values.||
-|[schemaValidatorMapper](/renderer/schema-validator)|object|Schema validators mapper. You can control schemas of your components, validators and actions.||
+|[schemaValidatorMapper](/mappers/schema-validator-mapper)|object|Schema validators mapper. You can control schemas of your components, validators and actions.||
 |subscription|object|You can pass your own [subscription](https://final-form.org/docs/react-final-form/types/FormProps#subscription), which will be added to default settings.|`{ pristine: true, submitting: true, valid: true }`|
-|[validate](/renderer/validators)|func|A function which receives all form values and returns an object with errors.||
-|[validatorMapper](/renderer/validators#validatormapper)|object|A mapper containing custom validators, it's automatically merged with the default one.||
+|[validate](/schema/introduction#validate)|func|A function which receives all form values and returns an object with errors.||
+|[validatorMapper](/mappers/validator-mapper)|object|A mapper containing custom validators, it's automatically merged with the default one.||
 
 # Schema
 
-The root object of the schema represents the Form component, that needs only this prop:
-
-|Prop|Type|Description|
-|----|:--:|----------:|
-|fields|array of objects|[Components](/renderer/component-api) of the form. Required!|
-
-You can use all other props in your `formTemplate` components.
+The root object of the schema represents the Form component. Please read more [here](/schema/introduction).
 
 ## Example
 
diff --git a/packages/react-renderer-demo/src/pages/hooks/use-field-api.md b/packages/react-renderer-demo/src/pages/hooks/use-field-api.md
@@ -13,7 +13,7 @@ components, you can access these features via `FieldProvider` component or `useF
 
 `useFieldApi` is a wrapper around [React Final Form useField hook](https://final-form.org/docs/react-final-form/api/useField).
 
-You can read more about that in [Component mapping](/renderer/component-mapping).
+You can read more about that in [Component mapping](/mappers/custom-mapper).
 
 ## Usage
 
diff --git a/packages/react-renderer-demo/src/pages/index.js b/packages/react-renderer-demo/src/pages/index.js
@@ -68,8 +68,8 @@ const LandingPage = () => {
           Data Driven Forms converts JSON form definitions into fully functional React forms.
         </Typography>
         <div className={classes.getStartedLink}>
-          <Link href="/renderer/get-started">
-            <a className={classes.getStartedAnchor} href="/renderer/get-started">
+          <Link href="/introduction">
+            <a className={classes.getStartedAnchor} href="/introduction">
               <Button variant="outlined" className={classes.getStartedButton}>
                 Get started
               </Button>
diff --git a/packages/react-renderer-demo/src/pages/introduction.md b/packages/react-renderer-demo/src/pages/introduction.md
@@ -10,9 +10,9 @@ It uses [React Final Form](https://github.com/final-form/react-final-form) for t
 It is highly recommended to check their documentations first to fully understand how
 the [Data Driven Forms](https://github.com/data-driven-forms/react-forms) libraries work.
 
-All you need is to [install](/renderer/installation) the form renderer and choose the component mapper you want ([or create your own](/renderer/component-mapping)).
+All you need is to [install](/installation) the form renderer and choose the component mapper you want ([or create your own](/mappers/custom-mapper)).
 
-Import `FormRenderer` from the react-form-renderer. This component takes four required props: FormTemplate, schema, componentMapper and onSubmit. You can read about them [here](/renderer/renderer-api#requiredprops).
+Import `FormRenderer` from the react-form-renderer. This component takes four required props: FormTemplate, schema, componentMapper and onSubmit. You can read about them [here](/components/renderer#requiredprops).
 
 You can check the simple example below.
 
diff --git a/packages/react-renderer-demo/src/pages/mappers/action-mapper.md b/packages/react-renderer-demo/src/pages/mappers/action-mapper.md
@@ -5,7 +5,7 @@ import DocPage from '@docs/doc-page';
 
 # Action Mapper
 
-The [ActionMapper](/renderer/renderer-api#optionalprops) allows you to map schema props to functions. This is useful when your schema is not written in JavaScript and you cannot use function inside of it, especially for schemas stored in databases.
+The [ActionMapper](/components/renderer#optionalprops) allows you to map schema props to functions. This is useful when your schema is not written in JavaScript and you cannot use function inside of it, especially for schemas stored in databases.
 
 ## Mapper
 
diff --git a/packages/react-renderer-demo/src/pages/mappers/component-api.md b/packages/react-renderer-demo/src/pages/mappers/component-api.md
@@ -32,7 +32,7 @@ Standard components are:
 
 # Form fields components
 
-Basic components that can change the form state (inputs) share common props. These components are using [useFieldApi](/renderer/component-mapping#usefieldapi) or [FieldProvider](/renderer/component-mapping#fieldprovider) to access the form state.
+Basic components that can change the form state (inputs) share common props. These components are using [useFieldApi](/mappers/custom-mapper#usefieldapi) or [FieldProvider](/mappers/custom-mapper#fieldprovider) to access the form state.
 
 |Prop|Type|Description|
 |----|:--:|----------:|
@@ -43,7 +43,7 @@ Basic components that can change the form state (inputs) share common props. The
 |isRequired|boolean|Is the field required?|
 |isDisabled|boolean|Is the field disabled?|
 |isReadOnly|boolean|Is the field readOnly?|
-|initialValue|custom|There are two ways how to set initial values in the form: you can use either the [initialValues](/renderer/renderer-api) prop for the whole form or you can set the value in the schema for each field separately. For more information, please see [here](https://final-form.org/docs/react-final-form/types/FieldProps#initialvalue).|
+|initialValue|custom|There are two ways how to set initial values in the form: you can use either the [initialValues](/components/renderer) prop for the whole form or you can set the value in the schema for each field separately. For more information, please see [here](https://final-form.org/docs/react-final-form/types/FieldProps#initialvalue).|
 
 ## Text field
 
@@ -175,7 +175,7 @@ Wizard step <br/>
 |----|:--:|----------:|
 |title|node/string|Step title|
 |name|string, number|Uniq name of the step|
-|nextStep|object/name of next step|See [wizard documentation](/component-example/wizard)|
+|nextStep|object/name of next step|See [wizard documentation](/mappers/wizard)|
 |fields|array|An array of form fields|
 
 <ExampleLink to='wizard' />
diff --git a/packages/react-renderer-demo/src/pages/mappers/global-component-props.md b/packages/react-renderer-demo/src/pages/mappers/global-component-props.md
@@ -5,7 +5,7 @@ import CodeExample from '@docs/code-example';
 
 # Global component props
 
-If you need to set the same value to prop to every component occurance in a form, you can do so via [component mapper](/renderer/component-mapping).
+If you need to set the same value to prop to every component occurance in a form, you can do so via [component mapper](/mappers/custom-mapper).
 
 Always keep in mind, that the props depend on component mapper.
 
diff --git a/packages/react-renderer-demo/src/pages/mappers/schema-validator-mapper.md b/packages/react-renderer-demo/src/pages/mappers/schema-validator-mapper.md
@@ -5,7 +5,7 @@ import CodeExample from '@docs/code-example';
 
 # Schema validation
 
-Data Driven Forms contains default schema validator, that controls basic schema attributes: `name`, `component`, conditions, validators, etc. If you want to control your own validators, components or actions, use [schemaValidatorMapper](/renderer/renderer-api#optionalprops) prop.
+Data Driven Forms contains default schema validator, that controls basic schema attributes: `name`, `component`, conditions, validators, etc. If you want to control your own validators, components or actions, use [schemaValidatorMapper](/components/renderer#optionalprops) prop.
 
 It's a simple object containing three keys: `components`, `actions`, `validators`. Each of these is an another object with names as keys and functions as returns. Components' validators receive the whole field object, actions'/validators' validators receive two arguments: action/validator as the first one and the name of the field as the second one.
 
diff --git a/packages/react-renderer-demo/src/pages/mappers/suir-component-mapper.md b/packages/react-renderer-demo/src/pages/mappers/suir-component-mapper.md
diff --git a/packages/react-renderer-demo/src/pages/mappers/validator-mapper.md b/packages/react-renderer-demo/src/pages/mappers/validator-mapper.md
diff --git a/packages/react-renderer-demo/src/pages/schema/condition-actions.md b/packages/react-renderer-demo/src/pages/schema/condition-actions.md
diff --git a/packages/react-renderer-demo/src/pages/schema/condition-sequence.md b/packages/react-renderer-demo/src/pages/schema/condition-sequence.md
diff --git a/packages/react-renderer-demo/src/pages/schema/initialize-on-mount.md b/packages/react-renderer-demo/src/pages/schema/initialize-on-mount.md

Original file line number	Diff line number	Diff line change
`@@ -89,22 +89,22 @@ const buildFeatures = [`
`89`	`89`	`{`
`90`	`90`	`text: 'Multiple provided libraries - MaterialUI included!',`
`91`	`91`	`Icon: LocalLibraryIcon,`
`92`		`- link: '/renderer/component-api'`
	`92`	`+ link: '/mappers/component-api'`
`93`	`93`	`},`
`94`	`94`	`{`
`95`	`95`	`text: 'Validation - basic types are provided, supports async validators!',`
`96`	`96`	`Icon: VerifiedUserIcon,`
`97`		`- link: '/renderer/validators'`
	`97`	`+ link: '/schema/introduction#validate'`
`98`	`98`	`},`
`99`	`99`	`{`
`100`	`100`	`text: 'Conditions - hide and modify fields according to values of other fields!',`
`101`	`101`	`Icon: PlaylistAddCheckIcon,`
`102`		`- link: '/renderer/condition'`
	`102`	`+ link: '/schema/introduction#condition'`
`103`	`103`	`},`
`104`	`104`	`{`
`105`	`105`	`text: 'Fully customizable - you can use any components you are using right now!',`
`106`	`106`	`Icon: EditAttributesIcon,`
`107`		`- link: '/renderer/component-mapping'`
	`107`	`+ link: '/mappers/custom-mapper'`
`108`	`108`	`},`
`109`	`109`	`{`
`110`	`110`	`text: 'Online editor - you can build your form using comfy DnD!',`
Original file line number	Diff line number	Diff line change
`@@ -48,4 +48,4 @@ const fields = [`
`48`	`48`
`49`	`49`	`Custom component`
`50`	`50`
`51`		`-To implement a custom component, please take a look [here](/renderer/dynamic-fields).`
	`51`	`+To implement a custom component, please take a look [here](/components/field-array).`
Original file line number	Diff line number	Diff line change
`@@ -2,4 +2,4 @@`
`2`	`2`
`3`	`3`	`In order to fully leverage material UI styling, this component accepts a number of different props. These props are distributed to respective components.`
`4`	`4`
`5`		`-To avoid manually setting common styles and props to each field in schema, please use the [global components props](/renderer/global-component-props) in component mapper.`
	`5`	`+To avoid manually setting common styles and props to each field in schema, please use the [global components props](/mappers/global-component-props) in component mapper.`
Original file line number	Diff line number	Diff line change
`@@ -46,4 +46,4 @@ const fields = [`
`46`	`46`
`47`	`47`	`Custom component`
`48`	`48`
`49`		`-To implement a custom component, please take a look [here](/renderer/dynamic-fields).`
	`49`	`+To implement a custom component, please take a look [here](/components/field-array).`