Blökkli Editor v1.3.4 Adds Runtime Visibility Controls, Edit Path Flexibility, and Dark Mode Fix

Staff Reporter

Blökkli Editor v1.3.4 Adds Runtime Visibility Control and Dark Mode Fix

The Blokkli editor has released version 1.3.4, bringing several improvements aimed at enhancing rendering logic and developer control. The update addresses CSS issues on dark mode websites, introduces new props for editing behavior, and simplifies custom component registration.

One key enhancement is the new shouldRenderItem prop on <BlokkliField>. This prop accepts a function that determines whether a block should render on the published page. While editing, all blocks appear, but those returning false are visually muted to indicate exclusion from final output. This gives editors visual feedback when blocks are excluded from published output.

Another addition is the editPath prop on <BlokkliProvider>, allowing projects to specify a different starting path for editing instead of defaulting to the current page. This improves flexibility for integrating Blokkli into headless or multi-path environments.

The release also fixes a long-standing issue where Blokkli styles could leak into unrelated dark mode interfaces. The patch ensures better isolation of editor styles in embedded environments. Additionally, Blokkli now supports improved type handling for custom features through the defineBlokkliFeature composable. Developers can register custom blocks by referencing them in the featureImports config option.

To view full release notes or upgrade, visit the official Blokkli repository on GitHub.

Headless CMS

Note: The vision of this web portal is to help promote news and stories around the Drupal community and promote and celebrate the people and organizations in the community. We strive to create and distribute our content based on these content policy. If you see any omission/variation on this please reach out to us at #thedroptimes channel on Drupal Slack and we will try to address the issue as best we can.