Outstanding Questions

Every real open question from across this documentation, in one place, grouped by feature, so the team can work through them together instead of hunting one page at a time. Each question previously lived at the bottom of its own page; that page now links back here instead.

Data Sources & Queries

Source: Data Sources & Queries

• Do two editors see each other’s saved Data Sources update in real time (matching the CRDT collaboration confirmed elsewhere in Publishing), or only after a refresh? Not yet tested directly.

Sitemap, Structured Data & Redirects

Source: Sitemap, Structured Data & Redirects

• Where/how does a redirect actually get created today? Confirmed there’s no redirects endpoint anywhere in @pantheon-systems/css-client, read or write, and the one read method we found (getRedirect()) lives in a different package (p1-next-sdk) entirely. Whatever creates a redirect isn’t visible from either SDK; worth asking Pantheon directly rather than searching further.
• Does parenting: true on a RedirectInfo behave the way it sounds (an old section redirecting wholesale to a new one, preserving the trailing path segment), or something narrower? Worth confirming with Pantheon before relying on it for a section-level URL migration.

Analytics & Tracking

Source: Analytics & Tracking

• Does every Brown-Forman brand run its own GTM container (own container ID, own tag configuration), or is there a shared container/workspace across brands the way Salesforce orgs are segmented per brand? Not yet confirmed.
• Is Consent Mode actually configured correctly inside herradura.com’s GTM container today, or does the container merely have the capability wired up (dataLayer events present) without every individual tag actually respecting it? Not verifiable from outside the container’s own admin UI; worth asking Brown-Forman’s marketing/analytics team directly rather than assuming from the dataLayer evidence alone.
• Beyond GTM/GA4, does Brown-Forman run any other tracking (Meta Pixel, TikTok Pixel, an ad-platform conversion tag) that should go through the same @brown-forman/p1-analytics wrapper rather than being added ad hoc per brand site?

Media: Bulk Management & a Library View

Source: Media: Bulk Management & a Library View

• Would Pantheon export MediaLibrary (and whatever config/context it depends on) directly, given it’s already fully built? This is the single highest-leverage question on this list: it could turn a draft into a two-line integration. Worth asking before investing further in the draft’s browse-only approach or extending it toward edit/delete/upload.
• Is GET /media rate-limited or otherwise not intended for calls outside the picker’s own controlled usage pattern? Pantheon’s dev guide confirms no rate limiting on the delivery/transform endpoint specifically; that’s a different endpoint from the listing call the draft plugin uses, and we haven’t found an equivalent statement for /media itself. Worth confirming that’s an acceptable integration path before relying on it.
• Is a browse-only library view (see everything, flag what’s missing alt text) sufficient on its own, or does the real pain point specifically require inline bulk-editing? Worth confirming with whoever’s hitting this gap day to day before deciding whether the draft needs edit/delete/upload added.

API Keys & Secrets

Source: API Keys & Secrets

• Does dashboard.pantheon.io (the Pantheon hosting dashboard, not content.pantheon.io) have a UI for setting environment variables, or is Terminus the only documented path today? Checked Pantheon’s public docs for a dashboard walkthrough and didn’t find one; the CLI command is confirmed, a visual equivalent is not.
• For a Brown-Forman multi-brand rollout, does each brand’s Next.js site get its own independently-managed set of secrets (separate Terminus/dashboard access per brand), or is there ever a shared secrets-management layer across brands? Given Salesforce orgs and OneTrust projects are already confirmed segmented per brand (see Web Forms & Salesforce and Cookie Consent), per-brand secrets is the likely pattern; worth confirming explicitly rather than assuming.

Content Relationships

Source: Content Relationships

• Would Pantheon consider building a native document-picker field, the same question worth raising alongside the Bulk Management & a Library View feature request, since both are “this benefits every P1 site” asks worth raising together?

Deployment & Environments

Source: Deployment & Environments

• What does a realistic environment-promotion workflow look like specifically for a Brown-Forman multi-brand rollout: does each brand site get its own repository (and therefore its own independent Test/Live tag sequence), or is there ever a shared deployment pipeline across brands? Not yet decided.

Site Search

Source: Site Search

• Does any Brown-Forman brand site actually need search today, or is this speculative ahead of real demand? Worth confirming against an actual site’s page count/catalog size before committing effort.
• If a hosted service is chosen, who owns the ongoing cost and account (Prolific Digital, or handed to Brown-Forman)? Same shape as the vendor-ownership question below for Email Delivery.

Email Delivery

Source: Email Delivery

• Who owns the Postmark (or chosen vendor) account and API credentials per site: is this provisioned per brand/client, or shared across a Prolific Digital account with per-site sending domains?
• What volume is realistic per site? Confirms whether Postmark’s free/starter tier is sufficient or a paid plan needs budgeting into the engagement.
• Does the client need branded email templates (logo, brand colors) for these notifications, or is a plain internal-facing notification sufficient for v1?

Localization

Source: Localization

• Does every brand/site need multi-locale support, or is this specific to sites with real international reach (like Jack Daniel’s)? Herradura’s tour page shows a real need for country-aware behavior (age gate), but that’s a narrower requirement than full page-by-page translation; confirm whether Herradura itself needs the latter before building for it.
• Who produces translated content: a translation vendor, an internal team, or machine translation with human review? Determines whether the P1 editor workflow needs to support side-by-side locale editing, or whether locales are built as fully independent content trees with no expectation of staying in sync page-for-page.
• Is there an existing Brown-Forman convention for locale URL structure (/de-de/ vs /de/ vs a ccTLD-per-market approach) we should match, or is jackdaniels.com’s /xx-xx/ pattern the de facto standard worth adopting directly?

Retail Locator

Source: Retail Locator

• What actually populates the retailer dataset for Herradura’s locator today? A CMS/admin list, a distributor feed, a manual CSV: this is the real unknown, and it determines most of the actual build effort. Worth asking directly rather than reverse-engineering further.
• Is the “shop assistant” a shared WordPress plugin across other Brown-Forman brands (like the forms/tour-booking plugins appear to be), or Herradura-specific? If shared, there may already be a spec or even an internal API we should ask for instead of rebuilding from scratch.
• Given Jack Daniel’s already pays for and runs Dotter successfully, is a custom Maps-based build for Herradura a deliberate choice (cost, data ownership) or just how it happened to get built historically? Worth surfacing before committing engineering time to replicate it rather than adopting Dotter for consistency.

Book a Tour (Visit Us)

Source: Book a Tour (Visit Us)

• Is Xola a Herradura-specific vendor choice (distillery tours are a Herradura thing, not every brand’s), or does Brown-Forman have other brands running distillery/visit experiences through Xola too? Determines whether this is worth a shared package at all, versus a one-off Herradura build.
• Who owns the Xola account/button provisioning for new experiences: marketing, ops, or us? Affects how new tour types get added later.

Form Builder: Submission Storage

Source: Form Builder → Submission Storage

• Does Pantheon’s P1 platform offer any provisionable database service, or does storage need to be built and hosted entirely outside P1? Checked Pantheon’s public docs for a Next.js-specific storage/database offering and only found MariaDB/MySQL guides scoped to traditional WordPress/Drupal hosting, not confirmation either way for a P1 site. Confirm before scoping implementation effort.
• Who needs access to stored submissions when the CRM/email both fail: is a simple internal admin view sufficient, or does this need to feed into an existing ops/support tool?
• Retention policy for stored submissions (especially anything containing PII: emails, names): how long is a client required or willing to retain raw submission data once it’s confirmed delivered downstream?

Age Gate

Source: Age Gate

• The disclaimer text on both reference sites says “I understand that my personal information will be processed in accordance with the privacy policy” despite the DOB never leaving the browser in a network request we could observe. That phrasing may exist because a birthdate is legally “personal information” under GDPR/CCPA the moment it’s captured and stored in a cookie, even client-side-only. Worth confirming the exact required disclosure language with Brown-Forman’s legal team rather than inventing our own; the package should accept this copy as config, not hardcode it.

Cookie Consent

Source: Cookie Consent (OneTrust)

• Who provisions the OneTrust domain/project for a new brand site: is that something Brown-Forman’s compliance team sets up centrally per brand, or something we request access to configure? Affects whether domainScriptId is handed to us or something we help generate.