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

h1 {
  font-size: 6rem;
}

h2 {
  font-size: 4rem;
}

h3 {
  font-size: 2rem;
}

body {
    height:100vh;
}

/* In your application.css */
.trix-content .btn.btn-primary {
  display: inline-block;
  padding: 0.5rem 1rem;
  text-align: center;
  text-decoration: none;
  color: #fff;
}

.trix-content a {
  color: #D95D39;
  text-decoration-line: underline;
  text-decoration-color: #D95D39;
}

.trix-content ul {
  list-style-type: disc !important;
  padding-left: 2rem !important;
}

.trix-content ol {
  list-style-type: decimal !important;
  padding-left: 2rem !important;
}

/* (Optional) Better styling for nested lists */
.trix-content ul ul {
  list-style-type: circle !important;
}

.trix-content ol ol {
  list-style-type: lower-alpha !important;
}

.aktuality {
  font-size: 4vh;
}

/* In your global CSS or directly in the navbar element */
.navbar {
  min-height: 4rem;   /* adjust to match your actual navbar height */
  line-height: 1.5;   /* consistent line-height */
}

.navbar a, .navbar span, .navbar .btn {
  line-height: 1.5;
}

.symbol-of-tolerance {
  height:.25em;
  background:linear-gradient(90deg,#ea392f 0% 9.091%,#f28917 9.091% 18.182%,#eecb12 18.182% 27.273%,#78b82a 27.273% 36.364%,#4375ca 36.364% 45.455%,#c346e3 45.455% 54.545%,#7bcce5 54.545% 63.636%,#eaeaea 63.636% 72.727%,#f4aec8 72.727% 81.818%,#000 81.818% 90.909%,#945516 90.909% 100%)
}

.navbar-center a h1 {
  font-size: 1.5rem;
  line-height: 1.5;
}

th {
  color: #3b2f2f;
}

article .attachment__caption {
  display: none;
}