feat: move OFREP OpenAPI docs to Other Technologies section

Signed-off-by: Jonathan Norris <[email protected]>

Author: jonathannorris

docs/reference/other-technologies/ofrep/_category_.json

@@ -0,0 +1,10 @@
+{
+    "label": "OFREP",
+    "position": 2,
+    "collapsible": true,
+    "collapsed": false,
+    "link": {
+        "type": "doc",
+        "id": "reference/other-technologies/ofrep/index"
+    }
+}

docs/reference/other-technologies/ofrep.mdx renamed to docs/reference/other-technologies/ofrep/index.mdx

@@ -1,16 +1,14 @@
 ---
 title: OpenFeature Remote Evaluation Protocol (OFREP)
-sidebar_label: OFREP
-sidebar_position: 2
-id: ofrep
+sidebar_position: 1
 ---
 
-The **OpenFeature Remote Evaluation Protocol (OFREP)** is an API specification for feature flagging that enables vendor-agnostic communication between applications and flag management systems. It defines a standard API layer between the provider and the flag management system, allowing any OpenSource or commercial system to implement the protocol and be compatible with community-maintained providers.
+The **OpenFeature Remote Evaluation Protocol (OFREP)** is an [API specification](./openapi) for feature flagging that enables vendor-agnostic communication between applications and flag management systems. It defines a standard API layer between the provider and the flag management system, allowing any OpenSource or commercial system to implement the protocol and be compatible with community-maintained providers.
 
 ### Key Benefits
 
 - **Vendor Agnostic**: Connect to any OFREP-compliant flag management system without vendor-specific implementations
-- **Standardized**: Built on a common OpenAPI specification for consistent integration
+- **Standardized**: Built on a [common OpenAPI specification](./openapi) for consistent integration
 - **Flexible**: Works on both client-side and server-side applications
 - **Community Maintained**: Generic OFREP providers maintained by the OpenFeature project
 
@@ -29,7 +27,7 @@ graph LR
 1. Your application uses the OpenFeature SDK
 2. The OpenFeature SDK uses an OFREP provider
 3. The OFREP provider communicates with your flag management system via the standardized OFREP API
-4. Your flag management system implements the OFREP specification
+4. Your flag management system implements the [OFREP specification](./openapi)
 
 ### Server vs Client
 
@@ -71,7 +69,7 @@ To create an OFREP provider for a new language:
 
 To make your flag management system OFREP-compliant:
 
-1. Implement the [OFREP OpenAPI specification](https://github.com/open-feature/protocol/blob/docs-update-readme-for-website/service/openapi.yaml)
+1. Implement the [OFREP OpenAPI specification](./openapi)
 2. Test your implementation with existing OFREP providers
 3. Register your system in the [OpenFeature ecosystem](https://github.com/open-feature/openfeature.dev/issues)
 

docs/reference/other-technologies/ofrep/openapi.mdx

@@ -0,0 +1,12 @@
+---
+title: "OpenAPI Spec"
+sidebar_position: 2
+hide_title: true
+---
+
+import Redoc from '@theme/Redoc';
+
+<div className="redoc-container">
+  <Redoc />
+</div>
+

external-content/specification

@@ -297,4 +297,9 @@ article:has(.redoc-container) {
 .redocusaurus a[href*="redocly.com"],
 .redocusaurus [class*="powered-by"] {
   display: none !important;
+}
+
+/* Hide menu border on API viewer pages */
+.redoc-container .menu-content {
+  border-right: none !important;
 }