NebulaKit relies heavily on the slot approach for structuring components. You'll see it throughout the library - it's one of the core patterns behind how layouts and composite elements are built.
Slots define where content goes. Some slots accept only a single instance, while others can be used multiple times within the same component.
Certain slots are required for a component to render correctly, while others are optional, letting you extend or adjust structure without extra wrappers.
Understanding how slots work will help you read component APIs faster, compose layouts more intuitively and recognize where NebulaKit handles structure for you.
Components that rely on slots automatically check for required ones during render. If a required slot is missing, NebulaKit logs a warning in the console to help you catch structural issues early. Optional slots are ignored when absent, so you can extend layouts without noise.
Example