/* Long-form text pages: /privacy, and anything like it later.
 *
 * Separate from style.css because it is the only place in kame with running
 * prose. style.css dresses an app -- a search box, a transport, sentence spans
 * -- and has no rules for h2, p or ul at all, since no page needed them. Adding
 * bare-element rules there would reach the reader, where a <p> is article text
 * the reader stylesheet already controls.
 *
 * Scoped under .prose for the same reason: .reader is shared with the article
 * view, so these must not apply to it.
 */

.prose {
  /* The reader reserves 190px at the foot for the player. There is no player
     here, so the page would otherwise end in a band of empty space. */
  padding-bottom: 60px;
  line-height: 1.65;
}

.prose h1 { margin-bottom: 4px; }

.prose h2 {
  font-family: var(--serif);
  font-size: 22px;
  line-height: 1.3;
  margin: 36px 0 10px;
}

.prose h3 {
  font-size: 15px;
  font-weight: 600;
  letter-spacing: .01em;
  color: var(--muted);
  margin: 24px 0 6px;
}

.prose p { margin: 0 0 14px; }

.prose ul { margin: 0 0 14px; padding-left: 22px; }
.prose li { margin-bottom: 6px; }

.prose strong { font-weight: 600; }

.prose code {
  font-size: .92em;
  padding: 1px 5px;
  border-radius: 5px;
  background: var(--accent-soft);
}

.prose a { color: var(--accent); }

/* The colophon is centred under a hero on the homepage; here it follows a wall
   of text and needs a rule above it to read as a footer rather than a stray
   line of body copy. */
.prose + .colophon,
.prose .colophon {
  margin-top: 40px;
  border-top: 1px solid var(--border);
}