Add support for 3D printed rack-mount solutions, including internal multi-splits.

[dirtyformal]

Summary

Support 3D printed rack-mount enclosures (OpenRack, RackMod, etc.) that contain multiple devices in defined bays/slots.

Problem

Users have 3D printed rack enclosures with internal bays:

Each enclosure is a single rack unit with multiple internal "bays" for mini PCs, SBCs, etc. Current workaround is text annotations, which isn't ideal.

Solution: Container Devices with Slots

Container devices define their internal slot layout. Child devices are placed into specific slots.

┌─────────────────────────────────┐
│ U6  ┌───────────────┬──────────┐│
│     │ Bay 1 (70%)   │Bay 2(30%)││  ← Container with custom slot widths
│ U5  │[Beelink EQR6] │  [Vent]  ││  ← Children in slots
│     └───────────────┴──────────┘│
└─────────────────────────────────┘

Data Model

// Container DeviceType
interface DeviceType {
  // Defines slots for child devices
  slots?: Array<{
    id: string;             // "bay-1", "bay-2"
    width_fraction: number; // 0.7, 0.3 (must sum to 1.0)
    label?: string;         // "Left Bay", "Vent"
  }>;
}

// Child PlacedDevice
interface PlacedDevice {
  container_id?: string;  // ID of parent PlacedDevice
  slot_id?: string;       // Which slot ("bay-1")
}

Example: 1U Enclosure with 70/30 Split

// DeviceType for the enclosure
{
  slug: "openrack-1u-2bay",
  manufacturer: "Custom",
  model: "OpenRack 1U",
  u_height: 1,
  category: "accessory",
  slots: [
    { id: "bay-1", width_fraction: 0.7, label: "Main Bay" },
    { id: "bay-2", width_fraction: 0.3, label: "Vent/Small" }
  ]
}

// PlacedDevice for child in bay 1
{
  id: "device-123",
  device_type: "beelink-eqr6",
  position: 5,
  container_id: "enclosure-456",  // References parent
  slot_id: "bay-1"
}

Implementation

Depends on: #146 (half-width foundation)

1. Schema: Add slots to DeviceType, container_id + slot_id to PlacedDevice
2. Rendering: Draw slot dividers, render children within slot bounds
3. Placement UX: Click slot to place device, or drag into slot
4. Collision: Children don't collide with rack - only with other children in same container
5. Slot editor: UI to define slot count and width fractions

Slot Editor UX

Simple approach for defining slots:

1. Select number of bays: 2, 3, or 4 (buttons)
2. Default to equal widths
3. "Customize widths" expands sliders for each bay
4. Widths must sum to 100%

┌─────────────────────────────┐
│ Number of bays: [2] [3] [4] │
│                             │
│ ☑ Customize widths          │
│   Bay 1: [====70%====]      │
│   Bay 2: [==30%==]          │
│                             │
│ Preview:                    │
│ ┌──────────────┬───────┐    │
│ │    Bay 1     │ Bay 2 │    │
│ └──────────────┴───────┘    │
└─────────────────────────────┘

Acceptance Criteria

• slots array on DeviceType schema (id, width_fraction, label)
• container_id and slot_id on PlacedDevice schema
• Container renders with visible slot dividers
• Children render inside their assigned slot
• Slot editor UI for defining bay layout
• Variable width fractions (e.g., 70/30, 50/50, 33/33/34)
• Generic "Custom 1U Enclosure" and "Custom 2U Enclosure" device types
• Clicking empty slot opens device placement
• Save/load preserves container relationships

Constraints

• No nested containers: A container cannot be placed inside another container
• Children don't collide with rack: Only with siblings in same container
• Orphan handling: If container deleted, children are also removed

Files to Modify

• src/lib/types/index.ts - slots on DeviceType, container fields on PlacedDevice
• src/lib/schemas/index.ts - Zod schemas with slot validation
• src/lib/components/RackDevice.svelte - Container rendering with slots
• src/lib/components/SlotEditor.svelte - New component for slot configuration
• src/lib/stores/layout.svelte.ts - Container placement logic
• src/lib/utils/collision.ts - Container-aware collision

---

Original request from @username - thank you for the detailed feature request and images!

🤖 Generated with Claude Code

[ggfevans]

Thanks for this detailed submission @dirtyformal! (also love that name, hah)

I appreciate your thoughts & encouragement. This is certainly a nuanced approach that is worth considering.

You're right it is somewhat overlapping with existing work as you mentioned, my thought is #159 is the 'parent' to all of this conceptually.

Though, to your point, this might be (somewhat) easily achieved through a basic CSS grid approach. Basically HTML tables again, hah.

I will see what we can do to get this in efficiently as this concept of subdividing a shelf is something that is pertinent to almost every single homelabber so I see the value in including it.

[ggfevans]

Analysis Complete

Thank you for the detailed feature request! This use case has been analyzed alongside related issues (#146 half-width devices, #143 shelf items) and incorporated into epic #159 (Flexible Device Layouts).

How This Will Work

Your 3D printed enclosures with internal bays will be supported through a container device concept:

1. Container DeviceType - The enclosure itself (e.g., "OpenRack 1U") with a container_layout defining the bay structure
2. Bay Configuration - Preset templates (2-bay, 3-bay, 4-bay) with customizable width fractions for uneven splits like your Beelink + Vent example
3. Child Placement - Devices placed into specific bays via parent_device_id and bay_index

Visual Example

┌─────────────────────────────────┐
│ U6  ┌───────────────┬──────────┐│
│     │ Bay 1 (70%)   │Bay 2 (30%)│  ← 1U enclosure with custom widths
│ U5  │[Beelink EQR6] │  [Vent]   ││  ← Children in bays
│     └───────────────┴──────────┘│
└─────────────────────────────────┘

Implementation Order

This issue depends on foundational work from #146 and #143:

#146 (half-width) → #143 (shelves) → #372 (this issue)

Each phase builds on the previous - #146 establishes horizontal positioning, #143 introduces parent/child container concept, and #372 adds slotted grid containers.

Device Library

We'll include both:

• Generic templates: "Custom 1U Enclosure", "Custom 2U Enclosure" (user-configurable bays)
• Specific entries: OpenRack 1U/2U, RackMod 1U/2U (pre-configured based on the 3D printable projects you mentioned)

---

Added to v0.8.0 milestone as part of epic #159.

[ggfevans]

Dependency Update

Per the Layout Work Plan, this issue now depends on #452 (Container model schema foundation).

Implementation Order

1. feat: Container model schema foundation (slots + child devices) #452 - Container schema foundation (types, slots, collision detection, rendering)
2. Add support for 3D printed rack-mount solutions, including internal multi-splits. #372 - 3D printed rack-mount solutions (uses container model)

The container schema work (#452) extracts the foundation work from this issue:

• slots on DeviceType
• container_id and slot_id on PlacedDevice
• Container-aware collision detection
• Base container rendering in RackDevice

This issue (#372) then focuses on:

• Slot editor UI
• Specific device types (OpenRack, RackMod)
• Placement UX refinements
• Library additions

This dependency ensures the same container model also works for #143 (shelves) and #73 (blade chassis).

[ggfevans]

Converted to discussion as it is not a specifically actionable issue (but has plenty of em related!)