/*
 * 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.
 */
.auth-links {
  display: flex;
  gap: 10px;
  align-items: center;
}

.auth-btn {
  padding: 4px 10px;
  border-radius: 6px;
  font-weight: 600;
  text-decoration: none;
  color: white;
}

.auth-btn.login {
  background: #1e88e5; /* blue */
}

.auth-btn.signup {
  background: #43a047; /* green */
}

.auth-btn.logout {
  background: #e53935; /* red */
}

.auth-btn:hover {
  opacity: 0.85;
}
.net-card {
  background: #1a1a1a;
  border: 1px solid #333;
  border-radius: 10px;
  padding: 15px;
  margin-bottom: 20px;
  box-shadow: 0 0 10px rgba(0,0,0,0.4);
}

.net-card-header {
  font-size: 1.3rem;
  font-weight: bold;
  color: gold;
  margin-bottom: 10px;
}

.net-card-body p {
  margin: 4px 0;
  color: #ddd;
}

.net-card-actions {
  margin-top: 12px;
  display: flex;
  gap: 10px;
}

.btn-edit {
  background: #1e88e5;
  padding: 6px 12px;
  border-radius: 6px;
  color: white;
  text-decoration: none;
}

.btn-delete {
  background: #e53935;
  padding: 6px 12px;
  border-radius: 6px;
  color: white;
  text-decoration: none;
}

.btn-edit:hover,
.btn-delete:hover {
  opacity: 0.85;
}