Currently we do not have any end point from where we can get all details of the article data . A few brands use the search api endpoints to fetch article data for a brand-locale but that only gives limited data ( title , body text , url ) . Currently we have systems like AIBA which use article data to train their models to generate dynamic recommendations . To do so we need some end point from article which when hit , directly provides all data in the body content of the article
Use-case:
A structured data feed with a periodic synchronization enables AiBA recommendation engine and AiBA LLM engine capability to have latest content and avoid any incorrect recommendations and also avoid a manual process for feeding the latest updates in article content. Other initiatives currently being discussed for LLM and AI engine revamp may also benefit from this implementation.
Current/Experienced Behavior:
Currently there is no provision in the product for exposure of content feed outside AEM. The engineering team should review and implement this based on the priority for future releases.
Improved/Expected Behavior:
We need some end point from article which when hit , directly provides all data in the body content of the article
Environment Details (AEM version/service pack, any other specifics if applicable):
This has been reported to the engineering under the internal reference SITES-24118. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to the Jira status.
