/* ============================================================
   Kura — the grounds.

   Four surfaces had four different backgrounds: the site was white,
   the app was #F4F1EA, the downloads page was #0A0A0A, and capture
   inherited whichever of those it happened to link. This file is the
   single place the answer lives. Nothing below is a suggestion: a
   page that needs a background reads one of these tokens, and pages
   do not invent greys of their own.

   Two grounds:

     washi  #F1EFE8  the site — landing, downloads, changelog,
                     feature requests, capture. Everything a visitor
                     can reach without a token.
     paper  #FFFFFF  the app — the web app, macOS, iOS, the extension
                     surfaces. Everything behind the token.

   One alternate, for the dark theme on either: the void, #12100D.

   The brand void, #0A0A0A, is not a page ground and never was. It is
   the ground the mark is drawn on and the ground brand assets sit on.
   Do not reach for it to darken a page.

   One ink, at alpha. Every secondary tone is ink at a lower alpha —
   no second grey, no accent, no red.

   The mark itself takes none of these. It is fixed: #F2EDE0 / #B4AC98
   / #DAD3C1 sinking into a #12100D portal, on any ground, in either
   theme. Changing a page's ground never changes the logo.
   ============================================================ */

:root {
  --ground-site: #F1EFE8;
  --ground-app:  #FFFFFF;
  --ground-alt:  #12100D;
  --brand-void:  #0A0A0A;

  /* the ink, and the ink the alternate ground takes */
  --ink-base:    #17160F;
  --ink-alt:     #F2EDE0;

  /* the surface a card, well, or sunken row sits on, per ground */
  --surface-site: #FBFAF7;
  --surface-app:  #F7F5F0;
  --surface-alt:  #1A1813;

  /* the fixed mark, for anything that draws it in CSS */
  --mark-light:  #F2EDE0;
  --mark-mid:    #B4AC98;
  --mark-dark:   #DAD3C1;
  --mark-portal: #12100D;
}