fix image imports after merge

Author: jderochervlk

_blogposts/2020-08-28-new-rescript-logo.mdx

@@ -15,7 +15,7 @@ Here it is!
 
 <Image
   withShadow={false}
-  src="/static/blog/rescript-launch/ReScript-1.jpg"
+  src="/blog/rescript-launch/ReScript-1.jpg"
   caption="Comparison between the Reason, BuckleScript and ReScript logos"
 />
 
@@ -30,7 +30,7 @@ The new logo addresses all these and more:
 
 <Image
   withShadow={false}
-  src="/static/blog/rescript-launch/ReScript-2.jpg"
+  src="/blog/rescript-launch/ReScript-2.jpg"
   caption="Logo comparison on social media"
 />
 
@@ -40,7 +40,7 @@ A minimal logo design is achieved by putting aside all distractions while focusi
 
 <Image
   withShadow={false}
-  src="/static/blog/rescript-launch/ReScript-4.jpg"
+  src="/blog/rescript-launch/ReScript-4.jpg"
   caption="ReScript logo variations and usage examples"
 />
 

_blogposts/2020-11-26-editor-support-release-1-0.mdx

@@ -34,6 +34,6 @@ Happy thanksgiving!
 
 <Image
   withShadow={false}
-  src="/static/blog/editor_support_article.jpg"
+  src="/blog/editor_support_article.jpg"
   caption="ReScript now offers autocompletion for VSCode and neovim (Sublime coming soon)"
 />

_blogposts/2025-11-04-reforging-build-system.mdx

@@ -1,8 +1,8 @@
 ---
 author: rescript-team
 date: "2025-11-04"
-previewImg: /static/blog/rescript-12-reforging-build-system.png
-articleImg: /static/blog/rescript-12-reforging-build-system.png
+previewImg: /blog/rescript-12-reforging-build-system.png
+articleImg: /blog/rescript-12-reforging-build-system.png
 badge: roadmap
 title: "Reforging the ReScript Build System"
 description: |

_blogposts/archived/2020-03-26-generalize-uncurry.mdx

@@ -53,17 +53,17 @@ message leaks the underlying encoding -- now all those limitations are gone!
 **Previously:**
 
 <img
-  src="/static/blog/archive/poly-error.png"
+  src="/blog/archive/poly-error.png"
   className="my-4 mx-auto max-h-[500px]"
 />
 
 <img
-  src="/static/blog/archive/label-error.png"
+  src="/blog/archive/label-error.png"
   className="my-4 mx-auto max-h-[500px]"
 />
 
 <img
-  src="/static/blog/archive/recursive-error.png"
+  src="/blog/archive/recursive-error.png"
   className="my-4 mx-auto max-h-[500px]"
 />
 
@@ -72,12 +72,12 @@ The error messages above are cryptic and hard to understand. And the limitation
 Now those limitations are all gone, you can have polymorphic uncurried recursive functions and it support labels.
 
 <img
-  src="/static/blog/archive/uncurry-label.png"
+  src="/blog/archive/uncurry-label.png"
   className="my-4 mx-auto max-h-[500px]"
 />
 
 <img
-  src="/static/blog/archive/recursive.png"
+  src="/blog/archive/recursive.png"
   className="my-4 mx-auto max-h-[500px]"
 />
 

_blogposts/archived/2020-05-06-state-of-reasonml-org-2020-q2-pt1.mdx

@@ -51,7 +51,7 @@ The initial work was mostly about understanding the information architecture, re
 
 <Image
   withShadow={true}
-  src="/static/blog/archive/reasonml-org-color-palette-retina.jpg"
+  src="/blog/archive/reasonml-org-color-palette-retina.jpg"
   caption="Current state of the reasonml.org color palette"
 />
 
@@ -75,7 +75,7 @@ Our goal is to have a properly curated, well structured and streamlined overview
 
 <Image
   withShadow={true}
-  src="/static/blog/archive/reasonml-org-structure-retina.jpg"
+  src="/blog/archive/reasonml-org-structure-retina.jpg"
   caption="First hand-sketches of the reasonml.org structure"
 />
 

_blogposts/archived/2020-05-12-state-of-reasonml-org-2020-q2-pt3.mdx

@@ -35,7 +35,7 @@ We don't have any **search functionality** yet, and this will take some more tim
 There were some solutions, but still, Algolia turned out to be the best candidate with its smallest pricing tier. We don't want to rely on the Algolia OSS webscraping API, since it doesn't give us enough control on manipulating the search results, and we need more control if we want to be able to design a custom search experience.
 
 <Image
-  src="/static/blog/archive/search-mockup.jpg"
+  src="/blog/archive/search-mockup.jpg"
   withShadow={true}
   caption="A unified search overlay mockup for prose & API content"
 />
@@ -47,7 +47,7 @@ We did the ground work for our search feature and we will get into more detail a
 We also invested a lot of time into thinking about the future of the Reason playground from a UX perspective. Our most important goal is to make it possible to switch BuckleScript versions on demand. We also wanted the relevant Reason version to be part of the playground bundle.
 
 <Image
-  src="/static/blog/archive/playground-mockup.jpg"
+  src="/blog/archive/playground-mockup.jpg"
   withShadow={true}
   caption="UI mockup for the new playground (Desktop version)"
 />

_blogposts/archived/2020-05-15-state-of-reasonml-org-2020-q2-pt4.mdx

@@ -45,7 +45,7 @@ In the past few months, we observed more and more newcomers getting into the Buc
 Fair enough, the only "real numbers and statistics" we can showcase are vague, but still interesting: Just typing in ["reasonml" on Youtube](https://www.youtube.com/results?search_query=reasonml) shows a list of videos mostly targeted to JS audiences.
 
 <Image
-  src="/static/blog/archive/youtube-search-reasonml.jpg"
+  src="/blog/archive/youtube-search-reasonml.jpg"
   withShadow={true}
   caption="Top hits on Youtube for 'reasonml' (not logged in, anonymous browser session)"
 />