/* The cornerstone guides (app/views/pages/*.html.erb registered in Guide::ALL)
   and the /guides hub that lists them.

   These are long-form reading pages, so the rules here are about a comfortable
   measure and a legible outline rather than chrome. The .stats-table rules at
   the bottom of this file dress the data table inside the booking-window
   guide. */

.guide .guide-body,
.guide .page-title p {
  margin-left: auto;
  margin-right: auto;
  max-width: 52rem;
}

.guide .guide-dateline {
  margin: 0 auto 2.5rem;
  max-width: 52rem;
  text-align: center;
}

.guide .guide-section {
  margin-bottom: 3rem;
}
.guide .guide-section.center {
  text-align: center;
}
.guide .guide-section h3 {
  margin-bottom: 0.25rem;
}
.guide .guide-section h3 + p {
  margin-top: 0;
}

/* Body lists are plain <ul>/<ol> with their markers intact — .vertical-list is
   the site's nav-list style (87.5% and no markers), which is wrong for prose. */
.guide .guide-body li {
  margin-bottom: 0.5rem;
}

/* Two lists that ARE containers rather than bulleted prose: the hub's index of
   h2-headed entries, and the cross-links each guide closes on. A marker beside
   a heading competes with it. role="list" travels with every one of these in
   the markup — Safari/VoiceOver drops list semantics from list-style: none. */
.guide .guide-index,
.guide .guide-links {
  list-style: none;
  padding-left: 0;
}
.guide .guide-links li {
  margin-bottom: 1rem;
}
.guide .guide-index > li {
  border-bottom: 1px solid var(--border-gray);
  margin-bottom: 1.5rem;
  padding-bottom: 1.5rem;
}
.guide .guide-index > li:last-child {
  border-bottom: 0;
}
.guide .guide-index h2 {
  margin-bottom: 0.25rem;
}
.guide .guide-index p {
  margin-top: 0;
}

/* The data table inside the booking-window guide. Deliberately unscoped: these
   rules moved here from availability_stats.css when the public availability-stats
   page was removed (docs/completed_plans/public_stats_removal_plan.md, 2026-08-06), and this
   guide is now their only consumer.

   Scroll the wrapper, never the page: Tokyo ships a 98-character restaurant
   name, and the column beside it has to stay readable on a phone. Scrolling the
   <table> itself would mean making it a block box, which collapses it to its
   content width. */
.stats-table-scroll {
  margin-bottom: 1rem;
  overflow-x: auto;
}
.stats-table {
  border-spacing: 0;
  text-align: left;
  width: 100%;
}
.stats-table caption {
  color: var(--gray);
  font-size: 0.875rem;
  margin-bottom: 0.5rem;
  text-align: left;
}
.stats-table th,
.stats-table td {
  border-bottom: 1px solid var(--border-gray);
  padding: 0.5rem;
  vertical-align: top;
}
.stats-table thead th {
  background-color: var(--faint-gray);
  font-size: 0.875rem;
}
.stats-table tbody th {
  font-weight: 400;
}
.stats-table tfoot th,
.stats-table tfoot td {
  border-bottom: 0;
  font-weight: 700;
}
/* Figures never wrap; names may. A number broken across two lines is unreadable
   in a way a long restaurant name is not. */
.stats-table .right {
  text-align: right;
  white-space: nowrap;
}