Feature surface

Sites & Public Products

Sites are where NewsTeam becomes a real audience product. They combine brand, routing, feeds, metadata, analytics, advertising, app links, and starter frontend support into one public-product configuration model.

Site Brand, routing, metadata
Config
Feeds Curated content supply
Content
Starter Production implementation
Runtime

Sites are the public product layer

A Site holds the audience-facing configuration for a website, app, newsletter, or brand while editorial work continues in buckets, feeds, and workflows.

Learn more

Editors can manage real launch settings

Logos, icons, light and dark accents, SEO metadata, social metadata, verification tags, app links, navigation, feeds, and homepage behavior all live in Site settings.

Learn more

Commercial and measurement tools are configured there too

Google Tag Manager, Chartbeat, Google Ad Manager, VAST tags, ads.txt, custom metadata, and custom HTML are Site-managed fields rather than one-off frontend edits.

Learn more

The starter frontend already consumes the configuration

The production starter uses Site data for routing, metadata, theming, analytics, ads, app links, feeds, RSS, Atom, sitemap, and runtime snippets.

Learn more

Public products read through V1 apps

Apps give websites and other consumers a read-safe identity, optional Site context, and stable API credentials without exposing newsroom write workflows.

Learn more

Product changes do not have to become content migrations

Because Sites sit downstream of content creation, teams can adjust brands, routes, feeds, and commercial setup without remodelling the editorial archive.

Learn more