/*
 * 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.
 */

/* Site nav: on desktop the links sit inline with the logo (.ht-nav-links
   as a transparent flex passthrough); below the breakpoint they collapse
   behind a hamburger and drop down as a stacked panel when opened. */
.ht-nav-toggle {
  display: none;
  background: none; border: none; cursor: pointer;
  font-size: 1.4rem; line-height: 1; padding: 0.25rem;
}
.ht-nav-links { display: contents; }

@media (max-width: 640px) {
  .ht-nav-toggle { display: block; margin-left: auto; }
  .ht-nav-inner { flex-wrap: wrap; }
  .ht-nav-links {
    display: none;
    flex-basis: 100%;
    flex-direction: column;
    align-items: flex-start;
    gap: 0.65rem;
    padding-top: 0.75rem;
  }
  .ht-nav-links--open { display: flex; }
  .ht-nav-links .ht-nav-divider { display: none; }
  .ht-nav-links .ht-nav-spacer { display: none; }
}

@media (max-width: 520px) {
  .ht-nav-public .ht-nav-brand-text { display: none; }
  .ht-nav-public { padding-left: 0.85rem !important; padding-right: 0.85rem !important; }
  .ht-nav-public .ht-nav-inner { gap: 0.65rem !important; }
}

@media (max-width: 520px) {
  .ht-nav-admin .ht-nav-brand-text { display: none; }
}