chore: update roadmap content json (#8135)

Co-authored-by: kamranahmedse <4921183+kamranahmedse@users.noreply.github.com>

public/roadmap-content/api-design.json

@@ -709,7 +709,7 @@
     "links": [
       {
         "title": "API Authorization Methods",
-        "url": "https://konghq.com/blog/engineering/common-api-authentication-methods",
+        "url": "https://www.pingidentity.com/en/resources/identity-fundamentals/authorization/authorization-methods.html",
         "type": "article"
       }
     ]

public/roadmap-content/data-analyst.json

@@ -670,7 +670,7 @@
     "links": [
       {
         "title": "Outliers",
-        "url": "%5Bhttps://www.mathsisfun.com/data/outliers.html",
+        "url": "https://www.mathsisfun.com/data/outliers.html",
         "type": "article"
       }
     ]

public/roadmap-content/system-design.json

@@ -1665,10 +1665,21 @@
       }
     ]
   },
-  "backends-for-frontend@n4It-lr7FFtSY83DcGydX.md": {
+  "n4It-lr7FFtSY83DcGydX": {
     "title": "Backends for Frontend",
-    "description": "",
-    "links": []
+    "description": "Create separate backend services to be consumed by specific frontend applications or interfaces. This pattern is useful when you want to avoid customizing a single backend for multiple interfaces. This pattern was first described by Sam Newman.\n\nTo learn more, visit the following links:",
+    "links": [
+      {
+        "title": "Backends for Frontends pattern",
+        "url": "https://learn.microsoft.com/en-us/azure/architecture/patterns/backends-for-frontends",
+        "type": "article"
+      },
+      {
+        "title": "Explore top posts about Frontend Development",
+        "url": "https://app.daily.dev/tags/frontend?ref=roadmapsh",
+        "type": "article"
+      }
+    ]
   },
   "4hi7LvjLcv8eR6m-uk8XQ": {
     "title": "Anti-Corruption Layer",