As a developer I need to bridge the gap between the API response data and the PatternFly MCP data.
Acceptance criteria
-
Integrate data into the existing embedded docs aggregator
-
Confirm metadata title, descriptions, keywords of API entries
-
Working blend of embedded data and up-to-date API data
Assumptions and questions
-
Review api responses and component-schema blends and how it integrates into the embedded data
-
Component schema blending into the older/current aggregation could be a follow up if it becomes unexpectedly "more effort".
- We have follow up work that restructures the data into records and collections that may make this part easier
Jira Issue: PF-4402
As a developer I need to bridge the gap between the API response data and the PatternFly MCP data.
Acceptance criteria
Integrate data into the existing embedded docs aggregator
Confirm metadata title, descriptions, keywords of API entries
Working blend of embedded data and up-to-date API data
Assumptions and questions
Review api responses and component-schema blends and how it integrates into the embedded data
Component schema blending into the older/current aggregation could be a follow up if it becomes unexpectedly "more effort".
Jira Issue: PF-4402