/*
 * The live site's `wp-custom-css` block, verbatim from the document head.
 *
 * This MUST load after /theme/style.css. On the live site WordPress prints it
 * as an inline <style id="wp-custom-css"> at the very end of <head>, so it
 * wins over the theme's own media queries. Several of its rules exist purely
 * to override theme rules of identical specificity — most importantly the
 * #page-slider-top .img-sushi vertical offsets, where the theme says
 * `top: calc(100% - 300px)` and this block says `calc(100% - 330px)`.
 *
 * It previously lived in src/app/globals.css, which Next injects BEFORE the
 * vendored <link> tags, so every one of those overrides silently lost the
 * cascade and the hero sushi image sat ~30px off at every breakpoint.
 */

@media screen and (max-width: 992px) {
  #page-slider-top .img-sushi {
    bottom: auto;
    top: calc(100% - 330px);
  }
  .wpsushiyama-section.bg-parallax {
    padding-bottom: 60px;
  }
}
@media screen and (max-width: 820px) {
  #page-slider-top .img-sushi {
    top: calc(100% - 250px);
  }
}
@media screen and (max-width: 600px) {
  #page-slider-top .img-sushi {
    top: calc(100% - 240px);
    width: 1200px;
    -ms-transform: translate(-41.5%, 0);
    transform: translate(-41.5%, 0);
  }
}
#footer-sections .hours span.time {
  display: block;
}
.schedule-day-time {
  line-height: 30px;
}
#footer-sections .hours {
  padding: 4px 0 46px;
}
.developer {
  font-size: 11px;
  color: #ffffff;
  opacity: 0.3;
  text-align: center;
}
.developer a {
  color: #f5b4a7;
}
.developer a:hover {
  opacity: 1;
  color: #ffffff;
}
