Outbound feeds are heavily tied to PageBuilder. Clients that do not use pagebuilder (headless clients) are unable to utilize this powerful and important feature with their website.
Making outbound feeds accessible for headless clients would potentially free up so much time and so many resources.
Guest
Hi Mike, that sounds great!
I know there are a few people within our department who have additional expertise on where this new feature could be utilized. When you have something you'd like to connect on, I can extend the invite to them as well.
For context, at the time I wrote the idea we were trying to onboard a vendor that could accept data from your traditional outbound feeds, but since we were headless, we had to go though the process of building out extra queries within our API as well as a separate feed to call to those endpoints and generate XML data. In addition to that vendor, we also use it to feed places like Apple News.
I'm really excited to see what you and your team come up with, it would be nice to simplify the process on our end a bit.
We are investigating options to provide both sitemaps and feeds (like RSS and others) similar to pagebuilder OBF.
If it's ok, I would like to follow up with you on the planned solution to see if it meets your needs. Our main concerns are around the fact that, as a headless customer, you are responsible for your primary domain and page delivery process (CDN, etc...). Due to this, it's hard for us to "serve" that information when we aren't managing any of those components. The headless solution would likely be something similar to a set of new View API endpoints that you can call from your own code to get properly formatted data, and then format and serve based on your site architecture.
For example, most sitemaps for news sites have a parent sitemap.xml file that references multiple "child" sitemap files per day/week/month. We could create endpoints for the child pages with the links to the stories that is updated as new content is published or updated, but you would create and host the parent page that references them.