Docs as Code section - Content APIs

[lief-erickson]

3. All content can be single-sourced, meaning tech writers and engineers maintain one canonical source of truth, no matter how many places that content needs to appear in the generated docs.

This touches on, albeit without saying as much, as Docs as a Service or Content APIs. Content can be subscribed to and pull in based on requests. Consider pulling content into a mobile app, for instance. Too early to reference this sort of pipeline?

[briandominick]

Yeah this is great stuff. I don't know enough about it, and I knew even less when I was brushing up against it here.

[briandominick]

Lief I'm definitely interested in resources on this, or, frankly, a direct contribution.

[lief-erickson]

A Google search for "content api" turns up several resources. I have not used any of these, but am familiar that such things exist.

Contentful Seabourne Programmableweb seems to point to a lot of different tools making use of content APIs

[briandominick]

Ah okay, cool. I'll race you to it, then!