diff --git a/docs/components/select/use-cases.md b/docs/components/select/use-cases.md
index c7ef2f300..3e84ac692 100644
--- a/docs/components/select/use-cases.md
+++ b/docs/components/select/use-cases.md
@@ -54,3 +54,63 @@ Or by setting the `disabled` attribute on the entire `lion-select` field.
 ## Validation
 
 A validator can be used to make it e.g. `required`. If you want to know how to do that, please take a look at our [validation examples](../../fundamentals/systems/form/validate.md).
+
+## Rendering and updating select options
+
+A very common pattern is to keep the options in an array, and render them through a repeating template.
+
+```js
+import { html, LitElement } from 'lit';
+
+class MyOptions extends LitElement {
+  static properties = {
+    colours: Array,
+  };
+
+  constructor() {
+    super();
+
+    this.colours = ['red', 'hotpink', 'teal'];
+  }
+
+  render() {
+    return html`
+      <lion-select name="favoriteColor" label="Favorite color" disabled>
+        <select slot="input">
+          <option selected hidden value>Please select</option>
+          ${this.colours.map(colour => html`<option value="${colour}">${colour}</option>`)}
+        </select>
+      </lion-select>
+    `;
+  }
+}
+```
+
+Using the above method to build repeating templates is usually efficient. However, there are cases where you might want to update the list of options after an option has already been selected.
+
+For example, if we add a button to sort the array alphabetically, pressing it would update the list. However, the selected state and index would not reset or update accordingly.
+
+Lit is intelligent and updates the DOM with minimal effort. During a rerender, it only updates the values inside the template and doesn't check state values outside the template, such as the selected item from the parent element.
+
+So, if the first option was selected, the newly selected option would be whatever ends up in that position after sorting. This creates a confusing user experience where a seemingly random value is selected.
+
+The Lit `repeat` directive fixes this problem by attaching a unique ID to each DOM element using an item as the identifier, `colour` in our example. Any changes will then result in a complete rerender or reordering of the DOM nodes, rather than just changing the values of those nodes.
+
+```js
+import { repeat } from 'lit/directives/repeat.js';
+
+render() {
+  return html`
+    <lion-select name="favoriteColor" label="Favorite color" disabled>
+      <select slot="input">
+        <option selected hidden value>Please select</option>
+        ${repeat(
+          this.colours,
+          (colour) => colour,
+          (colour, index) => html`<option value="${colour}">${colour}</option>`
+        )}
+      </select>
+    </lion-select>
+  `;
+}
+```
diff --git a/package-lock.json b/package-lock.json
index 596463e3f..d2dc29222 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -28596,7 +28596,7 @@
     },
     "packages/ui": {
       "name": "@lion/ui",
-      "version": "0.8.1",
+      "version": "0.8.3",
       "license": "MIT",
       "dependencies": {
         "@bundled-es-modules/message-format": "^6.2.4",