Update readme docs excerpt format

Author: diegotid

v0/about/architecture.md

@@ -1,7 +1,17 @@
 ---
 title: API Architecture
-excerpt: The Open Gateway API Architecture is a cutting-edge framework designed to enable seamless integration of advanced network capabilities and services into your applications. Developed by the GSMA in collaboration with leading telecommunications operators, aggregators, cloud providers, and other telcos, this architecture focuses on promoting interoperability, enhancing innovation, and improving operational efficiency. By leveraging standardized APIs, the Open Gateway architecture empowers developers to create robust, scalable, and high-performance applications.
-category: 680a72d37e76400018040958
+category:
+  uri: About Open Gateway
+content:
+  excerpt: >-
+    The Open Gateway API Architecture is a cutting-edge framework designed to
+    enable seamless integration of advanced network capabilities and services
+    into your applications. Developed by the GSMA in collaboration with leading
+    telecommunications operators, aggregators, cloud providers, and other
+    telcos, this architecture focuses on promoting interoperability, enhancing
+    innovation, and improving operational efficiency. By leveraging standardized
+    APIs, the Open Gateway architecture empowers developers to create robust,
+    scalable, and high-performance applications.
 ---
 
 ## Introduction to Open Gateway API Architecture

v0/about/camara.md

@@ -1,7 +1,17 @@
 ---
 title: CAMARA project
-excerpt: CAMARA is an open-source initiative under the Linux Foundation focused on defining, developing, and testing telecom APIs. In collaboration with the GSMA Operator Platform Group, CAMARA ensures that API requirements are aligned, and API definitions are published for industry-wide use. The project achieves API harmonization by rapidly creating working code and providing developer-friendly documentation. All API definitions and reference implementations are available for free under the Apache 2.0 license.
-category: 680a72d37e76400018040958
+category:
+  uri: About Open Gateway
+content:
+  excerpt: >-
+    CAMARA is an open-source initiative under the Linux Foundation focused on
+    defining, developing, and testing telecom APIs. In collaboration with the
+    GSMA Operator Platform Group, CAMARA ensures that API requirements are
+    aligned, and API definitions are published for industry-wide use. The
+    project achieves API harmonization by rapidly creating working code and
+    providing developer-friendly documentation. All API definitions and
+    reference implementations are available for free under the Apache 2.0
+    license.
 ---
 
 With CAMARA Open APIs, enterprise software developers can integrate network capabilities once, and they’re ready to go. Imagine these APIs embedded in cloud provider stacks. Developers could then seamlessly incorporate lines of code from both the cloud provider and global telecommunication standards, covering services like identity, cybersecurity, billing, signaling, geolocation, and more.

v0/about/glossary.md

@@ -1,7 +1,11 @@
 ---
 title: Glossary of Terms
-excerpt: Reference guide to key terms and concepts used in the Open Gateway API documentation
-category: 680a72d37e76400018040958
+category:
+  uri: About Open Gateway
+content:
+  excerpt: >-
+    Reference guide to key terms and concepts used in the Open Gateway API
+    documentation
 ---
 
 ## Aggregator

v0/about/initiative.md

@@ -1,7 +1,13 @@
 ---
 title: The Open Gateway Initiative
-excerpt: Welcome to Open Gateway APIs, your gateway to leveraging advanced network capabilities in your applications. Whether you're a seasoned developer or just starting your journey, Open Gateway APIs provide the tools and resources you need to create innovative, high-performance applications.
-category: 680a72d37e76400018040958
+category:
+  uri: About Open Gateway
+content:
+  excerpt: >-
+    Welcome to Open Gateway APIs, your gateway to leveraging advanced network
+    capabilities in your applications. Whether you're a seasoned developer or
+    just starting your journey, Open Gateway APIs provide the tools and
+    resources you need to create innovative, high-performance applications.
 ---
 
 ## What is Open Gateway?

v0/about/privacy.md

@@ -1,7 +1,12 @@
 ---
 title: Privacy by Design
-excerpt: Open Gateway as an industry initiative has been designed with end-user's privacy in mind, to provide developers with telco capabilities while ensuring user data privacy and security.
-category: 680a72d37e76400018040958
+category:
+  uri: About Open Gateway
+content:
+  excerpt: >-
+    Open Gateway as an industry initiative has been designed with end-user's
+    privacy in mind, to provide developers with telco capabilities while
+    ensuring user data privacy and security.
 ---
 
 Open Gateway APIs allow applications to access and utilize end-users' personal information or data. "Utilizing" personal data encompasses any form of handling or processing related to an identified or identifiable individual, including merely viewing the data or having it accesible from the application's code and thus to its developer. Consequently, **the use of personal data must be justified and authorized**.

v0/callflows/apiintegration.md

@@ -1,7 +1,12 @@
 ---
 title: API Integration
-excerpt: In this guide we will go through the different ways to integrate with Open Gateway APIs so you can find the best fit for your use case and the offering from our Channel Partners.
-category: 680a72d37e7640001804095c
+category:
+  uri: API Call Flows
+content:
+  excerpt: >-
+    In this guide we will go through the different ways to integrate with Open
+    Gateway APIs so you can find the best fit for your use case and the offering
+    from our Channel Partners.
 ---
 
 ## RESTful by design 

v0/callflows/authorization/authorization.md

@@ -1,7 +1,11 @@
 ---
 title: Authorization
-excerpt: In this guide you will find a briefly introduction to authorization mechanisms and best practices for secure access to Open Gateway APIs
-category: 680a72d37e7640001804095c
+category:
+  uri: API Call Flows
+content:
+  excerpt: >-
+    In this guide you will find a briefly introduction to authorization
+    mechanisms and best practices for secure access to Open Gateway APIs
 ---
 
 ## Authorization standards
@@ -40,4 +44,4 @@ In case the lawful basis of the Open Gateway API and the purpose of your use cas
 
 The frontend authorization flow, as per the OIDC standard, will redirect your request to the operator's consent capture URL if needed, and then resume all the way to your application's redirect URI according to the user event.
 
-In case of implementing a backend authorization flow, there is no standard way to make the operator subscriber to get to a consent capture frontend, so you will have to implement a secondary flow, known as out-of-band, to capture the consent by other mean, so when your backend calls the Open Gateway API the user consent has been already granted. This secondary flow will usually be a registration, subscription or activation process on your customer journey, or similar.
+In case of implementing a backend authorization flow, there is no standard way to make the operator subscriber to get to a consent capture frontend, so you will have to implement a secondary flow, known as out-of-band, to capture the consent by other mean, so when your backend calls the Open Gateway API the user consent has been already granted. This secondary flow will usually be a registration, subscription or activation process on your customer journey, or similar.

v0/callflows/authorization/backend.md

@@ -1,7 +1,13 @@
 ---
 title: Backend authorization flow
-excerpt: If your use case does not involve end-user's interaction you will want to integrate with Open Gateway APIs from the backend. This guide will help you understand the flows to get your application authorized to call the APIs from your server or any other environment without a human interface.
-category: 680a72d37e7640001804095c
+category:
+  uri: API Call Flows
+content:
+  excerpt: >-
+    If your use case does not involve end-user's interaction you will want to
+    integrate with Open Gateway APIs from the backend. This guide will help you
+    understand the flows to get your application authorized to call the APIs
+    from your server or any other environment without a human interface.
 ---
 
 From a developer perspective, the backend authorization flow consists of two sequential steps implemented by performing HTTP requests to the following Open Gateway Channel Partner's API gateway endpoints, compliant with the ODIC standard **CIBA** (Client-Initiated Backchannel Authentication Flow).
@@ -83,4 +89,4 @@ In this portal, you can find the following references:
 
 External references:
 - [CAMARA APIs Access and User Consent Management](https://github.com/camaraproject/IdentityAndConsentManagement/blob/r0.2.0/documentation/CAMARA-API-access-and-user-consent.md)
-- [OIDC Client-Initiated Backchannel Authentication Flow](https://openid.net/specs/openid-client-initiated-backchannel-authentication-core-1_0.html)
+- [OIDC Client-Initiated Backchannel Authentication Flow](https://openid.net/specs/openid-client-initiated-backchannel-authentication-core-1_0.html)

v0/callflows/authorization/frontend.md

@@ -1,7 +1,14 @@
 ---
 title: Frontend authorization flow
-excerpt: If your application offers a human interface to provide your users with features enabled by Open Gateway, this is its frontend component, running on the end-user's device, that will trigger the API calling flow. This guide will show you how to authorize your application by identifying the end-user from their network connected devices.
-category: 680a72d37e7640001804095c
+category:
+  uri: API Call Flows
+content:
+  excerpt: >-
+    If your application offers a human interface to provide your users with
+    features enabled by Open Gateway, this is its frontend component, running on
+    the end-user's device, that will trigger the API calling flow. This guide
+    will show you how to authorize your application by identifying the end-user
+    from their network connected devices.
 ---
 
 From a developer perspective, the frontend authorization flow consists of two sequential steps implemented by performing HTTP requests to the following Open Gateway Channel Partner's API gateway endpoints, compliant with the OIDC standard **Authorization Code Flow**.
@@ -100,4 +107,4 @@ In this portal, you can find the following references:
 
 External references:
 - [CAMARA APIs Access and User Consent Management](https://github.com/camaraproject/IdentityAndConsentManagement/blob/r0.2.0/documentation/CAMARA-API-access-and-user-consent.md)
-- [OIDC Authorization Code flow specification](https://openid.net/specs/openid-connect-core-1_0.html#CodeFlowAuth)
+- [OIDC Authorization Code flow specification](https://openid.net/specs/openid-connect-core-1_0.html#CodeFlowAuth)

v0/catalog/ageverification/ageverification.md

@@ -1,7 +1,13 @@
 ---
 title: Age Verification API
-excerpt: The Age Verification API enables businesses to verify if users meet required age thresholds for age-restricted services using verified data from mobile network operators, ensuring compliance with regulations while protecting privacy.
-category: 681879c3afc1a0003709c745
+category:
+  uri: API Catalog
+content:
+  excerpt: >-
+    The Age Verification API enables businesses to verify if users meet required
+    age thresholds for age-restricted services using verified data from mobile
+    network operators, ensuring compliance with regulations while protecting
+    privacy.
 ---
 
 The standardized Age Verification API allows businesses to determine if users meet required age thresholds for accessing age-restricted subscriptions and services using verified data from mobile network operators.