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

/* Pagy pagination */
.pagy nav {
  display: flex;
  gap: 0.25rem;
  justify-content: center;
}

.pagy nav a, .pagy nav span {
  display: inline-block;
  padding: 0.25rem 0.625rem;
  font-size: 0.875rem;
  border-radius: 0.25rem;
  border: 1px solid #e5e7eb;
  color: #374151;
  text-decoration: none;
}

.pagy nav a:hover {
  background-color: #f3f4f6;
}

.pagy nav a.current, .pagy nav span.current {
  background-color: #3b82f6;
  color: white;
  border-color: #3b82f6;
}

.pagy nav span.gap {
  border: none;
}

/* GFM task lists: drop the bullet on list items that render a checkbox */
.prose li:has(> input[type="checkbox"]) {
  list-style: none;
  margin-left: -1.25em;
}
.prose li > input[type="checkbox"] {
  margin-right: 0.4em;
}
/* Loose lists (blank lines between items) wrap item text in a block <p>,
   which drops it below the checkbox — keep it inline with the box. */
.prose li:has(> input[type="checkbox"]) > p {
  display: inline;
  margin: 0;
}