/*
 * This is a manifest file that'll be compiled into application.css.
 *
 * With Propshaft, assets are served efficiently without preprocessing steps. You can still include
 * application-wide styles in this file, but keep in mind that CSS precedence will follow the standard
 * cascading order, meaning styles declared later in the document or manifest will override earlier ones,
 * depending on specificity.
 *
 * Consider organizing styles into separate files for maintainability.
 */

/* The authenticated dashboard shell must work before Tailwind's generated build is
 * refreshed (system tests serve the checked-in asset). Keep only the responsive
 * structural rules here; visual styling stays in the view's utility classes. */
.customer-shell {
  min-height: 100vh;
}

.customer-sidebar {
  position: relative;
  border-bottom: 1px solid rgb(229 231 235);
}

.customer-desktop-navigation {
  display: none;
}

.customer-mobile-navigation {
  display: block;
}

@media (min-width: 1024px) {
  .customer-shell {
    display: grid;
    grid-template-columns: 17rem minmax(0, 1fr);
  }

  .customer-sidebar {
    position: sticky;
    top: 0;
    display: flex;
    height: 100vh;
    flex-direction: column;
    border-right: 1px solid rgb(229 231 235);
    border-bottom: 0;
  }

  .customer-desktop-navigation {
    display: flex;
  }

  .customer-mobile-navigation {
    display: none;
  }
}