@supersoniks/concorde 3.2.1 → 3.2.2

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

@@ -1,3917 +0,0 @@
-[
-  {
-    "search": "Date",
-    "files": {
-      "core/components/functional/date/date.md": {
-        "title": "Date",
-        "hashes": {
-          "date": {
-            "count": 2,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Nothing is displayed.\n",
-    "files": {
-      "core/components/functional/date/date.md": {
-        "title": "Date",
-        "hashes": {
-          "no-attribute": {
-            "count": 1,
-            "title": "No attribute",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Displays the current date.\n",
-    "files": {
-      "core/components/functional/date/date.md": {
-        "title": "Date",
-        "hashes": {
-          "now": {
-            "count": 1,
-            "title": "Now",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Displays a date from a timestamp.\n",
-    "files": {
-      "core/components/functional/date/date.md": {
-        "title": "Date",
-        "hashes": {
-          "date": {
-            "count": 1,
-            "title": "",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Displays a date from a string.\n",
-    "files": {
-      "core/components/functional/date/date.md": {
-        "title": "Date",
-        "hashes": {
-          "date_string": {
-            "count": 1,
-            "title": "Date_string",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Displays a period of time from start_date to end_date.When by itself start_date will act as dateif a start_date is not specified it will be set by the current date.if the end_date is anterior to start date date it will be used as the start_date. \n",
-    "files": {
-      "core/components/functional/date/date.md": {
-        "title": "Date",
-        "hashes": {
-          "start_date--end_date": {
-            "count": 1,
-            "title": "Start_date / end_date",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "ISO 639-1 Language Codes\n",
-    "files": {
-      "core/components/functional/date/date.md": {
-        "title": "Date",
-        "hashes": {
-          "language": {
-            "count": 1,
-            "title": "Language",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "For the list of supported timeZones, run Intl.supportedValuesOf('timeZone') in the console\n",
-    "files": {
-      "core/components/functional/date/date.md": {
-        "title": "Date",
-        "hashes": {
-          "time_zone": {
-            "count": 1,
-            "title": "Time_zone",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Deprecated\n",
-    "files": {
-      "core/components/functional/date/date.md": {
-        "title": "Date",
-        "hashes": {
-          "renderif": {
-            "count": 1,
-            "title": ".renderIf",
-            "type": "paragraph"
-          }
-        }
-      },
-      "core/components/functional/fetch/fetch.md": {
-        "title": "Fetch",
-        "hashes": {
-          "headersdataprovider": {
-            "count": 1,
-            "title": "HeadersDataProvider",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Fetch",
-    "files": {
-      "core/components/functional/fetch/fetch.md": {
-        "title": "Fetch",
-        "hashes": {
-          "fetch": {
-            "count": 1,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "The sonic-fetch component is used to request and store data from an API.\nFetch extends the mixins Fetcher and Subscriber\n",
-    "files": {
-      "core/components/functional/fetch/fetch.md": {
-        "title": "Fetch",
-        "hashes": {
-          "fetch": {
-            "count": 1,
-            "title": "",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "In order to work properly the sonic-fetch component needs at least the following attributes.  \n",
-    "files": {
-      "core/components/functional/fetch/fetch.md": {
-        "title": "Fetch",
-        "hashes": {
-          "basic-usage": {
-            "count": 1,
-            "title": "Basic usage",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "If no endPoint is specified it will be filled by the dataProvider ID instead  \n",
-    "files": {
-      "core/components/functional/fetch/fetch.md": {
-        "title": "Fetch",
-        "hashes": {
-          "dataprovider-as-an-endpoint": {
-            "count": 1,
-            "title": "DataProvider as an endPoint",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "When the key attribute is present, only a sub-part of the data received is injected into the dataProvider.\nWe can use the dot syntax to target what we want to keep.\n",
-    "files": {
-      "core/components/functional/fetch/fetch.md": {
-        "title": "Fetch",
-        "hashes": {
-          "key": {
-            "count": 1,
-            "title": "Key",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "For example if the data is {my:{data:{a:1,b:2}}} and the key is key="my.data", the data available in the dataProvider will be {a:1 , b:2}\n",
-    "files": {
-      "core/components/functional/fetch/fetch.md": {
-        "title": "Fetch",
-        "hashes": {
-          "key": {
-            "count": 1,
-            "title": "Key",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "if the mime type of the content returned by the service begins with text/, then the dataProvider has a key named "text" which contains the text returned by the service.\n",
-    "files": {
-      "core/components/functional/fetch/fetch.md": {
-        "title": "Fetch",
-        "hashes": {
-          "text-mode": {
-            "count": 1,
-            "title": "Text mode",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "The noLoader attribute disables display of the default loader\n",
-    "files": {
-      "core/components/functional/fetch/fetch.md": {
-        "title": "Fetch",
-        "hashes": {
-          "noloader": {
-            "count": 1,
-            "title": "NoLoader",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "if",
-    "files": {
-      "core/components/functional/if/if.md": {
-        "title": "if",
-        "hashes": {
-          "if": {
-            "count": 1,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "The sonic-if component shows its content based on the value of its reactive property names condition\n",
-    "files": {
-      "core/components/functional/if/if.md": {
-        "title": "if",
-        "hashes": {
-          "if": {
-            "count": 1,
-            "title": "",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "List",
-    "files": {
-      "core/components/functional/list/list.md": {
-        "title": "List",
-        "hashes": {
-          "list": {
-            "count": 1,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "The sonic-list component creates list items.\n",
-    "files": {
-      "core/components/functional/list/list.md": {
-        "title": "List",
-        "hashes": {
-          "list": {
-            "count": 1,
-            "title": "",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "List extends the mixins  Subscriber and Fetcher : \n",
-    "files": {
-      "core/components/functional/list/list.md": {
-        "title": "List",
-        "hashes": {
-          "list": {
-            "count": 1,
-            "title": "",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "The list component loops over its template children to render each items of its props data.Consider the following example using 2 templates and 9 items :    \n",
-    "files": {
-      "core/components/functional/list/list.md": {
-        "title": "List",
-        "hashes": {
-          "template": {
-            "count": 1,
-            "title": "Template",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Note that for each line there is a dataProvider found at [list dataProvider name]/liste-item/[line index or key]\nYou can hover the list items in the examples to see it.\n",
-    "files": {
-      "core/components/functional/list/list.md": {
-        "title": "List",
-        "hashes": {
-          "template": {
-            "count": 1,
-            "title": "Template",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "The templateKey attribute allows you to bind a template to a props item.Consider the following example :  \n",
-    "files": {
-      "core/components/functional/list/list.md": {
-        "title": "List",
-        "hashes": {
-          "templatekey--data-value": {
-            "count": 1,
-            "title": "TemplateKey / data-value",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "A special template with attribute data-value="separator" will act as a separator between each list item\n",
-    "files": {
-      "core/components/functional/list/list.md": {
-        "title": "List",
-        "hashes": {
-          "special-templates--list-item-separator--empty-list-view": {
-            "count": 1,
-            "title": "Special templates : list item separator / empty list view",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "The same principle can be used to handle empty lists using a template with attribute data-value="no-item"\n",
-    "files": {
-      "core/components/functional/list/list.md": {
-        "title": "List",
-        "hashes": {
-          "special-templates--list-item-separator--empty-list-view": {
-            "count": 1,
-            "title": "Special templates : list item separator / empty list view",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Enables the list to get data from an external API in order to fill its props attribute with an array of items\nSee the [Fetch] web component(#core/components/functional/fetch/fetch.md/fetch)\n\n",
-    "files": {
-      "core/components/functional/list/list.md": {
-        "title": "List",
-        "hashes": {
-          "fetch": {
-            "count": 1,
-            "title": "Fetch",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Example of using the extractValues attribute with a service.\nAs in the previous example, the fetch attribute indicates that a service call should be made.\nNote that we use:\n",
-    "files": {
-      "core/components/functional/list/list.md": {
-        "title": "List",
-        "hashes": {
-          "extract-values": {
-            "count": 1,
-            "title": "Extract Values",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Mix",
-    "files": {
-      "core/components/functional/mix/mix.md": {
-        "title": "Mix",
-        "hashes": {
-          "mix": {
-            "count": 1,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Mix allows you to mix several subsets of dataProvider in a new key/value structure which is itself associated with a new dataProvider. The data update is then bidirectional.\n",
-    "files": {
-      "core/components/functional/mix/mix.md": {
-        "title": "Mix",
-        "hashes": {
-          "mix": {
-            "count": 1,
-            "title": "",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Dot notation is supported to extract a sub-part of the data.\n",
-    "files": {
-      "core/components/functional/mix/mix.md": {
-        "title": "Mix",
-        "hashes": {
-          "mix": {
-            "count": 1,
-            "title": "",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "For example, if we declare dataproviders as follows :\n\nWe can rearrange the data as follows\n\nThen we can change values in both dataProviders programaticaly this way, they will stay in sync\n\nOr by using a form element\n\n",
-    "files": {
-      "core/components/functional/mix/mix.md": {
-        "title": "Mix",
-        "hashes": {
-          "mix": {
-            "count": 1,
-            "title": "",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Queue",
-    "files": {
-      "core/components/functional/queue/queue.md": {
-        "title": "Queue",
-        "hashes": {
-          "queue": {
-            "count": 1,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "sonic-queue loads content in batches based on the expression provided in the dataProviderExpression attribute.\n",
-    "files": {
-      "core/components/functional/queue/queue.md": {
-        "title": "Queue",
-        "hashes": {
-          "queue": {
-            "count": 1,
-            "title": "",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "List extends the mixin Subscriber\n",
-    "files": {
-      "core/components/functional/queue/queue.md": {
-        "title": "Queue",
-        "hashes": {
-          "queue": {
-            "count": 1,
-            "title": "",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Router",
-    "files": {
-      "core/components/functional/router/router.md": {
-        "title": "Router",
-        "hashes": {
-          "router": {
-            "count": 1,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "The router observes the document.location changes and updates its view as follows\n",
-    "files": {
-      "core/components/functional/router/router.md": {
-        "title": "Router",
-        "hashes": {
-          "router": {
-            "count": 1,
-            "title": "",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "When the data-route attribute of a template matches the current url, the content of this template is rendered\n",
-    "files": {
-      "core/components/functional/router/router.md": {
-        "title": "Router",
-        "hashes": {
-          "data-route--basic": {
-            "count": 1,
-            "title": "Data-route / Basic",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "You can use any RegExp in the data-route attribute of your templates to match the current location and to extract variables from it using capturing groups.\nA dataProvider attribute is generated using the dataProviderExpression where $1, $2... are replaced with this variables.\n",
-    "files": {
-      "core/components/functional/router/router.md": {
-        "title": "Router",
-        "hashes": {
-          "data-route--regexp": {
-            "count": 1,
-            "title": "Data-route / Regexp",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "e.g., data-route="#couleur_(\\d+)" => dataProviderExpression="api/unknown/$1"\n",
-    "files": {
-      "core/components/functional/router/router.md": {
-        "title": "Router",
-        "hashes": {
-          "data-route--regexp": {
-            "count": 1,
-            "title": "Data-route / Regexp",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "The rendered content of the matching template is scoped with this  dataProvider.\nYou can make creative usage on this feature to generate dynamic content based on services.\n",
-    "files": {
-      "core/components/functional/router/router.md": {
-        "title": "Router",
-        "hashes": {
-          "data-route--regexp": {
-            "count": 1,
-            "title": "Data-route / Regexp",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Same as RegExp but using url patternse.g., data-route="#couleur_:id" => dataProviderExpression="api/unknown/:id"\n",
-    "files": {
-      "core/components/functional/router/router.md": {
-        "title": "Router",
-        "hashes": {
-          "data-route--url-pattern": {
-            "count": 1,
-            "title": "Data-route / Url-pattern",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Redirect allows to redirect to a url when a data is provided.\nHere Redirect waits that a data is available in the property theData of the dataProvider stupid-data-set-id\nWe are then redirected to the url #data-is-set which does nothing in itself.\n",
-    "files": {
-      "core/components/functional/router/router.md": {
-        "title": "Router",
-        "hashes": {
-          "redirect": {
-            "count": 1,
-            "title": "Redirect",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Example of use : use with a router and a submit to manage the steps of login/logout, display of user info.\n",
-    "files": {
-      "core/components/functional/router/router.md": {
-        "title": "Router",
-        "hashes": {
-          "redirect": {
-            "count": 1,
-            "title": "Redirect",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "The fallback route is rendered when no other route matches the current location.\n",
-    "files": {
-      "core/components/functional/router/router.md": {
-        "title": "Router",
-        "hashes": {
-          "fallback": {
-            "count": 1,
-            "title": "Fallback",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "SDUI",
-    "files": {
-      "core/components/functional/sdui/sdui.md": {
-        "title": "SDUI",
-        "hashes": {
-          "sdui": {
-            "count": 1,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "SDUI stands for Server Driven User Interfaces.\nBasically, it generates a user interface based on a JSON SDUI Descriptor.\n",
-    "files": {
-      "core/components/functional/sdui/sdui.md": {
-        "title": "SDUI",
-        "hashes": {
-          "what-is-sdui": {
-            "count": 1,
-            "title": "What is SDUI?",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "SDUI extends the mixin Subscriber.\nThis means that you must set a dataProvider with an id pointing to the publisher that will hold your SDUI Descriptor.\nThis also means that it has a reactive property named props that you can set with the JSON SDUI Descriptor in order to configure it.\n",
-    "files": {
-      "core/components/functional/sdui/sdui.md": {
-        "title": "SDUI",
-        "hashes": {
-          "subscriber-extension": {
-            "count": 1,
-            "title": "Subscriber extension:",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "SDUI extends the mixin Fetcher as Fetch and List.\n",
-    "files": {
-      "core/components/functional/sdui/sdui.md": {
-        "title": "SDUI",
-        "hashes": {
-          "fetcher-extension": {
-            "count": 1,
-            "title": "Fetcher extension:",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "In this case, it will parse the JSON coming from the request.\nThe JSON must comply with the SDUI descriptor format.\n",
-    "files": {
-      "core/components/functional/sdui/sdui.md": {
-        "title": "SDUI",
-        "hashes": {
-          "fetcher-extension": {
-            "count": 1,
-            "title": "Fetcher extension:",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "As a fetcher, invalidating the publisher or updating the endpoint will trigger a new fetch and update accordingly.\n",
-    "files": {
-      "core/components/functional/sdui/sdui.md": {
-        "title": "SDUI",
-        "hashes": {
-          "fetcher-extension": {
-            "count": 1,
-            "title": "Fetcher extension:",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "It has no shadowdom, and its display style is set to contents, so an empty SDUI has the fewest impact on the layout.\n",
-    "files": {
-      "core/components/functional/sdui/sdui.md": {
-        "title": "SDUI",
-        "hashes": {
-          "rendering": {
-            "count": 1,
-            "title": "Rendering:",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "An SDUINode represents an HTMLElement.\n",
-    "files": {
-      "core/components/functional/sdui/sdui.md": {
-        "title": "SDUI",
-        "hashes": {
-          "descriptor": {
-            "count": 1,
-            "title": "Descriptor",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "TypeScript definition:\n",
-    "files": {
-      "core/components/functional/sdui/sdui.md": {
-        "title": "SDUI",
-        "hashes": {
-          "descriptor": {
-            "count": 1,
-            "title": "Descriptor",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Summary of properties:\n",
-    "files": {
-      "core/components/functional/sdui/sdui.md": {
-        "title": "SDUI",
-        "hashes": {
-          "descriptor": {
-            "count": 1,
-            "title": "Descriptor",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Use it if you prefer to define your node entirely using an HTML string.\n",
-    "files": {
-      "core/components/functional/sdui/sdui.md": {
-        "title": "SDUI",
-        "hashes": {
-          "markup": {
-            "count": 1,
-            "title": "Markup",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Here we use the field tagName of SDUINode to create an element with tag name sonic-input.\n",
-    "files": {
-      "core/components/functional/sdui/sdui.md": {
-        "title": "SDUI",
-        "hashes": {
-          "tag-name": {
-            "count": 1,
-            "title": "Tag name",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "A string key/value pair storing each attribute name/value of the HTML element created.\nAs no tag name is defined, a div element is created.\nHere we define the style attribute to create a tiny red square.\n",
-    "files": {
-      "core/components/functional/sdui/sdui.md": {
-        "title": "SDUI",
-        "hashes": {
-          "attributes": {
-            "count": 1,
-            "title": "Attributes",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Children of the current node can be added using the field nodes recursively.\n",
-    "files": {
-      "core/components/functional/sdui/sdui.md": {
-        "title": "SDUI",
-        "hashes": {
-          "nodes": {
-            "count": 1,
-            "title": "Nodes",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "As no tag name is defined, a div element is created, and then we use innerHTML to add content to it.\n",
-    "files": {
-      "core/components/functional/sdui/sdui.md": {
-        "title": "SDUI",
-        "hashes": {
-          "innerhtml": {
-            "count": 1,
-            "title": "InnerHTML",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Use them if you want to wrap the component with some HTML string.\n",
-    "files": {
-      "core/components/functional/sdui/sdui.md": {
-        "title": "SDUI",
-        "hashes": {
-          "prefix-and-suffix": {
-            "count": 1,
-            "title": "Prefix and suffix",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "The libraryKey of SDUINode is an identifier that points to an SDUINode description in the library to be used as a model for this node.\n",
-    "files": {
-      "core/components/functional/sdui/sdui.md": {
-        "title": "SDUI",
-        "hashes": {
-          "library-key-and-contentelementselector": {
-            "count": 1,
-            "title": "Library key and contentElementSelector",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Note that the SDUI has a default library containing some basic component definitions useful for form declaration (see default-library.json).\n",
-    "files": {
-      "core/components/functional/sdui/sdui.md": {
-        "title": "SDUI",
-        "hashes": {
-          "library-key-and-contentelementselector": {
-            "count": 1,
-            "title": "Library key and contentElementSelector",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "This example uses the library key submit which points to a sonic-submit containing a button also coming from the library.\n",
-    "files": {
-      "core/components/functional/sdui/sdui.md": {
-        "title": "SDUI",
-        "hashes": {
-          "library-key-and-contentelementselector": {
-            "count": 1,
-            "title": "Library key and contentElementSelector",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "The element named button in the library is a sonic-button of type success containing a check icon as a prefix.\n",
-    "files": {
-      "core/components/functional/sdui/sdui.md": {
-        "title": "SDUI",
-        "hashes": {
-          "library-key-and-contentelementselector": {
-            "count": 1,
-            "title": "Library key and contentElementSelector",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Since the submit library element contains an attribute contentElementSelector with the value sonic-button, the "injected content" is put inside the button.\n",
-    "files": {
-      "core/components/functional/sdui/sdui.md": {
-        "title": "SDUI",
-        "hashes": {
-          "library-key-and-contentelementselector": {
-            "count": 1,
-            "title": "Library key and contentElementSelector",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "We used innerHTML for the sake of simplicity, but you can use nodes to add any complex content.\n",
-    "files": {
-      "core/components/functional/sdui/sdui.md": {
-        "title": "SDUI",
-        "hashes": {
-          "library-key-and-contentelementselector": {
-            "count": 1,
-            "title": "Library key and contentElementSelector",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "This special field lets you inject the content at any place in the HTML flow already set inside the parent SDUI component by using a CSS selector.\n",
-    "files": {
-      "core/components/functional/sdui/sdui.md": {
-        "title": "SDUI",
-        "hashes": {
-          "parentelementselector": {
-            "count": 1,
-            "title": "parentElementSelector",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "⚠️ Note that it doesn't work with top-level nodes.\n",
-    "files": {
-      "core/components/functional/sdui/sdui.md": {
-        "title": "SDUI",
-        "hashes": {
-          "parentelementselector": {
-            "count": 1,
-            "title": "parentElementSelector",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "The transformers let you transform the structure of the SDUI Descriptor into a new one before parsing and rendering it.\n",
-    "files": {
-      "core/components/functional/sdui/sdui.md": {
-        "title": "SDUI",
-        "hashes": {
-          "transformers": {
-            "count": 1,
-            "title": "Transformers:",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "To enable it, you must fill the transformation attribute of the component with a URL pointing to a Transform descriptor.\n",
-    "files": {
-      "core/components/functional/sdui/sdui.md": {
-        "title": "SDUI",
-        "hashes": {
-          "transformers": {
-            "count": 1,
-            "title": "Transformers:",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Each key of the library will be merged with the current library in the SDUI Descriptor, by replacing or creating items library key by key.\n",
-    "files": {
-      "core/components/functional/sdui/sdui.md": {
-        "title": "SDUI",
-        "hashes": {
-          "the-library": {
-            "count": 1,
-            "title": "The library:",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Each transform represents an action that will be done on the SDUI descriptor before the creation of the entire UI.\n",
-    "files": {
-      "core/components/functional/sdui/sdui.md": {
-        "title": "SDUI",
-        "hashes": {
-          "the-transform-actions": {
-            "count": 1,
-            "title": "The transform actions:",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "The action that will be done is a verb:\n",
-    "files": {
-      "core/components/functional/sdui/sdui.md": {
-        "title": "SDUI",
-        "hashes": {
-          "the-transform-actions": {
-            "count": 1,
-            "title": "The transform actions:",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "This is an HTML attribute to set on the component if needed. In this case, the component will not treat its props value directly as an SDUI descriptor. Internally, it will basically extract the SDUIDescriptor by doing something like this: const sduiDescriptor = this.props[this.sduikey].\n",
-    "files": {
-      "core/components/functional/sdui/sdui.md": {
-        "title": "SDUI",
-        "hashes": {
-          "sduikey": {
-            "count": 1,
-            "title": "sduiKey",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "This is an HTML attribute to set on the component if needed. In this case, the component will automatically create a sonic-toast-message-subscriber component. The data found in props[messageKey] will be treated as the data expected by the sonic-toast-message-subscriber. So, by respecting the format of data supported by this component, you will be able to show multiple toasts in the result of a request.\n",
-    "files": {
-      "core/components/functional/sdui/sdui.md": {
-        "title": "SDUI",
-        "hashes": {
-          "messagekey": {
-            "count": 1,
-            "title": "messageKey",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Example of JSON with messageKey=messages:\n\n",
-    "files": {
-      "core/components/functional/sdui/sdui.md": {
-        "title": "SDUI",
-        "hashes": {
-          "messagekey": {
-            "count": 1,
-            "title": "messageKey",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "This is an HTML attribute to set on the component if needed. You can set a URL pointing to a JSON describing a library with the same structure as the library in the SDUIDescriptor. The component will simply override its library with the given one.\n",
-    "files": {
-      "core/components/functional/sdui/sdui.md": {
-        "title": "SDUI",
-        "hashes": {
-          "library": {
-            "count": 1,
-            "title": "library",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Here is a little playground to let you test some simple tricks.\n",
-    "files": {
-      "core/components/functional/sdui/sdui.md": {
-        "title": "SDUI",
-        "hashes": {
-          "playground": {
-            "count": 1,
-            "title": "Playground",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "States",
-    "files": {
-      "core/components/functional/states/states.md": {
-        "title": "States",
-        "hashes": {
-          "states": {
-            "count": 1,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "When using capturing groups () the stored values are accessible via the dataProviderExpressione.g., data-value="#couleur_(\\d+)" => dataProviderExpression="api/unknown/$1"\n",
-    "files": {
-      "core/components/functional/states/states.md": {
-        "title": "States",
-        "hashes": {
-          "regexp": {
-            "count": 1,
-            "title": "Regexp",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Same as RegExp but using url patternse.g., data-value="#couleur_:id" => dataProviderExpression="api/unknown/:id"\n",
-    "files": {
-      "core/components/functional/states/states.md": {
-        "title": "States",
-        "hashes": {
-          "url-pattern": {
-            "count": 1,
-            "title": "Url-pattern",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Submit",
-    "files": {
-      "core/components/functional/submit/submit.md": {
-        "title": "Submit",
-        "hashes": {
-          "submit": {
-            "count": 1,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Result will show when something has been submit because the dataprovider used in this example is the same as the submitResultDataProvider used in the previous form.\n\n",
-    "files": {
-      "core/components/functional/submit/submit.md": {
-        "title": "Submit",
-        "hashes": {
-          "result-handling-example": {
-            "count": 1,
-            "title": "Result handling example",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "You can write the folowing code where the name attribute is written in dot notation.\n",
-    "files": {
-      "core/components/functional/submit/submit.md": {
-        "title": "Submit",
-        "hashes": {
-          "dot-notation": {
-            "count": 1,
-            "title": "dot notation",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "The data will be stored in the following format:\n",
-    "files": {
-      "core/components/functional/submit/submit.md": {
-        "title": "Submit",
-        "hashes": {
-          "dot-notation": {
-            "count": 1,
-            "title": "dot notation",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Subscriber",
-    "files": {
-      "core/components/functional/subscriber/subscriber.md": {
-        "title": "Subscriber",
-        "hashes": {
-          "subscriber": {
-            "count": 1,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "La mixin Subscriber permet lier un composant à un publisher.\nLa liaison à un publisher se fait via l'attribut dataProvider du composant qui représente ce que l'on obtient en appellant PublisherManager.get(dataProvider).\n",
-    "files": {
-      "core/components/functional/subscriber/subscriber.md": {
-        "title": "Subscriber",
-        "hashes": {
-          "subscriber": {
-            "count": 1,
-            "title": "",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Les propriétés du composant sont automatiquement remplies avec les propriétés du même nom dans les données du publisher.\n",
-    "files": {
-      "core/components/functional/subscriber/subscriber.md": {
-        "title": "Subscriber",
-        "hashes": {
-          "subscriber": {
-            "count": 1,
-            "title": "",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Le composant est automatiquement mis à jour lorsque les données du publisher sont mises à jour.\n",
-    "files": {
-      "core/components/functional/subscriber/subscriber.md": {
-        "title": "Subscriber",
-        "hashes": {
-          "subscriber": {
-            "count": 1,
-            "title": "",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Id of the dataProvider that the component will subscribe to\n",
-    "files": {
-      "core/components/functional/subscriber/subscriber.md": {
-        "title": "Subscriber",
-        "hashes": {
-          "dataprovider": {
-            "count": 1,
-            "title": "DataProvider",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Data object (json) that will be passed to the dataProvider\n",
-    "files": {
-      "core/components/functional/subscriber/subscriber.md": {
-        "title": "Subscriber",
-        "hashes": {
-          "props": {
-            "count": 1,
-            "title": "Props",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Helper, display the data held by the dataProvider in a floating div\n",
-    "files": {
-      "core/components/functional/subscriber/subscriber.md": {
-        "title": "Subscriber",
-        "hashes": {
-          "debug": {
-            "count": 1,
-            "title": "Debug",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Docs coming soon\n",
-    "files": {
-      "core/components/functional/subscriber/subscriber.md": {
-        "title": "Subscriber",
-        "hashes": {
-          "noautofill": {
-            "count": 1,
-            "title": "NoAutofill",
-            "type": "paragraph"
-          },
-          "propertymap": {
-            "count": 1,
-            "title": "PropertyMap",
-            "type": "paragraph"
-          },
-          "bindpublisher": {
-            "count": 1,
-            "title": "BindPublisher",
-            "type": "paragraph"
-          },
-          "instancecounter": {
-            "count": 1,
-            "title": "instanceCounter",
-            "type": "paragraph"
-          },
-          "publisher": {
-            "count": 1,
-            "title": "Publisher",
-            "type": "paragraph"
-          },
-          "args": {
-            "count": 1,
-            "title": "Args",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Permet de mapper un nom de propriété de donnée source vers une propriété du subscriber à la volée\n",
-    "files": {
-      "core/components/functional/subscriber/subscriber.md": {
-        "title": "Subscriber",
-        "hashes": {
-          "propertymap": {
-            "count": 1,
-            "title": "PropertyMap",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "On peut utiliser cette fonction pour lier un publisher spécifique au composant si besoin.\n",
-    "files": {
-      "core/components/functional/subscriber/subscriber.md": {
-        "title": "Subscriber",
-        "hashes": {
-          "bindpublisher": {
-            "count": 1,
-            "title": "BindPublisher",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Par défaut on crée un shadow dom mais on peut demander à ne pas en avoir via cette propriété et un attribut associé.Cela se fait à l'initialisation uniquement et n'est pas modifiable lors de la vie du composant.\n",
-    "files": {
-      "core/components/functional/subscriber/subscriber.md": {
-        "title": "Subscriber",
-        "hashes": {
-          "noshadowdom": {
-            "count": 1,
-            "title": "NoShadowDom",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "styles ??title ??_props ??onAssign ??defferedDebug ??\n",
-    "files": {
-      "core/components/functional/subscriber/subscriber.md": {
-        "title": "Subscriber",
-        "hashes": {
-          "other-attributes-gathered-from-subscriberstoriests": {
-            "count": 1,
-            "title": "Other attributes gathered from subscriber.stories.ts",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Value",
-    "files": {
-      "core/components/functional/value/value.md": {
-        "title": "Value",
-        "hashes": {
-          "value": {
-            "count": 1,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Simply shows a value from a data provider.\nYou can target sub data value using dot syntax.\nThe value reacts to changes.\n",
-    "files": {
-      "core/components/functional/value/value.md": {
-        "title": "Value",
-        "hashes": {
-          "value": {
-            "count": 1,
-            "title": "",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Alert",
-    "files": {
-      "core/components/ui/alert/alert.md": {
-        "title": "Alert",
-        "hashes": {
-          "alert": {
-            "count": 1,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Badge",
-    "files": {
-      "core/components/ui/badge/badge.md": {
-        "title": "Badge",
-        "hashes": {
-          "badge": {
-            "count": 1,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Button",
-    "files": {
-      "core/components/ui/button/button.md": {
-        "title": "Button",
-        "hashes": {
-          "button": {
-            "count": 1,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "The length of the button depends on the size of its content\n\n",
-    "files": {
-      "core/components/ui/button/button.md": {
-        "title": "Button",
-        "hashes": {
-          "loading": {
-            "count": 1,
-            "title": "Loading",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Captcha",
-    "files": {
-      "core/components/ui/captcha/captcha.md": {
-        "title": "Captcha",
-        "hashes": {
-          "captcha": {
-            "count": 1,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Card",
-    "files": {
-      "core/components/ui/card/card.md": {
-        "title": "Card",
-        "hashes": {
-          "card": {
-            "count": 1,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Divider",
-    "files": {
-      "core/components/ui/divider/divider.md": {
-        "title": "Divider",
-        "hashes": {
-          "divider": {
-            "count": 1,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Checkbox",
-    "files": {
-      "core/components/ui/form/checkbox/checkbox.md": {
-        "title": "Checkbox",
-        "hashes": {
-          "checkbox": {
-            "count": 1,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Fieldset",
-    "files": {
-      "core/components/ui/form/fieldset/fieldset.md": {
-        "title": "Fieldset",
-        "hashes": {
-          "fieldset": {
-            "count": 1,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Form-actions",
-    "files": {
-      "core/components/ui/form/form-actions/form-actions.md": {
-        "title": "Form-actions",
-        "hashes": {
-          "form-actions": {
-            "count": 1,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Form-layout",
-    "files": {
-      "core/components/ui/form/form-layout/form-layout.md": {
-        "title": "Form-layout",
-        "hashes": {
-          "form-layout": {
-            "count": 1,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Input",
-    "files": {
-      "core/components/ui/form/input/input.md": {
-        "title": "Input",
-        "hashes": {
-          "input": {
-            "count": 1,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Liste des types\n",
-    "files": {
-      "core/components/ui/form/input/input.md": {
-        "title": "Input",
-        "hashes": {
-          "type": {
-            "count": 1,
-            "title": "Type",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "\n",
-    "files": {
-      "core/components/ui/form/input/input.md": {
-        "title": "Input",
-        "hashes": {
-          "list": {
-            "count": 1,
-            "title": "List",
-            "type": "paragraph"
-          }
-        }
-      },
-      "core/components/ui/icon/icon.md": {
-        "title": "Icon",
-        "hashes": {
-          "custom": {
-            "count": 1,
-            "title": "Custom",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Input-autocomplete",
-    "files": {
-      "core/components/ui/form/input-autocomplete/input-autocomplete.md": {
-        "title": "Input-autocomplete",
-        "hashes": {
-          "input-autocomplete": {
-            "count": 1,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "The input-autocomplete component brings input and queue together in order to create a suggest behavior. This is why this component is partially configured as a form input and as a queue.\n",
-    "files": {
-      "core/components/ui/form/input-autocomplete/input-autocomplete.md": {
-        "title": "Input-autocomplete",
-        "hashes": {
-          "input-autocomplete": {
-            "count": 1,
-            "title": "",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Please note that only basic text input params and methods are implemented at this time. You should also be sure to understand the behavior of a queue in order to take full advantage of the input-autocomplete component.\n",
-    "files": {
-      "core/components/ui/form/input-autocomplete/input-autocomplete.md": {
-        "title": "Input-autocomplete",
-        "hashes": {
-          "input-autocomplete": {
-            "count": 1,
-            "title": "",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Here are some of the features of the input-autocomplete component:\n",
-    "files": {
-      "core/components/ui/form/input-autocomplete/input-autocomplete.md": {
-        "title": "Input-autocomplete",
-        "hashes": {
-          "input-autocomplete": {
-            "count": 1,
-            "title": "",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "If you are looking for a component to provide a suggest behavior, the input-autocomplete component is a good option. \n",
-    "files": {
-      "core/components/ui/form/input-autocomplete/input-autocomplete.md": {
-        "title": "Input-autocomplete",
-        "hashes": {
-          "input-autocomplete": {
-            "count": 1,
-            "title": "",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "In this example, the input will use its name as the search parameter when calling the service responsible for autocompletion.\n",
-    "files": {
-      "core/components/ui/form/input-autocomplete/input-autocomplete.md": {
-        "title": "Input-autocomplete",
-        "hashes": {
-          "simple-example": {
-            "count": 1,
-            "title": "Simple Example",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "The template is used to render the list items of results.\nThe list items are responsible for making a selection.\n",
-    "files": {
-      "core/components/ui/form/input-autocomplete/input-autocomplete.md": {
-        "title": "Input-autocomplete",
-        "hashes": {
-          "simple-example": {
-            "count": 1,
-            "title": "Simple Example",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "This time, we added buttons with the same name as the input while keeping the same data provider.\nThe result is that when you select an item, the input takes the value of the selected item, completing the classic suggest behavior.\n",
-    "files": {
-      "core/components/ui/form/input-autocomplete/input-autocomplete.md": {
-        "title": "Input-autocomplete",
-        "hashes": {
-          "simple-example": {
-            "count": 1,
-            "title": "Simple Example",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "In this example, the search parameter is separated from the name of the input. This means that the input will use the name "nom" as the search parameter, but the form data provider will be filled with the data named "siren" from the selected list item.\n",
-    "files": {
-      "core/components/ui/form/input-autocomplete/input-autocomplete.md": {
-        "title": "Input-autocomplete",
-        "hashes": {
-          "value-different-from-search-parameter": {
-            "count": 1,
-            "title": "Value different from search parameter",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "To do this, we need to use the searchParam attribute on the input element. This attribute specifies the name of the search parameter that will be used.\n",
-    "files": {
-      "core/components/ui/form/input-autocomplete/input-autocomplete.md": {
-        "title": "Input-autocomplete",
-        "hashes": {
-          "value-different-from-search-parameter": {
-            "count": 1,
-            "title": "Value different from search parameter",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "We also need to use the name and value attribute on the list items. This attribute specifies the value of the data provider that will be used for the selected list item.\n",
-    "files": {
-      "core/components/ui/form/input-autocomplete/input-autocomplete.md": {
-        "title": "Input-autocomplete",
-        "hashes": {
-          "value-different-from-search-parameter": {
-            "count": 1,
-            "title": "Value different from search parameter",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "By using these attributes, we can separate the search parameter from the name of the input and still fill the form data provider with the data from the selected list item.\n",
-    "files": {
-      "core/components/ui/form/input-autocomplete/input-autocomplete.md": {
-        "title": "Input-autocomplete",
-        "hashes": {
-          "value-different-from-search-parameter": {
-            "count": 1,
-            "title": "Value different from search parameter",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "This example is the same as the previous one, except that the select attribute is used. This attribute changes the look and feel of the component slightly.\n",
-    "files": {
-      "core/components/ui/form/input-autocomplete/input-autocomplete.md": {
-        "title": "Input-autocomplete",
-        "hashes": {
-          "select-autocomplete--value-different-from-search-parameter": {
-            "count": 1,
-            "title": "Select autocomplete / value different from search parameter",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Now the text is less free because, you must select either something from the list given by the service, or nothing else.\n",
-    "files": {
-      "core/components/ui/form/input-autocomplete/input-autocomplete.md": {
-        "title": "Input-autocomplete",
-        "hashes": {
-          "select-autocomplete--value-different-from-search-parameter": {
-            "count": 1,
-            "title": "Select autocomplete / value different from search parameter",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "The following code shows how to use the select attribute in an autocomplete input:\n",
-    "files": {
-      "core/components/ui/form/input-autocomplete/input-autocomplete.md": {
-        "title": "Input-autocomplete",
-        "hashes": {
-          "select-autocomplete--value-different-from-search-parameter": {
-            "count": 1,
-            "title": "Select autocomplete / value different from search parameter",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "At the moment you can enable keyboard up/down by adding an attribut "data-keyboard-nav" on the component and its listItems\n",
-    "files": {
-      "core/components/ui/form/input-autocomplete/input-autocomplete.md": {
-        "title": "Input-autocomplete",
-        "hashes": {
-          "keyboard-navigation": {
-            "count": 1,
-            "title": "keyboard navigation",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Radio",
-    "files": {
-      "core/components/ui/form/radio/radio.md": {
-        "title": "Radio",
-        "hashes": {
-          "radio": {
-            "count": 1,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Select",
-    "files": {
-      "core/components/ui/form/select/select.md": {
-        "title": "Select",
-        "hashes": {
-          "select": {
-            "count": 1,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Switch",
-    "files": {
-      "core/components/ui/form/switch/switch.md": {
-        "title": "Switch",
-        "hashes": {
-          "switch": {
-            "count": 1,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Textarea",
-    "files": {
-      "core/components/ui/form/textarea/textarea.md": {
-        "title": "Textarea",
-        "hashes": {
-          "textarea": {
-            "count": 1,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Group",
-    "files": {
-      "core/components/ui/group/group.md": {
-        "title": "Group",
-        "hashes": {
-          "group": {
-            "count": 1,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Icon",
-    "files": {
-      "core/components/ui/icon/icon.md": {
-        "title": "Icon",
-        "hashes": {
-          "icon": {
-            "count": 1,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Image",
-    "files": {
-      "core/components/ui/image/image.md": {
-        "title": "Image",
-        "hashes": {
-          "image": {
-            "count": 1,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Link",
-    "files": {
-      "core/components/ui/link/link.md": {
-        "title": "Link",
-        "hashes": {
-          "link": {
-            "count": 1,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Loader",
-    "files": {
-      "core/components/ui/loader/loader.md": {
-        "title": "Loader",
-        "hashes": {
-          "loader": {
-            "count": 1,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Menu",
-    "files": {
-      "core/components/ui/menu/menu.md": {
-        "title": "Menu",
-        "hashes": {
-          "menu": {
-            "count": 1,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Modal",
-    "files": {
-      "core/components/ui/modal/modal.md": {
-        "title": "Modal",
-        "hashes": {
-          "modal": {
-            "count": 1,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Pop",
-    "files": {
-      "core/components/ui/pop/pop.md": {
-        "title": "Pop",
-        "hashes": {
-          "pop": {
-            "count": 1,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Progress bar",
-    "files": {
-      "core/components/ui/progress/progress.md": {
-        "title": "Progress bar",
-        "hashes": {
-          "progress-bar": {
-            "count": 1,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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": {
-      "core/components/ui/table/table.md": {
-        "title": "Table",
-        "hashes": {
-          "table": {
-            "count": 1,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Values available : primary, info, success, warning, danger\n",
-    "files": {
-      "core/components/ui/table/table.md": {
-        "title": "Table",
-        "hashes": {
-          "type": {
-            "count": 1,
-            "title": "Type",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "The following attributes will be used to set the style of the component :  \n",
-    "files": {
-      "core/components/ui/table/table.md": {
-        "title": "Table",
-        "hashes": {
-          "cell-style-attributes": {
-            "count": 1,
-            "title": "Cell style attributes",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Every table is responsive by default\n",
-    "files": {
-      "core/components/ui/table/table.md": {
-        "title": "Table",
-        "hashes": {
-          "responsive": {
-            "count": 1,
-            "title": "Responsive",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Tooltip",
-    "files": {
-      "core/components/ui/tooltip/tooltip.md": {
-        "title": "Tooltip",
-        "hashes": {
-          "tooltip": {
-            "count": 1,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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": {
-      "docs/_core-concept/overview.md": {
-        "title": "lit + tailwind + vite",
-        "hashes": {
-          "lit--tailwind--vite": {
-            "count": 1,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Some notes for an overview of Concorde's functioning\n",
-    "files": {
-      "docs/_core-concept/overview.md": {
-        "title": "lit + tailwind + vite",
-        "hashes": {
-          "lit--tailwind--vite": {
-            "count": 1,
-            "title": "",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "A web component is simply a custom HTML element created using web standards:\n",
-    "files": {
-      "docs/_core-concept/overview.md": {
-        "title": "lit + tailwind + vite",
-        "hashes": {
-          "standard-web-components": {
-            "count": 1,
-            "title": "Standard Web components",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "web component = Custom Elements + shadowDom + HTML templates\n",
-    "files": {
-      "docs/_core-concept/overview.md": {
-        "title": "lit + tailwind + vite",
-        "hashes": {
-          "standard-web-components": {
-            "count": 1,
-            "title": "Standard Web components",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Concorde components are written using the lightweight Lit library: https://lit.dev/.\n",
-    "files": {
-      "docs/_core-concept/overview.md": {
-        "title": "lit + tailwind + vite",
-        "hashes": {
-          "lit-library": {
-            "count": 1,
-            "title": "Lit Library",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "A good portion of the elements documented on the Lit website are standard JavaScript concepts (e.g., mixins, tagged template literals).\n",
-    "files": {
-      "docs/_core-concept/overview.md": {
-        "title": "lit + tailwind + vite",
-        "hashes": {
-          "lit-library": {
-            "count": 1,
-            "title": "Lit Library",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "The library simplifies the writing of web components by automating certain tasks:\n",
-    "files": {
-      "docs/_core-concept/overview.md": {
-        "title": "lit + tailwind + vite",
-        "hashes": {
-          "lit-library": {
-            "count": 1,
-            "title": "Lit Library",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Our use of Lit rarely goes beyond this hello world\n",
-    "files": {
-      "docs/_core-concept/overview.md": {
-        "title": "lit + tailwind + vite",
-        "hashes": {
-          "lit-library": {
-            "count": 1,
-            "title": "Lit Library",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "We write the components in TypeScript, which is then compiled into JS.\n",
-    "files": {
-      "docs/_core-concept/overview.md": {
-        "title": "lit + tailwind + vite",
-        "hashes": {
-          "typescript-language": {
-            "count": 1,
-            "title": "Typescript Language",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Static and inferred typing provides stronger validation of the program's functioning during compilation.\nHowever, we often use the "any" type due to time constraints.\n",
-    "files": {
-      "docs/_core-concept/overview.md": {
-        "title": "lit + tailwind + vite",
-        "hashes": {
-          "typescript-language": {
-            "count": 1,
-            "title": "Typescript Language",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Lit uses TypeScript to simplify development through metadata:\n",
-    "files": {
-      "docs/_core-concept/overview.md": {
-        "title": "lit + tailwind + vite",
-        "hashes": {
-          "typescript-language": {
-            "count": 1,
-            "title": "Typescript Language",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "☢️Warning:\n",
-    "files": {
-      "docs/_core-concept/overview.md": {
-        "title": "lit + tailwind + vite",
-        "hashes": {
-          "typescript-language": {
-            "count": 1,
-            "title": "Typescript Language",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Compatibility issues may arise when using JS libraries, particularly regarding DOM traversal.\nThis is because these libraries are blocked from traversing the DOM due to the presence of the shadow DOM.\nHere are some examples of things that may cause problems:\n",
-    "files": {
-      "docs/_core-concept/overview.md": {
-        "title": "lit + tailwind + vite",
-        "hashes": {
-          "compatibility-with-classic-js-libraries": {
-            "count": 1,
-            "title": "Compatibility with Classic JS Libraries",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "🧱 Creating components\n",
-    "files": {
-      "docs/_core-concept/overview.md": {
-        "title": "lit + tailwind + vite",
-        "hashes": {
-          "topics-to-explore-for-further-learning": {
-            "count": 1,
-            "title": "Topics to Explore for Further Learning",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "🎨 Adding styles\n",
-    "files": {
-      "docs/_core-concept/overview.md": {
-        "title": "lit + tailwind + vite",
-        "hashes": {
-          "topics-to-explore-for-further-learning": {
-            "count": 1,
-            "title": "Topics to Explore for Further Learning",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "🥨 Sharing data\n",
-    "files": {
-      "docs/_core-concept/overview.md": {
-        "title": "lit + tailwind + vite",
-        "hashes": {
-          "topics-to-explore-for-further-learning": {
-            "count": 1,
-            "title": "Topics to Explore for Further Learning",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "The subscriber mixin",
-    "files": {
-      "docs/_core-concept/subscriber.md": {
-        "title": "The subscriber mixin",
-        "hashes": {
-          "the-subscriber-mixin": {
-            "count": 1,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "the-subscriber-mixin": {
-            "count": 1,
-            "title": "",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "dataprovider-attribute-automatic-filling-of-subscriber-properties": {
-            "count": 1,
-            "title": "DataProvider Attribute: Automatic Filling of Subscriber Properties",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "dataprovider-attribute-automatic-filling-of-subscriber-properties": {
-            "count": 1,
-            "title": "DataProvider Attribute: Automatic Filling of Subscriber Properties",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "dataprovider-attribute-automatic-filling-of-subscriber-properties": {
-            "count": 1,
-            "title": "DataProvider Attribute: Automatic Filling of Subscriber Properties",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "dataprovider-attribute-automatic-filling-of-subscriber-properties": {
-            "count": 1,
-            "title": "DataProvider Attribute: Automatic Filling of Subscriber Properties",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "dataprovider-attribute-automatic-filling-of-subscriber-properties": {
-            "count": 1,
-            "title": "DataProvider Attribute: Automatic Filling of Subscriber Properties",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "dataprovider-attribute-automatic-filling-of-subscriber-properties": {
-            "count": 1,
-            "title": "DataProvider Attribute: Automatic Filling of Subscriber Properties",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "automated-translation": {
-            "count": 1,
-            "title": "Automated Translation",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "automated-translation": {
-            "count": 1,
-            "title": "Automated Translation",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "reactive-property-props": {
-            "count": 1,
-            "title": "Reactive Property `props`",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "disabling-automatic-filling-of-reactive-properties": {
-            "count": 1,
-            "title": "Disabling Automatic Filling of Reactive Properties",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "disabling-automatic-filling-of-reactive-properties": {
-            "count": 1,
-            "title": "Disabling Automatic Filling of Reactive Properties",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "disabling-automatic-filling-of-reactive-properties": {
-            "count": 1,
-            "title": "Disabling Automatic Filling of Reactive Properties",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "disabling-automatic-filling-of-reactive-properties": {
-            "count": 1,
-            "title": "Disabling Automatic Filling of Reactive Properties",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Suppose that:\n",
-    "files": {
-      "docs/_core-concept/subscriber.md": {
-        "title": "The subscriber mixin",
-        "hashes": {
-          "data-binding": {
-            "count": 1,
-            "title": "Data Binding",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "This example also illustrates:\n",
-    "files": {
-      "docs/_core-concept/subscriber.md": {
-        "title": "The subscriber mixin",
-        "hashes": {
-          "data-binding": {
-            "count": 1,
-            "title": "Data Binding",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "data-binding": {
-            "count": 1,
-            "title": "Data Binding",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Special Variables:\n",
-    "files": {
-      "docs/_core-concept/subscriber.md": {
-        "title": "The subscriber mixin",
-        "hashes": {
-          "data-binding": {
-            "count": 1,
-            "title": "Data Binding",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "data-binding": {
-            "count": 1,
-            "title": "Data Binding",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Installation",
-    "files": {
-      "docs/_getting-started/concorde-outside.md": {
-        "title": "Installation",
-        "hashes": {
-          "installation": {
-            "count": 1,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "starter": {
-            "count": 1,
-            "title": "Starter",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "brand-new-vite-project": {
-            "count": 1,
-            "title": "Brand New Vite Project",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "creating-the-project": {
-            "count": 1,
-            "title": "Creating the Project",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Navigate to the project folder created and perform the installation:\n",
-    "files": {
-      "docs/_getting-started/concorde-outside.md": {
-        "title": "Installation",
-        "hashes": {
-          "installing-concorde": {
-            "count": 1,
-            "title": "Installing Concorde",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "shortcut-imports": {
-            "count": 1,
-            "title": "Shortcut Imports",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Shortcut imports replace the actual paths with aliases as follows:\n",
-    "files": {
-      "docs/_getting-started/concorde-outside.md": {
-        "title": "Installation",
-        "hashes": {
-          "shortcut-imports": {
-            "count": 1,
-            "title": "Shortcut Imports",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "shortcut-imports": {
-            "count": 1,
-            "title": "Shortcut Imports",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Import needed component in main.ts or wherever you want to use it:\n",
-    "files": {
-      "docs/_getting-started/concorde-outside.md": {
-        "title": "Installation",
-        "hashes": {
-          "simple-integration-in-html": {
-            "count": 1,
-            "title": "Simple Integration in HTML",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "simple-integration-in-html": {
-            "count": 1,
-            "title": "Simple Integration in HTML",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "For example, create a file my-element.ts at the root:\n",
-    "files": {
-      "docs/_getting-started/concorde-outside.md": {
-        "title": "Installation",
-        "hashes": {
-          "using-a-mixin-to-create-a-new-lit-component": {
-            "count": 1,
-            "title": "Using a Mixin to Create a New Lit Component",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "using-a-mixin-to-create-a-new-lit-component": {
-            "count": 1,
-            "title": "Using a Mixin to Create a New Lit Component",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "using-a-mixin-to-create-a-new-lit-component": {
-            "count": 1,
-            "title": "Using a Mixin to Create a New Lit Component",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "using-a-mixin-to-create-a-new-lit-component": {
-            "count": 1,
-            "title": "Using a Mixin to Create a New Lit Component",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "using-a-mixin-to-create-a-new-lit-component": {
-            "count": 1,
-            "title": "Using a Mixin to Create a New Lit Component",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Creating components",
-    "files": {
-      "docs/_getting-started/create-a-component.md": {
-        "title": "Creating components",
-        "hashes": {
-          "creating-components": {
-            "count": 1,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "where-to-put-it": {
-            "count": 1,
-            "title": "Where to put it?",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "where-to-put-it": {
-            "count": 1,
-            "title": "Where to put it?",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "starting-from-a-simple-model": {
-            "count": 1,
-            "title": "Starting from a Simple Model",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "starting-from-a-simple-model": {
-            "count": 1,
-            "title": "Starting from a Simple Model",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "starting-from-a-simple-model": {
-            "count": 1,
-            "title": "Starting from a Simple Model",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "starting-from-a-simple-model": {
-            "count": 1,
-            "title": "Starting from a Simple Model",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Regarding Subscriber, see:\n",
-    "files": {
-      "docs/_getting-started/create-a-component.md": {
-        "title": "Creating components",
-        "hashes": {
-          "starting-from-a-simple-model": {
-            "count": 1,
-            "title": "Starting from a Simple Model",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "naming-the-component": {
-            "count": 1,
-            "title": "Naming the Component",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "naming-the-component": {
-            "count": 1,
-            "title": "Naming the Component",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "creating-reactive-properties-and-modifying-the-render-function": {
-            "count": 1,
-            "title": "Creating Reactive Properties and Modifying the Render Function",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "html-structure-of-a-component": {
-            "count": 1,
-            "title": "HTML Structure of a Component",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "html-structure-of-a-component": {
-            "count": 1,
-            "title": "HTML Structure of a Component",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "html-structure-of-a-component": {
-            "count": 1,
-            "title": "HTML Structure of a Component",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "referencing-it": {
-            "count": 1,
-            "title": "Referencing It",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "referencing-it": {
-            "count": 1,
-            "title": "Referencing It",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "referencing-it": {
-            "count": 1,
-            "title": "Referencing It",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "using-it": {
-            "count": 1,
-            "title": "Using It",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "sharing-data": {
-            "count": 1,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "sharing-data": {
-            "count": 1,
-            "title": "",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Especialy, graphical components should not reference each other in order to remain decoupled.\n",
-    "files": {
-      "docs/_getting-started/pubsub.md": {
-        "title": "Sharing data",
-        "hashes": {
-          "sharing-data": {
-            "count": 1,
-            "title": "",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Thats why we use publish/subscribe paradigm to addresse this issue.\n",
-    "files": {
-      "docs/_getting-started/pubsub.md": {
-        "title": "Sharing data",
-        "hashes": {
-          "sharing-data": {
-            "count": 1,
-            "title": "",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "❇️ The order of data creation and subscription theoretically has no importance.\n",
-    "files": {
-      "docs/_getting-started/pubsub.md": {
-        "title": "Sharing data",
-        "hashes": {
-          "principle": {
-            "count": 1,
-            "title": "Principle",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "dataprovider": {
-            "count": 1,
-            "title": "DataProvider",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "The PublisherManager is a utility class to get publishers\n",
-    "files": {
-      "docs/_getting-started/pubsub.md": {
-        "title": "Sharing data",
-        "hashes": {
-          "publishermanager": {
-            "count": 1,
-            "title": "PublisherManager",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "publishermanager": {
-            "count": 1,
-            "title": "PublisherManager",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "publishermanager": {
-            "count": 1,
-            "title": "PublisherManager",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "basic-example": {
-            "count": 1,
-            "title": "Basic Example",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Introduction",
-    "files": {
-      "docs/_getting-started/start.md": {
-        "title": "Introduction",
-        "hashes": {
-          "introduction": {
-            "count": 1,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "what-is-concorde-": {
-            "count": 1,
-            "title": "What is Concorde ?",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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",
-        "hashes": {
-          "why-and-use-case": {
-            "count": 1,
-            "title": "Why and use case",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "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-easily": {
-            "count": 1,
-            "title": "Start a new project easily",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Adding styles",
-    "files": {
-      "docs/_getting-started/theming.md": {
-        "title": "Adding styles",
-        "hashes": {
-          "adding-styles": {
-            "count": 1,
-            "title": "",
-            "type": "page"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "No style crosses the shadow root of a component, except for inheritable properties (which have the "inherit" property possible) and CSS variables.\nProperties integrated via a "slot" remain stylizable in a conventional way.\n",
-    "files": {
-      "docs/_getting-started/theming.md": {
-        "title": "Adding styles",
-        "hashes": {
-          "normal-behavior": {
-            "count": 1,
-            "title": "Normal Behavior",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "The declaration of reactive properties is useful for selecting a particular configuration that mostly affects a set of properties.\n",
-    "files": {
-      "docs/_getting-started/theming.md": {
-        "title": "Adding styles",
-        "hashes": {
-          "choosing-style-presets-via-reactive-properties": {
-            "count": 1,
-            "title": "Choosing Style Presets via Reactive Properties:",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "For example, a size property (xs, sm, md, xl) will affect margins, font, line heights to align them with the corresponding CSS vars, which can be customized using the methods mentioned earlier if necessary.\n",
-    "files": {
-      "docs/_getting-started/theming.md": {
-        "title": "Adding styles",
-        "hashes": {
-          "choosing-style-presets-via-reactive-properties": {
-            "count": 1,
-            "title": "Choosing Style Presets via Reactive Properties:",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "It is recommended to use the {reflect: true} property for reactive properties that have an associated style on the :host(). For example: :host([type='primary']){...}\n",
-    "files": {
-      "docs/_getting-started/theming.md": {
-        "title": "Adding styles",
-        "hashes": {
-          "choosing-style-presets-via-reactive-properties": {
-            "count": 1,
-            "title": "Choosing Style Presets via Reactive Properties:",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "☢️ Caution: Passing class names via reactive properties / HTML attributes of the component should be avoided as it can quickly lead to difficult-to-manage situations.\n",
-    "files": {
-      "docs/_getting-started/theming.md": {
-        "title": "Adding styles",
-        "hashes": {
-          "choosing-style-presets-via-reactive-properties": {
-            "count": 1,
-            "title": "Choosing Style Presets via Reactive Properties:",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "By default, the display property is inline.\nTherefore, be careful to define it according to the needs, as one might mistakenly expect it to be block as with a regular <div>.\n",
-    "files": {
-      "docs/_getting-started/theming.md": {
-        "title": "Adding styles",
-        "hashes": {
-          "css-display-property": {
-            "count": 1,
-            "title": "CSS \"display\" Property",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "☢️ Caution: Defining the display property as contents may seem attractive at first, but:\n",
-    "files": {
-      "docs/_getting-started/theming.md": {
-        "title": "Adding styles",
-        "hashes": {
-          "css-display-property": {
-            "count": 1,
-            "title": "CSS \"display\" Property",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "tailwind has been integrated into Concorde and is available in scoped components (with Shadow DOM).\nTo use it, you need to import the following:\n",
-    "files": {
-      "docs/_getting-started/theming.md": {
-        "title": "Adding styles",
-        "hashes": {
-          "tailwind-functional-classes": {
-            "count": 1,
-            "title": "TAILWIND Functional Classes",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Then include the tailwind style in the static styles property of the component:\n",
-    "files": {
-      "docs/_getting-started/theming.md": {
-        "title": "Adding styles",
-        "hashes": {
-          "tailwind-functional-classes": {
-            "count": 1,
-            "title": "TAILWIND Functional Classes",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "Finally, use it in the HTML within the render function:\n",
-    "files": {
-      "docs/_getting-started/theming.md": {
-        "title": "Adding styles",
-        "hashes": {
-          "tailwind-functional-classes": {
-            "count": 1,
-            "title": "TAILWIND Functional Classes",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "The colors from Concorde's theme are referenced in Tailwind's theme.\n",
-    "files": {
-      "docs/_getting-started/theming.md": {
-        "title": "Adding styles",
-        "hashes": {
-          "tailwind-functional-classes": {
-            "count": 1,
-            "title": "TAILWIND Functional Classes",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "This operation is particularly useful when it comes to adding behavior to a simple existing element.\nIt may also become necessary to establish compatibility with a traditional JS library.\n",
-    "files": {
-      "docs/_getting-started/theming.md": {
-        "title": "Adding styles",
-        "hashes": {
-          "usefulness": {
-            "count": 1,
-            "title": "Usefulness",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "For example, with a text input:\n",
-    "files": {
-      "docs/_getting-started/theming.md": {
-        "title": "Adding styles",
-        "hashes": {
-          "usefulness": {
-            "count": 1,
-            "title": "Usefulness",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "If there is no shadow DOM (see the noShadowDom property of Subscriber):\n",
-    "files": {
-      "docs/_getting-started/theming.md": {
-        "title": "Adding styles",
-        "hashes": {
-          "consequences": {
-            "count": 1,
-            "title": "Consequences",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "For example, the components queue, list, and fetch do not have a shadow DOM.\n",
-    "files": {
-      "docs/_getting-started/theming.md": {
-        "title": "Adding styles",
-        "hashes": {
-          "consequences": {
-            "count": 1,
-            "title": "Consequences",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  },
-  {
-    "search": "ℹ️ Note: Specifically in this case, it may be useful to set the display property to contents.\n",
-    "files": {
-      "docs/_getting-started/theming.md": {
-        "title": "Adding styles",
-        "hashes": {
-          "consequences": {
-            "count": 1,
-            "title": "Consequences",
-            "type": "paragraph"
-          }
-        }
-      }
-    }
-  }
-]