@charset "UTF-8";
/* CSS Document */

@media screen and (max-width: 998px) {
    .spotlights .default-theme.wp-posts-carousel .owl-controls .owl-nav .owl-prev { left: 0 !important; opacity: 1 !important; }
    .spotlights .default-theme.wp-posts-carousel .owl-controls .owl-nav .owl-next { right: 0 !important; opacity: 1 !important; }
}

div.add-separator-below article
{
   border-bottom: 2px solid #ccc;
}
#notification-bar
{
    z-index: 99;
}

.fusion-events-single-title-content
{
  position: relative !important;
}
.fusion-megamenu-wrapper .fusion-megamenu-submenu
{
	padding: 0px 0px !important;
}
.fusion-header-v4 .fusion-header {
    /* padding-top: 30px; */
    padding-bottom: 30px;
    transition: none;
}
.fusion-logo img {
    /* margin-top: -75px; */
    width: 250px !important;
}

.blackText .fusion-button-text
{
	color: #000;
}

li
{
  line-height: 1.5em;
}

/* Restore the legacy .side-nav separator lines on the new AWB Vertical Menu.
 * Avada's framework gives any <ul class="side-nav"> a 1px #ededed top border
 * on the list and a 1px #ededed bottom border on each item — the visual
 * "lined-paper" look readers grew up with. The new AWB menu doesn't use the
 * side-nav class, so those framework rules don't apply. Two targeted rules
 * here add the same separators on the AWB menu when it sits inside a Fusion
 * column. Color, padding, active state, font already come from the AWB
 * inline CSS variables (--awb-color, --awb-active-bg, etc.) — we don't fight
 * those.
 *
 * The Fusion column shadow on Layout-Section columns (fusion-column-has-shadow)
 * is intentionally left in place — with the separator lines added, the
 * shadow frames the menu like a card, which reads as intentional design. */
.fusion-layout-column > .fusion-column-wrapper > nav.awb-menu.awb-menu_v-stacked > ul.awb-menu__main-ul {
    border-top: 1px solid #ededed;
    border-right: 1px solid #ededed;
}
.fusion-layout-column > .fusion-column-wrapper > nav.awb-menu.awb-menu_v-stacked > ul.awb-menu__main-ul > .awb-menu__main-li {
    border-bottom: 1px solid #ededed;
}

/* ===========================================================================
 * AWB Vertical Menu rendering fixes — migrated from pvamu-sidenav-migrate.php
 * so the migration plugin can be deactivated without breaking front-end
 * behavior on flipped pages.
 *
 * Three blocks:
 *   1. Auto-expand submenus when the current page is the parent or inside
 *      the active branch — mirrors the legacy side-nav behavior where the
 *      active branch's children were always visible.
 *   2. Convert mega-menu items (configured for horizontal top-nav) into
 *      inline stacked submenus when the menu is rendered vertically inside
 *      a side-nav column.
 *   3. Suppress AWB menus that are embedded inside page content (the ~14
 *      pages with [fusion_menu] baked into post_content). The Layout
 *      Section renders the authoritative menu in the 1/3 column; the
 *      embedded duplicate inside [fusion_tb_content]'s output is hidden.
 *
 * Selector strategy: scope by structural ancestor `.fusion-layout-column`
 * (Avada-stable across versions) instead of AWB's version-specific
 * `awb-menu_column` / `awb-menu_v-stacked` class names which drift across
 * Avada releases.
 * ========================================================================= */

/* Block 1: auto-expand active branch */
.fusion-layout-column nav.awb-menu .current-menu-ancestor > .awb-menu__sub-ul,
.fusion-layout-column nav.awb-menu .current-menu-parent   > .awb-menu__sub-ul,
.fusion-layout-column nav.awb-menu .current-menu-item     > .awb-menu__sub-ul,
.fusion-layout-column nav.awb-menu .current_page_ancestor > .awb-menu__sub-ul,
.fusion-layout-column nav.awb-menu .current_page_parent   > .awb-menu__sub-ul,
.fusion-layout-column nav.awb-menu .current_page_item     > .awb-menu__sub-ul,
.fusion-layout-column nav.awb-menu .current-page-ancestor > .awb-menu__sub-ul,
.fusion-layout-column nav.awb-menu .current-page-parent   > .awb-menu__sub-ul,
.fusion-layout-column nav.awb-menu .current-page-item     > .awb-menu__sub-ul,
.fusion-layout-column nav.awb-menu .awb-menu__sub-ul.is-opened {
    display: block !important;
    visibility: visible !important;
    opacity: 1 !important;
    height: auto !important;
    max-height: none !important;
    overflow: visible !important;
    transform: none !important;
    pointer-events: auto !important;
}

/* Block 2: mega-menu items rendered inline in vertical context.
 * The `fusion-megamenu-*` classes are Avada-stable across versions. */
.fusion-layout-column nav.awb-menu .fusion-megamenu-menu {
    position: relative !important;
}
.fusion-layout-column nav.awb-menu .fusion-megamenu-wrapper {
    position: static !important;
    display: none !important;
    width: 100% !important;
    max-width: 100% !important;
    top: auto !important;
    left: auto !important;
    box-shadow: none !important;
    border: none !important;
    background: transparent !important;
    padding: 0 !important;
    margin: 0 !important;
}
.fusion-layout-column nav.awb-menu .fusion-megamenu-menu.is-open               > .fusion-megamenu-wrapper,
.fusion-layout-column nav.awb-menu .fusion-megamenu-menu.expanded              > .fusion-megamenu-wrapper,
.fusion-layout-column nav.awb-menu .fusion-megamenu-menu.fusion-active-link    > .fusion-megamenu-wrapper,
.fusion-layout-column nav.awb-menu .fusion-megamenu-menu.current-menu-ancestor > .fusion-megamenu-wrapper,
.fusion-layout-column nav.awb-menu .fusion-megamenu-menu.current-menu-parent   > .fusion-megamenu-wrapper,
.fusion-layout-column nav.awb-menu .fusion-megamenu-menu.current-menu-item     > .fusion-megamenu-wrapper,
.fusion-layout-column nav.awb-menu .fusion-megamenu-menu.current_page_ancestor > .fusion-megamenu-wrapper,
.fusion-layout-column nav.awb-menu .fusion-megamenu-menu.current_page_parent   > .fusion-megamenu-wrapper,
.fusion-layout-column nav.awb-menu .fusion-megamenu-menu.current_page_item     > .fusion-megamenu-wrapper,
.fusion-layout-column nav.awb-menu .fusion-megamenu-menu.current-page-ancestor > .fusion-megamenu-wrapper,
.fusion-layout-column nav.awb-menu .fusion-megamenu-menu.current-page-parent   > .fusion-megamenu-wrapper {
    display: block !important;
}
.fusion-layout-column nav.awb-menu .fusion-megamenu-wrapper .fusion-megamenu-holder {
    width: 100% !important;
    max-width: 100% !important;
}
.fusion-layout-column nav.awb-menu .fusion-megamenu-wrapper .row {
    display: block !important;
    width: 100% !important;
    margin: 0 !important;
    padding: 0 !important;
}
.fusion-layout-column nav.awb-menu .fusion-megamenu-wrapper .fusion-megamenu {
    display: block !important;
    width: 100% !important;
    padding: 0 !important;
    margin: 0 !important;
}
.fusion-layout-column nav.awb-menu .fusion-megamenu-wrapper .fusion-megamenu-submenu {
    display: block !important;
    width: 100% !important;
    max-width: 100% !important;
    float: none !important;
    margin: 0 !important;
    padding: 0 !important;
    border: none !important;
}
.fusion-layout-column nav.awb-menu .fusion-megamenu-wrapper .fusion-megamenu-title {
    padding: 8px 0 !important;
    margin: 0 !important;
    font-size: inherit !important;
    font-weight: 600 !important;
    color: inherit !important;
    border: none !important;
}
.fusion-layout-column nav.awb-menu .fusion-megamenu-wrapper .sub-menu.deep-level {
    display: block !important;
    padding-left: 12px !important;
}

/* Block 3: hide AWB menus embedded inside page content (the ~14 pages
 * with [fusion_menu] baked into post_content). The Layout Section's
 * 1/3 column menu is authoritative; the embedded duplicate inside
 * [fusion_tb_content]'s `.fusion-content-tb` wrapper is suppressed. */
.fusion-content-tb nav.awb-menu {
    display: none !important;
}

/* ===========================================================================
 * Title-bar layout: H1 lives in the content, breadcrumb lives in the bar.
 *
 * The `avada_page_title_bar_contents` filter in functions.php clears
 * $title before Avada renders the bar, so the parent template's
 * `<h1 ...>` line never fires. The surrounding `.fusion-page-title-captions`
 * wrapper IS still emitted by the parent template (whitespace-only),
 * so `:empty` won't catch it — hide unconditionally instead. The
 * breadcrumb keeps its existing position; only the H1 is removed.
 * ========================================================================= */
.fusion-page-title-captions {
    display: none !important;
}

/* Center the injected content-area H1 (Phase 10 prepends this on
 * migrated pages with class `pvsdm-content-title`). Editors authored
 * their pre-migration manual H1s with center alignment; matching that
 * keeps the visual consistent across migrated and non-migrated pages. */
.pvsdm-content-title {
    text-align: center;
}