fix mdx links

Author: jderochervlk

markdown-pages/blog/archived/state-of-reasonml-org-2020-q2-pt4.mdx

@@ -10,7 +10,7 @@ description: |
 
 ## It's all Opinions
 
-This is the final part of our "State of reasonml.org Q1-2020" series. In [part 3](/blog/state-of-reasonml-org-2020-q2-pt3), we gave our readers some insights on advanced features we've been working on for `reasonml.org` and showed how our tools might help the community to build better documentation experiences themselves.
+This is the final part of our "State of reasonml.org Q1-2020" series. In [part 3](./state-of-reasonml-org-2020-q2-pt3.mdx), we gave our readers some insights on advanced features we've been working on for `reasonml.org` and showed how our tools might help the community to build better documentation experiences themselves.
 
 Apart from the general progress perspective of the `reasonml.org` project, we also want to give you some more context on how we envision the documentation landscape for the Reason language in the near future. It should give you a perspective on how we see things, and we hope it will kick off some constructive community discussions on where things should be heading.
 

markdown-pages/blog/bucklescript-is-rebranding.mdx

@@ -26,7 +26,7 @@ BuckleScript started with the idea that **JavaScript programmers deserved a grea
 - a fast & reliable toolchain much needed in front-end and Node development,
 - various JS interop features that spawned an ecosystem of well typed libraries,
 - a production-ready standard library,
-- [and recently](/blog/bucklescript-8-1-new-syntax), a fresh syntax made by a major contributor of Reason's old syntax.
+- [and recently](/blog/archived/bucklescript-8-1-new-syntax), a fresh syntax made by a major contributor of Reason's old syntax.
 
 These developments have attracted many people into our community. But one bigger challenge persisted: newcomers dropped out at the sheer amount of extra incongruent tools and learning overhead from having to understand OCaml concepts, Reason concepts, and BuckleScript's concepts. Take, for example, what's required to make a React app using BuckleScript:
 
@@ -72,7 +72,7 @@ No. The new syntax & tools sit alongside the existing code. We **won't** remove
 
 **What's the editor tooling story?**
 
-Much more streamlined now! See our [Editor Plugins](/docs/manual/editor-plugins) page.
+Much more streamlined now! See our [Editor Plugins](/docs/manual/editor-plugins.mdx) page.
 
 Reason-language-server will continue working as-is for existing usage. We as first party don't work on ocaml's language server.
 

markdown-pages/blog/first-class-dynamic-import-support.mdx

@@ -7,7 +7,7 @@ description: |
   A tour of new capabilities coming to ReScript v11
 ---
 
-> This is the third post covering new capabilities that'll ship in ReScript v11. You can check out the first post on [Better Interop with Customizable Variants](/blog/improving-interop) and the second post on [Enhanced Ergonomics for Record Types](/blog/enhanced-ergonomics-for-record-types).
+> This is the third post covering new capabilities that'll ship in ReScript v11. You can check out the first post on [Better Interop with Customizable Variants](./improving-interop.mdx) and the second post on [Enhanced Ergonomics for Record Types](./enhanced-ergonomics-for-record-types.mdx).
 
 ## Introduction
 

markdown-pages/blog/release-10-1.mdx

@@ -51,7 +51,7 @@ let logUserDetails = async (userId: string) => {
 }
 ```
 
-To learn more about our async / await feature, check out the relevant [manual section](/docs/manual/async-await).
+Learn more about async/await support in [our documentation](../../docs/manual/async-await.mdx).
 
 ## New `promise` builtin type and `Js.Promise2` module
 

markdown-pages/blog/release-11-0-0.mdx

@@ -16,7 +16,7 @@ Use your favorite package manager to install the new compiler release, e.g.:
 npm install rescript@11
 ```
 
-To upgrade your project or to find out if there are any breaking changes that affect you, please follow the [migration guide](/docs/manual/migrate-to-v11).
+You can find the complete migration guide [here](../../docs/manual/migrate-to-v11.mdx).
 
 The complete list of changes can be found [here](https://github.com/rescript-lang/rescript/blob/v11.0.0/CHANGELOG). Let's have a look at the most notable improvements.
 

markdown-pages/blog/uncurried-mode.mdx

@@ -7,7 +7,7 @@ description: |
   A tour of new capabilities coming to ReScript v11
 ---
 
-> This is the fourth post covering new capabilities that'll ship in ReScript v11. You can check out the first post on [Better Interop with Customizable Variants](/blog/improving-interop), the second post on [Enhanced Ergonomics for Record Types](/blog/enhanced-ergonomics-for-record-types) and the third post on [First-class Dynamic Import Support](/blog/first-class-dynamic-import-support).
+> This is the fourth post covering new capabilities that'll ship in ReScript v11. You can check out the first post on [Better Interop with Customizable Variants](./improving-interop.mdx), the second post on [Enhanced Ergonomics for Record Types](./enhanced-ergonomics-for-record-types.mdx), and the third post on [First-class Dynamic Import Support](./first-class-dynamic-import-support.mdx).
 
 ## Introduction
 

markdown-pages/community/overview.mdx

@@ -29,6 +29,4 @@ Your questions can go on:
 - Various GitHub repositories in our [GitHub org](https://github.com/rescript-lang/).
 - [Stack Overflow's `rescript` tag](https://stackoverflow.com/questions/tagged/rescript) (not frequently monitored).
 
-> We stand for inclusivity and good behavior. Please read our [Code of
-> Conduct](/community/code-of-conduct) and help us keeping our community healthy and
-> friendly!
+> We stand for inclusivity and good behavior. Please read our [Code of Conduct](./code-of-conduct.mdx) and help us keeping our community healthy and friendly!

markdown-pages/docs/manual/array-and-list.mdx

@@ -153,7 +153,7 @@ You'd use list for its resizability, its fast prepend (adding at the head), and
 
 Do **not** use list if you need to randomly access an item or insert at non-head position. Your code would end up obtuse and/or slow.
 
-The standard lib provides a [List module](api/stdlib/list).
+For accessing deeper, see [destructuring](./pattern-matching-destructuring.mdx).
 
 #### Immutable Prepend
 
@@ -192,7 +192,7 @@ var anotherList = {
 
 #### Access
 
-`switch` (described in the [pattern matching section](pattern-matching-destructuring)) is usually used to access list items:
+`switch` (described in the [pattern matching section](pattern-matching-destructuring.mdx)) is usually used to access list items:
 
 <CodeTab labels={["ReScript", "JS Output"]}>
 

markdown-pages/docs/manual/async-await.mdx

@@ -149,7 +149,7 @@ let checkAuth = async () => {
 }
 ```
 
-Note how we are essentially catching JS errors the same way as described in our [Exception](exception#catch-rescript-exceptions-from-js) section.
+Note how we are essentially catching JS errors the same way as described in our [Exception](./exception.mdx#catch-rescript-exceptions-from-js) section.
 
 You may unify error and value handling in a single switch as well:
 

markdown-pages/docs/manual/bind-to-js-function.mdx

@@ -109,7 +109,7 @@ In a `send`, the object is always the first argument. Actual arguments of the me
 
 ### Chaining
 
-Ever used `foo().bar().baz()` chaining ("fluent api") in JS OOP? We can model that in ReScript too, through the [pipe operator](pipe).
+Ever used `foo().bar().baz()` chaining ("fluent api") in JS OOP? We can model that in ReScript too, through the [pipe operator](pipe.mdx).
 
 ### Nested function call
 
@@ -164,7 +164,7 @@ var v = Path.join("a", "b");
 
 </CodeTab>
 
-`module` will be explained in [Import from/Export to JS](import-from-export-to-js).
+`module` will be explained in [Import from/Export to JS](import-from-export-to-js.mdx).
 
 ## Modeling Polymorphic Function