Sites
A Site in NewsTeam represents a customer-facing product — such as a website, mobile app, or newsletter. Sites are where audiences interact with your content, but they are decoupled from the editorial process.
This separation means teams can keep working in Buckets, Feeds, and Workflows without being disrupted whenever a site is launched, redesigned, or retired.
Why Sites Matter
Section titled “Why Sites Matter”- Provide a business-facing layer for managing how products are presented to audiences.
- Configure navigation, feeds, branding, metadata, app links, analytics, advertising, and custom runtime snippets.
- Enable rapid product changes without interfering with editorial workflows.
- Give public products a single source of truth for the configuration they need at runtime.
Managing Sites
Section titled “Managing Sites”Within an organization, you can create multiple Sites. Each Site can:
- Define its own navigation, homepage, and menu structure.
- Attach Feeds and decide which feeds are searchable or externally exposed.
- Configure logos, icons, thumbnails, social accounts, and light/dark accent colors.
- Manage title, description, keywords, locale, custom metadata, and verification tags.
- Add app-linking details for iOS and Android products.
- Enable production integrations such as Google Tag Manager, Chartbeat, Google Ad Manager, VAST, and ads.txt.
- Use NewsTeam’s widget framework to build flexible layouts and dynamic pages.
For example:
- A landing page that automatically pulls in articles from a specific feed.
- A unique “special project” page built by combining widgets, managed as easily as creating an article.
- A brand site that can switch logos, theme accents, app links, analytics IDs, ad network details, and custom HTML without a deploy.
This gives editors powerful tools to shape products dynamically, without waiting on developers for every change.
What Sites Configure
Section titled “What Sites Configure”The Site editor is split across the main product surfaces a public site needs:
- Navigation: menu groups, page links, external links, nested children, publish status, hidden items, thumbnails, and new-tab behavior.
- Feeds: the curated feed set a site can use, with feed policies for search and external exposure.
- Branding: light and dark logos, light and dark icons, site thumbnail, social accounts, and separate accent colors for light and dark modes.
- Metadata: site name, canonical URL, SEO title, description, keywords, locale, custom metadata, Google site verification, Facebook app ID, and Facebook domain verification.
- Apps: iOS URL scheme, App Store ID, Android URL scheme, and Android package name for app links and install prompts.
- Analytics and tags: Google Tag Manager ID and Chartbeat UID.
- Advertising: Google Ad Manager network code, ad unit name, site-wide advertising disable switch, VAST tag URL, and ads.txt content.
- Runtime snippets: custom HTML for the whole site and separate custom HTML that only runs on article pages.
- Widgets: widget editor settings that let teams control how structured page and article building behaves for the site.
This is not just descriptive metadata. The production starter frontend reads these fields and turns them into real runtime behavior.
Starter Frontend Support
Section titled “Starter Frontend Support”NewsTeam provides a production-ready starter frontend for public websites. It already consumes Site configuration for:
- Route resolution through the V1 read API, including article and page rendering.
- Theme and brand output, including light/dark icons, manifest data, app metadata, and accent colors.
- SEO and social metadata, including canonical URLs, Open Graph, Twitter cards, app links, verification tags, and custom metadata.
- Navigation and feeds, including menu-derived routes, feed-backed pages, RSS, Atom, sitemap, and site-aware metadata.
- Analytics, including Google Tag Manager page views, article events, and Chartbeat virtual page tracking.
- Advertising, including Google Publisher Tag loading, route-aware GAM ad unit paths, targeting, VAST-ready video ads, ads.txt, and site/entity-level advertising disable controls.
- Custom runtime HTML, with site-wide snippets and article-only snippets injected from Site settings.
That means teams can fork the starter, customize it, lift pieces out of it, or use it as the reference implementation for how Site configuration should power a real product.
Developer Role
Section titled “Developer Role”NewsTeam does not auto-generate websites or apps. Each Site still requires developers to build the front end with the frameworks and technologies they prefer. However:
- The application connects to its Site entity in NewsTeam.
- Editors then control what content is displayed, how sections are organized, and which product integrations are active dynamically.
This model is deliberate:
- Developers maintain ownership of the codebase, ensuring performance, scalability, and brand alignment.
- Editors gain the freedom to configure products and manage content without code changes.
The starter frontend makes that contract concrete: Site settings are not theoretical fields waiting for a future implementation. The available production settings are already wired into the starter pack that teams can use as their launch point.
Syndication and Reuse
Section titled “Syndication and Reuse”Because Sites are decoupled from content creation:
- The same article or asset can be published across multiple Sites within an organization.
- Content can be syndicated to different products (e.g. a flagship site, a niche vertical, and a newsletter) without duplication or retraining.
- Business teams can evolve presentation strategies freely, while editorial workflows remain stable.