From e1dedcb1b5057db2d2efcf7cd650def7574db738 Mon Sep 17 00:00:00 2001 From: Cory LaViska Date: Mon, 26 Jun 2023 12:20:13 -0400 Subject: [PATCH] Fix broken links (#1407) * add spacing * update old links --- docs/_includes/default.njk | 2 +- docs/pages/resources/changelog.md | 4 ++-- docs/pages/tutorials/integrating-with-laravel.md | 2 +- docs/pages/tutorials/integrating-with-nextjs.md | 2 +- docs/pages/tutorials/integrating-with-rails.md | 2 +- 5 files changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/_includes/default.njk b/docs/_includes/default.njk index bd21b7d3..bb4b097e 100644 --- a/docs/_includes/default.njk +++ b/docs/_includes/default.njk @@ -81,7 +81,7 @@ {# Theme selector #} - + diff --git a/docs/pages/resources/changelog.md b/docs/pages/resources/changelog.md index 3a549569..0327c623 100644 --- a/docs/pages/resources/changelog.md +++ b/docs/pages/resources/changelog.md @@ -1140,12 +1140,12 @@ The most elegant solution I found was to use the [Web Animations API](https://de ## 2.0.0-beta.34 -This release changes the way components are registered if you're [cherry picking](/getting-started/installation?id=cherry-picking) or [using a bundler](/getting-started/installation?id=bundling). This recommendation came from the LitElement team and simplifies Shoelace's dependency graph. It also eliminates the need to call a `register()` function before using each component. +This release changes the way components are registered if you're [cherry picking](/getting-started/installation#cherry-picking) or [using a bundler](/getting-started/installation#bundling). This recommendation came from the LitElement team and simplifies Shoelace's dependency graph. It also eliminates the need to call a `register()` function before using each component. From now on, importing a component will register it automatically. The caveat is that bundlers may not tree shake the library properly if you import from `@shoelace-style/shoelace`, so the recommendation is to import components and utilities from their corresponding files instead. - 🚨 BREAKING: removed `all.shoelace.js` (use `shoelace.js` instead) -- 🚨 BREAKING: component modules now have a side effect, so bundlers may not tree shake properly when importing from `@shoelace-style/shoelace` (see the [installation page](/getting-started/installation?id=bundling) for more details and how to update) +- 🚨 BREAKING: component modules now have a side effect, so bundlers may not tree shake properly when importing from `@shoelace-style/shoelace` (see the [installation page](/getting-started/installation#bundling) for more details and how to update) - Added `sl-clear` event to `` - Fixed a bug where dynamically changing menu items in `` would cause the display label to be blank [#374] - Fixed a bug where setting the `value` attribute or property on `` and `` would trigger validation too soon diff --git a/docs/pages/tutorials/integrating-with-laravel.md b/docs/pages/tutorials/integrating-with-laravel.md index 21bfe4ed..6f3ecc0d 100644 --- a/docs/pages/tutorials/integrating-with-laravel.md +++ b/docs/pages/tutorials/integrating-with-laravel.md @@ -40,7 +40,7 @@ Import the Shoelace default theme (stylesheet) in `/resources/css/app.css`: ### Import Your Shoelace Components -Import each Shoelace component you plan to use in `/resources/js/bootstrap.js`. Use the full path to each component (as outlined in the [Cherry Picking instructions](https://shoelace.style/getting-started/installation?id=cherry-picking)). You can find the full import statement for a component in the _Importing_ section of the component's documentation (use the _Bundler_ import). Your imports should look similar to: +Import each Shoelace component you plan to use in `/resources/js/bootstrap.js`. Use the full path to each component (as outlined in the [Cherry Picking instructions](https://shoelace.style/getting-started/installation#cherry-picking)). You can find the full import statement for a component in the _Importing_ section of the component's documentation (use the _Bundler_ import). Your imports should look similar to: ```js import '@shoelace-style/shoelace/dist/components/button/button.js'; diff --git a/docs/pages/tutorials/integrating-with-nextjs.md b/docs/pages/tutorials/integrating-with-nextjs.md index a4dc1794..76348424 100644 --- a/docs/pages/tutorials/integrating-with-nextjs.md +++ b/docs/pages/tutorials/integrating-with-nextjs.md @@ -84,7 +84,7 @@ If we use `useEffect` instead of `useLayoutEffect`, the initial render will occu ::: :::tip -This will import all Shoelace components for convenience. To selectively import components, refer to the [Using webpack](/getting-started/installation?id=using-webpack) section of the docs. +This will import all Shoelace components for convenience. To selectively import components, refer to the [Using webpack](/getting-started/installation#using-webpack) section of the docs. ::: You may be wondering where the `URL` property is coming from. We'll address that in the next few sections. diff --git a/docs/pages/tutorials/integrating-with-rails.md b/docs/pages/tutorials/integrating-with-rails.md index 9bb87610..251c4dee 100644 --- a/docs/pages/tutorials/integrating-with-rails.md +++ b/docs/pages/tutorials/integrating-with-rails.md @@ -37,7 +37,7 @@ The next step is to import Shoelace's default theme (stylesheet) in `app/javascr @import '@shoelace-style/shoelace/dist/themes/dark'; // Optional dark theme ``` -Fore more details about themes, please refer to [Theme Basics](/getting-started/themes?id=theme-basics). +Fore more details about themes, please refer to [Theme Basics](/getting-started/themes#theme-basics). ### Importing Required Scripts