Skip to main content

Frontend

The Company module uses a settings page with a single form and Alpine internal tabs to section the fields.

File Structure​

resources/views/settings/
├── business.blade.php
└── business/
    ├── _header.blade.php
    ├── _tabs-container.blade.php
    ├── _tabs-navigation.blade.php
    ├── _personal-info.blade.php
    ├── _legal-address.blade.php
    ├── _tax-info.blade.php
    ├── _contacts.blade.php
    ├── _business-info.blade.php
    ├── _integrations.blade.php
    └── _actions.blade.php

Frontend Pattern​

Orchestrator View​

resources/views/settings/business.blade.php:

  • includes header
  • contains the main form PUT settings.business.update
  • includes _tabs-container with all sections
  • contains separate hidden forms, outside the main form, for DELETE settings.business.delete-logo and DELETE settings.google-calendar.disconnect
No nested forms

Any action inside a tab that needs its own HTTP verb must follow the hidden-form pattern above: a <form> nested inside the main settings form is invalid HTML, the browser hoists it out, and the outer form loses its @method('PUT') spoofing — saving settings then fails with 405 Method Not Allowed. Trigger these with <button type="button" onclick="document.getElementById('...').submit()">.

Alpine Inline Tabs​

_tabs-container.blade.php manages tab state with:

  • x-data="{ activeTab: ... }"
  • hidden input _active_tab populated by activeTab
  • x-show + x-cloak for section content

_tabs-navigation.blade.php:

  • tab switch via @click="activeTab = '...'"
  • also updates window.location.hash for UX

Available tabs:

  • personal
  • legal
  • tax
  • contacts
  • business
  • documents
  • integrations — GitHub PAT, Google Calendar connection, billing tool URL

Form Sections​

The content partials use Blade form components (x-form-input, x-form-textarea) and separate responsibilities:

  • _personal-info: owner first/last name
  • _legal-address: complete legal address
  • _tax-info: tax/VAT + default currency (select from BusinessSettings::CURRENCIES), plus a "Regime Fiscale" section (tax_regime, profitability_coefficient, substitute_tax_rate, annual_revenue_cap, business_start_date) and the two fields feeding the tax estimation engine: Aliquota INPS (inps_rate) and Massimale Contributivo INPS (inps_ceiling, optional). Both have a hint explaining that leaving inps_rate empty disables the tax estimate everywhere in the app — see the Taxes backend docs
  • _contacts: email, certified email, phone
  • _business-info: business name/description, website, IBAN, logo

_actions.blade.php contains the form submit.

Logo Management​

In _business-info.blade.php:

  • shows logo preview if logo_path is present ($settings->logo_url)
  • supports logo deletion via submit of the hidden delete-logo-form
  • file input with client-side validations (accept) consistent with the backend

The module link is in the settings sidebar:

  • resources/views/layouts/sidebar/_nav-settings.blade.php
  • route settings.business.edit

Internationalization​

UI strings primarily use:

  • lang/*/business_settings.php

Dark Mode​

All partials are compatible with Tailwind dark:* classes.