diff --git a/docs/blog/posts/2021-10-06-sharedTest.md b/docs/blog/posts/2021-10-06-sharedTest.md
index 30d4c63f6..4bf422cac 100644
--- a/docs/blog/posts/2021-10-06-sharedTest.md
+++ b/docs/blog/posts/2021-10-06-sharedTest.md
@@ -124,7 +124,7 @@ There are some Google's projects have used sharedTest pattern to sharing test co
 [accompanist: [All] Share tests to run on Robolectric & Emulators by chrisbanes][10]
 
 [1]: https://medium.com/androiddevelopers/write-once-run-everywhere-tests-on-android-88adb2ba20c5 "Write Once, Run Everywhere Tests on Android"
-[2]: {{ site_url }}blog/2018/10/25/robolectric-4-0/ "Robolectric 4.0 release"
+[2]: {{ config.site_url }}blog/2018/10/25/robolectric-4-0/ "Robolectric 4.0 release"
 [3]: https://developer.android.com/training/testing/junit-runner "AndroidJUnit4 test runner"
 [4]: https://developer.android.com/training/testing/espresso/ "Espresso"
 [5]: https://developer.android.com/reference/androidx/test/core/app/ActivityScenario "ActivityScenario"
diff --git a/docs/contributing.md b/docs/contributing.md
index db9a86344..677369645 100644
--- a/docs/contributing.md
+++ b/docs/contributing.md
@@ -54,7 +54,7 @@ Robolectric uses javadoc to document API's behavior. There are special rules for
 * All visible non-`@Implementation` methods SHOULD have descriptive Javadoc.
 * Don't write javadoc comments like "Shadow for (whatever).". The javadoc will appear in a section clearly related to testing, so make it make sense in context.
 
-Robolectric will release javadoc at {{ site_url }} after every main version released. For example, Robolectric's {{ robolectric.version.current }} javadoc is released at {{ site_url }}javadoc/{{ robolectric.version.current }}/.
+Robolectric will release javadoc at {{ config.site_url }} after every main version released. For example, Robolectric's {{ robolectric.version.current }} javadoc is released at {{ config.site_url }}javadoc/{{ robolectric.version.current }}/.
 
 ### Deprecations and Backwards Compatibility
 
diff --git a/docs/index.md b/docs/index.md
index c834c0976..1ccd25df3 100644
--- a/docs/index.md
+++ b/docs/index.md
@@ -5,14 +5,14 @@ hide:
 ---
 
 <div align="center">
-  <img src="images/logotype.png" alt="{{ site_name }}" />
+  <img src="images/logotype.png" alt="{{ config.site_name }}" />
 
-  <h1>{{ site_description }}</h1>
+  <h1>{{ config.site_description }}</h1>
 </div>
 
 Running tests on an Android emulator or device is slow! Building, deploying, and launching the app often takes a minute or more. That's no way to do <abbr title="Test-Driven Development">TDD</abbr>. There must be a better way.
 
-[Robolectric]({{ site_url }}) is a framework that brings fast and reliable unit tests to Android. Tests run inside the JVM on your workstation in seconds. With Robolectric you can write tests like this:
+[Robolectric]({{ config.site_url }}) is a framework that brings fast and reliable unit tests to Android. Tests run inside the JVM on your workstation in seconds. With Robolectric you can write tests like this:
 
 ```java
 @RunWith(RobolectricTestRunner.class)
diff --git a/mkdocs.yml b/mkdocs.yml
index b603082eb..c02a37097 100644
--- a/mkdocs.yml
+++ b/mkdocs.yml
@@ -56,7 +56,9 @@ plugins:
       categories: false
       post_excerpt: required
       post_excerpt_max_authors: 5
-  - markdownextradata:
+  - macros:
+      on_error_fail: true
+      on_undefined: strict
   - redirects:
       redirect_maps:
         "activity-lifecycle.md": "androidx_test.md"
diff --git a/requirements.txt b/requirements.txt
index 702f5ee93..e78c59d4b 100644
--- a/requirements.txt
+++ b/requirements.txt
@@ -10,7 +10,7 @@ Markdown==3.6
 MarkupSafe==2.1.5
 mergedeep==1.3.4
 mkdocs==1.5.3
-mkdocs-markdownextradata-plugin==0.2.5
+mkdocs-macros-plugin==1.0.5
 mkdocs-material==9.5.17
 mkdocs-material-extensions==1.3.1
 mkdocs-redirects==1.2.1
@@ -26,5 +26,6 @@ pyyaml_env_tag==0.1
 regex==2023.12.25
 requests==2.31.0
 six==1.16.0
+termcolor==2.4.0
 urllib3==2.2.1
 watchdog==4.0.0