/*!*********************************************************************************************************************************************************************************************************************************************************************!*\
  !*** 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/blog.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.
 */
.blog-posts {
  --bs-gutter-x: 2.5rem;
  --bs-gutter-y: 2.5rem;
}
.blog-posts > * {
  flex: 0 0 auto;
  width: 50%;
}
@media (min-width: 768px) {
  .blog-posts > * {
    flex: 0 0 auto;
    width: 33.33333333%;
  }
}
.blog-posts .card-thumbnail__with-image .card-img-contained {
  aspect-ratio: 352/213;
}

.blog-category {
  background-color: #FFFFFF;
  border-radius: 50rem;
  padding-left: 1.75rem;
  padding-right: 1.75rem;
}
.blog-category__nav {
  --bs-nav-link-color: #BDBBB4;
  --bs-nav-link-hover-color: #808874;
  --bs-nav-link-active-color: #808874;
  --bs-nav-link-padding-y: 1.0625rem;
  --bs-nav-link-padding-x: 1.125rem;
}
.blog-category__nav .nav-link.active {
  color: var(--bs-nav-link-active-color);
}

.blog-featured {
  --bs-gutter-x: 2.5rem;
  --bs-gutter-y: 2.5rem;
}
.blog-featured > * {
  flex: 0 0 auto;
  width: 100%;
}
@media (min-width: 768px) {
  .blog-featured > * {
    flex: 0 0 auto;
    width: 50%;
  }
}
.blog-featured a {
  text-decoration: none;
  --bs-link-color-rgb: var(--bs-body-color-rgb);
  --bs-link-hover-color-rgb: var(--bs-body-color-rgb);
}
.blog-featured__image img {
  width: 100%;
  height: auto;
}
.blog-featured__detail__category {
  color: #BDBBB4;
}
.blog-featured__detail__date {
  margin-bottom: 1.5rem;
  color: #BDBBB4;
}

.blog-posts {
  margin-bottom: 3rem;
}