diff options
author | Jan Karlo Dela Cruz <jankarlo.delacruz@gmail.com> | 2017-08-11 16:26:51 +0300 |
---|---|---|
committer | XhmikosR <xhmikosr@gmail.com> | 2017-08-11 16:26:51 +0300 |
commit | 537b5f012771069b182aabab651eff9723d785b0 (patch) | |
tree | 35ab3e62ecbd8ed062b7bdb0bf469e04762f86ad | |
parent | 185fe1b444e88cd9091e5a304094ed43ad8f84fc (diff) |
Fix broken links in documentation. (#23315)
-rw-r--r-- | _includes/callout-danger-async-methods.md | 2 | ||||
-rw-r--r-- | docs/4.0/components/alerts.md | 2 | ||||
-rw-r--r-- | docs/4.0/components/carousel.md | 2 | ||||
-rw-r--r-- | docs/4.0/components/dropdowns.md | 2 | ||||
-rw-r--r-- | docs/4.0/components/navs.md | 2 | ||||
-rw-r--r-- | docs/4.0/components/popovers.md | 2 | ||||
-rw-r--r-- | docs/4.0/components/scrollspy.md | 2 | ||||
-rw-r--r-- | docs/4.0/components/tooltips.md | 2 | ||||
-rw-r--r-- | docs/4.0/getting-started/webpack.md | 6 |
9 files changed, 11 insertions, 11 deletions
diff --git a/_includes/callout-danger-async-methods.md b/_includes/callout-danger-async-methods.md index 809643e1dc..ea08965f6d 100644 --- a/_includes/callout-danger-async-methods.md +++ b/_includes/callout-danger-async-methods.md @@ -3,5 +3,5 @@ All API methods are **asynchronous** and start a **transition**. They returns to the caller as soon as the transition is started but **before it ends**. In addition, a method call on a **transitioning component will be ignored**. -[See our Javascript documentation for more informations.]({{ site.baseurl }}/getting-started/javascript/) +[See our Javascript documentation for more informations.]({{ site.baseurl }}/docs/{{ site.docs_version }}/getting-started/javascript/) {% endcallout %} diff --git a/docs/4.0/components/alerts.md b/docs/4.0/components/alerts.md index a6a6616d8a..d3eb8bd184 100644 --- a/docs/4.0/components/alerts.md +++ b/docs/4.0/components/alerts.md @@ -50,7 +50,7 @@ Alerts can also contain additional HTML elements like headings, paragraphs and d Using the alert JavaScript plugin, it's possible to dismiss any alert inline. Here's how: - Be sure you've loaded the alert plugin, or the compiled Bootstrap JavaScript. -- If you're building our JS from source, it [requires `util.js`]({{ site.baseurl }}/docs/getting-started/javascript/#util). The compiled version includes this. +- If you're building our JS from source, it [requires `util.js`]({{ site.baseurl }}/docs/{{ site.docs_version }}/getting-started/javascript/#util). The compiled version includes this. - Add a dismiss button and the `.alert-dismissible` class, which adds extra padding to the right of the alert and positions the `.close` button. - On the dismiss button, add the `data-dismiss="alert"` attribute, which triggers the JavaScript functionality. Be sure to use the `<button>` element with it for proper behavior across all devices. - To animate alerts when dismissing them, be sure to add the `.fade` and `.show` classes. diff --git a/docs/4.0/components/carousel.md b/docs/4.0/components/carousel.md index 5061c94069..4919e1ac28 100644 --- a/docs/4.0/components/carousel.md +++ b/docs/4.0/components/carousel.md @@ -14,7 +14,7 @@ In browsers where the [Page Visibility API](https://www.w3.org/TR/page-visibilit Please be aware that nested carousels are not supported, and carousels are generally not compliant with accessibility standards. -Lastly, if you're building our JS from source, it [requires `util.js`]({{ site.baseurl }}/docs/getting-started/javascript/#util). +Lastly, if you're building our JS from source, it [requires `util.js`]({{ site.baseurl }}/docs/{{ site.docs_version }}/getting-started/javascript/#util). ## Example diff --git a/docs/4.0/components/dropdowns.md b/docs/4.0/components/dropdowns.md index 6ebce5f042..6961c89fdb 100644 --- a/docs/4.0/components/dropdowns.md +++ b/docs/4.0/components/dropdowns.md @@ -12,7 +12,7 @@ Dropdowns are toggleable, contextual overlays for displaying lists of links and Dropdowns are built on a third party library, [Popper.js](https://popper.js.org), which provides dynamic positioning and viewport detection. Be sure to include [popper.min.js](https://cdnjs.cloudflare.com/ajax/libs/popper.js/1.11.0/umd/popper.min.js) before Bootstrap's JavaScript. -If you're building our JS from source, it [requires `util.js`]({{ site.baseurl }}/docs/getting-started/javascript/#util). +If you're building our JS from source, it [requires `util.js`]({{ site.baseurl }}/docs/{{ site.docs_version }}/getting-started/javascript/#util). ## Accessibility diff --git a/docs/4.0/components/navs.md b/docs/4.0/components/navs.md index de8230ecf9..dc014a1ca6 100644 --- a/docs/4.0/components/navs.md +++ b/docs/4.0/components/navs.md @@ -297,7 +297,7 @@ Add dropdown menus with a little extra HTML and the [dropdowns JavaScript plugin Use the tab JavaScript plugin—include it individually or through the compiled `bootstrap.js` file—to extend our navigational tabs and pills to create tabbable panes of local content, even via dropdown menus. -If you're building our JS from source, it [requires `util.js`]({{ site.baseurl }}/docs/getting-started/javascript/#util). +If you're building our JS from source, it [requires `util.js`]({{ site.baseurl }}/docs/{{ site.docs_version }}/getting-started/javascript/#util). Dynamic tabbed interfaces, as described in the [<abbr title="Web Accessibility Initiative">WAI</abbr> <abbr title="Accessible Rich Internet Applications">ARIA</abbr> Authoring Practices](https://www.w3.org/TR/wai-aria-practices/#tabpanel), require `role="tablist"`, `role="tab"`, `role="tabpanel"`, and additional `aria-` attributes in order to convey their structure, functionality and current state to users of assistive technologies (such as screen readers). diff --git a/docs/4.0/components/popovers.md b/docs/4.0/components/popovers.md index 2a4b5bd00b..32261eb6c5 100644 --- a/docs/4.0/components/popovers.md +++ b/docs/4.0/components/popovers.md @@ -13,7 +13,7 @@ Things to know when using the popover plugin: - Popovers rely on the 3rd party library [Popper.js](https://popper.js.org) for positioning. You must include [popper.min.js](https://cdnjs.cloudflare.com/ajax/libs/popper.js/1.11.0/umd/popper.min.js) before bootstrap.js in order for popovers to work! - Popovers require the [tooltip plugin]({{ site.baseurl }}/docs/{{ site.docs_version }}/components/tooltips/) as a dependency. -- If building our JS from source, it [requires `util.js`]({{ site.baseurl }}/docs/getting-started/javascript/#util). +- If building our JS from source, it [requires `util.js`]({{ site.baseurl }}/docs/{{ site.docs_version }}/getting-started/javascript/#util). - Popovers are opt-in for performance reasons, so **you must initialize them yourself**. - Zero-length `title` and `content` values will never show a popover. - Specify `container: 'body'` to avoid rendering problems in more complex components (like our input groups, button groups, etc). diff --git a/docs/4.0/components/scrollspy.md b/docs/4.0/components/scrollspy.md index 9d7e8f5024..32a86d839f 100644 --- a/docs/4.0/components/scrollspy.md +++ b/docs/4.0/components/scrollspy.md @@ -10,7 +10,7 @@ toc: true Scrollspy has a few requirements to function properly: -- If building our JS from source, it [requires `util.js`]({{ site.baseurl }}/docs/getting-started/javascript/#util). +- If building our JS from source, it [requires `util.js`]({{ site.baseurl }}/docs/{{ site.docs_version }}/getting-started/javascript/#util). - It must to be used on a Bootstrap [nav component]({{ site.baseurl }}/docs/{{ site.docs_version }}/components/navs/) or [list group]({{ site.baseurl }}/docs/{{ site.docs_version }}/components/list-group/). - Scrollspy requires `position: relative;` on the element you're spying on, usually the `<body>`. - When spying on elements other than the `<body>`, be sure to have a `height` set and `overflow-y: scroll;` applied. diff --git a/docs/4.0/components/tooltips.md b/docs/4.0/components/tooltips.md index 5b5578e098..7018b24425 100644 --- a/docs/4.0/components/tooltips.md +++ b/docs/4.0/components/tooltips.md @@ -11,7 +11,7 @@ toc: true Things to know when using the tooltip plugin: - Tooltips rely on the 3rd party library [Popper.js](https://popper.js.org) for positioning. You must include [popper.min.js](https://cdnjs.cloudflare.com/ajax/libs/popper.js/1.10.1/umd/popper.min.js) before bootstrap.js in order for tooltips to work! -- If building our JS from source, it [requires `util.js`]({{ site.baseurl }}/docs/getting-started/javascript/#util). +- If building our JS from source, it [requires `util.js`]({{ site.baseurl }}/docs/{{ site.docs_version }}/getting-started/javascript/#util). - Tooltips are opt-in for performance reasons, so **you must initialize them yourself**. - Tooltips with zero-length titles are never displayed. - Specify `container: 'body'` to avoid rendering problems in more complex components (like our input groups, button groups, etc). diff --git a/docs/4.0/getting-started/webpack.md b/docs/4.0/getting-started/webpack.md index 84ad74c7f7..ec748c48e3 100644 --- a/docs/4.0/getting-started/webpack.md +++ b/docs/4.0/getting-started/webpack.md @@ -8,11 +8,11 @@ toc: true ## Installing Bootstrap -[Install bootstrap](/getting-started/download/#npm) as a node module using npm. +[Install bootstrap]({{ site.baseurl }}/docs/{{ site.docs_version }}/getting-started/download/#npm) as a node module using npm. ## Importing JavaScript -Import [Bootstrap's JavaScript](/getting-started/javascript/) by adding this line to your app's entry point (usually `index.js` or `app.js`): +Import [Bootstrap's JavaScript]({{ site.baseurl }}/docs/{{ site.docs_version }}/getting-started/javascript/) by adding this line to your app's entry point (usually `index.js` or `app.js`): {% highlight js %} import 'bootstrap'; @@ -55,7 +55,7 @@ Notice that if you chose to **import plugins individually**, you must also insta To enjoy the full potential of Bootstrap and customize it to your needs, use the source files as a part of your project's bundling process. -First, create your own `_custom.scss` and use it to override the [built-in custom variables](/getting-started/options/). Then, use your main sass file to import your custom variables, followed by Bootstrap: +First, create your own `_custom.scss` and use it to override the [built-in custom variables]({{ site.baseurl }}/docs/{{ site.docs_version }}/getting-started/options/). Then, use your main sass file to import your custom variables, followed by Bootstrap: {% highlight scss %} @import "custom"; @import "~bootstrap/scss/bootstrap"; |