Multi-channel Developer Challenges

Developers have experienced different problems when working with content from multiple sources.

Although there are additional, nuanced points to consider, one of the first challenges that often arises is the need to transform content in some predictable way across all frontends.

Consistently transforming content

Consider a case where a headless CMS stores information about a site’s pages. Some of these pages may be designed to showcase lifestyle images of products, but the product information lives in a separate database.

Rather than needing to stitch the product to the page on any site where that page is used, it is often beneficial to have some mechanism that handles the stitching for all frontend code.

This is where content meshing solutions come into play. The next two sections touch on two different approaches to solving this problem — by building versus buying.