Publishing Ecosystem

Overview of different application related to T Brand Studio

The Paid Post publishing workflow is a cross-functional process that involves multiple areas of our publishing systems. This is a list of the main repositories hosting code that is related to it.

Repositories

Core Web Monorepo

⁠

Vi⁠

is the React based frontend application powering nytimes.com. The

Paid Post route⁠

renders our paid posts and includes components to render the page metadata, the branded content top bar and footer, etc.

This is where, for example, the branded content tooltip and disclaimer get rendered. Ad Experience say the wording has been approved by Legal so any change should be carefully considered.

CMS UI Paid Posts

The application powering the Scoop

CMS UI for the Paid Posts⁠

. A lot going on here, especially because it regards many functions.

Ad Experience made this example: adding a CMS field to customise the paid post disclaimer would require a cross functional effort between team because it touches Scoop, Database, Samizdat, Vi, Legal for approval...