@supersoniks/concorde 3.0.12 → 3.1.1

package/src/docs/search/docs-search.json

@@ -2144,6 +2144,21 @@
       }
     }
   },
+  {
+    "search": "Displays an indicator showing the completion progress of a task.\n",
+    "files": {
+      "core/components/ui/progress/progress.md": {
+        "title": "Progress bar",
+        "hashes": {
+          "progress-bar": {
+            "count": 1,
+            "title": "",
+            "type": "paragraph"
+          }
+        }
+      }
+    }
+  },
   {
     "search": "Table",
     "files": {
@@ -2190,14 +2205,14 @@
     }
   },
   {
-    "search": "A scroll bar is automatically added if the content if is wider than the table width\n",
+    "search": "Every table is responsive by default\n",
     "files": {
       "core/components/ui/table/table.md": {
         "title": "Table",
         "hashes": {
-          "scroll-x": {
+          "responsive": {
             "count": 1,
-            "title": "Scroll-x",
+            "title": "Responsive",
             "type": "paragraph"
           }
         }
@@ -2219,6 +2234,21 @@
       }
     }
   },
+  {
+    "search": "By default, tooltip is centered next to its content\n",
+    "files": {
+      "core/components/ui/tooltip/tooltip.md": {
+        "title": "Tooltip",
+        "hashes": {
+          "placement": {
+            "count": 1,
+            "title": "Placement",
+            "type": "paragraph"
+          }
+        }
+      }
+    }
+  },
   {
     "search": "lit + tailwind + vite",
     "files": {
@@ -2460,12 +2490,12 @@
     }
   },
   {
-    "search": "🔔 The subscriber mixin",
+    "search": "The subscriber mixin",
     "files": {
       "docs/_core-concept/subscriber.md": {
-        "title": "🔔 The subscriber mixin",
+        "title": "The subscriber mixin",
         "hashes": {
-          "-the-subscriber-mixin": {
+          "the-subscriber-mixin": {
             "count": 1,
             "title": "",
             "type": "page"
@@ -2478,9 +2508,9 @@
     "search": "This is a mixin that is commonly extended by Concorde core components and destination components. Pure UI components usually don't extend it, especially those outside of form components.\n",
     "files": {
       "docs/_core-concept/subscriber.md": {
-        "title": "🔔 The subscriber mixin",
+        "title": "The subscriber mixin",
         "hashes": {
-          "-the-subscriber-mixin": {
+          "the-subscriber-mixin": {
             "count": 1,
             "title": "",
             "type": "paragraph"
@@ -2493,7 +2523,7 @@
     "search": "Upon being added to the DOM (connectedCallback), subscribers search for the first occurrence of the dataProvider attribute in their parent's HTML structure.\n",
     "files": {
       "docs/_core-concept/subscriber.md": {
-        "title": "🔔 The subscriber mixin",
+        "title": "The subscriber mixin",
         "hashes": {
           "dataprovider-attribute-automatic-filling-of-subscriber-properties": {
             "count": 1,
@@ -2508,7 +2538,7 @@
     "search": "The value of this attribute is used to obtain a publisher via the PublisherManager (see 🥨 Sharing Data).\n",
     "files": {
       "docs/_core-concept/subscriber.md": {
-        "title": "🔔 The subscriber mixin",
+        "title": "The subscriber mixin",
         "hashes": {
           "dataprovider-attribute-automatic-filling-of-subscriber-properties": {
             "count": 1,
@@ -2523,7 +2553,7 @@
     "search": "The subscriber then subscribes to the publisher as a data template to be filled.\n",
     "files": {
       "docs/_core-concept/subscriber.md": {
-        "title": "🔔 The subscriber mixin",
+        "title": "The subscriber mixin",
         "hashes": {
           "dataprovider-attribute-automatic-filling-of-subscriber-properties": {
             "count": 1,
@@ -2538,7 +2568,7 @@
     "search": "The reactive properties of the component reflect in real-time the properties with the same name in the publisher.\n",
     "files": {
       "docs/_core-concept/subscriber.md": {
-        "title": "🔔 The subscriber mixin",
+        "title": "The subscriber mixin",
         "hashes": {
           "dataprovider-attribute-automatic-filling-of-subscriber-properties": {
             "count": 1,
@@ -2553,7 +2583,7 @@
     "search": "This functionality is commonly used in the generic components fetch, queue, and list.\n",
     "files": {
       "docs/_core-concept/subscriber.md": {
-        "title": "🔔 The subscriber mixin",
+        "title": "The subscriber mixin",
         "hashes": {
           "dataprovider-attribute-automatic-filling-of-subscriber-properties": {
             "count": 1,
@@ -2568,7 +2598,7 @@
     "search": "If the subscriber is inside another subscriber, it can subscribe to a data of its parent using the attribute subDataProvider = 'address.of.my.data' instead of the parent's data. This allows for dynamic behavior.\n",
     "files": {
       "docs/_core-concept/subscriber.md": {
-        "title": "🔔 The subscriber mixin",
+        "title": "The subscriber mixin",
         "hashes": {
           "dataprovider-attribute-automatic-filling-of-subscriber-properties": {
             "count": 1,
@@ -2583,7 +2613,7 @@
     "search": "In a similar manner, searching for ancestor attributes can be used to configure automatic translation for any property starting with "wording" and ending with a label identifier recognized by the wordingProvider API.\n",
     "files": {
       "docs/_core-concept/subscriber.md": {
-        "title": "🔔 The subscriber mixin",
+        "title": "The subscriber mixin",
         "hashes": {
           "automated-translation": {
             "count": 1,
@@ -2598,7 +2628,7 @@
     "search": "Normally, this API is globally configured and not within the component. Therefore, remember to prefix translatable label identifiers present in the ticketing system, for example, with "wording".\n",
     "files": {
       "docs/_core-concept/subscriber.md": {
-        "title": "🔔 The subscriber mixin",
+        "title": "The subscriber mixin",
         "hashes": {
           "automated-translation": {
             "count": 1,
@@ -2613,7 +2643,7 @@
     "search": "The value of this property can be provided as a JSON object or any other value. This value is then assigned to the associated publisher via the dataProvider attribute. As a result, the reactive properties of all subscribers associated with the same dataProvider are filled as mentioned above.\n",
     "files": {
       "docs/_core-concept/subscriber.md": {
-        "title": "🔔 The subscriber mixin",
+        "title": "The subscriber mixin",
         "hashes": {
           "reactive-property-props": {
             "count": 1,
@@ -2628,7 +2658,7 @@
     "search": "It is possible to disable the automatic filling of reactive properties in a particular component. To do so, set the variable noAutoFill = true in the component's class. However, the reactive property props will still be updated.\n",
     "files": {
       "docs/_core-concept/subscriber.md": {
-        "title": "🔔 The subscriber mixin",
+        "title": "The subscriber mixin",
         "hashes": {
           "disabling-automatic-filling-of-reactive-properties": {
             "count": 1,
@@ -2643,7 +2673,7 @@
     "search": "For example, sonic-subscriber and sonic-fetch have this attribute because they do not have reactive properties.\n",
     "files": {
       "docs/_core-concept/subscriber.md": {
-        "title": "🔔 The subscriber mixin",
+        "title": "The subscriber mixin",
         "hashes": {
           "disabling-automatic-filling-of-reactive-properties": {
             "count": 1,
@@ -2658,7 +2688,7 @@
     "search": "☢ CAUTION: When creating an object of type Subscriber or Fetcher, make sure to use the mixins and not directly extend the concrete fetch component (sonic-fetch) and subscriber component (sonic-subscriber). This is because the noAutofill = true attribute is set in those components.\n",
     "files": {
       "docs/_core-concept/subscriber.md": {
-        "title": "🔔 The subscriber mixin",
+        "title": "The subscriber mixin",
         "hashes": {
           "disabling-automatic-filling-of-reactive-properties": {
             "count": 1,
@@ -2673,7 +2703,7 @@
     "search": "TIPS: \nIf you disable automatic filling, you will likely make the rendering dynamic by writing expressions like this.props.my.subproperty. If props is updated, the rendering will be triggered. However, if this.props.my.subproperty is directly modified, the rendering will not be triggered. To achieve more reactivity, you can enable rendering when any subproperty is modified. Simply set the variable renderOnPropsInternalChange = true in the class that implements the corresponding mixin.\n",
     "files": {
       "docs/_core-concept/subscriber.md": {
-        "title": "🔔 The subscriber mixin",
+        "title": "The subscriber mixin",
         "hashes": {
           "disabling-automatic-filling-of-reactive-properties": {
             "count": 1,
@@ -2688,7 +2718,7 @@
     "search": "Suppose that:\n",
     "files": {
       "docs/_core-concept/subscriber.md": {
-        "title": "🔔 The subscriber mixin",
+        "title": "The subscriber mixin",
         "hashes": {
           "data-binding": {
             "count": 1,
@@ -2703,7 +2733,7 @@
     "search": "This example also illustrates:\n",
     "files": {
       "docs/_core-concept/subscriber.md": {
-        "title": "🔔 The subscriber mixin",
+        "title": "The subscriber mixin",
         "hashes": {
           "data-binding": {
             "count": 1,
@@ -2718,7 +2748,7 @@
     "search": "Note: Data binding implies that updating the img.src data via the publisher will change the photo without any additional calls.\n",
     "files": {
       "docs/_core-concept/subscriber.md": {
-        "title": "🔔 The subscriber mixin",
+        "title": "The subscriber mixin",
         "hashes": {
           "data-binding": {
             "count": 1,
@@ -2733,7 +2763,7 @@
     "search": "Special Variables:\n",
     "files": {
       "docs/_core-concept/subscriber.md": {
-        "title": "🔔 The subscriber mixin",
+        "title": "The subscriber mixin",
         "hashes": {
           "data-binding": {
             "count": 1,
@@ -2748,7 +2778,7 @@
     "search": "Disabling this functionality:\nYou can disable data binding if it is not needed by calling DataBinding.disable().\n",
     "files": {
       "docs/_core-concept/subscriber.md": {
-        "title": "🔔 The subscriber mixin",
+        "title": "The subscriber mixin",
         "hashes": {
           "data-binding": {
             "count": 1,
@@ -2760,10 +2790,10 @@
     }
   },
   {
-    "search": "installation",
+    "search": "Installation",
     "files": {
       "docs/_getting-started/concorde-outside.md": {
-        "title": "installation",
+        "title": "Installation",
         "hashes": {
           "installation": {
             "count": 1,
@@ -2775,25 +2805,10 @@
     }
   },
   {
-    "search": "The easiest way to use Concorde is by using the Concorde starter.\n",
-    "files": {
-      "docs/_getting-started/concorde-outside.md": {
-        "title": "installation",
-        "hashes": {
-          "starter": {
-            "count": 1,
-            "title": "Starter",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "The following command creates a new Vite project in TypeScript mode with Tailwind and an example component to get started.\n",
+    "search": "The easiest way to use Concorde is by using the Concorde starter.The following command creates a new Vite project in TypeScript mode with Tailwind and an example component to get started.\n",
     "files": {
       "docs/_getting-started/concorde-outside.md": {
-        "title": "installation",
+        "title": "Installation",
         "hashes": {
           "starter": {
             "count": 1,
@@ -2808,11 +2823,11 @@
     "search": "For a more manual configuration, you can refer to the following sections. \nHowever, the Tailwind configuration is not mentioned at the moment.\n",
     "files": {
       "docs/_getting-started/concorde-outside.md": {
-        "title": "installation",
+        "title": "Installation",
         "hashes": {
-          "starter": {
+          "brand-new-vite-project": {
             "count": 1,
-            "title": "Starter",
+            "title": "Brand New Vite Project",
             "type": "paragraph"
           }
         }
@@ -2823,7 +2838,7 @@
     "search": "Using Lit with TypeScript requires the following configuration in the "compilerOptions" section of the tsconfig.json file:\n",
     "files": {
       "docs/_getting-started/concorde-outside.md": {
-        "title": "installation",
+        "title": "Installation",
         "hashes": {
           "creating-the-project": {
             "count": 1,
@@ -2838,7 +2853,7 @@
     "search": "Navigate to the project folder created and perform the installation:\n",
     "files": {
       "docs/_getting-started/concorde-outside.md": {
-        "title": "installation",
+        "title": "Installation",
         "hashes": {
           "installing-concorde": {
             "count": 1,
@@ -2853,7 +2868,7 @@
     "search": "Shortcut imports work by default in JavaScript, but in TypeScript, they are activated by choice as they inject data into tsconfig.json. Here is the command:\n",
     "files": {
       "docs/_getting-started/concorde-outside.md": {
-        "title": "installation",
+        "title": "Installation",
         "hashes": {
           "shortcut-imports": {
             "count": 1,
@@ -2868,7 +2883,7 @@
     "search": "Shortcut imports replace the actual paths with aliases as follows:\n",
     "files": {
       "docs/_getting-started/concorde-outside.md": {
-        "title": "installation",
+        "title": "Installation",
         "hashes": {
           "shortcut-imports": {
             "count": 1,
@@ -2883,7 +2898,7 @@
     "search": "The original paths remain accessible. Shortcut imports are used for the examples later in this documentation.\n",
     "files": {
       "docs/_getting-started/concorde-outside.md": {
-        "title": "installation",
+        "title": "Installation",
         "hashes": {
           "shortcut-imports": {
             "count": 1,
@@ -2895,10 +2910,10 @@
     }
   },
   {
-    "search": "For example, to use a button:\nIn main.ts or main.js to be compiled:\n",
+    "search": "Import needed component in main.ts or wherever you want to use it:\n",
     "files": {
       "docs/_getting-started/concorde-outside.md": {
-        "title": "installation",
+        "title": "Installation",
         "hashes": {
           "simple-integration-in-html": {
             "count": 1,
@@ -2910,10 +2925,10 @@
     }
   },
   {
-    "search": "In the HTML of a JS or TS component or in the HTML of the web page that includes the compiled JS:\n",
+    "search": "Then in the render function ofyour component or in the HTML of the web page that includes the compiled JS, use the component as follows:\n",
     "files": {
       "docs/_getting-started/concorde-outside.md": {
-        "title": "installation",
+        "title": "Installation",
         "hashes": {
           "simple-integration-in-html": {
             "count": 1,
@@ -2928,7 +2943,7 @@
     "search": "For example, create a file my-element.ts at the root:\n",
     "files": {
       "docs/_getting-started/concorde-outside.md": {
-        "title": "installation",
+        "title": "Installation",
         "hashes": {
           "using-a-mixin-to-create-a-new-lit-component": {
             "count": 1,
@@ -2943,7 +2958,7 @@
     "search": "@customElement("my-element")\nexport class SonicComponent extends Fetcher(Subscriber(LitElement)) {\n  @property() email = "";\n  @property() first_name = "";\n  @property() last_name = "";\n",
     "files": {
       "docs/_getting-started/concorde-outside.md": {
-        "title": "installation",
+        "title": "Installation",
         "hashes": {
           "using-a-mixin-to-create-a-new-lit-component": {
             "count": 1,
@@ -2958,7 +2973,7 @@
     "search": "  render() {\n    return html<div>       ${this.first_name} ${this.last_name} : ${this.email}     </div>;\n  }\n}\n  \n\n",
     "files": {
       "docs/_getting-started/concorde-outside.md": {
-        "title": "installation",
+        "title": "Installation",
         "hashes": {
           "using-a-mixin-to-create-a-new-lit-component": {
             "count": 1,
@@ -2970,10 +2985,10 @@
     }
   },
   {
-    "search": "In main.ts or main.js or any other component that uses it to be compiled\n",
+    "search": "Import component main.ts or main.js or any other component that uses it to be compiled\n",
     "files": {
       "docs/_getting-started/concorde-outside.md": {
-        "title": "installation",
+        "title": "Installation",
         "hashes": {
           "using-a-mixin-to-create-a-new-lit-component": {
             "count": 1,
@@ -2988,7 +3003,7 @@
     "search": "In the HTML of a JS or TS component or in the HTML of the web page containing the compiled JS:\n",
     "files": {
       "docs/_getting-started/concorde-outside.md": {
-        "title": "installation",
+        "title": "Installation",
         "hashes": {
           "using-a-mixin-to-create-a-new-lit-component": {
             "count": 1,
@@ -3000,12 +3015,12 @@
     }
   },
   {
-    "search": "🧱 Creating components",
+    "search": "Creating components",
     "files": {
       "docs/_getting-started/create-a-component.md": {
-        "title": "🧱 Creating components",
+        "title": "Creating components",
         "hashes": {
-          "-creating-components": {
+          "creating-components": {
             "count": 1,
             "title": "",
             "type": "page"
@@ -3018,7 +3033,7 @@
     "search": "In this document, we consider the src directory of the project as the root.\nWe describe how we organize our components as an example, however it depends on your project.\n",
     "files": {
       "docs/_getting-started/create-a-component.md": {
-        "title": "🧱 Creating components",
+        "title": "Creating components",
         "hashes": {
           "where-to-put-it": {
             "count": 1,
@@ -3033,7 +3048,7 @@
     "search": "In concorde each component is currently organized in the following directory structure (at least we try):\n",
     "files": {
       "docs/_getting-started/create-a-component.md": {
-        "title": "🧱 Creating components",
+        "title": "Creating components",
         "hashes": {
           "where-to-put-it": {
             "count": 1,
@@ -3048,7 +3063,7 @@
     "search": "You can copy example.ts from the source to the desired destination to start with.\nThis file contains a web component in the form of a class that extends the Subscriber mixin, with a reactive property and a render function.\n",
     "files": {
       "docs/_getting-started/create-a-component.md": {
-        "title": "🧱 Creating components",
+        "title": "Creating components",
         "hashes": {
           "starting-from-a-simple-model": {
             "count": 1,
@@ -3063,7 +3078,7 @@
     "search": "@customElement("sonic-example")\nexport class SonicComponent extends Subscriber(LitElement) {\n  @property() text = "Example";\n  render() {\n    return html${this.text};\n  }\n}\n  \n\n",
     "files": {
       "docs/_getting-started/create-a-component.md": {
-        "title": "🧱 Creating components",
+        "title": "Creating components",
         "hashes": {
           "starting-from-a-simple-model": {
             "count": 1,
@@ -3078,7 +3093,7 @@
     "search": "You can remove the dependency on Subscriber if automatic population of the component with external data is not required.\nFor example, for a UI component:\n",
     "files": {
       "docs/_getting-started/create-a-component.md": {
-        "title": "🧱 Creating components",
+        "title": "Creating components",
         "hashes": {
           "starting-from-a-simple-model": {
             "count": 1,
@@ -3093,7 +3108,7 @@
     "search": "@customElement("sonic-example")\nexport class SonicComponent extends LitElement {\n  @property() text = "Example";\n  render() {\n    return html${this.text};\n  }\n}\n  \n\n",
     "files": {
       "docs/_getting-started/create-a-component.md": {
-        "title": "🧱 Creating components",
+        "title": "Creating components",
         "hashes": {
           "starting-from-a-simple-model": {
             "count": 1,
@@ -3108,7 +3123,7 @@
     "search": "Regarding Subscriber, see:\n",
     "files": {
       "docs/_getting-started/create-a-component.md": {
-        "title": "🧱 Creating components",
+        "title": "Creating components",
         "hashes": {
           "starting-from-a-simple-model": {
             "count": 1,
@@ -3123,7 +3138,7 @@
     "search": "The class name is not necessarily important. However, it is important to give it a component name prefixed with "sonic" (or a prefix of your own) using the dedicated metadata already present in the copied document. For example, a button component would be named as follows:\n",
     "files": {
       "docs/_getting-started/create-a-component.md": {
-        "title": "🧱 Creating components",
+        "title": "Creating components",
         "hashes": {
           "naming-the-component": {
             "count": 1,
@@ -3138,7 +3153,7 @@
     "search": "For less generic components with a specific destination, we advise to include the destination in the name.\nFor example, for a "title" component in the "event" destination, the name would be simply:\n",
     "files": {
       "docs/_getting-started/create-a-component.md": {
-        "title": "🧱 Creating components",
+        "title": "Creating components",
         "hashes": {
           "naming-the-component": {
             "count": 1,
@@ -3153,7 +3168,7 @@
     "search": "To do this, study the functioning of https://lit.dev and also refer to Subscriber.\n",
     "files": {
       "docs/_getting-started/create-a-component.md": {
-        "title": "🧱 Creating components",
+        "title": "Creating components",
         "hashes": {
           "creating-reactive-properties-and-modifying-the-render-function": {
             "count": 1,
@@ -3168,7 +3183,7 @@
     "search": "The HTML structure of a component should remain as simple as possible.\n",
     "files": {
       "docs/_getting-started/create-a-component.md": {
-        "title": "🧱 Creating components",
+        "title": "Creating components",
         "hashes": {
           "html-structure-of-a-component": {
             "count": 1,
@@ -3183,7 +3198,7 @@
     "search": "Ideally, there should be only one additional level of elements in addition to slots.\n",
     "files": {
       "docs/_getting-started/create-a-component.md": {
-        "title": "🧱 Creating components",
+        "title": "Creating components",
         "hashes": {
           "html-structure-of-a-component": {
             "count": 1,
@@ -3198,7 +3213,7 @@
     "search": "This leads to the creation of more components and thus raises questions about the hierarchical organization of files. However, this tends to atomize their roles.\n",
     "files": {
       "docs/_getting-started/create-a-component.md": {
-        "title": "🧱 Creating components",
+        "title": "Creating components",
         "hashes": {
           "html-structure-of-a-component": {
             "count": 1,
@@ -3213,7 +3228,7 @@
     "search": "To compile the component, it needs to be referenced somewhere through an import statement. In particular, it is important to reference it in any component that uses it.\n",
     "files": {
       "docs/_getting-started/create-a-component.md": {
-        "title": "🧱 Creating components",
+        "title": "Creating components",
         "hashes": {
           "referencing-it": {
             "count": 1,
@@ -3228,7 +3243,7 @@
     "search": "In the case where it can be directly used in a page, it should also be globally referenced, especially considering the creation of specific bundles in the future.\n",
     "files": {
       "docs/_getting-started/create-a-component.md": {
-        "title": "🧱 Creating components",
+        "title": "Creating components",
         "hashes": {
           "referencing-it": {
             "count": 1,
@@ -3243,7 +3258,7 @@
     "search": "Here's where we add imports based on the component's location inside concorde as an example\n",
     "files": {
       "docs/_getting-started/create-a-component.md": {
-        "title": "🧱 Creating components",
+        "title": "Creating components",
         "hashes": {
           "referencing-it": {
             "count": 1,
@@ -3258,7 +3273,7 @@
     "search": "As a reminder, the component is simply integrated into the context by adding a tag with the component's name, for example:\n",
     "files": {
       "docs/_getting-started/create-a-component.md": {
-        "title": "🧱 Creating components",
+        "title": "Creating components",
         "hashes": {
           "using-it": {
             "count": 1,
@@ -3270,12 +3285,117 @@
     }
   },
   {
-    "search": "🥨 Sharing data",
+    "search": "My first subscriber component",
+    "files": {
+      "docs/_getting-started/my-first-subscriber.md": {
+        "title": "My first subscriber component",
+        "hashes": {
+          "my-first-subscriber-component": {
+            "count": 1,
+            "title": "",
+            "type": "page"
+          }
+        }
+      }
+    }
+  },
+  {
+    "search": "Learn how to build a subscriber component, styled with tailwind, \nwhich could be used as a regular component or could be filled from a dataprovider.\n",
+    "files": {
+      "docs/_getting-started/my-first-subscriber.md": {
+        "title": "My first subscriber component",
+        "hashes": {
+          "my-first-subscriber-component": {
+            "count": 1,
+            "title": "",
+            "type": "paragraph"
+          }
+        }
+      }
+    }
+  },
+  {
+    "search": "First export tailwind, in a tailwind.ts file, stylesheet to add it in our component when needed.\n",
+    "files": {
+      "docs/_getting-started/my-first-subscriber.md": {
+        "title": "My first subscriber component",
+        "hashes": {
+          "style-with-tailwind-and-ui-components": {
+            "count": 1,
+            "title": "Style with tailwind and ui components",
+            "type": "paragraph"
+          }
+        }
+      }
+    }
+  },
+  {
+    "search": "Reactive properties can be filled by its attributes as a simple lit component.\n",
+    "files": {
+      "docs/_getting-started/my-first-subscriber.md": {
+        "title": "My first subscriber component",
+        "hashes": {
+          "basic-usage": {
+            "count": 1,
+            "title": "Basic usage",
+            "type": "paragraph"
+          }
+        }
+      }
+    }
+  },
+  {
+    "search": "Import Subscriber mixin, and add it around LitElement.\n\n",
+    "files": {
+      "docs/_getting-started/my-first-subscriber.md": {
+        "title": "My first subscriber component",
+        "hashes": {
+          "add-subscriber-mixin": {
+            "count": 1,
+            "title": "Add Subscriber mixin",
+            "type": "paragraph"
+          }
+        }
+      }
+    }
+  },
+  {
+    "search": "Without a dataProvider attribute, a subscriber set its own dataprovider from first ancestor found, and then reactive properties automatically filled and update from it.\nA fetcher is a simple component which set its fetch result to props of its dataprovider.\n\n",
+    "files": {
+      "docs/_getting-started/my-first-subscriber.md": {
+        "title": "My first subscriber component",
+        "hashes": {
+          "autofill-properties-from-a-dataprovider": {
+            "count": 1,
+            "title": "Autofill properties from a dataProvider",
+            "type": "paragraph"
+          }
+        }
+      }
+    }
+  },
+  {
+    "search": "A subscriber can subscribe data from anywhere in the DOM, with its dataprovider set as a provider id.\n",
+    "files": {
+      "docs/_getting-started/my-first-subscriber.md": {
+        "title": "My first subscriber component",
+        "hashes": {
+          "autofill-properties-from-a-dataprovider": {
+            "count": 1,
+            "title": "Autofill properties from a dataProvider",
+            "type": "paragraph"
+          }
+        }
+      }
+    }
+  },
+  {
+    "search": "Sharing data",
     "files": {
       "docs/_getting-started/pubsub.md": {
-        "title": "🥨 Sharing data",
+        "title": "Sharing data",
         "hashes": {
-          "-sharing-data": {
+          "sharing-data": {
             "count": 1,
             "title": "",
             "type": "page"
@@ -3288,9 +3408,9 @@
     "search": "This section describes how we share data between graphical and non graphical components and classes.\n",
     "files": {
       "docs/_getting-started/pubsub.md": {
-        "title": "🥨 Sharing data",
+        "title": "Sharing data",
         "hashes": {
-          "-sharing-data": {
+          "sharing-data": {
             "count": 1,
             "title": "",
             "type": "paragraph"
@@ -3303,9 +3423,9 @@
     "search": "Especialy, graphical components should not reference each other in order to remain decoupled.\n",
     "files": {
       "docs/_getting-started/pubsub.md": {
-        "title": "🥨 Sharing data",
+        "title": "Sharing data",
         "hashes": {
-          "-sharing-data": {
+          "sharing-data": {
             "count": 1,
             "title": "",
             "type": "paragraph"
@@ -3318,9 +3438,9 @@
     "search": "Thats why we use publish/subscribe paradigm to addresse this issue.\n",
     "files": {
       "docs/_getting-started/pubsub.md": {
-        "title": "🥨 Sharing data",
+        "title": "Sharing data",
         "hashes": {
-          "-sharing-data": {
+          "sharing-data": {
             "count": 1,
             "title": "",
             "type": "paragraph"
@@ -3333,7 +3453,7 @@
     "search": "❇️ The order of data creation and subscription theoretically has no importance.\n",
     "files": {
       "docs/_getting-started/pubsub.md": {
-        "title": "🥨 Sharing data",
+        "title": "Sharing data",
         "hashes": {
           "principle": {
             "count": 1,
@@ -3348,7 +3468,7 @@
     "search": "Denotes the identifier of a publisher as referenced in the PublisherManager (see below).\nUses the dataProvider attribut in html tags to scop the content with some data.\nsee Subscribers.\n",
     "files": {
       "docs/_getting-started/pubsub.md": {
-        "title": "🥨 Sharing data",
+        "title": "Sharing data",
         "hashes": {
           "dataprovider": {
             "count": 1,
@@ -3363,7 +3483,7 @@
     "search": "The PublisherManager is a utility class to get publishers\n",
     "files": {
       "docs/_getting-started/pubsub.md": {
-        "title": "🥨 Sharing data",
+        "title": "Sharing data",
         "hashes": {
           "publishermanager": {
             "count": 1,
@@ -3378,7 +3498,7 @@
     "search": "It plays a central role in the components, especially through the "subscriber" mixin.\nAutomatic data communication between components in concorde uses this principle in conjunction with Lit's reactive properties. \nRefer to the documentation for Subscriber.\n",
     "files": {
       "docs/_getting-started/pubsub.md": {
-        "title": "🥨 Sharing data",
+        "title": "Sharing data",
         "hashes": {
           "publishermanager": {
             "count": 1,
@@ -3393,7 +3513,7 @@
     "search": "It is declared on the window object to allow usage in a web page, so the equivalent one-liner would be:\n",
     "files": {
       "docs/_getting-started/pubsub.md": {
-        "title": "🥨 Sharing data",
+        "title": "Sharing data",
         "hashes": {
           "publishermanager": {
             "count": 1,
@@ -3408,7 +3528,7 @@
     "search": "This example can be tested in a console when Concorde is loaded on the page (for example, in a ticketing system).\nIn a component, you will need to perform an import as explained earlier.\n",
     "files": {
       "docs/_getting-started/pubsub.md": {
-        "title": "🥨 Sharing data",
+        "title": "Sharing data",
         "hashes": {
           "basic-example": {
             "count": 1,
@@ -3435,7 +3555,7 @@
     }
   },
   {
-    "search": "Based on lit.dev, Concorde is a collection of functional & UI webcomponents, created to build easily shared components, beetween apps and websites. Or even to build a website or an app from scratch.\nIt's like a toolbox to build user interfaces, faster, where everything is scoped, but preserving graphical consistency in set a few css variables.\n",
+    "search": "Based on lit.dev, Concorde is a collection of webcomponents made to build shared apps or websites.Develop user interfaces without thinking about the implementation context, where everything is scoped, but preserving graphic consistency by setting the strict minimum of css variables.\n",
     "files": {
       "docs/_getting-started/start.md": {
         "title": "Introduction",
@@ -3450,7 +3570,7 @@
     }
   },
   {
-    "search": "At Supersoniks, we've created a ticketing management system that needs shared components which could be implemented in mobile apps, modern websites, and also old ones made in php, without bundlers or whatever.Instead of creating a new library for each type of project, which would become hard to maintain, we've decided to create one shared library, that could be used in any environment and pre-bundled for legacy environment.\nWebcomponents appeared to be a the perfect solution to guarantee that compatibility with all past, present and futures stacks.\n",
+    "search": "In 2022, Supersoniks wanted to create a new version of his ticketing app, in production un nearly 100 websites. We needed shared components which could be implemented in mobile apps, modern websites, and also old ones made in php, without bundlers or whatever.Instead of building a new app for each type of project, which would become impossible to maintain, we've decided to create one app, composed by a few webcomponents wich could easily be recomposed on any website.\nWebcomponents appeared to be a the perfect solution to guarantee that compatibility with all past, present and futures environment, and lit seemed to be the best choice to build them.\n",
     "files": {
       "docs/_getting-started/start.md": {
         "title": "Introduction",
@@ -3465,14 +3585,14 @@
     }
   },
   {
-    "search": "A new project with Vite, Typescript and Tailwind already configured and a simple example of a subscriber component :  \n",
+    "search": "A new project with Vite, Typescript and Tailwind already configured and a simple example of a subscriber component : \n",
     "files": {
       "docs/_getting-started/start.md": {
         "title": "Introduction",
         "hashes": {
-          "start-a-new-project-from-scratch-": {
+          "start-a-new-project-easily": {
             "count": 1,
-            "title": "Start a new project from scratch ?",
+            "title": "Start a new project easily",
             "type": "paragraph"
           }
         }