BTB2C.tel

Enterprise website network public surface

The public website now shows the platform, not a placeholder.

This front-end exposes the same feature families the project is built around: Payload and Puck content, Shopify read-only commerce, SEO relationship intelligence, migration proof, autoblogging, theme templates, monetization gates, and governed external agent access.

Test live public featuresRefresh websiteNetwork control plane

Live public feature console

The website now exercises real visitor-facing platform paths.

These panels call the same public APIs a tenant site uses for content discovery, Shopify-safe product policy, search, and consent capture. If providers are missing, the page shows degraded truth instead of pretending the feature does not exist.

Payload content

empty

content API

Pages, posts, services, Payload layouts, and Puck blocks hydrate from the tenant source of truth.

Editorial queue

empty

draft-ready

Published articles, autoblogging drafts, canonical strategy, and relationship suggestions stay approval-led.

Shopify policy

empty

read-only

Product visibility uses the same Shopify snapshot and Payload enrichment policy used by admin previews.

Newsletter intake

empty

gated

Public leads write to Payload with consent text and audit metadata when the database is configured.

Public search

Search Payload content in-page

pending

Run a search to test the public content index.

Shopify storefront policy

Products stay tenant-branded

pending

Loading product policy context.

Newsletter and lead capture

Consent-aware intake

pending

Requires Payload storage. Missing configuration appears here, not as a silent failure.

{domain}

Public tenant site

Visitor-facing content, products, search, newsletter, schema, related-site widgets, and policy-safe monetization.

admin.{domain}

Site admin

Tenant-scoped content, commerce visibility, customers, services, SEO, graph, autoblogging, theme, and AI controls.

superadmin.{domain}

Superadmin

Network tenants, migrations, Shopify source, SEO intelligence, relationship moderation, monetization, security, cost, and deployment governance.

Feature family map

Every major requested feature has a public-facing story.

Some controls belong in admin or superadmin, but the public website must still show how those controls affect visitors: content, products, search, links, trust, policy gates, and conversion paths.

Tenant and domain governance

routed

Public, admin, www, superadmin, and legacy aliases route through the same branch-aware Vercel platform.

Payload and Puck editing

editable

Home pages, posts, services, products, and imported blocks share one editable layout contract.

Migration transformation

audited

Dry-runs, source snapshots, URL parity, canonical checks, media QA, redirects, and cutover evidence stay visible.

Shopify read-only commerce

read-only

Customer journeys use Storefront-safe product data with Payload enrichment and tenant visibility rules.

SEO and AEO intelligence

evidence-led

Metadata, schema, sitemap, GSC, GA, trends, internal links, and measured versus inferred signals stay separated.

Relationship graph

governed

Cross-site recommendations carry source, target, risk, impact direction, approval status, and audit history.

Autoblogging operations

approval-first

Strategy, source basis, draft generation, scheduler intent, duplicate risk, canonical policy, and review queues are draft-first.

Analytics and observability

truthful

Every surface distinguishes true-empty from degraded, missing config, provider error, quota, and stale cache.

Cost and feature gates

cost-safe

Payload, Vercel, Shopify, Google, AdSense, and AI capabilities are enabled only when plan and credentials allow.

AdSense and affiliate policy

gated

Ads and referral links fail closed until eligibility, disclosure, blocked categories, and placement rules are approved.

External AI governance

scoped

MCP/API clients stay deny-by-default, tenant-scoped, rate-limited, auditable, and draft-safe.

Production verification

verified

Completion requires build checks, browser workflows, responsive evidence, secret posture, runtime proof, and deployment truth.

Relationship graph preview

Impact, risk, and evidence are visible to humans.

Tenant
Post
Product
Keyword
Backlink
measured signalsinferred influencemoderation queue

Visitor journeys

The front-end now exposes the actual product model.

1Visitor readsPayload/Puck page modules, article lists, service cards, FAQ, contact paths, and related content render from tenant layout data.
2Visitor discoversSearch, topic links, relationship widgets, category paths, and SEO graph recommendations are visible without sending users to raw APIs.
3Visitor shopsProduct grids, product detail, cart, and checkout handoff stay on branded tenant routes until explicit Shopify checkout.
4Visitor convertsNewsletter, contact, and service inquiries write to Payload with consent and audit state when provider configuration is healthy.

Theme engine and templates

Global theme first, per-page variants when needed.

Admins can choose layout packs, colour packs, font and density styles, navigation behavior, product recipes, motion, focus rings, and document-specific templates without bypassing Payload or Puck.

Enterprise editorial

  • • sticky topbar
  • • wide content
  • • balanced rhythm
  • • strong focus ring

Premium commerce

  • • hybrid navigation
  • • product cards
  • • square images
  • • warm conversion tone

Editorial magazine

  • • light publication
  • • spacious sections
  • • article sidebar
  • • wide media

High contrast utility

  • • compact density
  • • outline cards
  • • reduced motion
  • • accessible defaults

Migration and autoblogging pipeline

Transformation is visible, not hidden.

  1. 1Discover source URLs and product context
  2. 2Transform into Payload documents and Puck blocks
  3. 3Apply tenant theme and URL policy
  4. 4Hydrate Shopify-safe product visibility
  5. 5Run SEO, canonical, backlink, and migration QA
  6. 6Publish only after provider, browser, and audit proof

AdSense readiness

No ad slot renders until eligibility, blocked categories, placement policy, CLS safety, and audit rationale are approved.

Affiliate governance

Referral links require disclosure, review flags, policy-safe placement, and optional AdSense exclusion when needed.

AI agent boundary

External clients can read, diagnose, and draft only through scoped policy tiers. Direct publish and secret access remain blocked.

Chatbot future scope

Conversational chatbot surfaces stay deferred until the project explicitly promotes them into a future SDD.