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

/* Keep active nav link styling independent of Tailwind builds.
   Tailwind recompiles can lag/stale in dev; this guarantees the active link stays visible. */
.nav-link-active {
  background-color: #285a34;
  color: #ffffff;
}

.nav-link-active:hover {
  background-color: #21492b;
}

/* Button fallbacks (avoid transparent buttons when Tailwind build is stale) */
.btn-primary,
.btn-secondary,
.btn-danger {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  gap: 0.5rem;
  border-radius: 0.5rem;
  padding: 0.625rem 1rem;
  font-size: 0.875rem;
  font-weight: 600;
  line-height: 1.25rem;
  text-decoration: none;
}

/* Surface fallback (cards/containers) for when Tailwind build is stale */
.app-surface {
  background-color: #ffffff;
  border: 1px solid #ddd7cd;
  border-radius: 1rem;
  box-shadow: 0 1px 2px rgba(16, 24, 40, 0.06), 0 1px 3px rgba(16, 24, 40, 0.10);
}

.btn-primary {
  background-color: #2f6b3d;
  color: #ffffff;
}
.btn-primary:hover {
  background-color: #285a34;
}

.btn-secondary {
  background-color: #ebdccf;
  color: #6a4b2a;
  border: 1px solid #d8bfa8;
}
.btn-secondary:hover {
  background-color: #d8bfa8;
}

.btn-danger {
  background-color: #b9382f;
  color: #ffffff;
}
.btn-danger:hover {
  background-color: #982c25;
}