Layout builder override indicator

The Layout Builder Override Indicator module adds a badge to the Navigation module's top bar that tells editors, at a glance, whether the entity they are currently viewing or editing uses its bundle's default layout or has its own Layout Builder override.

Core's Layout Builder has no built-in, always-visible way to tell editors
this. The "Manage layout" tab and the "Revert to defaults" button are shown
regardless of override state, so editors have no quick way to know whether
they're looking at a shared default layout or a one-off override until they
open the layout editor itself. This module surfaces that state directly in
the top bar on every route for an entity that supports Layout Builder
overrides.

Requirements

This module requires the following modules:

• Layout Builder (Drupal core)
• Navigation (Drupal core)

Installation

Install as you would normally install a contributed Drupal module. For
further information, see
Installing Modules.

Configuration

The module does not have a configuration page. Once enabled, the indicator
appears automatically in the top bar's context region for any content entity
whose bundle has Layout Builder overrides enabled, on any route where that
entity is resolvable (view, edit, layout, etc.).

Similar projects

• Layout Builder RDP
  hides the "Revert to defaults" button behind a permission. It controls
  access to reverting, but does not tell editors whether an entity is
  currently overridden — the two modules solve different problems and
  can be used together.
• Layout Builder Usage Reports
  gives administrators a site-wide report of which nodes use Layout Builder.
  It's an auditing tool for admins, not a live per-entity indicator for
  editors working on a single page.
• Gin LB can globally
  hide the "Revert to defaults" button, but has no per-entity override
  detection of its own.