Update docs to use placeholders

rawilk · rawilk · commit 5ecdd00793bf · 2021-07-05T09:58:51.000-05:00
diff --git a/docs/files/filepond.md b/docs/files/filepond.md
@@ -10,7 +10,7 @@ Before using this component, we recommend familiarizing yourself with the FilePo
 
 ## Installation
 
-While the `file-pond` component works out-of-the-box when you've [set the directive](/docs/laravel-form-components/v5/installation#directives),
+While the `file-pond` component works out-of-the-box when you've [set the directive](/docs/laravel-form-components/{version}/installation#directives),
 we recommend that you install and compile the JavaScript libraries before you deploy to production:
 
 - [Alpine.js](https://github.com/alpinejs/alpine) `^2.8`
diff --git a/docs/inputs/date-picker.md b/docs/inputs/date-picker.md
@@ -10,7 +10,7 @@ By using it, you can simply add a date and/or time picker to your form with one
 
 ## Installation
 
-While the `date-picker` component works out-of-the-box when you've [set the directives](/docs/laravel-form-componentsvalue-fieldinstallation#directives),
+While the `date-picker` component works out-of-the-box when you've [set the directives](/docs/laravel-form-components/installation#directives),
 we recommend that you install and compile the JavaScript libraries before you deploy to production:
 
 - [Alpine.js](https://github.com/alpinejs/alpine) `^2.8`
@@ -62,7 +62,7 @@ that flatpickr generates. If you want to prevent the button/icon from being disp
 > {note} If you disable the toggle button, be sure to set `click-opens` to `true` on the component.
 
 > {tip} You can also change the icon that is used for the toggle button either by setting the `toggle-icon` attribute, or by changing
-> it globally [in the config](https://github.com/rawilk/laravel-form-components/blob/master/config/form-components.php#L103).
+> it globally [in the config](https://github.com/rawilk/laravel-form-components/blob/{branch}/config/form-components.php#L103).
 
 ## Clearing
 
@@ -73,7 +73,7 @@ to `true` and an icon for clearing the input will be appended to the input.
 <x-date-picker name="birthday" clearable />
 ```
 
-The icon defaults to `heroicon-o-x-circle`, but you can easily customize this icon either [in the config](https://github.com/rawilk/laravel-form-components/blob/master/config/form-components.php#L109), or by setting the `clear-icon` attribute to the icon you want.
+The icon defaults to `heroicon-o-x-circle`, but you can easily customize this icon either [in the config](https://github.com/rawilk/laravel-form-components/blob/{branch}/config/form-components.php#L109), or by setting the `clear-icon` attribute to the icon you want.
 
 ## Options
 
@@ -133,4 +133,4 @@ For more information on the callbacks available, please consult [the events api]
 Like the other inputs, the date picker can also have leading and trailing addons, however by default you cannot add them.
 To add leading addons, you must disable the toggle icon, and for trailing addons, you must set `clearable` to `false`.
 
-See the [input documentation](/docs/laravel-form-components/v5/inputs/input#addons) for more information.
+See the [input documentation](/docs/laravel-form-components/{version}/inputs/input#addons) for more information.
diff --git a/docs/inputs/email.md b/docs/inputs/email.md
@@ -20,4 +20,4 @@ The most basic usage of the component is like this:
 By default an `email` type will be set for the input field as well as an `id` that allows it to be
 easily referenced by a `label` element.
 
-Besides this, the email element behaves exactly the same as the [input component](/docs/laravel-form-components/v5/inputs/input).
+Besides this, the email element behaves exactly the same as the [input component](/docs/laravel-form-components/{version}/inputs/input).
diff --git a/docs/inputs/input.md b/docs/inputs/input.md
@@ -59,7 +59,7 @@ When there are errors for a field, the `aria-invalid` and `aria-describedby` att
 ```
 
 The actual error message won't be rendered from the input component itself, but it can be automatically rendered for you
-by wrapping the `<x-input />` component inside of a `<x-form-group />` component. Please refer to the [form-group documentation](/docs/laravel-form-components/v5/form/form-group#error-handling) for more information.
+by wrapping the `<x-input />` component inside of a `<x-form-group />` component. Please refer to the [form-group documentation](/docs/laravel-form-components/{version}/form/form-group#error-handling) for more information.
 
 The `aria-describedby` attribute takes the `name` attribute and appends `-error` to it, which will be the id given to the error message rendered by the `<x-form-group />` component. If you already have `aria-describedby` set on the input, the attribute
 value will be merged with the error attribute value.
diff --git a/docs/inputs/password.md b/docs/inputs/password.md
@@ -71,4 +71,4 @@ Like the other inputs, the password input can also have leading addons, but sinc
 includes a password toggle as a trailing icon addon, you are not able to add a trailing addon
 to the password input. If you need a trailing addon, you should use the input component instead.
 
-See the [input documentation](/docs/laravel-form-components/v5/inputs/input#addons) for more information.
+See the [input documentation](/docs/laravel-form-components/{version}/inputs/input#addons) for more information.
diff --git a/docs/inputs/switch-toggle.md b/docs/inputs/switch-toggle.md
@@ -12,7 +12,7 @@ for more info.
 
 ## Installation
 
-While the `switch-toggle` component works out-of-the-box when you've [set the directive](/docs/laravel-form-components/v5/installation#directives),
+While the `switch-toggle` component works out-of-the-box when you've [set the directive](/docs/laravel-form-components/{version}/installation#directives),
 we recommend that you install and compile the JavaScript libraries before you deploy to production:
 
 - [Alpine.js](https://github.com/alpinejs/alpine) `^2.8`
@@ -120,7 +120,7 @@ These sizes also come in responsive variants, so if you wanted the switch small
 <x-switch-toggle class="switch-toggle--sm lg:switch-toggle--lg" />
 ```
 
-You are free to add your own sizes in your own stylesheets. Just reference the [switch toggle styles](https://github.com/rawilk/laravel-form-components/blob/master/resources/sass/utils/_switch.scss#L126) for guidance.
+You are free to add your own sizes in your own stylesheets. Just reference the [switch toggle styles](https://github.com/rawilk/laravel-form-components/blob/{branch}/resources/sass/utils/_switch.scss#L126) for guidance.
 
 ## Icons
 
diff --git a/docs/inputs/textarea.md b/docs/inputs/textarea.md
@@ -44,5 +44,5 @@ If you are using livewire, the textarea will allow livewire to set the value ins
 
 ## Reference
 
-Since the textarea component extends the [input component](/docs/laravel-form-components/v5/inputs/input), you are able
+Since the textarea component extends the [input component](/docs/laravel-form-components/{version}/inputs/input), you are able
 to do a lot of the same things you can with the input element, such as error handling and addons.
diff --git a/docs/installation.md b/docs/installation.md
@@ -27,7 +27,7 @@ You may publish the config file via:
 php artisan fc:publish
 ```
 
-[Click here](https://github.com/rawilk/laravel-form-components/blob/master/config/form-components.php) to view the default configuration.
+[Click here](https://github.com/rawilk/laravel-form-components/blob/{branch}/config/form-components.php) to view the default configuration.
 
 ## Directives
 
@@ -86,9 +86,9 @@ This is assuming your stylesheet is located in the `./resources/css/` directory
 
 You could copy the built CSS from `vendor/rawilk/laravel-components/resources/js/laravel-form-components-styles/dist/styles.css` into your public folder, and then use a `link` tag in your blade/html to get it: `<link rel="stylesheet" href="{{ asset('css/laravel-form-components.css') }}">`.
 
-If you would like to customize the CSS we provide, head over to [the section on Customizing CSS](/docs/laravel-form-components/v5/advanced-usage/customizing-css).
+If you would like to customize the CSS we provide, head over to [the section on Customizing CSS](/docs/laravel-form-components/{version}/advanced-usage/customizing-css).
 
-> {tip} If you are using Purge CSS or Tailwind's JIT compiler, you should check out the section on [Purge CSS](/docs/laravel-form-components/v5/advanced-usage/customizing-css#purge-csstailwind-jit)
+> {tip} If you are using Purge CSS or Tailwind's JIT compiler, you should check out the section on [Purge CSS](/docs/laravel-form-components/{version}/advanced-usage/customizing-css#purge-csstailwind-jit)
 > to prevent styles from being lost in production or at compile time.
 
 ## Components
@@ -104,7 +104,7 @@ and/or view of your own.
 
 ## Component JavaScript
 
-Some components, such as the [custom select component](/docs/laravel-form-components/v5/selects/custom-select), require custom
+Some components, such as the [custom select component](/docs/laravel-form-components/{version}/selects/custom-select), require custom
 JavaScript to run. The JavaScript is extracted to an external file since it is pretty substantial and should be minified. If
 you are using any components that depend on this JavaScript, be sure you are pulling the scripts in through either the
 `@fcJavaScript` or `@fcScripts` blade directives in your layout file. See [directives](#directives) for more information.
diff --git a/docs/selects/custom-select.md b/docs/selects/custom-select.md
@@ -12,13 +12,13 @@ custom option markup while still providing usability functionalities such as key
 ## Installation
 
 The custom select component requires Alpine.js and Popper.js, as well as some custom JavaScript written into the package to work.
-Ensure you have the proper [directives](/docs/laravel-form-componentsvalue-fieldinstallation#directives) in your layout file.
+Ensure you have the proper [directives](/docs/laravel-form-components/installation#directives) in your layout file.
 In production, we recommend you install and compile the JavaScript libraries before you deploy:
 
 - [Alpine.js](https://github.com/alpinejs/alpine) `^2.8`
 - [Popper.js](https://popper.js.org/) `^2.9.1`
 
-> {tip} See the [JavaScript Dependencies section](/docs/laravel-form-components/v5/installation#javascript-dependencies) for more information on installing them.
+> {tip} See the [JavaScript Dependencies section](/docs/laravel-form-components/{version}/installation#javascript-dependencies) for more information on installing them.
 
 ## Basic Usage
 
@@ -234,4 +234,4 @@ the select menu now. In addition to positioning the menu when opened, Popper.js
 ## Addons
 
 The custom select component supports leading addons, but since there are already elements appended to the end
-of the button trigger, trailing addons are not supported. For more information on addons, see [the input documentation](/docs/laravel-form-components/v5/inputs/input#addons).
+of the button trigger, trailing addons are not supported. For more information on addons, see [the input documentation](/docs/laravel-form-components/{version}/inputs/input#addons).
diff --git a/docs/selects/select.md b/docs/selects/select.md
@@ -82,5 +82,5 @@ You can easily create a multiple select by setting `multiple` to `true`:
 
 ## Reference
 
-Since the select component extends the [input component](/docs/laravel-form-components/v5/inputs/input), you are able
+Since the select component extends the [input component](/docs/laravel-form-components/{version}/inputs/input), you are able
 to do a lot of the same things you can with the input element, such as error handling and addons.
diff --git a/docs/selects/timezone-select.md b/docs/selects/timezone-select.md
@@ -38,7 +38,7 @@ With both methods, you can use a boolean value `false` to include every timezone
 ## Custom Select Support
 
 As of version `1.4.0`, the timezone select can be rendered either as a native select input, or by using the
-[custom-select component](/docs/laravel-form-componentsvalue-fieldcomponents/custom-select). To use the custom-select
+[custom-select component](/docs/laravel-form-components/components/custom-select). To use the custom-select
 component, simply pass in a true boolean value for the `use-custom-select` attribute on the timezone select.
 
 ```html
@@ -49,4 +49,4 @@ By default, the timezone select uses the native select input, so you will explic
 the custom-select component any time you render the timezone select component.
 
 > {note} If you want to render it as a custom-select, you need to ensure you have followed the
-[installation steps](/docs/laravel-form-components/v5/selects/custom-select#installation) for the `custom-select` component.
+[installation steps](/docs/laravel-form-components/{version}/selects/custom-select#installation) for the `custom-select` component.
diff --git a/docs/upgrade.md b/docs/upgrade.md
@@ -18,7 +18,7 @@ window.Alpine = Alpine;
 Alpine.start();
 ```
 
-This won't affect you if you are using the CDN scripts from the [configuration](https://github.com/rawilk/laravel-form-components/blob/master/config/form-components.php).
+This won't affect you if you are using the CDN scripts from the [configuration](https://github.com/rawilk/laravel-form-components/blob/{branch}/config/form-components.php).
 
 ### Additional stylesheet option
 
@@ -28,7 +28,7 @@ If you choose to import the compiled styles for this package into your own style
 @import "../../vendor/rawilk/laravel-form-components/resources/js/laravel-form-components-styles/dist/styles.min.css";
 ```
 
-See [customizing css](/docs/laravel-form-components/v5/advanced-usage/customizing-css#option-2-override-only-portions-in-your-css) for more information.
+See [customizing css](/docs/laravel-form-components/{version}/advanced-usage/customizing-css#option-2-override-only-portions-in-your-css) for more information.
 
 ## Upgrading from v3 to v4
 
@@ -42,13 +42,13 @@ Another major change with the styling is laravel-form-components now uses a sing
 
 In addition, we have stopped using the `primary` and `danger` variant names in favor of `blue` and `red` respectively. Be sure to update your tailwind config and stylesheets accordingly.
 
-For more info on styling, please see [the Customizing CSS section](/docs/laravel-form-components/v5/advanced-usage/customizing-css).
+For more info on styling, please see [the Customizing CSS section](/docs/laravel-form-components/{version}/advanced-usage/customizing-css).
 
 ### Added Dependencies
 
 Some components, such as the `custom-select` component, have a dependency on `Popper.js` now for positioning the menu. This will require you to ensure that dependency is installed in your project. If you customized the package's configuration file, you should make sure you pull in any updates to the configuration as well.
 
-See [the custom select docs](/docs/laravel-form-components/v5/selects/custom-select#installation) for more information.
+See [the custom select docs](/docs/laravel-form-components/{version}/selects/custom-select#installation) for more information.
 
 ### Custom Select
 
