/**
 * Helper variables for media queries. Makes sure we use standard queries and not make up our own
 */
@font-face {
  font-family: "Open Sans";
  font-display: swap;
  src: url("../styles/fonts/open-sans-regular.woff") format("woff"), url(".woff") format("woff");
  font-style: normal;
  font-weight: normal;
}
@font-face {
  font-family: "Open Sans";
  font-display: swap;
  src: url("../styles/fonts/open-sans-semibold.woff") format("woff"), url(".woff") format("woff");
  font-style: normal;
  font-weight: 600;
}
@font-face {
  font-family: "Open Sans";
  font-display: swap;
  src: url("../styles/fonts/open-sans-bold700.woff") format("woff"), url(".woff") format("woff");
  font-style: normal;
  font-weight: bold;
}
html {
  font-size: 16px;
}

/**
 * As of 2019-12-10, W3C has put forward a standard for the css rule inset-inline-start
 * (which should be used instead of right/left to support right-to-left languages).
 * However, as it's not supported yet in Safari, and is still in experimental mode for Chrome,
 * we're stuck with this mixin for now. See also mixin, inset-inline-end.
 */
/**
 * As of 2019-12-10, W3C has put forward a standard for the css rule inset-inline-start
 * (which should be used instead of right/left to support right-to-left languages).
 * However, as it's not supported yet in Safari, and is still in experimental mode for Chrome,
 * we're stuck with this mixin for now. See also mixin, inset-inline-start.
 */
/**
 * Most browsers do not yet support float with relative values (inline-start).
 * Therefore, we are forced to rely upon our own mixin, if we are to support right-to-left languages.
 */
/**
 * Most browsers do not yet support float with relative values (inline-end).
 * Therefore, we are forced to rely upon our own mixin, if we are to support right-to-left languages.
 */
/**
 * Most browsers do not yet support clear with relative values (inline-start).
 * Therefore, we are forced to rely upon our own mixin, if we are to support right-to-left languages.
 */
/**
 * Most browsers do not yet support clear with relative values (inline-end).
 * Therefore, we are forced to rely upon our own mixin, if we are to support right-to-left languages.
 */
/**
 * Most browsers do not yet support border with relative values.
 * Therefore, we are forced to rely upon our own mixin, if we are to support right-to-left languages.
 * This one replaces border-top-right-radius (in LTR).
 */
/**
 * Most browsers do not yet support border with relative values.
 * Therefore, we are forced to rely upon our own mixin, if we are to support right-to-left languages.
 * This one replaces border-bottom-right-radius (in LTR).
 */
/**
 * Most browsers do not yet support border with relative values.
 * Therefore, we are forced to rely upon our own mixin, if we are to support right-to-left languages.
 * This one replaces border-bottom-left-radius (in LTR).
 */
/**
 * Most browsers do not yet support border with relative values.
 * Therefore, we are forced to rely upon our own mixin, if we are to support right-to-left languages.
 * This one replaces border-top-left-radius (in LTR).
 */
/**
 * Wrap _reflexive-property with support for both ltr and rtl cases.
 * @param $ltr-property the property you'd expect in ltr
 * @param $rtl-property the property you'd expect in rtl
 * @param $left-value the value that the property should have when ltr
 * @param $right-value the value that the property should have when rtl
 */
/**
 * Despite Angular scoping, and bug causing nested host-context declarations to fail,
 * select elements that are preceeded by an ancestor which sets dir
 * @param $dir the direction to look for
 * @param $property the property to set the value for
 * @param $value the value that the property should have
 * Due to a bug in Angular related to the usage of host-context with or (,)
 * we use two cases of @at-root instead.
 */
/**
 * Set sticky position
 */
/**
 * As of 2019-12-10, W3C has put forward a standard for the css rule inset-inline-start
 * (which should be used instead of right/left to support right-to-left languages).
 * However, as it's not supported yet in Safari, and is still in experimental mode for Chrome,
 * we're stuck with this mixin for now. See also mixin, inset-inline-end.
 */
/**
 * As of 2019-12-10, W3C has put forward a standard for the css rule inset-inline-start
 * (which should be used instead of right/left to support right-to-left languages).
 * However, as it's not supported yet in Safari, and is still in experimental mode for Chrome,
 * we're stuck with this mixin for now. See also mixin, inset-inline-start.
 */
/**
 * Most browsers do not yet support float with relative values (inline-start).
 * Therefore, we are forced to rely upon our own mixin, if we are to support right-to-left languages.
 */
/**
 * Most browsers do not yet support float with relative values (inline-end).
 * Therefore, we are forced to rely upon our own mixin, if we are to support right-to-left languages.
 */
/**
 * Most browsers do not yet support clear with relative values (inline-start).
 * Therefore, we are forced to rely upon our own mixin, if we are to support right-to-left languages.
 */
/**
 * Most browsers do not yet support clear with relative values (inline-end).
 * Therefore, we are forced to rely upon our own mixin, if we are to support right-to-left languages.
 */
/**
 * Most browsers do not yet support border with relative values.
 * Therefore, we are forced to rely upon our own mixin, if we are to support right-to-left languages.
 * This one replaces border-top-right-radius (in LTR).
 */
/**
 * Most browsers do not yet support border with relative values.
 * Therefore, we are forced to rely upon our own mixin, if we are to support right-to-left languages.
 * This one replaces border-bottom-right-radius (in LTR).
 */
/**
 * Most browsers do not yet support border with relative values.
 * Therefore, we are forced to rely upon our own mixin, if we are to support right-to-left languages.
 * This one replaces border-bottom-left-radius (in LTR).
 */
/**
 * Most browsers do not yet support border with relative values.
 * Therefore, we are forced to rely upon our own mixin, if we are to support right-to-left languages.
 * This one replaces border-top-left-radius (in LTR).
 */
/**
 * Wrap _reflexive-property with support for both ltr and rtl cases.
 * @param $ltr-property the property you'd expect in ltr
 * @param $rtl-property the property you'd expect in rtl
 * @param $left-value the value that the property should have when ltr
 * @param $right-value the value that the property should have when rtl
 */
/**
 * Despite Angular scoping, and bug causing nested host-context declarations to fail,
 * select elements that are preceeded by an ancestor which sets dir
 * @param $dir the direction to look for
 * @param $property the property to set the value for
 * @param $value the value that the property should have
 * Due to a bug in Angular related to the usage of host-context with or (,)
 * we use two cases of @at-root instead.
 */
.page-section {
  margin-top: 2rem;
  width: 100%;
  display: -webkit-flex;
  display: -moz-box;
  display: -ms-flexbox;
  display: flex;
  justify-content: center;
  -webkit-flex-wrap: wrap;
  -ms-flex-wrap: wrap;
  flex-wrap: wrap;
}
@media only screen and (max-width: 599px) {
  .page-section {
    -webkit-flex-direction: column;
    -ms-flex-direction: column;
    flex-direction: column;
    align-items: center;
  }
}

.page-section:not(:last-child) {
  margin-bottom: 3rem;
}

.element {
  display: -webkit-flex;
  display: -moz-box;
  display: -ms-flexbox;
  display: flex;
}
@media only screen and (max-width: 599px) {
  .element {
    width: 100%;
    justify-content: center;
  }
}

.nav-link {
  text-decoration: none;
  display: -webkit-flex;
  display: -moz-box;
  display: -ms-flexbox;
  display: flex;
}
@media only screen and (max-width: 599px) {
  .nav-link {
    width: 100%;
    justify-content: center;
    margin: 0 2rem;
  }
}

.element-container {
  text-align: center;
  padding: 1rem;
  max-width: 16.625rem;
  width: 16.625rem;
  display: -webkit-flex;
  display: -moz-box;
  display: -ms-flexbox;
  display: flex;
  -webkit-flex-direction: column;
  -ms-flex-direction: column;
  flex-direction: column;
}
@media only screen and (max-width: 599px) {
  .element-container {
    max-width: none;
    padding: 0;
    margin: 1rem 0;
    width: 100%;
  }
}

.element-container:hover .element-nav {
  text-decoration: underline;
}

.element-top {
  background: #F4F2F4;
  color: black;
  padding-left: 1rem;
  padding-right: 1rem;
  padding-top: 2rem;
  padding-bottom: 2rem;
  height: 100%;
}

.element-header {
  font-weight: bold;
  font-size: 1rem;
  line-height: 1.5rem;
  padding-left: 3rem;
  padding-right: 3rem;
  margin-bottom: 1rem;
}

.element-content {
  font-weight: normal;
  font-size: 0.875rem;
  line-height: 1.3125rem;
  padding-left: 0.5rem;
  padding-right: 0.5rem;
}
@media only screen and (max-width: 599px) {
  .element-content {
    padding-left: 3rem;
    padding-right: 3rem;
  }
}

.element-bot {
  background: #0087C1;
  color: white;
  padding: 0.5rem 0.5rem 0.5rem 0.5rem;
  border-radius: 0px 0px 0.5rem 0.5rem;
}

.element-bot:hover {
  background: #006996;
}

.element-bot-add-on {
  background: #FFAA35;
  color: white;
  padding: 0.5rem 0.5rem 0.5rem 0.5rem;
  border-radius: 0px 0px 0.5rem 0.5rem;
}

.element-bot-add-on:hover {
  background: #E79C36;
}

.element-bot-docs {
  background: #00D89E;
  color: white;
  padding: 0.5rem 0.5rem 0.5rem 0.5rem;
  border-radius: 0px 0px 0.5rem 0.5rem;
}

.element-bot-docs:hover {
  background: #0DC191;
}

.element-nav {
  font-weight: bold;
  font-size: 1rem;
  line-height: 1.5rem;
}

/*# sourceMappingURL=landing-page.css.map */