From 495a59e33ec950d4fb9699c09fd9bb952e9233b4 Mon Sep 17 00:00:00 2001
From: Cory LaViska <cory@abeautifulsite.net>
Date: Fri, 21 Jun 2024 11:19:12 -0400
Subject: [PATCH] fix links

---
 docs/docs/components/checkbox.md     | 2 +-
 docs/docs/components/color-picker.md | 2 +-
 docs/docs/components/input.md        | 2 +-
 docs/docs/components/page.md         | 4 ++--
 docs/docs/components/radio.md        | 2 +-
 docs/docs/components/range.md        | 2 +-
 docs/docs/components/select.md       | 4 ++--
 docs/docs/components/switch.md       | 2 +-
 docs/docs/components/textarea.md     | 2 +-
 docs/docs/installation.md            | 2 +-
 docs/docs/themes.md                  | 2 +-
 11 files changed, 13 insertions(+), 13 deletions(-)

diff --git a/docs/docs/components/checkbox.md b/docs/docs/components/checkbox.md
index 5d7e61c2b..4251983ff 100644
--- a/docs/docs/components/checkbox.md
+++ b/docs/docs/components/checkbox.md
@@ -9,7 +9,7 @@ layout: component
 ```
 
 :::info
-This component works with standard `<form>` elements. Please refer to the section on [form controls](/getting-started/form-controls) to learn more about form submission and client-side validation.
+This component works with standard `<form>` elements. Please refer to the section on [form controls](/docs/form-controls) to learn more about form submission and client-side validation.
 :::
 
 ## Examples
diff --git a/docs/docs/components/color-picker.md b/docs/docs/components/color-picker.md
index 5c9522024..baf5547cf 100644
--- a/docs/docs/components/color-picker.md
+++ b/docs/docs/components/color-picker.md
@@ -9,7 +9,7 @@ layout: component
 ```
 
 :::info
-This component works with standard `<form>` elements. Please refer to the section on [form controls](/getting-started/form-controls) to learn more about form submission and client-side validation.
+This component works with standard `<form>` elements. Please refer to the section on [form controls](/docs/form-controls) to learn more about form submission and client-side validation.
 :::
 
 ## Examples
diff --git a/docs/docs/components/input.md b/docs/docs/components/input.md
index d28f0fe04..267fc1587 100644
--- a/docs/docs/components/input.md
+++ b/docs/docs/components/input.md
@@ -9,7 +9,7 @@ layout: component
 ```
 
 :::info
-This component works with standard `<form>` elements. Please refer to the section on [form controls](/getting-started/form-controls) to learn more about form submission and client-side validation.
+This component works with standard `<form>` elements. Please refer to the section on [form controls](/docs/form-controls) to learn more about form submission and client-side validation.
 :::
 
 ## Examples
diff --git a/docs/docs/components/page.md b/docs/docs/components/page.md
index 078b74236..578b91993 100644
--- a/docs/docs/components/page.md
+++ b/docs/docs/components/page.md
@@ -6,7 +6,7 @@ layout: component
 
 The layout component is designed to power full webpages. It is flexible enough to handle most modern designs and includes a simple mechanism for handling desktop and mobile navigation.
 
-A number of sections are available as part of the layout, most of which are optional. Content is added by [slotting elements](/getting-started/usage/#slots) into various locations.
+A number of sections are available as part of the layout, most of which are optional. Content is added by [slotting elements](/docs/usage/#slots) into various locations.
 
 This component _does not_ implement any [content sectioning](https://developer.mozilla.org/en-US/docs/Web/HTML/Element#content_sectioning) or "semantic elements" internally (such as `<main>`, `<header>`, `<footer>`, etc.). Instead, it is recommended that you slot in content sectioning elements wherever you feel they're appropriate.
 
@@ -19,7 +19,7 @@ Most slots are optional. Slots that have no content will not be shown, allowing
 ![Screenshot of Layout Anatomy showing various slots](/assets/images/layout-anatomy.svg)
 
 :::info
-If you're not familiar with how slots work in HTML, you might want to [learn more about slots](/getting-started/usage/#slots) before using this component.
+If you're not familiar with how slots work in HTML, you might want to [learn more about slots](/docs/usage/#slots) before using this component.
 :::
 
 ## Sticky Sections
diff --git a/docs/docs/components/radio.md b/docs/docs/components/radio.md
index 9b72f1c7d..53eee6bdb 100644
--- a/docs/docs/components/radio.md
+++ b/docs/docs/components/radio.md
@@ -15,7 +15,7 @@ Radios are designed to be used with [radio groups](/docs/components/radio-group)
 ```
 
 :::info
-This component works with standard `<form>` elements. Please refer to the section on [form controls](/getting-started/form-controls) to learn more about form submission and client-side validation.
+This component works with standard `<form>` elements. Please refer to the section on [form controls](/docs/form-controls) to learn more about form submission and client-side validation.
 :::
 
 ## Examples
diff --git a/docs/docs/components/range.md b/docs/docs/components/range.md
index bfa043e70..85fec2b17 100644
--- a/docs/docs/components/range.md
+++ b/docs/docs/components/range.md
@@ -9,7 +9,7 @@ layout: component
 ```
 
 :::info
-This component works with standard `<form>` elements. Please refer to the section on [form controls](/getting-started/form-controls) to learn more about form submission and client-side validation.
+This component works with standard `<form>` elements. Please refer to the section on [form controls](/docs/form-controls) to learn more about form submission and client-side validation.
 :::
 
 ## Examples
diff --git a/docs/docs/components/select.md b/docs/docs/components/select.md
index b05a78241..f08a44994 100644
--- a/docs/docs/components/select.md
+++ b/docs/docs/components/select.md
@@ -16,7 +16,7 @@ layout: component
 ```
 
 :::info
-This component works with standard `<form>` elements. Please refer to the section on [form controls](/getting-started/form-controls) to learn more about form submission and client-side validation.
+This component works with standard `<form>` elements. Please refer to the section on [form controls](/docs/form-controls) to learn more about form submission and client-side validation.
 :::
 
 ## Examples
@@ -228,7 +228,7 @@ Use the `prefix` slot to prepend an icon to the control.
 
 When multiple options can be selected, you can provide custom tags by passing a function to the `getTag` property. Your function can return a string of HTML, a <a href="https://lit.dev/docs/templates/overview/">Lit Template</a>, or an [`HTMLElement`](https://developer.mozilla.org/en-US/docs/Web/API/HTMLElement). The `getTag()` function will be called for each option. The first argument is an `<wa-option>` element and the second argument is the tag's index (its position in the tag list).
 
-Remember that custom tags are rendered in a shadow root. To style them, you can use the `style` attribute in your template or you can add your own [parts](/getting-started/customizing/#css-parts) and target them with the [`::part()`](https://developer.mozilla.org/en-US/docs/Web/CSS/::part) selector.
+Remember that custom tags are rendered in a shadow root. To style them, you can use the `style` attribute in your template or you can add your own [parts](/docs/customizing/#css-parts) and target them with the [`::part()`](https://developer.mozilla.org/en-US/docs/Web/CSS/::part) selector.
 
 ```html {.example}
 <wa-select
diff --git a/docs/docs/components/switch.md b/docs/docs/components/switch.md
index 4abb792da..d6c96b7a7 100644
--- a/docs/docs/components/switch.md
+++ b/docs/docs/components/switch.md
@@ -9,7 +9,7 @@ layout: component
 ```
 
 :::info
-This component works with standard `<form>` elements. Please refer to the section on [form controls](/getting-started/form-controls) to learn more about form submission and client-side validation.
+This component works with standard `<form>` elements. Please refer to the section on [form controls](/docs/form-controls) to learn more about form submission and client-side validation.
 :::
 
 ## Examples
diff --git a/docs/docs/components/textarea.md b/docs/docs/components/textarea.md
index 08692760e..d3fbbab05 100644
--- a/docs/docs/components/textarea.md
+++ b/docs/docs/components/textarea.md
@@ -9,7 +9,7 @@ layout: component
 ```
 
 :::info
-This component works with standard `<form>` elements. Please refer to the section on [form controls](/getting-started/form-controls) to learn more about form submission and client-side validation.
+This component works with standard `<form>` elements. Please refer to the section on [form controls](/docs/form-controls) to learn more about form submission and client-side validation.
 :::
 
 ## Examples
diff --git a/docs/docs/installation.md b/docs/docs/installation.md
index 525ae6fa8..0bdda4dfe 100644
--- a/docs/docs/installation.md
+++ b/docs/docs/installation.md
@@ -31,7 +31,7 @@ The autoloader is the easiest way to use Web Awesome. A lightweight script watch
 <script type="module" src="{% cdnUrl 'webawesome.loader.js' %}"></script>
 ```
 
-Now you can [start using Web Awesome!](/getting-started/usage)
+Now you can [start using Web Awesome!](/docs/usage)
 
 :::info
 While convenient, autoloading may lead to a [Flash of Undefined Custom Elements](https://www.abeautifulsite.net/posts/flash-of-undefined-custom-elements/). The linked article describes some ways to alleviate it.
diff --git a/docs/docs/themes.md b/docs/docs/themes.md
index 02ce40979..9ffb7670b 100644
--- a/docs/docs/themes.md
+++ b/docs/docs/themes.md
@@ -53,7 +53,7 @@ There are two ways to create themes. The easiest way is to customize the default
 
 ### Customizing a Built-in Theme
 
-Overriding the default theme is the easiest way to customize Web Awesome. You can do this by importing the default theme as-is, then creating a separate stylesheet that overrides [the theming API](/getting-started/customizing#design-tokens) and adds [component styles](/getting-started/customizing#component-parts) to your liking. You must import your theme _after_ the default theme.
+Overriding the default theme is the easiest way to customize Web Awesome. You can do this by importing the default theme as-is, then creating a separate stylesheet that overrides [the theming API](/docs/customizing#design-tokens) and adds [component styles](/docs/customizing#css-parts) to your liking. You must import your theme _after_ the default theme.
 
 If you're customizing the default light styles, scope your styles to the following selectors.