diff --git a/content/guides/use-case/images/wiremock-accuweatherapi.webp b/content/guides/images/wiremock-accuweatherapi.webp
similarity index 100%
rename from content/guides/use-case/images/wiremock-accuweatherapi.webp
rename to content/guides/images/wiremock-accuweatherapi.webp
diff --git a/content/guides/use-case/images/wiremock-arch.webp b/content/guides/images/wiremock-arch.webp
similarity index 100%
rename from content/guides/use-case/images/wiremock-arch.webp
rename to content/guides/images/wiremock-arch.webp
diff --git a/content/guides/use-case/images/wiremock-logs-docker-desktop.webp b/content/guides/images/wiremock-logs-docker-desktop.webp
similarity index 100%
rename from content/guides/use-case/images/wiremock-logs-docker-desktop.webp
rename to content/guides/images/wiremock-logs-docker-desktop.webp
diff --git a/content/guides/use-case/images/wiremock-using-docker.webp b/content/guides/images/wiremock-using-docker.webp
similarity index 100%
rename from content/guides/use-case/images/wiremock-using-docker.webp
rename to content/guides/images/wiremock-using-docker.webp
diff --git a/content/guides/use-case/pre-seeding.md b/content/guides/pre-seeding.md
similarity index 98%
rename from content/guides/use-case/pre-seeding.md
rename to content/guides/pre-seeding.md
index ecad45f02a..a707540f36 100644
--- a/content/guides/use-case/pre-seeding.md
+++ b/content/guides/pre-seeding.md
@@ -1,8 +1,13 @@
 ---
-description: Pre-seeding database with schema and data at startup for development environment
-keywords: Pre-seeding, database, postgres, container-supported development
 title: Pre-seeding database with schema and data at startup for development environment
 linktitle: Pre-seeding database  
+description: &desc Pre-seeding database with schema and data at startup for development environment
+keywords: Pre-seeding, database, postgres, container-supported development
+summary: *desc
+levels: [intermediate]
+subjects: [databases]
+params:
+  time: 20 minutes
 ---
 
 Pre-seeding databases with essential data and schema during local development is a common practice to enhance the development and testing workflow. By simulating real-world scenarios, this practice helps catch frontend issues early, ensures alignment between Database Administrators and Software Engineers, and facilitates smoother collaboration. Pre-seeding offers benefits like confident deployments, consistency across environments, and early issue detection, ultimately improving the overall development process.
diff --git a/content/guides/use-case/wiremock.md b/content/guides/wiremock.md
similarity index 98%
rename from content/guides/use-case/wiremock.md
rename to content/guides/wiremock.md
index 78e61f9d92..f0d198e0aa 100644
--- a/content/guides/use-case/wiremock.md
+++ b/content/guides/wiremock.md
@@ -1,8 +1,13 @@
 ---
-description: Mocking API services in development and testing with WireMock
-keywords: WireMock, container-supported development
 title: Mocking API services in development and testing with WireMock
+description: &desc Mocking API services in development and testing with WireMock
+keywords: WireMock, container-supported development
 linktitle: Mocking API services with WireMock
+summary: *desc
+levels: [intermediate]
+subjects: [distributed-systems]
+params:
+  time: 20 minutes
 ---
 
 During local development and testing, it's quite common to encounter situations where your app is dependent on the remote APIs. Network issues, rate limits, or even downtime of the API provider can halt your progress. This can significantly hinder your productivity and make testing more challenging. This is where WireMock comes into play.