/*!*********************************************************************************************************************************************************************************************************************************************************************!*\
  !*** css ./node_modules/css-loader/dist/cjs.js!./node_modules/postcss-loader/dist/cjs.js??ruleSet[1].rules[0].use[2]!./node_modules/resolve-url-loader/index.js!./node_modules/sass-loader/dist/cjs.js??ruleSet[1].rules[0].use[4]!./theme/src/scss/page/home.scss ***!
  \*********************************************************************************************************************************************************************************************************************************************************************/
/*
 * WARN: THIS FILE SHOULD ONLY BE FILLED WITH SCSS-SPECIFIC VARIABLE OVERRIDES.
 *
 * This file will be imported for each page to help managing the styles. To help
 * make the styling slimmer, and lesser doubled styling for the same components,
 * actual CSSes should be imported only on the `_theme.scss` file only.
 */
/*
 * This specific file introduces new variable to the theme that are not actually
 * exists in the theme, such as new component and such.
 */
/*
 * Little context for the line height calculation. In the design spec, the line
 * height of each font is actually defined, this is why I, chez14, add the line
 * height to the this part as well.
 *
 * Since the unit that being used in the original design are in px, we need to
 * convert this to rem, to make it responsive. REM are actually defined in the
 * device settings, hence for people with visually challenged limitations, if
 * they set the font really big, our website's font big too.
 *
 * That being said, people said 1 rem usually set to 16px. Hence all pixels here
 * are calculated by dividing them to 16, then times 1rem to convert them to
 * rem.
 *
 * ==================================================
 *
 * Notes for "Why do you use Mixins". My reasoning is:
 * 1. There's a lot of pitfals for @extend that may cause alot of trouble. I.e.
 *    older browser support problem, source ordering problem, @extend chaining
 *    that causes problematic things, and more. Please check following
 *    StackOverflow discussion to learn more:
 *    https://stackoverflow.com/q/18008700.
 *
 * 2. By using Mixins, we can use the same stylesheets, and apply them to
 *    certain components, for example, the cards, without extending it.
 */
.slick-container--banner {
  position: relative;
}
.slick-container--banner .slick-slide .section-band-image {
  background-color: #cccccc;
  display: flex;
  align-items: center;
}
@media (min-width: 768px) {
  .slick-container--banner .slick-slide .section-band-image {
    aspect-ratio: 5/2;
  }
}
.slick-container--articles {
  --bs-gutter-x: 1rem;
  --bs-gutter-y: 0;
  display: flex;
  flex-wrap: wrap;
  margin-top: calc(-1 * var(--bs-gutter-y));
  margin-right: calc(-0.5 * var(--bs-gutter-x));
  margin-left: calc(-0.5 * var(--bs-gutter-x));
}
.slick-container--articles .card-thumbnail__with-image .card-img-contained {
  aspect-ratio: 352/213;
}
.slick-container--articles .card {
  margin: 0rem calc(1rem / 2);
}

.home-banner {
  position: relative;
}
.home-banner__arrow-container {
  position: absolute;
  bottom: 0px;
  width: 100%;
}
.home-banner__arrow-container .section {
  padding: 1rem 0rem;
  min-height: unset;
}
@media (min-width: 768px) {
  .home-banner__arrow-container .section {
    padding: 5rem 0rem;
  }
}
.home-banner__slick-arrows {
  justify-content: flex-start;
}
@media (min-width: 768px) {
  .home-banner__slick-arrows {
    justify-content: flex-end;
  }
}

.home-news__header {
  align-items: flex-end;
  margin-bottom: 1.5rem;
}
.home-news__slick-arrows {
  justify-content: flex-start;
}
@media (min-width: 768px) {
  .home-news__slick-arrows {
    justify-content: flex-end;
  }
}