/* ==========================================================================
   OrgGuard Marketing Site — About Page
   ========================================================================== */

.about-section {
  padding: var(--section-padding-y) 0;
}

.about-section--alt {
  background-color: var(--gray-50);
}

.about-section h2 {
  text-align: center;
  margin-bottom: 1rem;
}

.about-section__lead {
  text-align: center;
  font-size: 1.125rem;
  color: var(--gray-600);
  max-width: 42rem;
  margin: 0 auto 3rem;
}

.about-prose {
  max-width: 42rem;
  margin: 0 auto;
  font-size: 1rem;
  color: var(--gray-700);
  line-height: 1.8;
}

.about-prose p {
  margin-bottom: 1.25rem;
}

/* ---------- Legal pages (/privacy/, /terms/) ----------
   These reuse .about-prose but are reference documents, not marketing prose:
   long, many sections, two heading levels, and read by scanning for one
   section rather than top to bottom. The modifier is deliberate. Do NOT move
   these rules onto bare .about-prose: /about/ also uses that class and has an
   h2 inside it, so unscoped rules silently restyle a public page. */

/* reset.css zeroes every margin and .about-prose sets none for headings, so
   without these the section headings sit flush against the paragraph above.
   Space above is larger than space below on purpose: a heading should read as
   attached to the text it introduces, not floating between two blocks.

   text-align overrides `.about-section h2` (line 13), which centers headings.
   Centering suits the marketing sections on /about/; it hurts here, because
   scanning for a section needs a consistent left rail. Same specificity as
   the rule it overrides (0,1,1), so this works only because it comes later in
   the file. Do not move it above .about-section. */
.about-prose--legal h2 {
  margin-top: 2.5rem;
  margin-bottom: 0.75rem;
  text-align: left;
}

.about-prose--legal h3 {
  margin-top: 1.75rem;
  margin-bottom: 0.5rem;
}

/* These lists have full sentences as items. With the reset's zeroed margins
   they butt against each other and read as one run-on block, which on /terms/
   hid the boundary between the three program phases.

   reset.css also strips list markers globally. That is right for nav and card
   lists, wrong here: "Your rights" and "How long we keep it" are enumerations
   a reader counts, and without markers they render as a run of short
   paragraphs. Markers restored for the legal pages only. */
.about-prose--legal ul {
  margin-bottom: 1.25rem;
  padding-left: 1.25rem;
  list-style: disc;
}

.about-prose--legal li {
  margin-bottom: 0.625rem;
}

/* The first heading follows the section's own top padding, so it does not
   need the stacking gap as well. */
.about-prose--legal > h2:first-child {
  margin-top: 0;
}

/* ---------- Founder card ---------- */
.founder-card {
  max-width: 42rem;
  margin: 0 auto;
  background-color: #fff;
  border: 1px solid var(--gray-200);
  border-radius: 1rem;
  padding: 2.5rem;
  display: flex;
  flex-direction: column;
  align-items: center;
  text-align: center;
  gap: 1.5rem;
}

.founder-card__avatar {
  width: 5rem;
  height: 5rem;
  border-radius: 9999px;
  background: linear-gradient(135deg, var(--brand-600), var(--brand-700));
  color: #fff;
  display: flex;
  align-items: center;
  justify-content: center;
  font-size: 1.75rem;
  font-weight: 800;
  flex-shrink: 0;
}

.founder-card__name {
  font-size: 1.25rem;
  font-weight: 700;
  color: var(--brand-900);
}

.founder-card__title {
  font-size: 0.875rem;
  color: var(--gray-500);
  margin-top: 0.25rem;
}

.founder-card__bio {
  margin-top: 1rem;
  font-size: 0.9375rem;
  color: var(--gray-700);
  line-height: 1.7;
}

.founder-card__avatar--photo {
  object-fit: cover;
  background: #fff;
  border: 1px solid var(--gray-200);
}

.founder-card__linkedin {
  display: inline-block;
  margin-top: 0.75rem;
  font-size: 0.8125rem;
  font-weight: 600;
  color: var(--brand-600);
  transition: color var(--transition-fast);
}

.founder-card__linkedin:hover {
  color: var(--brand-700);
  text-decoration: underline;
}

@media (min-width: 768px) {
  .founder-card {
    flex-direction: row;
    text-align: left;
    align-items: flex-start;
  }

  .founder-card__name-block {
    text-align: left;
  }
}

/* ---------- Roadmap teaser ---------- */
.roadmap-grid {
  display: grid;
  grid-template-columns: 1fr;
  gap: 1.5rem;
  max-width: 56rem;
  margin: 0 auto;
}

.roadmap-card {
  background-color: #fff;
  border: 1px solid var(--gray-200);
  border-radius: 1rem;
  padding: 1.75rem;
}

.roadmap-card__phase {
  font-size: 0.75rem;
  font-weight: 700;
  text-transform: uppercase;
  letter-spacing: 0.05em;
  color: var(--brand-600);
  margin-bottom: 0.5rem;
}

.roadmap-card h3 {
  font-size: 1.125rem;
  font-weight: 700;
  color: var(--brand-900);
  margin-bottom: 0.5rem;
}

.roadmap-card p {
  font-size: 0.875rem;
  color: var(--gray-600);
  line-height: 1.7;
}

@media (min-width: 768px) {
  .roadmap-grid {
    grid-template-columns: repeat(3, 1fr);
  }
}

/* ---------- Aetrum context block ---------- */
.aetrum-block {
  max-width: 42rem;
  margin: 0 auto;
  text-align: center;
}

/* Underline treatment comes from the global `main p a:not([class])` rule in
   components.css, which is (0,1,3) and outweighs this (0,1,1). The thickness
   and offset declared here were being silently discarded, so they are gone
   rather than left looking effective. font-weight is the one thing this block
   still contributes, and nothing else sets it. */
.aetrum-block a {
  color: var(--brand-600);
  font-weight: 600;
}

.aetrum-block a:hover {
  color: var(--brand-700);
}

/* ---------- Hero trust badges ---------- */
.about-hero__trust-badges {
  margin-top: 1.5rem;
  margin-bottom: 0;
}