Patch all 404 errors

docs/1.0/components/alerts.html

@@ -762,7 +762,7 @@
 
 <ul>
   <li>Be sure you’ve loaded the alert plugin, or the compiled Bootstrap JavaScript.</li>
-  <li>If you’re building our JavaScript from source, it <a href="/docs/1.0/getting-started/javascript/#util">requires <code class="highlighter-rouge">util.js</code></a>. The compiled version includes this.</li>
+  <li>If you’re building our JavaScript from source, it requires <code class="highlighter-rouge">util.js</code>. The compiled version includes this.</li>
   <li>Add a dismiss button and the <code class="highlighter-rouge">.alert-dismissible</code> class, which adds extra padding to the right of the alert and positions the <code class="highlighter-rouge">.close</code> button.</li>
   <li>On the dismiss button, add the <code class="highlighter-rouge">data-dismiss="alert"</code> attribute, which triggers the JavaScript functionality. Be sure to use the <code class="highlighter-rouge">&lt;button&gt;</code> element with it for proper behavior across all devices.</li>
   <li>To animate alerts when dismissing them, be sure to add the <code class="highlighter-rouge">.fade</code> and <code class="highlighter-rouge">.show</code> classes.</li>

docs/1.0/components/card.html

@@ -959,7 +959,7 @@
 
 <h2 id="text-alignment">Text alignment</h2>
 
-<p>You can quickly change the text alignment of any card—in its entirety or specific parts—with our <a href="/docs/1.0/utilities/text/#text-alignment">text align classes</a>.</p>
+<p>You can quickly change the text alignment of any card—in its entirety or specific parts—with our text align classes.</p>
 
 <div class="bd-example" data-example-id="">
 <div class="card" style="width: 20rem;">

docs/1.0/components/collapse.html

@@ -709,7 +709,7 @@
 
 <h2 id="accordion-example">Accordion example</h2>
 
-<p>Using the <a href="/docs/1.0/components/card/">card</a> component, you can extend the default collapse behavior to create an accordion.</p>
+<p>Using the <strong>card</strong> component, you can extend the default collapse behavior to create an accordion.</p>
 
 <div class="bd-example" data-example-id="">
 <div id="accordion" role="tablist" aria-multiselectable="true" class="card-collapse">

docs/1.0/components/forms.html

@@ -1385,7 +1385,8 @@
 <div class="bd-callout bd-callout-warning">
 <h4 id="caveat-with-anchors">Caveat with anchors</h4>
 
-<p>By default, browsers will treat all native form controls (<code class="highlighter-rouge">&lt;input&gt;</code>, <code class="highlighter-rouge">&lt;select&gt;</code> and <code class="highlighter-rouge">&lt;button&gt;</code> elements) inside a <code class="highlighter-rouge">&lt;fieldset disabled&gt;</code> as disabled, preventing both keyboard and mouse interactions on them. However, if your form also includes <code class="highlighter-rouge">&lt;a ... class="btn btn-*"&gt;</code> elements, these will only be given a style of <code class="highlighter-rouge">pointer-events: none</code>. As noted in the section about <a href="/docs/1.0/components/buttons/#disabled-state">disabled state for buttons</a> (and specifically in the sub-section for anchor elements), this CSS property is not yet standardized and isn’t fully supported in Opera 18 and below, or in Internet Explorer 10, and won’t prevent keyboard users from being able to focus or activate these links. So to be safe, use custom JavaScript to disable such links.</p>
+<p>By default, browsers will treat all native form controls (<code class="highlighter-rouge">&lt;input&gt;</code>, <code class="highlighter-rouge">&lt;select&gt;</code> and <code class="highlighter-rouge">&lt;button&gt;</code> elements) inside a <code class="highlighter-rouge">&lt;fieldset disabled&gt;</code> as disabled, preventing both keyboard and mouse interactions on them. However, if your form also includes <code class="highlighter-rouge">&lt;a ... class="btn btn-*"&gt;</code> elements, these will only be given a style of <code class="highlighter-rouge">pointer-events: none</code>. 
+As noted in the section about disabled state for buttons (and specifically in the sub-section for anchor elements), this CSS property is not yet standardized and isn’t fully supported in Opera 18 and below, or in Internet Explorer 10, and won’t prevent keyboard users from being able to focus or activate these links. So to be safe, use custom JavaScript to disable such links.</p>
 </div>
 
 <div class="bd-callout bd-callout-danger">

docs/1.0/components/modal.html

@@ -905,7 +905,7 @@
 
 <h3 id="tooltips-and-popovers">Tooltips and popovers</h3>
 
-<p><a href="/docs/1.0/components/tooltips/">Tooltips</a> and <a href="/docs/1.0/components/popovers/">popovers</a> can be placed within modals as needed. When modals are closed, any tooltips and popovers within are also automatically dismissed.</p>
+<p>Tooltips and popovers can be placed within modals as needed. When modals are closed, any tooltips and popovers within are also automatically dismissed.</p>
 
 <div id="exampleModalPopovers" class="modal fade" tabindex="-1" role="dialog" aria-labelledby="exampleModalPopoversLabel" aria-hidden="true">
   <div class="modal-dialog" role="document">

docs/1.0/components/navbar.html

@@ -686,9 +686,9 @@
 <ul>
   <li>Navbars require a wrapping <code class="highlighter-rouge">.navbar</code> with <code class="highlighter-rouge">.navbar-expand{-sm|-md|-lg|-xl}</code> for responsive collapsing and <a href="#color-schemes">color scheme</a> classes.</li>
   <li>Navbars and their contents are fluid by default. Use <a href="#containers">optional containers</a> to limit their horizontal width.</li>
-  <li>Use our <a href="/docs/1.0/utilities/spacing/">spacing</a> and <a href="/docs/1.0/utilities/flex/">flex</a> utility classes for controlling spacing and alignment within navbars.</li>
+  <li>Use our spacing and flex utility classes for controlling spacing and alignment within navbars.</li>
   <li>Navbars are responsive by default, but you can easily modify them to change that. Responsive behavior depends on our Collapse JavaScript plugin.</li>
-  <li>Navbars are hidden by default when printing. Force them to be printed by adding <code class="highlighter-rouge">.d-print</code> to the <code class="highlighter-rouge">.navbar</code>. See the <a href="/docs/1.0/utilities/display/">display</a> utility class.</li>
+  <li>Navbars are hidden by default when printing. Force them to be printed by adding <code class="highlighter-rouge">.d-print</code> to the <code class="highlighter-rouge">.navbar</code>. See the display utility class.</li>
   <li>Ensure accessibility by using a <code class="highlighter-rouge">&lt;nav&gt;</code> element or, if using a more generic element such as a <code class="highlighter-rouge">&lt;div&gt;</code>, add a <code class="highlighter-rouge">role="navigation"</code> to every navbar to explicitly identify it as a landmark region for users of assistive technologies.</li>
 </ul>
 
@@ -834,7 +834,7 @@
 <nav class="navbar navbar-expand-lg bg-primary">
     <div class="container">
         <div class="navbar-translate">
-            <a class="navbar-brand" href="/presentation.html">Brand</a>
+            <a class="navbar-brand" href="#">Brand</a>
             <button class="navbar-toggler" type="button" data-toggle="collapse" aria-expanded="false" aria-label="Toggle navigation">
                 <span class="navbar-toggler-icon"></span>
                 <span class="navbar-toggler-icon"></span>
@@ -867,7 +867,7 @@
 <div class="highlight"><pre><code class="language-html" data-lang="html"><span class="nt">&lt;nav</span> <span class="na">class=</span><span class="s">"navbar navbar-expand-lg bg-primary"</span><span class="nt">&gt;</span>
     <span class="nt">&lt;div</span> <span class="na">class=</span><span class="s">"container"</span><span class="nt">&gt;</span>
         <span class="nt">&lt;div</span> <span class="na">class=</span><span class="s">"navbar-translate"</span><span class="nt">&gt;</span>
-            <span class="nt">&lt;a</span> <span class="na">class=</span><span class="s">"navbar-brand"</span> <span class="na">href=</span><span class="s">"/presentation.html"</span><span class="nt">&gt;</span>Brand<span class="nt">&lt;/a&gt;</span>
+            <span class="nt">&lt;a</span> <span class="na">class=</span><span class="s">"navbar-brand"</span> <span class="na">href=</span><span class="s">"#"</span><span class="nt">&gt;</span>Brand<span class="nt">&lt;/a&gt;</span>
             <span class="nt">&lt;button</span> <span class="na">class=</span><span class="s">"navbar-toggler"</span> <span class="na">type=</span><span class="s">"button"</span> <span class="na">data-toggle=</span><span class="s">"collapse"</span> <span class="na">aria-expanded=</span><span class="s">"false"</span> <span class="na">aria-label=</span><span class="s">"Toggle navigation"</span><span class="nt">&gt;</span>
                 <span class="nt">&lt;span</span> <span class="na">class=</span><span class="s">"navbar-toggler-icon"</span><span class="nt">&gt;&lt;/span&gt;</span>
                 <span class="nt">&lt;span</span> <span class="na">class=</span><span class="s">"navbar-toggler-icon"</span><span class="nt">&gt;&lt;/span&gt;</span>
@@ -1281,7 +1281,7 @@
 
 <h2 id="placement">Placement</h2>
 
-<p>Use our <a href="/docs/1.0/utilities/position/">position utilities</a> to place navbars in non-static positions. Choose from fixed to the top, fixed to the bottom, or stickied to the top (scrolls with the page until it reaches the top, then stays there). Fixed navbars use <code class="highlighter-rouge">position: fixed</code>, meaning they’re pulled from the normal flow of the DOM and may require custom CSS (e.g., <code class="highlighter-rouge">padding-top</code> on the <code class="highlighter-rouge">&lt;body&gt;</code>) to prevent overlap with other elements.</p>
+<p>Use our position utilities to place navbars in non-static positions. Choose from fixed to the top, fixed to the bottom, or stickied to the top (scrolls with the page until it reaches the top, then stays there). Fixed navbars use <code class="highlighter-rouge">position: fixed</code>, meaning they’re pulled from the normal flow of the DOM and may require custom CSS (e.g., <code class="highlighter-rouge">padding-top</code> on the <code class="highlighter-rouge">&lt;body&gt;</code>) to prevent overlap with other elements.</p>
 
 <p>Also note that <strong><code class="highlighter-rouge">.sticky-top</code> uses <code class="highlighter-rouge">position: sticky</code>, which <a href="https://caniuse.com/#feat=css-sticky">isn’t fully supported in every browser</a></strong>.</p>
 

docs/1.0/components/navs.html

@@ -735,7 +735,7 @@
 
 <h3 id="horizontal-alignment">Horizontal alignment</h3>
 
-<p>Change the horizontal alignment of your nav with <a href="/docs/1.0/layout/grid/#horizontal-alignment">flexbox utilities</a>. By default, navs are left-aligned, but you can easily change them to center or right aligned.</p>
+<p>Change the horizontal alignment of your nav with flexbox utilities. By default, navs are left-aligned, but you can easily change them to center or right aligned.</p>
 
 <p>Centered with <code class="highlighter-rouge">.justify-content-center</code>:</p>
 

docs/1.0/components/nucleo-icons.html

@@ -664,7 +664,8 @@
         <main class="col-12 col-md-9 col-xl-8 py-md-3 pl-md-5 bd-content" role="main">
           <h1 class="bd-title" id="content">Nucleo Icons</h1>
           <p class="bd-lead"></p>
-          <p>Through most of the examples in this kit, we have used 100 Nucleo Icons for the Black Dashboard. View all the <a href="https://demos.creative-tim.com/black-dashboard-pro/nucleo-icons.html">example icons</a>. If you want more than 2100 icons please check the official <a href="https://nucleoapp.com/?ref=1712">Nucleo Icons Pack</a>.</p>
+          <p>Through most of the examples in this kit, we have used 100 Nucleo Icons for the Black Dashboard. 
+          If you want more than 2100 icons please check the official <a href="https://nucleoapp.com/?ref=1712">Nucleo Icons Pack</a>.</p>
 
 <div class="bd-example" data-example-id="">
 <i class="tim-icons icon-single-02"></i>

docs/1.0/getting-started/flask-deploy-on-heroku.html

@@ -700,7 +700,7 @@
 <h2 id="what-is-flask">What is <a href="https://palletsprojects.com/p/flask/">Flask</a></h2>
 <hr />
 
-<p>Flask is a lightweight <a href="/what-is/wsgi/">WSGI</a> web application framework. It is designed to make getting started quick and easy, with the ability to scale up to complex applications.
+<p>Flask is a lightweight <a href="https://docs.appseed.us/what-is/wsgi/">WSGI</a> web application framework. It is designed to make getting started quick and easy, with the ability to scale up to complex applications.
 Classified as a microframework, Flask is written in Python and it does not require particular tools or libraries. It has no database abstraction layer, form validation, or any other components where pre-existing third-party libraries provide common functions.</p>
 
 <blockquote>

docs/1.0/getting-started/getting-started-flask.html

@@ -726,7 +726,7 @@
 <h2 id="what-is-flask">What is <a href="https://palletsprojects.com/p/flask/">Flask</a></h2>
 <hr />
 
-<p>Flask is a lightweight <a href="/what-is/wsgi/">WSGI</a> web application framework. It is designed to make getting started quick and easy, with the ability to scale up to complex applications.
+<p>Flask is a lightweight <a href="https://docs.appseed.us/what-is/wsgi/">WSGI</a> web application framework. It is designed to make getting started quick and easy, with the ability to scale up to complex applications.
 Classified as a microframework, Flask is written in Python and it does not require particular tools or libraries. It has no database abstraction layer, form validation, or any other components where pre-existing third-party libraries provide common functions.</p>
 
 <blockquote>
@@ -776,9 +776,9 @@ $ git version 2.10.1.windows.1 # <span class="nt">&lt;---</span> <span class="na
 <p>For more information on how to set up your environment please access the resources listed below. In case we’ve missed something, contact us on Discord.</p>
 
 <ul>
-  <li><a href="./setup-centos-for-development.md">Setup CentOS for development</a></li>
+  <li><a href="./setup-centos-for-development.html">Setup CentOS for development</a></li>
-  <li><a href="./setup-ubuntu-for-development.md">Setup Ubuntu for development</a></li>
+  <li><a href="./setup-ubuntu-for-development.html">Setup Ubuntu for development</a></li>
-  <li><a href="./setup-windows-for-development.md">Setup Windows for development</a></li>
+  <li><a href="./setup-windows-for-development.html">Setup Windows for development</a></li>
 </ul>
 
 <p><br /></p>