{{-- The customer's own settings. ## What was wrong, three times over First it was one column 768px wide in a 1240px shell, holding everything a customer might ever change, two thousand pixels deep. Then it became four tabs — better — but the cards inside them were still boxes of different heights in a grid, which on the contract tab produced a short one, a wide one and a short one again: a staircase with no rhythm and half the width empty beside it. ## What it is now Panels and rows (x-ui.panel, x-ui.row). A group is a card with a header that names it; a setting is a ROW inside that card — what it is on the left, the control on the right, dividers between. That is the shape every settings page worth copying uses, and it is the shape that uses the width: a label column of 280px with the control beside it fills the line, where a stack of full-width inputs leaves two thirds of it empty. Below `sm` the rows stack, because on a telephone a label belongs above its field. --}}
{{ __('settings.eyebrow') }}
{{ __('settings.subtitle') }}
{{ __('settings.twofa_sub') }}
@if ($cancellationScheduled) {{ __('settings.cancel_scheduled_body', ['date' => $instance?->service_ends_at?->local()->isoFormat('LL')]) }} @elseif ($hasActivePackage) {{ __('settings.package_active', ['plan' => $instance ? __('billing.plan.'.$instance->plan) : '—']) }} @else {{ __('settings.no_package') }} @endif
@if ($hasActivePackage && ! $cancellationScheduled)@if ($withdrawal->open) {{ __('withdrawal.card_sub', [ 'date' => $withdrawal->endsAt->local()->isoFormat('LL'), 'days' => $withdrawal->daysLeft(), ]) }} @else {{ $withdrawal->refusal }} @endif
@if ($withdrawal->open)
{{ __('dpa.in_force_note') }}