Streaming

Enterprise Macro Test

Test page for the enterprise inline macro from docs-extensions-and-macros (DOC-887). The markup below replicates the macro’s exact rendered output so the enterprise-feature class can be styled in this UI bundle. Every output shape the macro can emit appears here, plus stress contexts for the lock glyph and underline. The first two sections use the link targets the macro really resolves to: the licensing page for Topic Deletion Control, which has no feature page in the registry, and the feature page for Tiered Storage, which has one. Later sections vary only the tooltip, role, or link handling, so their targets are placeholders.

Default output

The macro enterprise:Topic Deletion Control[] with a registry entry that carries no xref renders, linking to the licensing page:

This cluster uses Topic Deletion Control to block accidental topic deletes.

With a feature xref

The macro enterprise:Tiered Storage[] with a registry entry that carries an xref (or a per-use xref= attribute) renders the same shape, linking to the feature page:

Enable Tiered Storage to offload data to object storage.

Display text override

enterprise:Audit Logging[text=audit logging] keeps the canonical feature name in the tooltip while the sentence reads naturally:

Enable audit logging before compliance review.

Tooltip override

enterprise:Iceberg Topics[tooltip=…​] replaces the generated tooltip sentence:

Set up Iceberg Topics for your lakehouse.

Without a link

With the enterprise-links attribute set to false:

Configure Audit Logging on a SASL listener.

Without a tooltip

With enterprise-tooltip set to false, the span carries no tooltip attribute at all (underline and lock must still render):

Use Leader Pinning to keep leaders in one zone.

Data-attribute tooltip variant

With enterprise-tooltip set to true, the tooltip renders as data-enterprise-tooltip for UI-driven tooltips instead of the native title (activated as a tippy tooltip by 12-activate-tooltips.js):

Set up Iceberg Topics for your lakehouse.

Custom role

With enterprise-feature-role set to something other than enterprise-feature, the UI applies no styling. This one should look like a plain link, with no underline or lock:

A custom role renders Shadowing unstyled.

Stress contexts

Multiple terms in one paragraph, with punctuation directly after the term:

Both Tiered Storage, Remote Read Replicas, and Whole Cluster Restore (WCR) share one license gate.

A long feature name that wraps across lines (the lock glyph must sit after the last word, not float alone):

Narrow container: Continuous Intra-Broker Partition Balancing wraps here.

In a list:

In a table cell:

Tiered Storage

Feature description in the next cell

In an admonition:

This note mentions an enterprise feature: Shadowing inside admonition content.

Enterprise properties share the lock

Enterprise-only configuration properties get the same lock glyph through code.is-enterprise-property (added by 19-property-tooltips.js):

The property cloud_storage_enabled requires an Enterprise license, while log_segment_size does not.

Styling notes

The implemented treatment for .enterprise-feature:

  • A dotted underline in --link-highlight-color, matching the glossary term affordance, applied to the inner link or to the span when links are disabled.

  • A small lock glyph (0.9em) after the term, rendered as an SVG mask filled with --link-highlight-color. The mask variable lives in the global :root design tokens so dark mode adapts automatically.

  • code.is-enterprise-property reuses the same mask variable, so feature terms and enterprise properties carry an identical lock.

  • The data-enterprise-tooltip variant is activated as a tippy tooltip by 12-activate-tooltips.js, mirroring the site’s other tooltips. The default title variant keeps the native browser tooltip.

  • The generated enterprise_features:: tables need no UI styling: they render as ordinary AsciiDoc tables whose feature cells contain the same linked spans shown above.