Skip to content

docs(platform): IA content-sharing decision — self-canonical + inline transclusion (#7233)#7301

Open
jstirnaman wants to merge 8 commits into
masterfrom
feat-platform-faq-expansion-7202
Open

docs(platform): IA content-sharing decision — self-canonical + inline transclusion (#7233)#7301
jstirnaman wants to merge 8 commits into
masterfrom
feat-platform-faq-expansion-7202

Conversation

@jstirnaman

@jstirnaman jstirnaman commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

Summary

Records the IA content-sharing decision for the job-led docs IA: how engine and
reference content is shared across InfluxDB 3 Core, Enterprise, and the
deployment variants, and how to set rel=canonical so shared content doesn't
strand readers in the wrong edition.

Adds one design doc —
docs/exec-plans/active/2026-06-03-ia-sharing-canonical-validation-design.md.
No content or template changes. (The platform FAQ work that originally shared
this branch already landed via #7295, so the net diff here is the design doc
alone.)

Closes #7233 · Unblocks #7232 · Advances #7245

Decision

Each edition stays self-canonical; shared content is transcluded inline. A
Core reader stays in Core docs — search, AI, and internal links keep them there.
Sharing is handled by authoring shared prose once and rendering it in each
edition, not by pointing one edition's canonical at another.

The four decisions:

  • D1 — Invert the sharing mechanism. Author shared content once as clean
    prose (no show-in/hide-in) and transclude it into each edition. Each page
    is complete at its own URL. Cross-edition links are allowed only to suggest an
    upgrade, never to complete a page.
  • D2 — Do the canonical cleanup now; don't gate it on a test. No outcome of
    the original decision rubric argues against canonical work, and field evidence
    shows canonical signals are honored at the index layer — so canonical: self
    reliably keeps each edition distinct. The measurement test can't change the
    action, so it isn't a gate.
  • D3 — Keep each edition self-canonical. Every edition owns its own
    canonical. This folds in the reference-vs-usage classification.
  • D4 — Validate after cleanup, non-blocking. Before/after citation check on
    the pilot pages (Phase 2 AI visibility: pilot content-sharing conversion (IA migration de-risk) #7298); never gates the migration.

What this changes for #7245

The urgent task flips. It is not "point shared pages at Enterprise" — that's
already the automatic behavior: a page with source: and no canonical
inherits a sibling edition's canonical (Enterprise first), so Core engine pages
already route to Enterprise today. The fix is to add canonical: self where
it's missing, so Core readers stay in Core. One-line, reversible change.

Byte-identical reference shared across all five v3 editions (client libraries,
line protocol, SQL/InfluxQL) is a separate case where consolidating to one owner
may be worth it — deferred to the broader cross-edition IA work.

Reviewing

This is a design / decision record (an exec-plan), not rendered content — no
preview pages. Review the decision and its rationale. Start with D1 (the
mechanism and the canonical: self example) and D3 (the canonical rule and
the #7245 re-scope).

The doc lives under docs/exec-plans/active/ and is intended to persist on
master (the cleanup-ephemeral-docs workflow scrubs only PLAN.md /
HANDOVER.md, not this path).

Checklist

  • Rebased/mergeable (master merged into branch)
  • Local build passes — docs-only change, no content or template impact

Move /platform/faq/ to the data-driven faq pattern: questions live in
data/faqs/platform.yml, rendered by the faq shortcode and emitted as
schema.org FAQPage JSON-LD via faq_data/faq_canonical frontmatter.

Add four category-level Q&As (what InfluxDB is used for, which industries,
when to use a time series database, is it open source), expand the
relational-database comparison, and keep the decision-page cross-link.

Add a Cypress spec asserting the visible Q&As, stable anchors, and the
FAQPage JSON-LD shape.

Closes #7202
Validate-first design for the Phase 2 IA content-sharing mechanism:
a canonical-honoring test protocol (dual target: byte-identical
release-notes with canonical vs. identical engine pages without) and
an outcome-keyed decision rubric. Defers the route choice until data
lands. Splits downstream work into #7297 (mechanism spike) and #7298
(pilot conversion).

Refs #7230, #7232
Decide Route 2 (conventional split) + promote #7245 canonical cleanup to
do-now, on field evidence and rubric structure rather than the gated
hand-run audit. Repurpose the section-3 test as non-blocking before/after
validation. Add field-evidence and reference-vs-usage sections.
…erence

Scope the #7245 urgent pass to Core<->Enterprise shared content (canonical
to Enterprise as the most complete edition). Defer canonical ownership for
reference shared across all v3 editions (client libraries, etc.) to broader
cross-edition IA work; keep current canonical in the meantime.
@jstirnaman jstirnaman marked this pull request as ready for review June 8, 2026 18:09
@jstirnaman jstirnaman requested a review from a team as a code owner June 8, 2026 18:09
@jstirnaman jstirnaman requested review from sanderson and removed request for a team June 8, 2026 18:09
@jstirnaman jstirnaman removed the request for review from sanderson June 12, 2026 15:05
@jstirnaman jstirnaman changed the title Feat platform faq expansion 7202 docs(platform): IA content-sharing canonical decision (#7233) Jun 30, 2026
… transclusion

Rewrite the IA content-sharing decision doc around canonical: self.
Each edition stays self-canonical and shares content by inline
transclusion, rather than consolidating shared pages to a sibling
edition (which would route Core readers into Enterprise docs).

- D1: transclude shared prose inline; cross-edition links only for
  upgrade suggestions, never to complete a page
- D3: keep each edition self-canonical; fold reference-vs-usage
  classification in; #7245 becomes 'add canonical: self'
- Tighten from 336 to ~140 lines, Google developer style
@jstirnaman jstirnaman changed the title docs(platform): IA content-sharing canonical decision (#7233) docs(platform): IA content-sharing decision — self-canonical + inline transclusion (#7233) Jul 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Phase 2 AI visibility: design review — sharing mechanism for IA migration

1 participant