upgrade to docusaurus v3

Author: jaimergp

blog/2020-02-04-gsoc.md

@@ -39,7 +39,7 @@ detailed listing of the issues that need work.
       > Run true integration testing on a copy of the graph to better
       > test code changes and improve our CI process.
       >
-      > **Issue**: <https://github.com/regro/cf-scripts/issues/261>
+      > **Issue**: [regro/cf-scripts261](https://github.com/regro/cf-scripts/issues/261)
       >
       > **Experience Level**: advanced
 
@@ -49,7 +49,7 @@ detailed listing of the issues that need work.
       Address any of the issues in the milestone above related to code
       refactoring and cleanup.
 
-      **Issues**: <https://github.com/regro/cf-scripts/milestone/4>
+      **Issues**: [regro/cf-scripts milestone #4](https://github.com/regro/cf-scripts/milestone/4)
 
       **Experience Level**: beginner to advanced
 
@@ -63,7 +63,7 @@ detailed listing of the issues that need work.
     automated infrastructure to propose the migration of the pin itself.
     The project here is to add this functionality to our infrastructure.
 
-    **Issue**: <https://github.com/regro/cf-scripts/issues/665>
+    **Issue**: [regro/cf-scripts#665](https://github.com/regro/cf-scripts/issues/665)
 
     **Experience Level**: advanced
 
@@ -76,7 +76,7 @@ detailed listing of the issues that need work.
     `conda` index. We currently do not take this delay into account when
     issuing PRs in a migration.
 
-    **Issue**: <https://github.com/regro/cf-scripts/issues/595>
+    **Issue**: [regro/cf-scripts#595](https://github.com/regro/cf-scripts/issues/595)
 
     **Experience Level**: beginner
 
@@ -89,7 +89,7 @@ detailed listing of the issues that need work.
     have determined that a suitable fraction of the packages effected by
     a migration have been properly rebuilt.
 
-    **Issue**: <https://github.com/regro/cf-scripts/issues/595>
+    **Issue**: [regro/cf-scripts#595](https://github.com/regro/cf-scripts/issues/595)
 
     **Experience Level**: moderate
 
@@ -107,6 +107,6 @@ detailed listing of the issues that need work.
     and also scaling that process to the entire set of `conda-forge`
     packages.
 
-    **Issue**: <https://github.com/regro/cf-scripts/issues/664>
+    **Issue**: [regro/cf-scripts#664](https://github.com/regro/cf-scripts/issues/664)
 
     **Experience Level**: moderate

blog/2020-03-05-grayskull.md

@@ -27,7 +27,7 @@ looking for packages on [PyPI](https://pypi.org/), and it is available
 on [PyPI](https://pypi.org/project/grayskull/) and
 [conda-forge](https://github.com/conda-forge/grayskull-feedstock). The
 GitHub repository for this package is:
-<https://github.com/marcelotrevisani/grayskull>.
+[marcelotrevisani/grayskull](https://github.com/marcelotrevisani/grayskull).
 
 Before Grayskull, we just had `conda-build skeleton` to generate recipes
 for Python packages on PyPI. In all other aspects, the difference of
@@ -356,8 +356,8 @@ grayskul pypi pytest requests=2.21.0 colorama
 
 ## Issues
 
-Any problem, question, suggestions please feel free to open an issue on
-the repository: <https://github.com/marcelotrevisani/grayskull/issues>.
+Any problem, question, suggestions please feel free to open [an issue on
+the repository](https://github.com/marcelotrevisani/grayskull/issues).
 
 Contributions are very welcome! :)
 

blog/2020-11-20-anaconda-tos.md

@@ -38,8 +38,8 @@ employees also provide help with maintaining some of the most complex
 package recipes in conda-forge.
 
 Note that Anaconda Inc has also said that part of the revenue from the
-TOS change will be donated to OSS projects. (See this blog post:
-<https://www.anaconda.com/blog/sustaining-our-stewardship-of-the-open-source-data-science-community>).
+TOS change will be donated to OSS projects. (see this [blog 
+post](https://www.anaconda.com/blog/sustaining-our-stewardship-of-the-open-source-data-science-community)).
 You should be aware that `conda-forge` is a part of NumFOCUS, and so it
 stands to benefit from the change in TOS, as do many other OSS projects.
 

blog/2021-11-03-tensorflow-gpu.md

@@ -46,8 +46,7 @@ libraries.
 We are still missing Windows builds for TensorFlow (CPU & CUDA,
 unfortunately) and would love the community to help us out with that.
 There is an open PR, but it probably needs some poking in Bazel to get
-it to pass:
-<https://github.com/conda-forge/tensorflow-feedstock/pull/111>.
+it to pass: [conda-forge/tensorflow-feedstock#111](https://github.com/conda-forge/tensorflow-feedstock/pull/111).
 
 We hope that these new GPU builds will enable many more packages to be
 added to the conda-forge channel! We are already looking forward to the