STICKY BLOCK FOR GUTENBERG
Sticky Block for Gutenberg compatibility with REEID Translate
Sticky Block for Gutenberg compatibility with REEID Translate is being evaluated from available plugin evidence. Supports a per-block mode to keep the sticky behavior confined to the visible area of a parent container (“Within parent container”). No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Sticky Block for Gutenberg.
Official plugin information supports the compatibility context documented for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Sticky Block for Gutenberg is documented in the Other category with 7 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How Sticky Block for Gutenberg compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Supports a per-block mode to keep the sticky behavior confined to the visible area of a parent container (“Within parent container”).
- Offers configurable sticky behavior triggers including immediate display, scroll-threshold-based triggering (pixel/percentage), and time-delay triggering.
- Includes optional visitor dismissal via a close button, with an option to remember the dismissal for a configurable number of days.
- Provides editor and frontend sticky-state styling controls (e.g., top offset, z-index control, sticky-state background/text/shadow/padding/border/border-radius/opacity) and applies state classes such as `is-sticky` / `is-not-sticky`.
- Supports responsive enable/disable behavior with configurable viewport breakpoints (disable on mobile and/or disable on desktop).
- Can stop/un-stick before overlapping a specified element using a CSS selector (“Stop before an element”).
- Works in both the classic block editor and the Full Site Editing (Site Editor) context in WordPress 5.9+ (per plugin FAQ).
Distinctive features
Provides a Gutenberg container block that can make its inner blocks stick to the top or bottom of the viewport using `position: fixed` with scroll detection. Supports a per-block mode to keep the sticky behavior confined to the visible area of a parent container (“Within parent container”). Offers configurable sticky behavior triggers including immediate display, scroll-threshold-based triggering (pixel/percentage), and time-delay triggering. Includes optional visitor dismissal via a close button, with an option to remember the dismissal for a configurable number of days. Provides editor and frontend sticky-state styling controls (e.g., top offset, z-index control, sticky-state background/text/shadow/padding/border/border-radius/opacity) and applies state classes such as `is-sticky` / `is-not-sticky`. Supports responsive enable/disable behavior with configurable viewport breakpoints (disable on mobile and/or disable on desktop). Can stop/un-stick before overlapping a specified element using a CSS selector (“Stop before an element”). Works in both the classic block editor and the Full Site Editing (Site Editor) context in WordPress 5.9+ (per plugin FAQ).
CONTENT BOUNDARY
Sticky Block for Gutenberg capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
Sticky Block for Gutenberg and REEID Translate FAQ.
What does Sticky Block for Gutenberg do according to the available plugin evidence?
Sticky Block for Gutenberg has 7 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for Sticky Block for Gutenberg?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Sticky Block for Gutenberg?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate Sticky Block for Gutenberg in a multilingual WordPress workflow.
REEID documents Sticky Block for Gutenberg functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.