{{--
Booking Types listing — docs/wireframes-v12/booking-type.html, content
region for content region.
The content region of that page is ONE card and nothing else: a
`.card-header` carrying the module icon, the heading and the primary Add
button, and a `.table-wrapper` with the `.data-table` under it.
**No filter bar and no search input** (CR-7 §1, §4). This is where the page
departs from the Projects and Inquiries listings, and it departs because the
wireframe does: those pages draw a `.filter-bar` as the card's header strip
and this one draws a heading row instead. Nothing here feeds a search box,
and BookingTypesDataTable sets `searching => false` to match — do not add
one without the client asking.
The primary action is inside the card header, not on a row above it. Same
reason: Projects and Inquiries put it above the card because their card
header is the filter bar and has no room; this card's header is a heading
row with the button already in it.
DataTables drives the table, and both the markup and the configuration come
from the html builder, so the column list exists in exactly one place:
BookingTypesDataTable::getColumns().
The two dialogs are included once at the foot, and nrems-master-modals.js
re-targets the Edit one per row — see partials/modals for why one instance
each rather than one per row.
--}}
@extends('layouts.app')
@section('title', __('booking_types.title'))
@section('breadcrumbs')
{{-- The wireframe's trail is Home / Administration / Booking Types.
"Administration" is the sidebar section and has no screen of its own,
so it renders as plain text — a null url — the way the wireframe writes
it. --}}