From fdba51f5ebcd025a04bebde77c1ef0f47603f8e2 Mon Sep 17 00:00:00 2001
From: Louise Foussat <louisefoussat@gmail.com>
Date: Mon, 22 Apr 2019 14:51:05 +0100
Subject: [PATCH 01/21] create first doc for step creation in
 signup/administrative part

---
 doc/create-steps.md | 152 ++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 152 insertions(+)
 create mode 100644 doc/create-steps.md

diff --git a/doc/create-steps.md b/doc/create-steps.md
new file mode 100644
index 00000000..0f583973
--- /dev/null
+++ b/doc/create-steps.md
@@ -0,0 +1,152 @@
+# How to create onboarding steps
+
+## Usage
+This documentation explains how to create steps in your onboarding. 2 kind of steps can be generated in a modular way :
+* forms
+* documents to sign
+
+These steps are used for the "sign up" phase, and for the administrative part of the onboarding.
+
+## Description & examples
+The sign up phase and the administration part of the onboarding are related to major objects in the admin. all the steps for each of these two sections are children of these two big objects, that you can create, update, or delete, and order as you wish. 
+The objects contained in the sign up phase are object of type "sign up".
+The objects contained in the administration part of the onboarding phase are object of type "onboarding".
+
+### Relate a step to a major object
+Every step is related to the major object you want to costum as a child. To create a child, you must :
+1. Create a new object for your step in the admin (in Admin > "Add new object")
+  * The title of your object will be the title displayed for the step you're creating. Use a intellegible title for your user.
+  * This object must have the same type as your major object ("signup" for the sign up phase, "onboarding" for the administration part of the onboarding)
+2. Add this new object as a child of your major object
+  1. Edit the major object
+  2. Go to "Children" > "Add a child"
+  3. Set up the new child:
+    * Enter its name in the input "Add a child name"
+    * Select you child in the select input
+    * Click on "ADD"
+
+### Settings for a form step
+In the child object you've created, 2 attributes must be filled:
+1. subtype
+2. form
+
+To set up the child object you've created with these elements :
+1. Edit you child object
+2. Go to "Object attributes"
+3. Add the attributes :
+  1. Add a new key "subtype" of type `<String>` with the value 'onb-adm-form'
+  2. Add a new key "form" of type `<Object>` 
+    * The form you're creating can have several sections. Each section is displayed with a title, and its inputs. 
+    NB : The submission of the form will check the required inputs of all the sections you've created. 
+    * To create a section, add a new key to your form object, of type `<Object>`, that contains :
+      1. A key "title" of type `<String>`. The value of this property will be the title displayed in the top of your form section. If you have only one section in your form step, and you don't need a section title, you don't have to set up this property.
+      2. An "inputs" key of type `<Object>`, which will contain all the inputs of the section. For each input you want to add, you must set up the input as this :
+        * Add a new `<Object>` element in the "inputs" object. The key of this object will be used as the "name" attribute of your input. The values will be considered as the props of your input.
+
+Set up of an input props :
+* You must declare a "type" key of type `<String>`, wich define the type of your input : `<tel>`, `<text>`, `<date>`, `<select>`, `<radio>`, `<switch>`, `<checkbox>`, `<textarea>`. 
+* Then you can fill the props you need for your input, according to its type : `<placeholder>`, `<id>`, `<required>`, `<label>`, `<items>`, `<emptyItems>`, `<index>`, etc.
+
+Here are examples of the structure the form attribute could have, with two sections and an example of set up for every kind of input type :
+
+```javascript
+const formStepAttributes = {
+  subtype: "onb-adm-form",
+  form: {
+    section1: {
+      title: "My section title",
+      inputs: {
+        firstName: {
+          index: 0,
+          placeholder: 'First name',
+          type: 'text',
+          required: true,
+        },
+        tel: {
+          index: 1,
+          required: true,
+          type: 'tel',
+          label: 'Phone number',
+          placeholder: '+333 33 33 33 33',
+          pattern: '[+][3][0-9]{2}[0-9]{2}[0-9]{2}[0-9]{2}[0-9]{2}',
+        },
+        medicalInfo: {
+          label: 'Medical informations',
+          index: 6,
+          placeholder: 'Medical Informations',
+          type: 'textarea',
+        },
+        dateOfBirth: {
+          index: 2,
+          required: true,
+          type: 'date',
+          label: 'Date of birth',
+          value: '2000-01-01',
+        },
+        gender: {
+          index: 3,
+          type: 'select',
+          id: 'genders',
+          required: true,
+          emptyItem: { label: 'Select your gender' },
+          items: [
+            { label: 'Male', data: 'male' },
+            { label: 'Female', data: 'female' },
+          ],
+        },
+        environment: {
+          index: 4,
+          type: 'radio',
+          required: true,
+          label: 'Which environment do you live in ?',
+          inlineBlock: true,
+          items: [
+            { label: 'City', data: 'city' },
+            { label: 'Countryside', data: 'countryside' },
+          ],
+        },
+        programmingAbilities: {
+          index: 5,
+          type: 'switch',
+          label: 'I am new in programming',
+          value: true,
+        },
+        generalContions: {
+          index: 7,
+          type: 'checkbox',
+          label: 'I have read and I accept the general conditions',
+          value: false,
+        },
+      },
+    },
+    section2: {
+      title: "My second section title",
+      inputs: {
+        firstName: {
+          index: 0,
+          placeholder: 'First name',
+          type: 'text',
+          required: true,
+        }
+      }
+    }
+  }
+}
+```
+
+This for step would look like this :
+
+
+NB : 
+* The index property is used to order your inputs. It won't be spread in the input.
+* The type property is resquired. It will be used to determine the kind of input we must generate. It is spread in the input only if the input type attribute is required (type 'tel' or 'text' for example, but not for type 'select' - in this case, we will generate a select element)
+* Each input type has its own attributes. You can check how to set up your inputs hey : 
+  * [textInput documentation](https://alem.01-edu.org/design/Components/FormInputs/TextInput) - used for inputs type 'text', 'tel', and 'date'
+  * [textArea documentation](https://alem.01-edu.org/design/Components/FormInputs/TextArea)
+  * [select documentation](https://alem.01-edu.org/design/Components/FormControls/Select)
+  * [radio button documentation](https://alem.01-edu.org/design/Components/FormControls/Radio)
+  * [switch documentation](https://alem.01-edu.org/design/Components/FormControls/Switch)
+  * [checkbox documentation](https://alem.01-edu.org/design/Components/FormControls/Checkbox)
+* For switch and checkbox inputs type, you have to set the default value as a boolean property named "value".
+
+### Settings for a document to sign step

From d726316b04d94b50100706225f6633f07349266a Mon Sep 17 00:00:00 2001
From: Louise Foussat <louisefoussat@gmail.com>
Date: Mon, 22 Apr 2019 15:14:08 +0100
Subject: [PATCH 02/21] add image to the form step section

---
 doc/create-steps.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/create-steps.md b/doc/create-steps.md
index 0f583973..39764d74 100644
--- a/doc/create-steps.md
+++ b/doc/create-steps.md
@@ -135,7 +135,7 @@ const formStepAttributes = {
 ```
 
 This for step would look like this :
-
+![form step example](https://user-images.githubusercontent.com/35296671/56503976-012aae80-650f-11e9-82c8-dd7d026b6eb1.png)
 
 NB : 
 * The index property is used to order your inputs. It won't be spread in the input.

From 31c0e3ec07a3afebfc4c22c6cd6ee7a21c17515e Mon Sep 17 00:00:00 2001
From: Louise Foussat <louisefoussat@gmail.com>
Date: Mon, 22 Apr 2019 15:14:28 +0100
Subject: [PATCH 03/21] fix name of subtype for form step doc

---
 doc/create-steps.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/create-steps.md b/doc/create-steps.md
index 39764d74..2fb5e330 100644
--- a/doc/create-steps.md
+++ b/doc/create-steps.md
@@ -34,7 +34,7 @@ To set up the child object you've created with these elements :
 1. Edit you child object
 2. Go to "Object attributes"
 3. Add the attributes :
-  1. Add a new key "subtype" of type `<String>` with the value 'onb-adm-form'
+  1. Add a new key "subtype" of type `<String>` with the value 'onb-adm-form-generator'
   2. Add a new key "form" of type `<Object>` 
     * The form you're creating can have several sections. Each section is displayed with a title, and its inputs. 
     NB : The submission of the form will check the required inputs of all the sections you've created. 

From 7caaacff2776f0d97d2aa39eb1c740e6d383f719 Mon Sep 17 00:00:00 2001
From: Louise Foussat <louisefoussat@gmail.com>
Date: Mon, 22 Apr 2019 15:16:57 +0100
Subject: [PATCH 04/21] add document to sign step example

---
 doc/create-steps.md | 39 ++++++++++++++++++++++++++++++++++++++-
 1 file changed, 38 insertions(+), 1 deletion(-)

diff --git a/doc/create-steps.md b/doc/create-steps.md
index 2fb5e330..86251af1 100644
--- a/doc/create-steps.md
+++ b/doc/create-steps.md
@@ -134,7 +134,7 @@ const formStepAttributes = {
 }
 ```
 
-This for step would look like this :
+This form step would look like this :
 ![form step example](https://user-images.githubusercontent.com/35296671/56503976-012aae80-650f-11e9-82c8-dd7d026b6eb1.png)
 
 NB : 
@@ -150,3 +150,40 @@ NB :
 * For switch and checkbox inputs type, you have to set the default value as a boolean property named "value".
 
 ### Settings for a document to sign step
+In the child object you've created, 2 attributes must be filled:
+1. subtype
+2. text
+3. buttonText
+4. checkbox (facultative)
+
+To set up the child object you've created with these elements :
+1. Edit you child object
+2. Go to "Object attributes"
+3. Add the attributes :
+  1. Add a new key "subtype" of type `<String>` with the value 'onb-adm-sign'
+  2. Add a new key "text" of type `<String>` with all the text of your document to sign as value
+  3. Add a new key "buttonText" of type `<String>` with the text you want to display in the submit button of your step
+  4. Add a new key "checkbox" of type `<Object>` if you want to force your user to click on a checkbox (ex: 'I have read and accepted the conditions') before validating his document. In the checkbox object, you should define :
+    * A "label" key of type `<String>`, with the text you want to associate to the checkbox
+    * A "required" key of type `<Boolean>`, set at true if you want to force the user to check it
+    * A "name" key of type `<String>`
+    * Then you can add all the properties you want to your checkbox.
+
+Here is an example of the structure a 'document to sign' step could have :
+
+```javascript
+const signStepExample = {
+  subtype: "onb-adm-sign",
+  text: "Lorem ipsum dolor sit amet, consectetur adipiscing elit. Praesent ornare non sem eu pretium. Integer porttitor risus eget nibh iaculis, ac lacinia orci dictum. Nunc ullamcorper consequat enim in posuere. Aliquam volutpat est odio, vel maximus arcu maximus sit amet. Donec ultricies faucibus magna id luctus. Duis et dapibus elit. In vestibulum ipsum erat, at commodo tortor convallis vel. Nunc ut ultrices nulla. Etiam lorem justo, consequat a consectetur a, porttitor non turpis. Mauris eu mollis nisl, id dignissim quam. Curabitur condimentum sollicitudin rutrum. Aenean blandit, arcu nec ullamcorper rhoncus, lectus sem lacinia lorem, venenatis dignissim velit mi et sapien. Nullam posuere augue ut magna ullamcorper dignissim. Ut rhoncus sapien vel nulla commodo finibus. Cras non leo vel urna finibus volutpat. Praesent et ex eget diam tincidunt suscipit. Phasellus bibendum neque vel placerat iaculis. Vestibulum bibendum ultrices ipsum, non sodales lectus. Cras eget orci eget elit blandit scelerisque at ut nulla. Integer ligula eros, eleifend quis sodales a, porttitor sit amet neque. Fusce mollis magna at lectus varius, quis suscipit mi cursus. Etiam id imperdiet metus, in malesuada quam. Aliquam facilisis nunc non sapien condimentum, quis iaculis nisl auctor. Nunc lorem sapien, interdum vel efficitur ac, dapibus a diam. Ut ante urna, sodales in bibendum vel, lacinia ut mauris. In vel placerat leo. In libero dui, tincidunt at sem id, faucibus sollicitudin elit.",
+  buttonText: "Sign chart",
+  checkbox: {
+    name:"acceptChart",
+    label:"I have read and accepted the Chart 01",
+    required:true
+  },
+}
+```
+
+This 'document to sign' step would look like this :
+![document to sign step example](https://user-images.githubusercontent.com/35296671/56504782-8f079900-6511-11e9-9a0e-bb638b6d7d03.png)
+

From 35e7547d961c90fd260cfc88b6ba32150adcc853 Mon Sep 17 00:00:00 2001
From: Louise Foussat <louisefoussat@gmail.com>
Date: Mon, 22 Apr 2019 15:36:52 +0100
Subject: [PATCH 05/21] no more <> around element in ``

---
 doc/create-steps.md | 32 ++++++++++++++++----------------
 1 file changed, 16 insertions(+), 16 deletions(-)

diff --git a/doc/create-steps.md b/doc/create-steps.md
index 86251af1..e7a0798c 100644
--- a/doc/create-steps.md
+++ b/doc/create-steps.md
@@ -34,18 +34,18 @@ To set up the child object you've created with these elements :
 1. Edit you child object
 2. Go to "Object attributes"
 3. Add the attributes :
-  1. Add a new key "subtype" of type `<String>` with the value 'onb-adm-form-generator'
-  2. Add a new key "form" of type `<Object>` 
+  1. Add a new key "subtype" of type `String` with the value 'onb-adm-form-generator'
+  2. Add a new key "form" of type `Object` 
     * The form you're creating can have several sections. Each section is displayed with a title, and its inputs. 
     NB : The submission of the form will check the required inputs of all the sections you've created. 
-    * To create a section, add a new key to your form object, of type `<Object>`, that contains :
-      1. A key "title" of type `<String>`. The value of this property will be the title displayed in the top of your form section. If you have only one section in your form step, and you don't need a section title, you don't have to set up this property.
-      2. An "inputs" key of type `<Object>`, which will contain all the inputs of the section. For each input you want to add, you must set up the input as this :
-        * Add a new `<Object>` element in the "inputs" object. The key of this object will be used as the "name" attribute of your input. The values will be considered as the props of your input.
+    * To create a section, add a new key to your form object, of type `Object`, that contains :
+      1. A key "title" of type `String`. The value of this property will be the title displayed in the top of your form section. If you have only one section in your form step, and you don't need a section title, you don't have to set up this property.
+      2. An "inputs" key of type `Object`, which will contain all the inputs of the section. For each input you want to add, you must set up the input as this :
+        * Add a new `Object` element in the "inputs" object. The key of this object will be used as the "name" attribute of your input. The values will be considered as the props of your input.
 
 Set up of an input props :
-* You must declare a "type" key of type `<String>`, wich define the type of your input : `<tel>`, `<text>`, `<date>`, `<select>`, `<radio>`, `<switch>`, `<checkbox>`, `<textarea>`. 
-* Then you can fill the props you need for your input, according to its type : `<placeholder>`, `<id>`, `<required>`, `<label>`, `<items>`, `<emptyItems>`, `<index>`, etc.
+* You must declare a "type" key of type `String`, wich define the type of your input : `tel`, `text`, `date`, `select`, `radio`, `switch`, `checkbox`, `textarea`. 
+* Then you can fill the props you need for your input, according to its type : `placeholder`, `id`, `required`, `label`, `items`, `emptyItems`, `index`, etc.
 
 Here are examples of the structure the form attribute could have, with two sections and an example of set up for every kind of input type :
 
@@ -153,20 +153,20 @@ NB :
 In the child object you've created, 2 attributes must be filled:
 1. subtype
 2. text
-3. buttonText
+3. buttonText (facultative)
 4. checkbox (facultative)
 
 To set up the child object you've created with these elements :
 1. Edit you child object
 2. Go to "Object attributes"
 3. Add the attributes :
-  1. Add a new key "subtype" of type `<String>` with the value 'onb-adm-sign'
-  2. Add a new key "text" of type `<String>` with all the text of your document to sign as value
-  3. Add a new key "buttonText" of type `<String>` with the text you want to display in the submit button of your step
-  4. Add a new key "checkbox" of type `<Object>` if you want to force your user to click on a checkbox (ex: 'I have read and accepted the conditions') before validating his document. In the checkbox object, you should define :
-    * A "label" key of type `<String>`, with the text you want to associate to the checkbox
-    * A "required" key of type `<Boolean>`, set at true if you want to force the user to check it
-    * A "name" key of type `<String>`
+  1. Add a new key "subtype" of type `String` with the value 'onb-adm-sign'
+  2. Add a new key "text" of type `String` with all the text of your document to sign as value
+  3. Add a new key "buttonText" of type `String` with the text you want to display in the submit button of your step
+  4. Add a new key "checkbox" of type `Object` if you want to force your user to click on a checkbox (ex: 'I have read and accepted the conditions') before validating his document. In the checkbox object, you should define :
+    * A "label" key of type `String`, with the text you want to associate to the checkbox
+    * A "required" key of type `Boolean`, set at true if you want to force the user to check it
+    * A "name" key of type `String`
     * Then you can add all the properties you want to your checkbox.
 
 Here is an example of the structure a 'document to sign' step could have :

From f094fdacefd473a549e444383d017533d1e1d61f Mon Sep 17 00:00:00 2001
From: lfoussat <35296671+lfoussat@users.noreply.github.com>
Date: Mon, 22 Apr 2019 15:45:47 +0100
Subject: [PATCH 06/21] enhance display of markdown

---
 doc/create-steps.md | 70 ++++++++++++++++++++++-----------------------
 1 file changed, 35 insertions(+), 35 deletions(-)

diff --git a/doc/create-steps.md b/doc/create-steps.md
index e7a0798c..cab174be 100644
--- a/doc/create-steps.md
+++ b/doc/create-steps.md
@@ -1,7 +1,7 @@
 # How to create onboarding steps
 
 ## Usage
-This documentation explains how to create steps in your onboarding. 2 kind of steps can be generated in a modular way :
+This documentation explains how to create steps in your onboarding. 2 kind of steps can be generated in a modular way:
 * forms
 * documents to sign
 
@@ -13,41 +13,41 @@ The objects contained in the sign up phase are object of type "sign up".
 The objects contained in the administration part of the onboarding phase are object of type "onboarding".
 
 ### Relate a step to a major object
-Every step is related to the major object you want to costum as a child. To create a child, you must :
+Every step is related to the major object you want to costum as a child. To create a child, you must:
 1. Create a new object for your step in the admin (in Admin > "Add new object")
-  * The title of your object will be the title displayed for the step you're creating. Use a intellegible title for your user.
-  * This object must have the same type as your major object ("signup" for the sign up phase, "onboarding" for the administration part of the onboarding)
+   * The title of your object will be the title displayed for the step you're creating. Use a intellegible title for your user.
+   * This object must have the same type as your major object ("signup" for the sign up phase, "onboarding" for the administration part of the onboarding)
 2. Add this new object as a child of your major object
   1. Edit the major object
   2. Go to "Children" > "Add a child"
   3. Set up the new child:
-    * Enter its name in the input "Add a child name"
-    * Select you child in the select input
-    * Click on "ADD"
+     * Enter its name in the input "Add a child name"
+     * Select you child in the select input
+     * Click on "ADD"
 
 ### Settings for a form step
 In the child object you've created, 2 attributes must be filled:
 1. subtype
 2. form
 
-To set up the child object you've created with these elements :
+To set up the child object you've created with these elements:
 1. Edit you child object
 2. Go to "Object attributes"
-3. Add the attributes :
-  1. Add a new key "subtype" of type `String` with the value 'onb-adm-form-generator'
-  2. Add a new key "form" of type `Object` 
-    * The form you're creating can have several sections. Each section is displayed with a title, and its inputs. 
-    NB : The submission of the form will check the required inputs of all the sections you've created. 
-    * To create a section, add a new key to your form object, of type `Object`, that contains :
-      1. A key "title" of type `String`. The value of this property will be the title displayed in the top of your form section. If you have only one section in your form step, and you don't need a section title, you don't have to set up this property.
-      2. An "inputs" key of type `Object`, which will contain all the inputs of the section. For each input you want to add, you must set up the input as this :
-        * Add a new `Object` element in the "inputs" object. The key of this object will be used as the "name" attribute of your input. The values will be considered as the props of your input.
-
-Set up of an input props :
+3. Add the attributes:
+   * Add a new key "subtype" of type `String` with the value 'onb-adm-form-generator'
+   * Add a new key "form" of type `Object` 
+     * The form you're creating can have several sections. Each section is displayed with a title, and its inputs. 
+       * The submission of the form will check the required inputs of all the sections you've created. 
+     * To create a section, add a new key to your form object, of type `Object`, that contains :
+       * A key "title" of type `String`. The value of this property will be the title displayed in the top of your form section. If you have only one section in your form step, and you don't need a section title, you don't have to set up this property.
+       * An "inputs" key of type `Object`, which will contain all the inputs of the section. For each input you want to add, you must set up the input as this :
+         * Add a new `Object` element in the "inputs" object. The key of this object will be used as the "name" attribute of your input. The values will be considered as the props of your input.
+
+Set up of an input props:
 * You must declare a "type" key of type `String`, wich define the type of your input : `tel`, `text`, `date`, `select`, `radio`, `switch`, `checkbox`, `textarea`. 
 * Then you can fill the props you need for your input, according to its type : `placeholder`, `id`, `required`, `label`, `items`, `emptyItems`, `index`, etc.
 
-Here are examples of the structure the form attribute could have, with two sections and an example of set up for every kind of input type :
+Here are examples of the structure the form attribute could have, with two sections and an example of set up for every kind of input type:
 
 ```javascript
 const formStepAttributes = {
@@ -134,10 +134,10 @@ const formStepAttributes = {
 }
 ```
 
-This form step would look like this :
+This form step would look like this:
 ![form step example](https://user-images.githubusercontent.com/35296671/56503976-012aae80-650f-11e9-82c8-dd7d026b6eb1.png)
 
-NB : 
+NB: 
 * The index property is used to order your inputs. It won't be spread in the input.
 * The type property is resquired. It will be used to determine the kind of input we must generate. It is spread in the input only if the input type attribute is required (type 'tel' or 'text' for example, but not for type 'select' - in this case, we will generate a select element)
 * Each input type has its own attributes. You can check how to set up your inputs hey : 
@@ -156,20 +156,20 @@ In the child object you've created, 2 attributes must be filled:
 3. buttonText (facultative)
 4. checkbox (facultative)
 
-To set up the child object you've created with these elements :
+To set up the child object you've created with these elements:
 1. Edit you child object
 2. Go to "Object attributes"
-3. Add the attributes :
-  1. Add a new key "subtype" of type `String` with the value 'onb-adm-sign'
-  2. Add a new key "text" of type `String` with all the text of your document to sign as value
-  3. Add a new key "buttonText" of type `String` with the text you want to display in the submit button of your step
-  4. Add a new key "checkbox" of type `Object` if you want to force your user to click on a checkbox (ex: 'I have read and accepted the conditions') before validating his document. In the checkbox object, you should define :
-    * A "label" key of type `String`, with the text you want to associate to the checkbox
-    * A "required" key of type `Boolean`, set at true if you want to force the user to check it
-    * A "name" key of type `String`
-    * Then you can add all the properties you want to your checkbox.
-
-Here is an example of the structure a 'document to sign' step could have :
+3. Add the attributes:
+   * Add a new key "subtype" of type `String` with the value 'onb-adm-sign'
+   * Add a new key "text" of type `String` with all the text of your document to sign as value
+   * Add a new key "buttonText" of type `String` with the text you want to display in the submit button of your step
+   * Add a new key "checkbox" of type `Object` if you want to force your user to click on a checkbox (ex: 'I have read and accepted the conditions') before validating his document. In the checkbox object, you should define:
+     * A "label" key of type `String`, with the text you want to associate to the checkbox
+     * A "required" key of type `Boolean`, set at true if you want to force the user to check it
+     * A "name" key of type `String`
+     * Then you can add all the properties you want to your checkbox.
+
+Here is an example of the structure a 'document to sign' step could have:
 
 ```javascript
 const signStepExample = {
@@ -184,6 +184,6 @@ const signStepExample = {
 }
 ```
 
-This 'document to sign' step would look like this :
+This 'document to sign' step would look like this:
 ![document to sign step example](https://user-images.githubusercontent.com/35296671/56504782-8f079900-6511-11e9-9a0e-bb638b6d7d03.png)
 

From 4ebd777d2b662f777eb6417c8ab51ea92c8f1feb Mon Sep 17 00:00:00 2001
From: Louise Foussat <louisefoussat@gmail.com>
Date: Mon, 22 Apr 2019 15:52:02 +0100
Subject: [PATCH 07/21] add attributes key in bold

---
 doc/create-steps.md | 22 +++++++++++-----------
 1 file changed, 11 insertions(+), 11 deletions(-)

diff --git a/doc/create-steps.md b/doc/create-steps.md
index cab174be..7ca101c8 100644
--- a/doc/create-steps.md
+++ b/doc/create-steps.md
@@ -34,13 +34,13 @@ To set up the child object you've created with these elements:
 1. Edit you child object
 2. Go to "Object attributes"
 3. Add the attributes:
-   * Add a new key "subtype" of type `String` with the value 'onb-adm-form-generator'
-   * Add a new key "form" of type `Object` 
+   * Add a new key **"subtype"** of type `String` with the value 'onb-adm-form-generator'
+   * Add a new key **"form"** of type `Object` 
      * The form you're creating can have several sections. Each section is displayed with a title, and its inputs. 
        * The submission of the form will check the required inputs of all the sections you've created. 
      * To create a section, add a new key to your form object, of type `Object`, that contains :
-       * A key "title" of type `String`. The value of this property will be the title displayed in the top of your form section. If you have only one section in your form step, and you don't need a section title, you don't have to set up this property.
-       * An "inputs" key of type `Object`, which will contain all the inputs of the section. For each input you want to add, you must set up the input as this :
+       * A **"title"** key of type `String`. The value of this property will be the title displayed in the top of your form section. If you have only one section in your form step, and you don't need a section title, you don't have to set up this property.
+       * An **"inputs"** key of type `Object`, which will contain all the inputs of the section. For each input you want to add, you must set up the input as this :
          * Add a new `Object` element in the "inputs" object. The key of this object will be used as the "name" attribute of your input. The values will be considered as the props of your input.
 
 Set up of an input props:
@@ -160,13 +160,13 @@ To set up the child object you've created with these elements:
 1. Edit you child object
 2. Go to "Object attributes"
 3. Add the attributes:
-   * Add a new key "subtype" of type `String` with the value 'onb-adm-sign'
-   * Add a new key "text" of type `String` with all the text of your document to sign as value
-   * Add a new key "buttonText" of type `String` with the text you want to display in the submit button of your step
-   * Add a new key "checkbox" of type `Object` if you want to force your user to click on a checkbox (ex: 'I have read and accepted the conditions') before validating his document. In the checkbox object, you should define:
-     * A "label" key of type `String`, with the text you want to associate to the checkbox
-     * A "required" key of type `Boolean`, set at true if you want to force the user to check it
-     * A "name" key of type `String`
+   * Add a new key **"subtype"** of type `String` with the value 'onb-adm-sign'
+   * Add a new key **"text"** of type `String` with all the text of your document to sign as value
+   * Add a new key **"buttonText"** of type `String` with the text you want to display in the submit button of your step
+   * Add a new key **"checkbox"** of type `Object` if you want to force your user to click on a checkbox (ex: 'I have read and accepted the conditions') before validating his document. In the checkbox object, you should define:
+     * A **"label"** key of type `String`, with the text you want to associate to the checkbox
+     * A **"required"** key of type `Boolean`, set at true if you want to force the user to check it
+     * A **"name"** key of type `String`
      * Then you can add all the properties you want to your checkbox.
 
 Here is an example of the structure a 'document to sign' step could have:

From c86d6fb434e654e750ad328d057e68c25411e0fa Mon Sep 17 00:00:00 2001
From: lfoussat <35296671+lfoussat@users.noreply.github.com>
Date: Mon, 22 Apr 2019 15:54:52 +0100
Subject: [PATCH 08/21] Update create-steps.md

---
 doc/create-steps.md | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/doc/create-steps.md b/doc/create-steps.md
index 7ca101c8..d898ac81 100644
--- a/doc/create-steps.md
+++ b/doc/create-steps.md
@@ -26,9 +26,9 @@ Every step is related to the major object you want to costum as a child. To crea
      * Click on "ADD"
 
 ### Settings for a form step
-In the child object you've created, 2 attributes must be filled:
-1. subtype
-2. form
+> In the child object you've created, 2 attributes must be filled:
+> 1. subtype
+> 2. form
 
 To set up the child object you've created with these elements:
 1. Edit you child object
@@ -150,11 +150,11 @@ NB:
 * For switch and checkbox inputs type, you have to set the default value as a boolean property named "value".
 
 ### Settings for a document to sign step
-In the child object you've created, 2 attributes must be filled:
-1. subtype
-2. text
-3. buttonText (facultative)
-4. checkbox (facultative)
+> In the child object you've created, 2 attributes must be filled:
+> 1. subtype
+> 2. text
+> 3. buttonText (facultative)
+> 4. checkbox (facultative)
 
 To set up the child object you've created with these elements:
 1. Edit you child object

From f04cb0d1f19eff0812ae39737a62d4208ade2532 Mon Sep 17 00:00:00 2001
From: lfoussat <35296671+lfoussat@users.noreply.github.com>
Date: Mon, 22 Apr 2019 16:12:16 +0100
Subject: [PATCH 09/21] add capture of admin to illustrate documentation

---
 doc/create-steps.md | 17 +++++++++++------
 1 file changed, 11 insertions(+), 6 deletions(-)

diff --git a/doc/create-steps.md b/doc/create-steps.md
index d898ac81..b3d4abb3 100644
--- a/doc/create-steps.md
+++ b/doc/create-steps.md
@@ -15,15 +15,19 @@ The objects contained in the administration part of the onboarding phase are obj
 ### Relate a step to a major object
 Every step is related to the major object you want to costum as a child. To create a child, you must:
 1. Create a new object for your step in the admin (in Admin > "Add new object")
+   <img width="664" alt="Capture d’écran 2019-04-22 à 15 57 37" src="https://user-images.githubusercontent.com/35296671/56507169-6505a500-6518-11e9-89bb-04c7fd9b41ca.png">
+   <img width="450" alt="Capture d’écran 2019-04-22 à 15 58 21" src="https://user-images.githubusercontent.com/35296671/56507180-6afb8600-6518-11e9-97a5-4dcff8f0a069.png">
    * The title of your object will be the title displayed for the step you're creating. Use a intellegible title for your user.
    * This object must have the same type as your major object ("signup" for the sign up phase, "onboarding" for the administration part of the onboarding)
+   
 2. Add this new object as a child of your major object
-  1. Edit the major object
-  2. Go to "Children" > "Add a child"
-  3. Set up the new child:
-     * Enter its name in the input "Add a child name"
-     * Select you child in the select input
-     * Click on "ADD"
+   1. Edit the major object
+   2. Go to "Children" > "Add a child"
+      ![add child to major object](https://user-images.githubusercontent.com/35296671/56506977-de50c800-6517-11e9-9c71-d19a1ec4e5cd.png)
+   3. Set up the new child:
+      * Enter its name in the input "Add a child name"
+      * Select you child in the select input
+      * Click on "ADD"
 
 ### Settings for a form step
 > In the child object you've created, 2 attributes must be filled:
@@ -33,6 +37,7 @@ Every step is related to the major object you want to costum as a child. To crea
 To set up the child object you've created with these elements:
 1. Edit you child object
 2. Go to "Object attributes"
+   <img width="1073" alt="Capture d’écran 2019-04-22 à 15 59 33" src="https://user-images.githubusercontent.com/35296671/56507445-3936ef00-6519-11e9-90c8-d85056e9330b.png">
 3. Add the attributes:
    * Add a new key **"subtype"** of type `String` with the value 'onb-adm-form-generator'
    * Add a new key **"form"** of type `Object` 

From d721f0fb55efab73af3165b0f3464fcc1c9bd615 Mon Sep 17 00:00:00 2001
From: lfoussat <35296671+lfoussat@users.noreply.github.com>
Date: Mon, 22 Apr 2019 16:29:06 +0100
Subject: [PATCH 10/21] rm "" for keys, add italic style for paths

---
 doc/create-steps.md | 51 +++++++++++++++++++++++----------------------
 1 file changed, 26 insertions(+), 25 deletions(-)

diff --git a/doc/create-steps.md b/doc/create-steps.md
index b3d4abb3..78f3dc19 100644
--- a/doc/create-steps.md
+++ b/doc/create-steps.md
@@ -1,20 +1,20 @@
 # How to create onboarding steps
 
 ## Usage
-This documentation explains how to create steps in your onboarding. 2 kind of steps can be generated in a modular way:
-* forms
-* documents to sign
+> This documentation explains how to create steps in your onboarding. 2 kind of steps can be generated in a modular way:
+> * forms
+> * documents to sign
 
-These steps are used for the "sign up" phase, and for the administrative part of the onboarding.
+These steps are used for the "sign up" phase, and for the "administrative" part of the onboarding.
 
 ## Description & examples
 The sign up phase and the administration part of the onboarding are related to major objects in the admin. all the steps for each of these two sections are children of these two big objects, that you can create, update, or delete, and order as you wish. 
-The objects contained in the sign up phase are object of type "sign up".
-The objects contained in the administration part of the onboarding phase are object of type "onboarding".
+* The objects contained in the sign up phase are object of type **sign up**.
+* The objects contained in the administration part of the onboarding phase are object of type **onboarding**.
 
 ### Relate a step to a major object
 Every step is related to the major object you want to costum as a child. To create a child, you must:
-1. Create a new object for your step in the admin (in Admin > "Add new object")
+1. Create a new object for your step in the admin (in *Admin* > *Add new object*)
    <img width="664" alt="Capture d’écran 2019-04-22 à 15 57 37" src="https://user-images.githubusercontent.com/35296671/56507169-6505a500-6518-11e9-89bb-04c7fd9b41ca.png">
    <img width="450" alt="Capture d’écran 2019-04-22 à 15 58 21" src="https://user-images.githubusercontent.com/35296671/56507180-6afb8600-6518-11e9-97a5-4dcff8f0a069.png">
    * The title of your object will be the title displayed for the step you're creating. Use a intellegible title for your user.
@@ -22,7 +22,7 @@ Every step is related to the major object you want to costum as a child. To crea
    
 2. Add this new object as a child of your major object
    1. Edit the major object
-   2. Go to "Children" > "Add a child"
+   2. Go to *Children* > *Add a child*
       ![add child to major object](https://user-images.githubusercontent.com/35296671/56506977-de50c800-6517-11e9-9c71-d19a1ec4e5cd.png)
    3. Set up the new child:
       * Enter its name in the input "Add a child name"
@@ -36,20 +36,20 @@ Every step is related to the major object you want to costum as a child. To crea
 
 To set up the child object you've created with these elements:
 1. Edit you child object
-2. Go to "Object attributes"
+2. Go to *Object attributes*
    <img width="1073" alt="Capture d’écran 2019-04-22 à 15 59 33" src="https://user-images.githubusercontent.com/35296671/56507445-3936ef00-6519-11e9-90c8-d85056e9330b.png">
 3. Add the attributes:
-   * Add a new key **"subtype"** of type `String` with the value 'onb-adm-form-generator'
-   * Add a new key **"form"** of type `Object` 
+   * Add a new key **subtype** of type `String` with the value 'onb-adm-form-generator'
+   * Add a new key **form** of type `Object` 
      * The form you're creating can have several sections. Each section is displayed with a title, and its inputs. 
        * The submission of the form will check the required inputs of all the sections you've created. 
      * To create a section, add a new key to your form object, of type `Object`, that contains :
-       * A **"title"** key of type `String`. The value of this property will be the title displayed in the top of your form section. If you have only one section in your form step, and you don't need a section title, you don't have to set up this property.
-       * An **"inputs"** key of type `Object`, which will contain all the inputs of the section. For each input you want to add, you must set up the input as this :
+       * A **title** key of type `String`. The value of this property will be the title displayed in the top of your form section. If you have only one section in your form step, and you don't need a section title, you don't have to set up this property.
+       * An **inputs** key of type `Object`, which will contain all the inputs of the section. For each input you want to add, you must set up the input as this :
          * Add a new `Object` element in the "inputs" object. The key of this object will be used as the "name" attribute of your input. The values will be considered as the props of your input.
 
 Set up of an input props:
-* You must declare a "type" key of type `String`, wich define the type of your input : `tel`, `text`, `date`, `select`, `radio`, `switch`, `checkbox`, `textarea`. 
+* You must declare a **type** key of type `String`, wich define the type of your input : `tel`, `text`, `date`, `select`, `radio`, `switch`, `checkbox`, `textarea`. 
 * Then you can fill the props you need for your input, according to its type : `placeholder`, `id`, `required`, `label`, `items`, `emptyItems`, `index`, etc.
 
 Here are examples of the structure the form attribute could have, with two sections and an example of set up for every kind of input type:
@@ -143,8 +143,9 @@ This form step would look like this:
 ![form step example](https://user-images.githubusercontent.com/35296671/56503976-012aae80-650f-11e9-82c8-dd7d026b6eb1.png)
 
 NB: 
-* The index property is used to order your inputs. It won't be spread in the input.
-* The type property is resquired. It will be used to determine the kind of input we must generate. It is spread in the input only if the input type attribute is required (type 'tel' or 'text' for example, but not for type 'select' - in this case, we will generate a select element)
+* The **index** property is used to order your inputs. It won't be spread in the input.
+* The **type** property is resquired. It will be used to determine the kind of input we must generate. It is spread in the input only if the input type attribute is required (type 'tel' or 'text' for example, but not for type 'select' - in this case, we will generate a select element)
+* Don't declare an **onChange**, it's handled by the app
 * Each input type has its own attributes. You can check how to set up your inputs hey : 
   * [textInput documentation](https://alem.01-edu.org/design/Components/FormInputs/TextInput) - used for inputs type 'text', 'tel', and 'date'
   * [textArea documentation](https://alem.01-edu.org/design/Components/FormInputs/TextArea)
@@ -152,7 +153,7 @@ NB:
   * [radio button documentation](https://alem.01-edu.org/design/Components/FormControls/Radio)
   * [switch documentation](https://alem.01-edu.org/design/Components/FormControls/Switch)
   * [checkbox documentation](https://alem.01-edu.org/design/Components/FormControls/Checkbox)
-* For switch and checkbox inputs type, you have to set the default value as a boolean property named "value".
+* For switch and checkbox inputs type, you have to set the default value as a boolean property named **value**.
 
 ### Settings for a document to sign step
 > In the child object you've created, 2 attributes must be filled:
@@ -163,15 +164,15 @@ NB:
 
 To set up the child object you've created with these elements:
 1. Edit you child object
-2. Go to "Object attributes"
+2. Go to *Object attributes*
 3. Add the attributes:
-   * Add a new key **"subtype"** of type `String` with the value 'onb-adm-sign'
-   * Add a new key **"text"** of type `String` with all the text of your document to sign as value
-   * Add a new key **"buttonText"** of type `String` with the text you want to display in the submit button of your step
-   * Add a new key **"checkbox"** of type `Object` if you want to force your user to click on a checkbox (ex: 'I have read and accepted the conditions') before validating his document. In the checkbox object, you should define:
-     * A **"label"** key of type `String`, with the text you want to associate to the checkbox
-     * A **"required"** key of type `Boolean`, set at true if you want to force the user to check it
-     * A **"name"** key of type `String`
+   * Add a new key **subtype** of type `String` with the value 'onb-adm-sign'
+   * Add a new key **text** of type `String` with all the text of your document to sign as value
+   * Add a new key **buttonText** of type `String` with the text you want to display in the submit button of your step
+   * Add a new key **checkbox** of type `Object` if you want to force your user to click on a checkbox (ex: 'I have read and accepted the conditions') before validating his document. In the checkbox object, you should define:
+     * A **label** key of type `String`, with the text you want to associate to the checkbox
+     * A **required** key of type `Boolean`, set at true if you want to force the user to check it
+     * A **name** key of type `String`
      * Then you can add all the properties you want to your checkbox.
 
 Here is an example of the structure a 'document to sign' step could have:

From 6745dabfd93a9ced8cbda81492bb529fa39d00f0 Mon Sep 17 00:00:00 2001
From: Louise Foussat <louisefoussat@gmail.com>
Date: Mon, 22 Apr 2019 20:30:26 +0100
Subject: [PATCH 11/21] enhance steps management doc - reorganise paragraphs,
 rewrite some ununderstandable texts

---
 doc/create-steps.md | 266 ++++++++++++++++++++++++--------------------
 1 file changed, 147 insertions(+), 119 deletions(-)

diff --git a/doc/create-steps.md b/doc/create-steps.md
index 78f3dc19..6a31be57 100644
--- a/doc/create-steps.md
+++ b/doc/create-steps.md
@@ -1,27 +1,39 @@
-# How to create onboarding steps
+# Sign up & onboarding's Administration section - Modular steps management
 
 ## Usage
-> This documentation explains how to create steps in your onboarding. 2 kind of steps can be generated in a modular way:
-> * forms
-> * documents to sign
+> After their first authentication in the app, every candidate has to effectuate his **sign up** and his **onboarding**. The steps that compose the **sign up** and the **administration** section of the onboarding are: 
+> * Of two kinds: 
+>   * forms (identification, medical information, etc.)
+>   * documents to sign (general conditions, charts, regulations, etc.)
+> * Modular: you can add, update, delete and order it as you wish. 
 
-These steps are used for the "sign up" phase, and for the "administrative" part of the onboarding.
+> This documentation explains how to manage these steps. 
 
-## Description & examples
-The sign up phase and the administration part of the onboarding are related to major objects in the admin. all the steps for each of these two sections are children of these two big objects, that you can create, update, or delete, and order as you wish. 
-* The objects contained in the sign up phase are object of type **sign up**.
-* The objects contained in the administration part of the onboarding phase are object of type **onboarding**.
+## Create a step
 
-### Relate a step to a major object
-Every step is related to the major object you want to costum as a child. To create a child, you must:
+Every step that you want to create must :
+* Be related as a child to the correct parent object in the *Admin*
+  * Steps related to the Sign up -> *Admin* > *Objects* > *SignUp* > ***Sign Up*** 
+  * Steps related to the onboarding's Administration section -> *Admin* > *Objects* > *Onboarding* > ***Administration*** 
+* Be defined with the correct object **type**
+  * Steps related to the Sign up -> type **sign up**
+  * Steps related to the onboarding's Administration section -> type **onboarding**
+
+---
+
+To create a step, you must:
 1. Create a new object for your step in the admin (in *Admin* > *Add new object*)
    <img width="664" alt="Capture d’écran 2019-04-22 à 15 57 37" src="https://user-images.githubusercontent.com/35296671/56507169-6505a500-6518-11e9-89bb-04c7fd9b41ca.png">
    <img width="450" alt="Capture d’écran 2019-04-22 à 15 58 21" src="https://user-images.githubusercontent.com/35296671/56507180-6afb8600-6518-11e9-97a5-4dcff8f0a069.png">
    * The title of your object will be the title displayed for the step you're creating. Use a intellegible title for your user.
    * This object must have the same type as your major object ("signup" for the sign up phase, "onboarding" for the administration part of the onboarding)
+
+> Your step is then available in the *Admin*. You can find it in the section of its type (*SignUp* or *Onboarding*) or thanks to the search bar of the cursus object's page.
    
-2. Add this new object as a child of your major object
-   1. Edit the major object
+2. Add this new object as a child of your parent object
+   1. Edit the parent object (*Sign up* or *Administration*)
+      <img width="640" alt="Capture d’écran 2019-04-22 à 19 24 23" src="https://user-images.githubusercontent.com/35296671/56517407-cb98bc00-6534-11e9-98d6-a2b1c0193a38.png">
+      <img width="640" alt="Capture d’écran 2019-04-22 à 19 24 10" src="https://user-images.githubusercontent.com/35296671/56517421-d0f60680-6534-11e9-86ef-97fb9e59786e.png">
    2. Go to *Children* > *Add a child*
       ![add child to major object](https://user-images.githubusercontent.com/35296671/56506977-de50c800-6517-11e9-9c71-d19a1ec4e5cd.png)
    3. Set up the new child:
@@ -29,17 +41,23 @@ Every step is related to the major object you want to costum as a child. To crea
       * Select you child in the select input
       * Click on "ADD"
 
-### Settings for a form step
-> In the child object you've created, 2 attributes must be filled:
+> Your step is then related to its parent. You can see it in the *Children* section of the parent object. There, you can now : 
+> * Delete the step as a child of its parent (the actual object of your step won't be deleted)
+> * Reorder it in the children's list, by dragging it to the place you cant
+> * Go to update its settings by clicking on the eye of its reference (it will redirect you to the actual object of your step).
+<img width="1229" alt="Capture d’écran 2019-04-22 à 19 51 12" src="https://user-images.githubusercontent.com/35296671/56518936-a1e19400-6538-11e9-81c7-520ffd365cff.png">
+
+## Settings for a form step
+> In the step object you've created, 2 attributes must be filled:
 > 1. subtype
 > 2. form
 
-To set up the child object you've created with these elements:
-1. Edit you child object
-2. Go to *Object attributes*
+### Description
+###### Edit the step object you've created :
+1. Go to *Object attributes*
    <img width="1073" alt="Capture d’écran 2019-04-22 à 15 59 33" src="https://user-images.githubusercontent.com/35296671/56507445-3936ef00-6519-11e9-90c8-d85056e9330b.png">
-3. Add the attributes:
-   * Add a new key **subtype** of type `String` with the value 'onb-adm-form-generator'
+2. Add the attributes:
+   * Add a new key **subtype** of type `String` with the exact value 'onb-adm-form-generator'
    * Add a new key **form** of type `Object` 
      * The form you're creating can have several sections. Each section is displayed with a title, and its inputs. 
        * The submission of the form will check the required inputs of all the sections you've created. 
@@ -48,90 +66,107 @@ To set up the child object you've created with these elements:
        * An **inputs** key of type `Object`, which will contain all the inputs of the section. For each input you want to add, you must set up the input as this :
          * Add a new `Object` element in the "inputs" object. The key of this object will be used as the "name" attribute of your input. The values will be considered as the props of your input.
 
-Set up of an input props:
+###### Set up of an input props:
 * You must declare a **type** key of type `String`, wich define the type of your input : `tel`, `text`, `date`, `select`, `radio`, `switch`, `checkbox`, `textarea`. 
 * Then you can fill the props you need for your input, according to its type : `placeholder`, `id`, `required`, `label`, `items`, `emptyItems`, `index`, etc.
 
-Here are examples of the structure the form attribute could have, with two sections and an example of set up for every kind of input type:
-
-```javascript
-const formStepAttributes = {
-  subtype: "onb-adm-form",
-  form: {
-    section1: {
-      title: "My section title",
-      inputs: {
-        firstName: {
-          index: 0,
-          placeholder: 'First name',
-          type: 'text',
-          required: true,
-        },
-        tel: {
-          index: 1,
-          required: true,
-          type: 'tel',
-          label: 'Phone number',
-          placeholder: '+333 33 33 33 33',
-          pattern: '[+][3][0-9]{2}[0-9]{2}[0-9]{2}[0-9]{2}[0-9]{2}',
+###### Important indication: 
+* The **index** property is used to order your inputs. It won't be spread in the input.
+* The **type** property is resquired. It will be used to determine the kind of input we must generate. It is spread in the input only if the input type attribute is required (type 'tel' or 'text' for example, but not for type 'select' - in this case, we will generate a select element)
+  * We're creating a special type 'countries' (select displaying all the countries). Documentation will be updated as soon as it's available.
+* Don't declare an **onChange**, it's handled by the app
+* Each input type has its own attributes. You can check how to set up your inputs hey : 
+  * [textInput documentation](https://alem.01-edu.org/design/Components/FormInputs/TextInput) - used for inputs type 'text', 'tel', and 'date'
+  * [textArea documentation](https://alem.01-edu.org/design/Components/FormInputs/TextArea)
+  * [select documentation](https://alem.01-edu.org/design/Components/FormControls/Select)
+  * [radio button documentation](https://alem.01-edu.org/design/Components/FormControls/Radio)
+  * [switch documentation](https://alem.01-edu.org/design/Components/FormControls/Switch)
+  * [checkbox documentation](https://alem.01-edu.org/design/Components/FormControls/Checkbox)
+* For switch and checkbox inputs type, you have to set the default value as a boolean property named **value**.
+
+### Examples
+
+Here is an example of the form step's attributes. It presents a form with two sections, and an example of each kind of input type. 
+NB : this example object will soon be provided in the admin.
+
+```json
+{
+  "subtype": "onb-adm-form",
+  "form": {
+    "section1": {
+      "title": "My section title",
+      "inputs": {
+        "firstName": {
+          "index": 0,
+          "placeholder": "First name",
+          "type": "text",
+          "required": true
         },
-        medicalInfo: {
-          label: 'Medical informations',
-          index: 6,
-          placeholder: 'Medical Informations',
-          type: 'textarea',
+        "tel": {
+          "index": 1,
+          "required": true,
+          "type": "tel",
+          "label": "Phone number",
+          "placeholder": "+333 33 33 33 33",
+          "pattern": "[+][3][0-9]{2}[0-9]{2}[0-9]{2}[0-9]{2}[0-9]{2}"
         },
-        dateOfBirth: {
-          index: 2,
-          required: true,
-          type: 'date',
-          label: 'Date of birth',
-          value: '2000-01-01',
+        "medicalInfo": {
+          "label": "Medical informations",
+          "index": 6,
+          "placeholder": "Medical Informations",
+          "type": "textarea"
         },
-        gender: {
-          index: 3,
-          type: 'select',
-          id: 'genders',
-          required: true,
-          emptyItem: { label: 'Select your gender' },
-          items: [
-            { label: 'Male', data: 'male' },
-            { label: 'Female', data: 'female' },
-          ],
+        "dateOfBirth": {
+          "index": 2,
+          "required": true,
+          "type": "date",
+          "label": "Date of birth",
+          "value": "2000-01-01"
         },
-        environment: {
-          index: 4,
-          type: 'radio',
-          required: true,
-          label: 'Which environment do you live in ?',
-          inlineBlock: true,
-          items: [
-            { label: 'City', data: 'city' },
-            { label: 'Countryside', data: 'countryside' },
-          ],
+        "gender": {
+          "index": 3,
+          "type": "select",
+          "id": "genders",
+          "required": true,
+          "emptyItem": { "label": "Select your gender" },
+          "items": [
+            { "label": "Male", "data": "male" },
+            { "label": "Female", "data": "female" }
+          ]
         },
-        programmingAbilities: {
-          index: 5,
-          type: 'switch',
-          label: 'I am new in programming',
-          value: true,
+        "environment": {
+          "index": 4,
+          "type": "radio",
+          "required": true,
+          "label": "Which environment do you live in ?",
+          "inlineBlock": true,
+          "items": [
+            { "label": "City", "data": "city" },
+            { "label": "Countryside", "data": "countryside" }
+          ]
         },
-        generalContions: {
-          index: 7,
-          type: 'checkbox',
-          label: 'I have read and I accept the general conditions',
-          value: false,
+        "programmingAbilities": {
+          "index": 5,
+          "type": "switch",
+          "label": "I am new in programming",
+          "value": true
         },
-      },
+        "generalContions": {
+          "index": 7,
+          "type": "checkbox",
+          "label": "I have read and I accept the general conditions",
+          "value": false
+        }
+      }
     },
-    section2: {
-      title: "My second section title",
-      inputs: {
-        firstName: {
-          index: 0,
-          placeholder: 'First name',
-          type: 'text',
-          required: true,
+    "section2": {
+      "title": "My second section title",
+      "inputs": {
+        "firstName": {
+          "index": 0,
+          "placeholder": "First name",
+          "type": "text",
+          "required": true
         }
       }
     }
@@ -139,30 +174,20 @@ const formStepAttributes = {
 }
 ```
 
-This form step would look like this:
-![form step example](https://user-images.githubusercontent.com/35296671/56503976-012aae80-650f-11e9-82c8-dd7d026b6eb1.png)
+This 'form' step would look like this:
 
-NB: 
-* The **index** property is used to order your inputs. It won't be spread in the input.
-* The **type** property is resquired. It will be used to determine the kind of input we must generate. It is spread in the input only if the input type attribute is required (type 'tel' or 'text' for example, but not for type 'select' - in this case, we will generate a select element)
-* Don't declare an **onChange**, it's handled by the app
-* Each input type has its own attributes. You can check how to set up your inputs hey : 
-  * [textInput documentation](https://alem.01-edu.org/design/Components/FormInputs/TextInput) - used for inputs type 'text', 'tel', and 'date'
-  * [textArea documentation](https://alem.01-edu.org/design/Components/FormInputs/TextArea)
-  * [select documentation](https://alem.01-edu.org/design/Components/FormControls/Select)
-  * [radio button documentation](https://alem.01-edu.org/design/Components/FormControls/Radio)
-  * [switch documentation](https://alem.01-edu.org/design/Components/FormControls/Switch)
-  * [checkbox documentation](https://alem.01-edu.org/design/Components/FormControls/Checkbox)
-* For switch and checkbox inputs type, you have to set the default value as a boolean property named **value**.
+![form step example](https://user-images.githubusercontent.com/35296671/56503976-012aae80-650f-11e9-82c8-dd7d026b6eb1.png)
 
-### Settings for a document to sign step
+## Settings for a document to sign step
 > In the child object you've created, 2 attributes must be filled:
 > 1. subtype
 > 2. text
 > 3. buttonText (facultative)
 > 4. checkbox (facultative)
 
-To set up the child object you've created with these elements:
+### Description
+
+###### To set up the child object you've created with these elements:
 1. Edit you child object
 2. Go to *Object attributes*
 3. Add the attributes:
@@ -175,21 +200,24 @@ To set up the child object you've created with these elements:
      * A **name** key of type `String`
      * Then you can add all the properties you want to your checkbox.
 
+### Example
+
 Here is an example of the structure a 'document to sign' step could have:
 
-```javascript
-const signStepExample = {
-  subtype: "onb-adm-sign",
-  text: "Lorem ipsum dolor sit amet, consectetur adipiscing elit. Praesent ornare non sem eu pretium. Integer porttitor risus eget nibh iaculis, ac lacinia orci dictum. Nunc ullamcorper consequat enim in posuere. Aliquam volutpat est odio, vel maximus arcu maximus sit amet. Donec ultricies faucibus magna id luctus. Duis et dapibus elit. In vestibulum ipsum erat, at commodo tortor convallis vel. Nunc ut ultrices nulla. Etiam lorem justo, consequat a consectetur a, porttitor non turpis. Mauris eu mollis nisl, id dignissim quam. Curabitur condimentum sollicitudin rutrum. Aenean blandit, arcu nec ullamcorper rhoncus, lectus sem lacinia lorem, venenatis dignissim velit mi et sapien. Nullam posuere augue ut magna ullamcorper dignissim. Ut rhoncus sapien vel nulla commodo finibus. Cras non leo vel urna finibus volutpat. Praesent et ex eget diam tincidunt suscipit. Phasellus bibendum neque vel placerat iaculis. Vestibulum bibendum ultrices ipsum, non sodales lectus. Cras eget orci eget elit blandit scelerisque at ut nulla. Integer ligula eros, eleifend quis sodales a, porttitor sit amet neque. Fusce mollis magna at lectus varius, quis suscipit mi cursus. Etiam id imperdiet metus, in malesuada quam. Aliquam facilisis nunc non sapien condimentum, quis iaculis nisl auctor. Nunc lorem sapien, interdum vel efficitur ac, dapibus a diam. Ut ante urna, sodales in bibendum vel, lacinia ut mauris. In vel placerat leo. In libero dui, tincidunt at sem id, faucibus sollicitudin elit.",
-  buttonText: "Sign chart",
-  checkbox: {
-    name:"acceptChart",
-    label:"I have read and accepted the Chart 01",
-    required:true
-  },
+```json
+{
+  "subtype": "onb-adm-sign",
+  "text": "Lorem ipsum dolor sit amet, consectetur adipiscing elit. Praesent ornare non sem eu pretium. Integer porttitor risus eget nibh iaculis, ac lacinia orci dictum. Nunc ullamcorper consequat enim in posuere. Aliquam volutpat est odio, vel maximus arcu maximus sit amet. Donec ultricies faucibus magna id luctus. Duis et dapibus elit. In vestibulum ipsum erat, at commodo tortor convallis vel. Nunc ut ultrices nulla. Etiam lorem justo, consequat a consectetur a, porttitor non turpis. Mauris eu mollis nisl, id dignissim quam. Curabitur condimentum sollicitudin rutrum. Aenean blandit, arcu nec ullamcorper rhoncus, lectus sem lacinia lorem, venenatis dignissim velit mi et sapien. Nullam posuere augue ut magna ullamcorper dignissim. Ut rhoncus sapien vel nulla commodo finibus. Cras non leo vel urna finibus volutpat. Praesent et ex eget diam tincidunt suscipit. Phasellus bibendum neque vel placerat iaculis. Vestibulum bibendum ultrices ipsum, non sodales lectus. Cras eget orci eget elit blandit scelerisque at ut nulla. Integer ligula eros, eleifend quis sodales a, porttitor sit amet neque. Fusce mollis magna at lectus varius, quis suscipit mi cursus. Etiam id imperdiet metus, in malesuada quam. Aliquam facilisis nunc non sapien condimentum, quis iaculis nisl auctor. Nunc lorem sapien, interdum vel efficitur ac, dapibus a diam. Ut ante urna, sodales in bibendum vel, lacinia ut mauris. In vel placerat leo. In libero dui, tincidunt at sem id, faucibus sollicitudin elit.",
+  "buttonText": "Sign chart",
+  "checkbox": {
+    "name":"acceptChart",
+    "label":"I have read and accepted the Chart 01",
+    "required":true
+  }
 }
 ```
 
 This 'document to sign' step would look like this:
+
 ![document to sign step example](https://user-images.githubusercontent.com/35296671/56504782-8f079900-6511-11e9-9a0e-bb638b6d7d03.png)
 

From 2ee4213a1189b455c358a64a5f310f1f0f5e60af Mon Sep 17 00:00:00 2001
From: Louise Foussat <louisefoussat@gmail.com>
Date: Mon, 22 Apr 2019 20:37:28 +0100
Subject: [PATCH 12/21] add some space

---
 doc/create-steps.md | 21 ++++++++++++++++-----
 1 file changed, 16 insertions(+), 5 deletions(-)

diff --git a/doc/create-steps.md b/doc/create-steps.md
index 6a31be57..74a9eb23 100644
--- a/doc/create-steps.md
+++ b/doc/create-steps.md
@@ -21,21 +21,28 @@ Every step that you want to create must :
 
 ---
 
-To create a step, you must:
+#### To create a step, you must:
 1. Create a new object for your step in the admin (in *Admin* > *Add new object*)
+
    <img width="664" alt="Capture d’écran 2019-04-22 à 15 57 37" src="https://user-images.githubusercontent.com/35296671/56507169-6505a500-6518-11e9-89bb-04c7fd9b41ca.png">
    <img width="450" alt="Capture d’écran 2019-04-22 à 15 58 21" src="https://user-images.githubusercontent.com/35296671/56507180-6afb8600-6518-11e9-97a5-4dcff8f0a069.png">
+
    * The title of your object will be the title displayed for the step you're creating. Use a intellegible title for your user.
    * This object must have the same type as your major object ("signup" for the sign up phase, "onboarding" for the administration part of the onboarding)
 
 > Your step is then available in the *Admin*. You can find it in the section of its type (*SignUp* or *Onboarding*) or thanks to the search bar of the cursus object's page.
-   
+ 
+
 2. Add this new object as a child of your parent object
+
    1. Edit the parent object (*Sign up* or *Administration*)
+
       <img width="640" alt="Capture d’écran 2019-04-22 à 19 24 23" src="https://user-images.githubusercontent.com/35296671/56517407-cb98bc00-6534-11e9-98d6-a2b1c0193a38.png">
       <img width="640" alt="Capture d’écran 2019-04-22 à 19 24 10" src="https://user-images.githubusercontent.com/35296671/56517421-d0f60680-6534-11e9-86ef-97fb9e59786e.png">
+   
    2. Go to *Children* > *Add a child*
       ![add child to major object](https://user-images.githubusercontent.com/35296671/56506977-de50c800-6517-11e9-9c71-d19a1ec4e5cd.png)
+   
    3. Set up the new child:
       * Enter its name in the input "Add a child name"
       * Select you child in the select input
@@ -53,10 +60,14 @@ To create a step, you must:
 > 2. form
 
 ### Description
-###### Edit the step object you've created :
+
+#### Edit the step object you've created :
 1. Go to *Object attributes*
+
    <img width="1073" alt="Capture d’écran 2019-04-22 à 15 59 33" src="https://user-images.githubusercontent.com/35296671/56507445-3936ef00-6519-11e9-90c8-d85056e9330b.png">
+
 2. Add the attributes:
+
    * Add a new key **subtype** of type `String` with the exact value 'onb-adm-form-generator'
    * Add a new key **form** of type `Object` 
      * The form you're creating can have several sections. Each section is displayed with a title, and its inputs. 
@@ -66,11 +77,11 @@ To create a step, you must:
        * An **inputs** key of type `Object`, which will contain all the inputs of the section. For each input you want to add, you must set up the input as this :
          * Add a new `Object` element in the "inputs" object. The key of this object will be used as the "name" attribute of your input. The values will be considered as the props of your input.
 
-###### Set up of an input props:
+#### Set up of an input props:
 * You must declare a **type** key of type `String`, wich define the type of your input : `tel`, `text`, `date`, `select`, `radio`, `switch`, `checkbox`, `textarea`. 
 * Then you can fill the props you need for your input, according to its type : `placeholder`, `id`, `required`, `label`, `items`, `emptyItems`, `index`, etc.
 
-###### Important indication: 
+#### Important indication: 
 * The **index** property is used to order your inputs. It won't be spread in the input.
 * The **type** property is resquired. It will be used to determine the kind of input we must generate. It is spread in the input only if the input type attribute is required (type 'tel' or 'text' for example, but not for type 'select' - in this case, we will generate a select element)
   * We're creating a special type 'countries' (select displaying all the countries). Documentation will be updated as soon as it's available.

From 0981beab1bedc503856ed2f9b6f5277a415f882d Mon Sep 17 00:00:00 2001
From: Louise Foussat <louisefoussat@gmail.com>
Date: Mon, 22 Apr 2019 20:41:53 +0100
Subject: [PATCH 13/21] add forgotten corrections

---
 doc/create-steps.md | 11 +++++++----
 1 file changed, 7 insertions(+), 4 deletions(-)

diff --git a/doc/create-steps.md b/doc/create-steps.md
index 74a9eb23..1b9b9f11 100644
--- a/doc/create-steps.md
+++ b/doc/create-steps.md
@@ -27,6 +27,7 @@ Every step that you want to create must :
    <img width="664" alt="Capture d’écran 2019-04-22 à 15 57 37" src="https://user-images.githubusercontent.com/35296671/56507169-6505a500-6518-11e9-89bb-04c7fd9b41ca.png">
    <img width="450" alt="Capture d’écran 2019-04-22 à 15 58 21" src="https://user-images.githubusercontent.com/35296671/56507180-6afb8600-6518-11e9-97a5-4dcff8f0a069.png">
 
+
    * The title of your object will be the title displayed for the step you're creating. Use a intellegible title for your user.
    * This object must have the same type as your major object ("signup" for the sign up phase, "onboarding" for the administration part of the onboarding)
 
@@ -41,6 +42,7 @@ Every step that you want to create must :
       <img width="640" alt="Capture d’écran 2019-04-22 à 19 24 10" src="https://user-images.githubusercontent.com/35296671/56517421-d0f60680-6534-11e9-86ef-97fb9e59786e.png">
    
    2. Go to *Children* > *Add a child*
+
       ![add child to major object](https://user-images.githubusercontent.com/35296671/56506977-de50c800-6517-11e9-9c71-d19a1ec4e5cd.png)
    
    3. Set up the new child:
@@ -198,10 +200,11 @@ This 'form' step would look like this:
 
 ### Description
 
-###### To set up the child object you've created with these elements:
-1. Edit you child object
+#### To set up the child object you've created with these elements:
+
+1. Edit you step object
 2. Go to *Object attributes*
-3. Add the attributes:
+3. Add the following attributes:
    * Add a new key **subtype** of type `String` with the value 'onb-adm-sign'
    * Add a new key **text** of type `String` with all the text of your document to sign as value
    * Add a new key **buttonText** of type `String` with the text you want to display in the submit button of your step
@@ -211,7 +214,7 @@ This 'form' step would look like this:
      * A **name** key of type `String`
      * Then you can add all the properties you want to your checkbox.
 
-### Example
+### Examples
 
 Here is an example of the structure a 'document to sign' step could have:
 

From 3027c8646572eef1764f6dac9384127931345d4d Mon Sep 17 00:00:00 2001
From: Louise Foussat <louisefoussat@gmail.com>
Date: Mon, 22 Apr 2019 21:09:16 +0100
Subject: [PATCH 14/21] correction after reading

---
 doc/create-steps.md | 34 ++++++++++++++++++----------------
 1 file changed, 18 insertions(+), 16 deletions(-)

diff --git a/doc/create-steps.md b/doc/create-steps.md
index 1b9b9f11..fabb2f2a 100644
--- a/doc/create-steps.md
+++ b/doc/create-steps.md
@@ -28,8 +28,9 @@ Every step that you want to create must :
    <img width="450" alt="Capture d’écran 2019-04-22 à 15 58 21" src="https://user-images.githubusercontent.com/35296671/56507180-6afb8600-6518-11e9-97a5-4dcff8f0a069.png">
 
 
-   * The title of your object will be the title displayed for the step you're creating. Use a intellegible title for your user.
-   * This object must have the same type as your major object ("signup" for the sign up phase, "onboarding" for the administration part of the onboarding)
+   * The title of your object will be the title displayed to your candidates (for the step you're creating). Use a intellegible title for your user.
+     * NB : you can always edit it in the *Admin*
+   * This object must have the same type as its future parent object ("signup" or "onboarding").
 
 > Your step is then available in the *Admin*. You can find it in the section of its type (*SignUp* or *Onboarding*) or thanks to the search bar of the cursus object's page.
  
@@ -47,7 +48,7 @@ Every step that you want to create must :
    
    3. Set up the new child:
       * Enter its name in the input "Add a child name"
-      * Select you child in the select input
+      * Select your step object in the select input
       * Click on "ADD"
 
 > Your step is then related to its parent. You can see it in the *Children* section of the parent object. There, you can now : 
@@ -73,29 +74,30 @@ Every step that you want to create must :
    * Add a new key **subtype** of type `String` with the exact value 'onb-adm-form-generator'
    * Add a new key **form** of type `Object` 
      * The form you're creating can have several sections. Each section is displayed with a title, and its inputs. 
-       * The submission of the form will check the required inputs of all the sections you've created. 
+       * NB : The submission of the form will check the required inputs of all the sections you've created for the form. 
      * To create a section, add a new key to your form object, of type `Object`, that contains :
-       * A **title** key of type `String`. The value of this property will be the title displayed in the top of your form section. If you have only one section in your form step, and you don't need a section title, you don't have to set up this property.
+       * A **title** key of type `String`. The value of this property will be the title displayed in the top of your form section. 
+         * If you have only one section in your form step, and you don't need a section title, you don't have to set up this property.
        * An **inputs** key of type `Object`, which will contain all the inputs of the section. For each input you want to add, you must set up the input as this :
          * Add a new `Object` element in the "inputs" object. The key of this object will be used as the "name" attribute of your input. The values will be considered as the props of your input.
 
 #### Set up of an input props:
-* You must declare a **type** key of type `String`, wich define the type of your input : `tel`, `text`, `date`, `select`, `radio`, `switch`, `checkbox`, `textarea`. 
+* You must declare a **type** key of type `String`, wich define the type of your input : `tel`, `text`, `date`, `select`, `radio`, `switch`, `checkbox`, `textarea` (and soon a special type `countries`). 
 * Then you can fill the props you need for your input, according to its type : `placeholder`, `id`, `required`, `label`, `items`, `emptyItems`, `index`, etc.
 
 #### Important indication: 
-* The **index** property is used to order your inputs. It won't be spread in the input.
+* The **index** property is used to order your inputs. It won't be spread in the input. But be careful not to set the same index two times.
 * The **type** property is resquired. It will be used to determine the kind of input we must generate. It is spread in the input only if the input type attribute is required (type 'tel' or 'text' for example, but not for type 'select' - in this case, we will generate a select element)
-  * We're creating a special type 'countries' (select displaying all the countries). Documentation will be updated as soon as it's available.
-* Don't declare an **onChange**, it's handled by the app
-* Each input type has its own attributes. You can check how to set up your inputs hey : 
+  * At the moment, we're creating a special type 'countries' (select displaying all the countries). Documentation will be updated as soon as it's available.
+* Don't declare an **onChange** in your props, the event is handled by the app. It would break the functioning of the form.
+* For switch and checkbox inputs type, you have to set the default value as a boolean property named **value**.
+* For more informations, each input type has its own attributes. You can check how to set up your inputs in the design documentation : 
   * [textInput documentation](https://alem.01-edu.org/design/Components/FormInputs/TextInput) - used for inputs type 'text', 'tel', and 'date'
   * [textArea documentation](https://alem.01-edu.org/design/Components/FormInputs/TextArea)
   * [select documentation](https://alem.01-edu.org/design/Components/FormControls/Select)
   * [radio button documentation](https://alem.01-edu.org/design/Components/FormControls/Radio)
   * [switch documentation](https://alem.01-edu.org/design/Components/FormControls/Switch)
   * [checkbox documentation](https://alem.01-edu.org/design/Components/FormControls/Checkbox)
-* For switch and checkbox inputs type, you have to set the default value as a boolean property named **value**.
 
 ### Examples
 
@@ -205,14 +207,14 @@ This 'form' step would look like this:
 1. Edit you step object
 2. Go to *Object attributes*
 3. Add the following attributes:
-   * Add a new key **subtype** of type `String` with the value 'onb-adm-sign'
-   * Add a new key **text** of type `String` with all the text of your document to sign as value
-   * Add a new key **buttonText** of type `String` with the text you want to display in the submit button of your step
-   * Add a new key **checkbox** of type `Object` if you want to force your user to click on a checkbox (ex: 'I have read and accepted the conditions') before validating his document. In the checkbox object, you should define:
+   * Add a new key **subtype** of type `String` with the exact value 'onb-adm-sign'
+   * Add a new key **text** of type `String` with the text of your document to sign as value
+   * Add a new key **buttonText** of type `String` with the text you want to display in the submit button of your step. If you don't fill this property, the default value if 'Sign'.
+   * Add a new key **checkbox** of type `Object`, if you want to force your user to click on a checkbox before validating his document (ex: 'I have read and accepted the conditions'). In the checkbox object, you should define:
      * A **label** key of type `String`, with the text you want to associate to the checkbox
      * A **required** key of type `Boolean`, set at true if you want to force the user to check it
      * A **name** key of type `String`
-     * Then you can add all the properties you want to your checkbox.
+     * Then you can add all other properties you want to your checkbox.
 
 ### Examples
 

From 016466717f46bc2cf8d02e96a42c96280c0feeae Mon Sep 17 00:00:00 2001
From: lfoussat <35296671+lfoussat@users.noreply.github.com>
Date: Mon, 22 Apr 2019 21:16:46 +0100
Subject: [PATCH 15/21] change file name

---
 doc/{create-steps.md => modular-steps-management.md} | 0
 1 file changed, 0 insertions(+), 0 deletions(-)
 rename doc/{create-steps.md => modular-steps-management.md} (100%)

diff --git a/doc/create-steps.md b/doc/modular-steps-management.md
similarity index 100%
rename from doc/create-steps.md
rename to doc/modular-steps-management.md

From 555608267e5a612b2463355aa3f4709c7de83ff8 Mon Sep 17 00:00:00 2001
From: Frenchris <34804391+Frenchris@users.noreply.github.com>
Date: Mon, 22 Apr 2019 23:57:48 +0100
Subject: [PATCH 16/21] Update modular-steps-management.md

On a pas tout lu mais demain on continue :heart:
---
 doc/modular-steps-management.md | 120 ++++++++++++++------------------
 1 file changed, 53 insertions(+), 67 deletions(-)

diff --git a/doc/modular-steps-management.md b/doc/modular-steps-management.md
index fabb2f2a..431acf4b 100644
--- a/doc/modular-steps-management.md
+++ b/doc/modular-steps-management.md
@@ -1,97 +1,83 @@
 # Sign up & onboarding's Administration section - Modular steps management
 
 ## Usage
-> After their first authentication in the app, every candidate has to effectuate his **sign up** and his **onboarding**. The steps that compose the **sign up** and the **administration** section of the onboarding are: 
-> * Of two kinds: 
->   * forms (identification, medical information, etc.)
->   * documents to sign (general conditions, charts, regulations, etc.)
-> * Modular: you can add, update, delete and order it as you wish. 
-
+> After their first authentication in the app, every candidate has to do his **sign up** and his **onboarding**. The steps that compose the **sign up** and the **administration** section of the onboarding are either:
+>   * Forms (identification, medical information, etc.)
+>   * Documents to sign (general conditions, charts, regulations, etc.)
+>
+> All the sections are modular: you can add, update, delete and order them as you wish. 
+>
 > This documentation explains how to manage these steps. 
 
-## Create a step
-
-Every step that you want to create must :
-* Be related as a child to the correct parent object in the *Admin*
-  * Steps related to the Sign up -> *Admin* > *Objects* > *SignUp* > ***Sign Up*** 
-  * Steps related to the onboarding's Administration section -> *Admin* > *Objects* > *Onboarding* > ***Administration*** 
-* Be defined with the correct object **type**
-  * Steps related to the Sign up -> type **sign up**
-  * Steps related to the onboarding's Administration section -> type **onboarding**
-
----
+## Creating a step:
+### Create a new object for your step in the admin
+> (in *Admin* > *Add new object*)
 
-#### To create a step, you must:
-1. Create a new object for your step in the admin (in *Admin* > *Add new object*)
+<img width="664" alt="Capture d’écran 2019-04-22 à 15 57 37" src="https://user-images.githubusercontent.com/35296671/56507169-6505a500-6518-11e9-89bb-04c7fd9b41ca.png">
+<img width="450" alt="Capture d’écran 2019-04-22 à 15 58 21" src="https://user-images.githubusercontent.com/35296671/56507180-6afb8600-6518-11e9-97a5-4dcff8f0a069.png">
 
-   <img width="664" alt="Capture d’écran 2019-04-22 à 15 57 37" src="https://user-images.githubusercontent.com/35296671/56507169-6505a500-6518-11e9-89bb-04c7fd9b41ca.png">
-   <img width="450" alt="Capture d’écran 2019-04-22 à 15 58 21" src="https://user-images.githubusercontent.com/35296671/56507180-6afb8600-6518-11e9-97a5-4dcff8f0a069.png">
 
-
-   * The title of your object will be the title displayed to your candidates (for the step you're creating). Use a intellegible title for your user.
-     * NB : you can always edit it in the *Admin*
-   * This object must have the same type as its future parent object ("signup" or "onboarding").
+* The title of your object will be the title displayed to your candidates (for the step you are creating). Use an intellegible title for your user.
+  > NB: you can always edit it in the *Admin*
+* This object must have the same type as its future parent object ("signup" or "onboarding").
 
 > Your step is then available in the *Admin*. You can find it in the section of its type (*SignUp* or *Onboarding*) or thanks to the search bar of the cursus object's page.
  
 
-2. Add this new object as a child of your parent object
+### Add this new object as a child of your parent's object
 
-   1. Edit the parent object (*Sign up* or *Administration*)
+#### 1. Edit the parent object (*Sign up* or *Administration*)
+<img width="640" alt="Capture d’écran 2019-04-22 à 19 24 23" src="https://user-images.githubusercontent.com/35296671/56517407-cb98bc00-6534-11e9-98d6-a2b1c0193a38.png">
+<img width="640" alt="Capture d’écran 2019-04-22 à 19 24 10" src="https://user-images.githubusercontent.com/35296671/56517421-d0f60680-6534-11e9-86ef-97fb9e59786e.png">
 
-      <img width="640" alt="Capture d’écran 2019-04-22 à 19 24 23" src="https://user-images.githubusercontent.com/35296671/56517407-cb98bc00-6534-11e9-98d6-a2b1c0193a38.png">
-      <img width="640" alt="Capture d’écran 2019-04-22 à 19 24 10" src="https://user-images.githubusercontent.com/35296671/56517421-d0f60680-6534-11e9-86ef-97fb9e59786e.png">
-   
-   2. Go to *Children* > *Add a child*
+#### 2. Go to *Children* > *Add a child*
+![add child to major object](https://user-images.githubusercontent.com/35296671/56506977-de50c800-6517-11e9-9c71-d19a1ec4e5cd.png)
 
-      ![add child to major object](https://user-images.githubusercontent.com/35296671/56506977-de50c800-6517-11e9-9c71-d19a1ec4e5cd.png)
-   
-   3. Set up the new child:
-      * Enter its name in the input "Add a child name"
-      * Select your step object in the select input
-      * Click on "ADD"
+#### 3. Set up the new child:
+* Enter its name in the input "Add a child name"
+* Select your step object in the select input
+* Click on "ADD"
 
-> Your step is then related to its parent. You can see it in the *Children* section of the parent object. There, you can now : 
-> * Delete the step as a child of its parent (the actual object of your step won't be deleted)
-> * Reorder it in the children's list, by dragging it to the place you cant
+> Your step is then related to its parent. You can see it in the *Children* section of the parent's object. There, you can now: 
+> * Delete the step as a child of its parent (the actual object of your step will not be deleted).
+> * Reorder it in the children's list, by dragging it to the place you want.
 > * Go to update its settings by clicking on the eye of its reference (it will redirect you to the actual object of your step).
 <img width="1229" alt="Capture d’écran 2019-04-22 à 19 51 12" src="https://user-images.githubusercontent.com/35296671/56518936-a1e19400-6538-11e9-81c7-520ffd365cff.png">
 
 ## Settings for a form step
-> In the step object you've created, 2 attributes must be filled:
-> 1. subtype
-> 2. form
+> In the step object you have created, 2 attributes must be filled:
+> 1. Subtype
+> 2. Form
 
 ### Description
 
-#### Edit the step object you've created :
-1. Go to *Object attributes*
-
-   <img width="1073" alt="Capture d’écran 2019-04-22 à 15 59 33" src="https://user-images.githubusercontent.com/35296671/56507445-3936ef00-6519-11e9-90c8-d85056e9330b.png">
+#### Edit the step object you have created :
+> in *Object attributes*
 
-2. Add the attributes:
+<img width="1073" alt="Capture d’écran 2019-04-22 à 15 59 33" src="https://user-images.githubusercontent.com/35296671/56507445-3936ef00-6519-11e9-90c8-d85056e9330b.png">
 
-   * Add a new key **subtype** of type `String` with the exact value 'onb-adm-form-generator'
-   * Add a new key **form** of type `Object` 
-     * The form you're creating can have several sections. Each section is displayed with a title, and its inputs. 
-       * NB : The submission of the form will check the required inputs of all the sections you've created for the form. 
-     * To create a section, add a new key to your form object, of type `Object`, that contains :
-       * A **title** key of type `String`. The value of this property will be the title displayed in the top of your form section. 
-         * If you have only one section in your form step, and you don't need a section title, you don't have to set up this property.
-       * An **inputs** key of type `Object`, which will contain all the inputs of the section. For each input you want to add, you must set up the input as this :
-         * Add a new `Object` element in the "inputs" object. The key of this object will be used as the "name" attribute of your input. The values will be considered as the props of your input.
+* Add a new key **subtype** of type `String` with the exact value 'onb-adm-form-generator'
+* Add a new key **form** of type `Object` 
+  * The form you are creating can have several sections. Each section is displayed with a title, and its inputs. 
+    > NB: The submission of the form will check the required inputs of all the sections you have created for the form. 
+  * To create a section, add a new key to your form object, of type `Object`, that contains:
+    * A **title** key of type `String`. The value of this property will be the title displayed in the top of your form section. 
+      > If you have only one section in your form step, and you don't need a section title, you do not have to set up this property.
+    * An **inputs** key of type `Object`, which will contain all the inputs of the section. For each wanted input, add a new `Object` element in the "inputs" object.
+      > The key of this object will be used as the "name" attribute of your input.  
+      > The values will be considered as the properties of your input.
 
-#### Set up of an input props:
-* You must declare a **type** key of type `String`, wich define the type of your input : `tel`, `text`, `date`, `select`, `radio`, `switch`, `checkbox`, `textarea` (and soon a special type `countries`). 
-* Then you can fill the props you need for your input, according to its type : `placeholder`, `id`, `required`, `label`, `items`, `emptyItems`, `index`, etc.
+#### Defining an input:
+* You must declare a **type** key of type `String`, which define the type of your input : `tel`, `text`, `date`, `select`, `radio`, `switch`, `checkbox`, `textarea` (and soon a special type `countries`). 
+* Then you can fill the props you need for your input, according to its type: `placeholder`, `id`, `required`, `label`, `items`, `emptyItems`, `index`, etc...
 
 #### Important indication: 
-* The **index** property is used to order your inputs. It won't be spread in the input. But be careful not to set the same index two times.
-* The **type** property is resquired. It will be used to determine the kind of input we must generate. It is spread in the input only if the input type attribute is required (type 'tel' or 'text' for example, but not for type 'select' - in this case, we will generate a select element)
-  * At the moment, we're creating a special type 'countries' (select displaying all the countries). Documentation will be updated as soon as it's available.
-* Don't declare an **onChange** in your props, the event is handled by the app. It would break the functioning of the form.
-* For switch and checkbox inputs type, you have to set the default value as a boolean property named **value**.
-* For more informations, each input type has its own attributes. You can check how to set up your inputs in the design documentation : 
+* The **index** property is used to order your inputs. It will not be passed onto the input. Be mindful not to set the same index twice.
+* The **type** property is required. It will be used to determine the kind of input we must generate. It is passed onto the input only if the input type attribute is required (type 'tel' or 'text' for example, but not for type 'select' - in this case, we will generate a select element)
+  * At the moment, we are creating a special type 'countries' (a `Select` displaying all the countries). Documentation will be updated as soon as it is available.
+* `onChange` prop are ignored as the event is handled by the app.
+* For `switch` and `checkbox` input types, the default value has to be set as a boolean property named **value**.
+* More information for each inputs is available in the design documentation: 
   * [textInput documentation](https://alem.01-edu.org/design/Components/FormInputs/TextInput) - used for inputs type 'text', 'tel', and 'date'
   * [textArea documentation](https://alem.01-edu.org/design/Components/FormInputs/TextArea)
   * [select documentation](https://alem.01-edu.org/design/Components/FormControls/Select)
@@ -102,7 +88,7 @@ Every step that you want to create must :
 ### Examples
 
 Here is an example of the form step's attributes. It presents a form with two sections, and an example of each kind of input type. 
-NB : this example object will soon be provided in the admin.
+> NB : this example object will soon be provided in the admin.
 
 ```json
 {

From 7af8b81e423b5d7e2961d0f658447df029b447b6 Mon Sep 17 00:00:00 2001
From: Frenchris <34804391+Frenchris@users.noreply.github.com>
Date: Tue, 23 Apr 2019 16:27:10 +0100
Subject: [PATCH 17/21] First pass

Done with the first pass
---
 doc/modular-steps-management.md | 23 +++++++++++++----------
 1 file changed, 13 insertions(+), 10 deletions(-)

diff --git a/doc/modular-steps-management.md b/doc/modular-steps-management.md
index 431acf4b..65c5a593 100644
--- a/doc/modular-steps-management.md
+++ b/doc/modular-steps-management.md
@@ -44,7 +44,7 @@
 > * Go to update its settings by clicking on the eye of its reference (it will redirect you to the actual object of your step).
 <img width="1229" alt="Capture d’écran 2019-04-22 à 19 51 12" src="https://user-images.githubusercontent.com/35296671/56518936-a1e19400-6538-11e9-81c7-520ffd365cff.png">
 
-## Settings for a form step
+## Settings for a `form` step
 > In the step object you have created, 2 attributes must be filled:
 > 1. Subtype
 > 2. Form
@@ -152,7 +152,7 @@ Here is an example of the form step's attributes. It presents a form with two se
           "label": "I am new in programming",
           "value": true
         },
-        "generalContions": {
+        "generalConditions": {
           "index": 7,
           "type": "checkbox",
           "label": "I have read and I accept the general conditions",
@@ -179,23 +179,26 @@ This 'form' step would look like this:
 
 ![form step example](https://user-images.githubusercontent.com/35296671/56503976-012aae80-650f-11e9-82c8-dd7d026b6eb1.png)
 
-## Settings for a document to sign step
-> In the child object you've created, 2 attributes must be filled:
-> 1. subtype
-> 2. text
-> 3. buttonText (facultative)
-> 4. checkbox (facultative)
+## Settings for a `document to sign` step
+The newly created child can be customized with these attributes :
+
+| name       | fullfillment |
+| ---------- | ---------    |
+| subtype    | **required** |
+| text       | **required** |
+| buttonText | optionnal    |
+| checkbox   | optionnal    |
 
 ### Description
 
-#### To set up the child object you've created with these elements:
+#### To set up the child object you have created with these elements:
 
 1. Edit you step object
 2. Go to *Object attributes*
 3. Add the following attributes:
    * Add a new key **subtype** of type `String` with the exact value 'onb-adm-sign'
    * Add a new key **text** of type `String` with the text of your document to sign as value
-   * Add a new key **buttonText** of type `String` with the text you want to display in the submit button of your step. If you don't fill this property, the default value if 'Sign'.
+   * Add a new key **buttonText** of type `String` with the text that you want to display in the submit button of your step. If you do not fill this property, the default value is 'Sign'.
    * Add a new key **checkbox** of type `Object`, if you want to force your user to click on a checkbox before validating his document (ex: 'I have read and accepted the conditions'). In the checkbox object, you should define:
      * A **label** key of type `String`, with the text you want to associate to the checkbox
      * A **required** key of type `Boolean`, set at true if you want to force the user to check it

From e65a5c19229bda1f966336c637b9b4ba61af2748 Mon Sep 17 00:00:00 2001
From: Louise Foussat <louisefoussat@gmail.com>
Date: Wed, 24 Apr 2019 12:01:24 +0100
Subject: [PATCH 18/21] cutting the documentation in 3 files : object-creation,
 child-object-creation, modular-step-management

---
 doc/child-object-creation.md    | 33 ++++++++++++++++++++
 doc/modular-steps-management.md | 30 ++++---------------
 doc/object-creation.md          | 53 +++++++++++++++++++++++++++++++++
 3 files changed, 91 insertions(+), 25 deletions(-)
 create mode 100644 doc/child-object-creation.md
 create mode 100644 doc/object-creation.md

diff --git a/doc/child-object-creation.md b/doc/child-object-creation.md
new file mode 100644
index 00000000..c14166b3
--- /dev/null
+++ b/doc/child-object-creation.md
@@ -0,0 +1,33 @@
+# Admin object's management - create a child object
+
+## Usage
+> Objects of the Admin can be configured :
+>   * By setting particular **attributes** to the object
+>   * By associating **children** to the object
+>
+> Children can be added, deleted, reordered in the list. Also, it's possible to configure it in a special way for the parent object, by setting children attributes for all the children. 
+>
+> This documentation explains how to associate a child to a parent object. 
+
+### Create a new object for your child in the admin
+> Information is available for object's creation: [Modular step management](https://github.com/01-edu/public/blob/master/doc/object-creation.md)
+
+### Add this new object as a child of your parent's object
+
+#### 1. Edit the parent object
+<img width="640" alt="Capture d’écran 2019-04-22 à 19 24 23" src="https://user-images.githubusercontent.com/35296671/56517407-cb98bc00-6534-11e9-98d6-a2b1c0193a38.png">
+<img width="640" alt="Capture d’écran 2019-04-22 à 19 24 10" src="https://user-images.githubusercontent.com/35296671/56517421-d0f60680-6534-11e9-86ef-97fb9e59786e.png">
+
+#### 2. Go to *Children* > *Add a child*
+![add child to parent object](https://user-images.githubusercontent.com/35296671/56506977-de50c800-6517-11e9-9c71-d19a1ec4e5cd.png)
+
+#### 3. Set up the new child:
+* Enter its name in the input "Add a child name"
+* Select your step object in the select input
+* Click on "ADD"
+
+> Your step is then related to its parent. You can see it in the *Children* section of the parent's object. There, you can now: 
+> * Delete the child from its parent (the actual object of your child will not be deleted).
+> * Reorder it in the children's list, by dragging it to the place you want.
+> * Go to update its settings by clicking on the eye of its reference (it will redirect you to the actual object of your step).
+<img width="1229" alt="Capture d’écran 2019-04-22 à 19 51 12" src="https://user-images.githubusercontent.com/35296671/56518936-a1e19400-6538-11e9-81c7-520ffd365cff.png">
diff --git a/doc/modular-steps-management.md b/doc/modular-steps-management.md
index 65c5a593..cd2ac6ff 100644
--- a/doc/modular-steps-management.md
+++ b/doc/modular-steps-management.md
@@ -9,40 +9,20 @@
 >
 > This documentation explains how to manage these steps. 
 
-## Creating a step:
+## Create your step child object
 ### Create a new object for your step in the admin
-> (in *Admin* > *Add new object*)
+> Information is available for object's creation: [Modular step management](https://github.com/01-edu/public/blob/master/doc/object-creation.md)
 
-<img width="664" alt="Capture d’écran 2019-04-22 à 15 57 37" src="https://user-images.githubusercontent.com/35296671/56507169-6505a500-6518-11e9-89bb-04c7fd9b41ca.png">
-<img width="450" alt="Capture d’écran 2019-04-22 à 15 58 21" src="https://user-images.githubusercontent.com/35296671/56507180-6afb8600-6518-11e9-97a5-4dcff8f0a069.png">
-
-
-* The title of your object will be the title displayed to your candidates (for the step you are creating). Use an intellegible title for your user.
-  > NB: you can always edit it in the *Admin*
-* This object must have the same type as its future parent object ("signup" or "onboarding").
+* This object must have the same type as its future parent object (*signup* or *onboarding*).
 
 > Your step is then available in the *Admin*. You can find it in the section of its type (*SignUp* or *Onboarding*) or thanks to the search bar of the cursus object's page.
  
 
 ### Add this new object as a child of your parent's object
 
-#### 1. Edit the parent object (*Sign up* or *Administration*)
-<img width="640" alt="Capture d’écran 2019-04-22 à 19 24 23" src="https://user-images.githubusercontent.com/35296671/56517407-cb98bc00-6534-11e9-98d6-a2b1c0193a38.png">
-<img width="640" alt="Capture d’écran 2019-04-22 à 19 24 10" src="https://user-images.githubusercontent.com/35296671/56517421-d0f60680-6534-11e9-86ef-97fb9e59786e.png">
-
-#### 2. Go to *Children* > *Add a child*
-![add child to major object](https://user-images.githubusercontent.com/35296671/56506977-de50c800-6517-11e9-9c71-d19a1ec4e5cd.png)
-
-#### 3. Set up the new child:
-* Enter its name in the input "Add a child name"
-* Select your step object in the select input
-* Click on "ADD"
+* Edit the parent object: *Sign up* or *Administration*
 
-> Your step is then related to its parent. You can see it in the *Children* section of the parent's object. There, you can now: 
-> * Delete the step as a child of its parent (the actual object of your step will not be deleted).
-> * Reorder it in the children's list, by dragging it to the place you want.
-> * Go to update its settings by clicking on the eye of its reference (it will redirect you to the actual object of your step).
-<img width="1229" alt="Capture d’écran 2019-04-22 à 19 51 12" src="https://user-images.githubusercontent.com/35296671/56518936-a1e19400-6538-11e9-81c7-520ffd365cff.png">
+> Information is available for object's creation: [Modular step management](https://github.com/01-edu/public/blob/master/doc/child-object-creation.md)
 
 ## Settings for a `form` step
 > In the step object you have created, 2 attributes must be filled:
diff --git a/doc/object-creation.md b/doc/object-creation.md
new file mode 100644
index 00000000..cdf1b915
--- /dev/null
+++ b/doc/object-creation.md
@@ -0,0 +1,53 @@
+# Admin object's management - create an object
+
+## Usage
+> Elements of the app are managed threw objects in *Admin*.
+
+> Objects of the Admin are first created and defined:
+>   * By their **title**,
+>   * By their **type**.
+
+> Then it can be configured threw:
+  * Attributes,
+  * Children.
+>
+> This documentation explains how to create an object. 
+
+### Create a new object in the admin
+> (in *Admin* > *Add new object*)
+
+<img width="664" alt="Capture d’écran 2019-04-22 à 15 57 37" src="https://user-images.githubusercontent.com/35296671/56507169-6505a500-6518-11e9-89bb-04c7fd9b41ca.png">
+<img width="450" alt="Capture d’écran 2019-04-22 à 15 58 21" src="https://user-images.githubusercontent.com/35296671/56507180-6afb8600-6518-11e9-97a5-4dcff8f0a069.png">
+
+
+* The **title** of your object will be the title displayed to your candidates. Use an intellegible title for your user.
+  > NB: you can always edit it in the *Admin*
+
+* The **type** depends on the nature of your object:
+  * **Campus** is used to declare a school.
+    * Examples: *Alem*, *Madeira*, etc.
+    * Campus can contains cursus: *Alem* contains for example *01-classical* and *Piscine Go*.
+  * **Cursus** is used to declare a course. 
+    * Examples: *01-classical*, *Piscine Go*, etc.
+    * Cursuses can contains cursuses: the main cursus *01-classical*, for example, contains cursuses like *Piscine Go*, but also all the branches that the student have access to, as *Web*, *Security*, *Algorythm*, *Design*, etc.
+    * Cursuses can contains quests: *Piscine Go* of *01-classical* contains quests like *Quest 1* or *Quest 2*.
+  * **Quest** is used to declare a project.
+    * Examples: *Quest 1*, *Quest 2*, etc.
+    * Quest contains exercises: *Quest 1* of *Piscine Go* contains exercises like *printalphabet* or *printcomb*. 
+  * Exercise is used to declare exercises
+    * Examples: *printalphabet*, *printcomb*, *atoi*, etc.
+    * Exercises doesn't contains any children.
+  * Signup is used to declare steps of the registration.
+    * Examples: *Using our services*, *Tell us more about you*, etc.
+    * One major object *Sign up* contains all the sign up's modular steps : *Using our services*, *Tell us more about you*, etc.
+  * Onbaording is used to declare steps of the onbaording.
+    * Examples: *Toad*, *Administration*, *Additional Informations*, *Chart 01*, etc.
+    * Three main objects define the major steps of the onboarding : *Toad*, *Administration*, *Piscine*.
+    * *Administration* contains modular steps: *Additional Informations*, *Chart 01*, etc.
+
+> The child object is then available in the *Admin*. It can be found in the section of its type or thanks to the search bar of the cursus object's page.
+
+> More information is available:
+  * for setting attributes of an object: (soon available)
+  * for setting children of an object: [Child object creation](https://github.com/01-edu/public/blob/master/doc/child-object-creation.md) 
+  * for creation of modular steps in Sign up and onboarding's Administration object: [Modular step management](https://github.com/01-edu/public/blob/master/doc/modular-steps-management.md)

From b0c94e579a08d5f3fe3ca8edbc85eabde7c6b461 Mon Sep 17 00:00:00 2001
From: lfoussat <35296671+lfoussat@users.noreply.github.com>
Date: Wed, 24 Apr 2019 12:03:41 +0100
Subject: [PATCH 19/21] fix display of quotes

---
 doc/object-creation.md | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/doc/object-creation.md b/doc/object-creation.md
index cdf1b915..94329485 100644
--- a/doc/object-creation.md
+++ b/doc/object-creation.md
@@ -4,13 +4,13 @@
 > Elements of the app are managed threw objects in *Admin*.
 
 > Objects of the Admin are first created and defined:
->   * By their **title**,
->   * By their **type**.
+> * By their **title**,
+> * By their **type**.
 
 > Then it can be configured threw:
-  * Attributes,
-  * Children.
->
+> * Attributes,
+> * Children.
+
 > This documentation explains how to create an object. 
 
 ### Create a new object in the admin
@@ -48,6 +48,6 @@
 > The child object is then available in the *Admin*. It can be found in the section of its type or thanks to the search bar of the cursus object's page.
 
 > More information is available:
-  * for setting attributes of an object: (soon available)
-  * for setting children of an object: [Child object creation](https://github.com/01-edu/public/blob/master/doc/child-object-creation.md) 
-  * for creation of modular steps in Sign up and onboarding's Administration object: [Modular step management](https://github.com/01-edu/public/blob/master/doc/modular-steps-management.md)
+> * for setting attributes of an object: (soon available)
+> * for setting children of an object: [Child object creation](https://github.com/01-edu/public/blob/master/doc/child-object-creation.md) 
+> * for creation of modular steps in Sign up and onboarding's Administration object: [Modular step management](https://github.com/01-edu/public/blob/master/doc/modular-steps-management.md)

From 75741ba30c0257515045297a470ac7e57db6d8dc Mon Sep 17 00:00:00 2001
From: lfoussat <35296671+lfoussat@users.noreply.github.com>
Date: Wed, 24 Apr 2019 12:09:52 +0100
Subject: [PATCH 20/21] fix link to objectcreation & child object creation

---
 doc/modular-steps-management.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/modular-steps-management.md b/doc/modular-steps-management.md
index cd2ac6ff..1197caca 100644
--- a/doc/modular-steps-management.md
+++ b/doc/modular-steps-management.md
@@ -11,7 +11,7 @@
 
 ## Create your step child object
 ### Create a new object for your step in the admin
-> Information is available for object's creation: [Modular step management](https://github.com/01-edu/public/blob/master/doc/object-creation.md)
+> Information is available for object's creation: [Object creation](https://github.com/01-edu/public/blob/master/doc/object-creation.md)
 
 * This object must have the same type as its future parent object (*signup* or *onboarding*).
 
@@ -22,7 +22,7 @@
 
 * Edit the parent object: *Sign up* or *Administration*
 
-> Information is available for object's creation: [Modular step management](https://github.com/01-edu/public/blob/master/doc/child-object-creation.md)
+> Information is available for object's creation: [Child object creation](https://github.com/01-edu/public/blob/master/doc/child-object-creation.md)
 
 ## Settings for a `form` step
 > In the step object you have created, 2 attributes must be filled:

From 909b50f267512b2b5a2bacd6b074573b0116850f Mon Sep 17 00:00:00 2001
From: Louise Foussat <louisefoussat@gmail.com>
Date: Wed, 24 Apr 2019 14:58:26 +0100
Subject: [PATCH 21/21] corrections (you => it), and some english errors of
 vocabulary

---
 doc/child-object-creation.md    |  2 +-
 doc/modular-steps-management.md | 30 +++++++++++++++---------------
 doc/object-creation.md          |  4 ++--
 3 files changed, 18 insertions(+), 18 deletions(-)

diff --git a/doc/child-object-creation.md b/doc/child-object-creation.md
index c14166b3..45c8d7e8 100644
--- a/doc/child-object-creation.md
+++ b/doc/child-object-creation.md
@@ -29,5 +29,5 @@
 > Your step is then related to its parent. You can see it in the *Children* section of the parent's object. There, you can now: 
 > * Delete the child from its parent (the actual object of your child will not be deleted).
 > * Reorder it in the children's list, by dragging it to the place you want.
-> * Go to update its settings by clicking on the eye of its reference (it will redirect you to the actual object of your step).
+> * Update its original settings by clicking on the eye icon of its reference (redirection to object edit page of the child).
 <img width="1229" alt="Capture d’écran 2019-04-22 à 19 51 12" src="https://user-images.githubusercontent.com/35296671/56518936-a1e19400-6538-11e9-81c7-520ffd365cff.png">
diff --git a/doc/modular-steps-management.md b/doc/modular-steps-management.md
index 1197caca..ccaf253c 100644
--- a/doc/modular-steps-management.md
+++ b/doc/modular-steps-management.md
@@ -38,23 +38,23 @@
 
 * Add a new key **subtype** of type `String` with the exact value 'onb-adm-form-generator'
 * Add a new key **form** of type `Object` 
-  * The form you are creating can have several sections. Each section is displayed with a title, and its inputs. 
-    > NB: The submission of the form will check the required inputs of all the sections you have created for the form. 
-  * To create a section, add a new key to your form object, of type `Object`, that contains:
-    * A **title** key of type `String`. The value of this property will be the title displayed in the top of your form section. 
-      > If you have only one section in your form step, and you don't need a section title, you do not have to set up this property.
+  * Form can have several sections. Each section is displayed with a title, and its inputs. 
+    > NB: The submission of the form will check the required inputs of all the sections created for the form. 
+  * To create a section, add a new key to the form object, of type `Object`, that contains:
+    * A **title** key of type `String`. The value of this property will be the title displayed in the top of the form section. 
+      > If there is only one section in the form step, and no section title is needed, this property can be ignored.
     * An **inputs** key of type `Object`, which will contain all the inputs of the section. For each wanted input, add a new `Object` element in the "inputs" object.
       > The key of this object will be used as the "name" attribute of your input.  
       > The values will be considered as the properties of your input.
 
 #### Defining an input:
-* You must declare a **type** key of type `String`, which define the type of your input : `tel`, `text`, `date`, `select`, `radio`, `switch`, `checkbox`, `textarea` (and soon a special type `countries`). 
-* Then you can fill the props you need for your input, according to its type: `placeholder`, `id`, `required`, `label`, `items`, `emptyItems`, `index`, etc...
+* A **type** key of type `String` must be declared. It defines the type of the input : `tel`, `text`, `date`, `select`, `radio`, `switch`, `checkbox`, `textarea` (and soon a special type `countries`). 
+* All other attributes needed for the input can be added to the object, according to the input type: `placeholder`, `id`, `required`, `label`, `items`, `emptyItems`, `index`, etc...
 
 #### Important indication: 
-* The **index** property is used to order your inputs. It will not be passed onto the input. Be mindful not to set the same index twice.
-* The **type** property is required. It will be used to determine the kind of input we must generate. It is passed onto the input only if the input type attribute is required (type 'tel' or 'text' for example, but not for type 'select' - in this case, we will generate a select element)
-  * At the moment, we are creating a special type 'countries' (a `Select` displaying all the countries). Documentation will be updated as soon as it is available.
+* The **index** property is used to order the inputs. It will not be passed onto the input. Be mindful not to set the same index twice.
+* The **type** property is required. It will be used to determine the kind of input should be generated. It is passed onto the input only if the input type attribute is required (type 'tel' or 'text' for example, but not for type 'select' - in this case, we will generate a select element)
+  * At the moment, our team is creating a special type 'countries' (a `Select` displaying all the countries). Documentation will be updated as soon as it is available.
 * `onChange` prop are ignored as the event is handled by the app.
 * For `switch` and `checkbox` input types, the default value has to be set as a boolean property named **value**.
 * More information for each inputs is available in the design documentation: 
@@ -178,12 +178,12 @@ The newly created child can be customized with these attributes :
 3. Add the following attributes:
    * Add a new key **subtype** of type `String` with the exact value 'onb-adm-sign'
    * Add a new key **text** of type `String` with the text of your document to sign as value
-   * Add a new key **buttonText** of type `String` with the text that you want to display in the submit button of your step. If you do not fill this property, the default value is 'Sign'.
-   * Add a new key **checkbox** of type `Object`, if you want to force your user to click on a checkbox before validating his document (ex: 'I have read and accepted the conditions'). In the checkbox object, you should define:
-     * A **label** key of type `String`, with the text you want to associate to the checkbox
-     * A **required** key of type `Boolean`, set at true if you want to force the user to check it
+   * Add a new key **buttonText** of type `String` with the text that you want to display in the submit button of your step. Default value for this attribute is 'Sign'.
+   * Add a new key **checkbox** of type `Object`, if the user has to be forced to click on a checkbox before validating his document (ex: 'I have read and accepted the conditions'). In the checkbox object, the following attributes should be defined:
+     * A **label** key of type `String`, for the text associated to the checkbox
+     * A **required** key of type `Boolean`, set at true if the user has to check it
      * A **name** key of type `String`
-     * Then you can add all other properties you want to your checkbox.
+     * All other attributes wanted for the checkbox.
 
 ### Examples
 
diff --git a/doc/object-creation.md b/doc/object-creation.md
index 94329485..1fa5d31f 100644
--- a/doc/object-creation.md
+++ b/doc/object-creation.md
@@ -1,13 +1,13 @@
 # Admin object's management - create an object
 
 ## Usage
-> Elements of the app are managed threw objects in *Admin*.
+> Elements of the app are managed through objects in *Admin*.
 
 > Objects of the Admin are first created and defined:
 > * By their **title**,
 > * By their **type**.
 
-> Then it can be configured threw:
+> Then it can be configured through:
 > * Attributes,
 > * Children.