Current limitations

Inlay is pre-1.0. This release deliberately does not include:

• Navigation/menu building.
• A media library. The image field type is a single file upload; there's no asset browser.
• Rich-text editing. richtext is presently a plain textarea. The package does not sanitize this field's HTML - if your block renders it with {!! !!}, whatever an editor enters is output as-is. Only give editor access to people you'd trust with that.
• Nested blocks, slots/regions, or reusable "global" blocks. Composition is a flat, ordered list rendered inside a layout your own route or controller already provides.
• Finer-grained Page Definition rules - maximum/minimum block instance counts, locking or requiring one specific instance rather than every instance of a block, conditional allow-lists, role-specific Page Definitions, editor-built Page Definitions, and reassigning a Page's type after creation. See Page Definitions.
• Additional rendering adapters. There is exactly one renderer: a real Blade component tag, resolved through a registered alias. A directly-registered Livewire, Vue, or React outer component is not, and will not be, supported the same way a Blade component is.
• A more visible warning for an orphaned enum value. An enum case removed after content was authored against it falls back to the constructor default and logs a warning, the same as public rendering - there's no distinct admin-facing warning or publish-time block yet. See Enums.
• Settings versioning/migration for a block whose settings shape has changed since content was authored against it.

If you're evaluating Inlay for a project that needs any of the above today, treat this list as the current gap - none of it is silently half-implemented, it's simply not there yet.