/*!*********************************************************************************************************************************************************************************************************************************************************************************!*\
  !*** 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/natural/src/scss/page/services.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.
 */

 .banner{
  background-color: #7F7F7F;
 }

 .banner-text{
  color: #FFFFFF;
 }

 .section-divider{
  padding-bottom: calc(65rem/16);
 }

.h3{
  font-weight: 400;
}

.partners-section{
  padding-top: 0rem;
  padding-bottom: calc(86rem/16);
}

.list-partners-image{
  padding-bottom: calc(115rem/16);
}

.partners-heading{
  padding-top: 0rem;
  padding-bottom: calc(110rem/16);
}

.first-idx-logo{
  margin-bottom: calc(34rem/16);
}

.index-partners-list{
  padding-top: 0rem;
}

.h2{
  font-size: calc(36rem/16);
  font-weight: 400;
}

 .news__carousel-title {
  margin-top: 1.5rem;
  margin-bottom: 1.5rem;
}
.news__carousel-title--arrow-column {
  position: relative;
}
.news__carousel-title--arrow-column__arrows {
  position: absolute;
  bottom: 25%;
  right: 0;
}
.news__carousel-title--arrow-column__arrows__prev-arrow, .news__carousel-title--arrow-column__arrows__next-arrow {
  margin-right: 1rem;
}
.news--slick-carousel .slick-slide {
  margin: 0rem 1rem;
}
.news--slick-carousel .slick-list {
  margin: 0rem -1rem;
}

.services-main-content .h5, .services-main-content h3 {
  margin-bottom: 1.5rem;
}

.image-section{
  padding-right: calc(20rem / 16);
}

.text-section{
  padding-left: calc(20rem / 16);
  padding-right: calc(20rem / 16);
}

@media (max-width: 576px) {
  .first-partners-img{
    margin-bottom: calc(24rem / 16);
  }
  .partners-img{
    display: none;
  }
}