# `PhoenixKitWeb.Components.LayoutWrapper`
[🔗](https://github.com/BeamLabEU/phoenix_kit/blob/v2.32.1/lib/phoenix_kit_web/components/layout_wrapper.ex#L1)
Dynamic layout wrapper component for Phoenix v1.7- and v1.8+ compatibility.
This component automatically detects the Phoenix version and layout configuration
to provide seamless integration with parent applications while maintaining
backward compatibility.
## Usage
Replace direct layout calls with the wrapper:
<%!-- OLD (Phoenix v1.7-) --%>
<%!-- Templates relied on router-level layout config --%>
<%!-- NEW (Phoenix v1.8+) --%>
<%!-- content --%>
## Configuration
Configure parent layout in config.exs:
config :phoenix_kit,
layout: {MyAppWeb.Layouts, :app}
# `admin_sidebar_compact_bootstrap`
Styles + pre-paint stamp for the admin sidebar's compact (icon-only) mode.
Render once, immediately BEFORE the sidebar markup. Everything about compact
mode lives client-side, and deliberately so:
* the sidebar is a **function component**, not a LiveView — there is no
`handle_event/3` owner for a `phx-click`, and giving one to every admin
page (or bolting a global `attach_hook` onto the admin `on_mount` chain)
would be a lot of machinery for a display preference;
* it is a per-browser density choice, exactly like the theme, so it belongs
in `localStorage` next to it rather than in a settings row;
* a client-side toggle costs no round trip, and nothing for morphdom to
fight over — the DOM is identical either way, only `` changes.
Which makes the first paint the whole problem, and the reason this is a
synchronous inline `