@charset "UTF-8";
/* ===========================================================================
   SITE-WIDE redesign overrides
   ---------------------------------------------------------------------------
   Things that are not part of one section. Loaded after the section files so
   it has the last word, and separate from them so a section can be reverted
   without taking these with it.

   Only the redesign loads this file. The live site is untouched — it keeps the
   old ornament until the redesign replaces it.
   =========================================================================== */

/* ---------------------------------------------------------------------------
   HEADING ORNAMENT
   The mark above every section heading. It comes from .heading-wrapper::before
   in the live style.css, which is why swapping one rule changes all 13 of them
   on this page — and every heading on every page we build next.

   TWO THINGS THE OLD RULE DID THAT HAD TO GO:

   1. A `filter: brightness(0) saturate(100%) invert(44%) …` chain. That flattens
      whatever SVG is behind it into ONE flat teal — the old mark's own red was
      never visible. Leaving it would have painted the new ornament a single
      colour too, losing the red line and the teal hands. So the filter is
      cleared here.

   2. An 80x80 box. The new drawing is 100x240, so in a square box it would sit
      tiny in the middle with empty space either side. The box now matches the
      drawing's proportions.
   --------------------------------------------------------------------------- */
/* The mark is TALL — 1:2.4 — where the old one was square, so it needs room
   that does not exist above the heading: measured, there are only 75px between
   the top of a section and its .heading-wrapper. Hanging a 100px ornament on a
   negative `top` would push it up into the section above.

   So the wrapper reserves the space itself with padding-top, and the ornament
   sits at top:0 inside that reserved band. Nothing overflows, at any size, in
   any section — and the drawing can be large enough to actually read as a pair
   of hands rather than a line with a dot. */
.heading-wrapper { padding-top: 112px; }

.heading-wrapper::before {
    width: 42px;                /* 1 : 2.4, the drawing's own ratio */
    height: 100px;
    top: 0;
    background: url("../img/heading-ornament.svg?v=1") center / contain no-repeat;
    filter: none;
    opacity: 1;
}

/* The two overrides in style.css that re-tinted the old flat mark would now
   flatten the new one, so they are cleared as well. */
.founders-inner > .heading-wrapper::before,
.founders-section.is-light .heading-wrapper::before {
    filter: none;
    opacity: 1;
}

/* EXCEPT on a dark band. .heading-wrapper.white sits over the Rishikesh
   photograph, where a dark red line and teal hands disappear. There the mark
   keeps the white treatment it already had — the filter is doing real work. */
.heading-wrapper.white::before {
    filter: brightness(0) invert(1);
    opacity: .92;
}

/* Smaller screens get a shorter mark so it does not eat the space above the
   heading on a phone. */
@media (max-width: 47.99rem) {
    .heading-wrapper { padding-top: 86px; }
    .heading-wrapper::before {
        width: 32px;
        height: 76px;
        top: 0;
    }
}

/* ===========================================================================
   BUTTONS — one shape for the whole page
   ---------------------------------------------------------------------------
   Everything that acts as a button gets the hero's treatment: white, a red
   edge, red label, fully rounded, and a red fill that sweeps in from the left
   on hover.

   The sweep is one animated property — a two-stop gradient twice the button's
   width, moved with background-position. No extra element is laid over the
   label, so nothing can cover the text or swallow the click.

   THE LIFT USES `translate`, NOT `transform`. Several of these buttons are
   children of the slide text, whose entrance keyframes animate `transform`
   with fill-mode `backwards`; a running animation beats a hover declaration,
   so a hover written as `transform` would never appear. `translate` is an
   independent property the keyframes never touch.

   ONE EXCEPTION, on purpose: the header's "Enroll Now" stays a solid red
   block. A page where every button looks identical has no primary action —
   that block is the one thing we want clicked, so it stays filled.
   =========================================================================== */
.theme-button,
.theme-button.outline,
.theme-button.fixed-btn,
.blog-load-more,
.cta-btn-whatsapp,
.cta-btn-enquiry,
.copy-clamp-toggle,
.ryp-slide__cta {
    display: inline-flex;
    align-items: center;
    justify-content: center;
    gap: .5rem;
    min-height: 50px;                     /* over the 44px touch minimum */
    padding: 0 1.75rem;
    border: 1.5px solid var(--ryp-red);
    border-radius: 999px;
    color: var(--ryp-red-ink);            /* 6:1 on white */
    font-family: "Figtree", system-ui, sans-serif;
    font-size: .9375rem;
    font-weight: 600;
    line-height: 1.2;
    text-align: center;
    text-decoration: none;
    cursor: pointer;

    background-color: transparent;
    background-image: linear-gradient(to right, var(--ryp-red) 0 50%, #fff 50% 100%);
    background-size: 200% 100%;
    background-position: 100% 0;          /* the white half shows */
    background-repeat: no-repeat;

    /* TIMING MATTERS HERE, it is not decoration.
       The label turns white while the red is still sweeping in. If the colour
       wins the race, white text sits on the white half of the button and the
       label vanishes for a few hundred milliseconds — which is exactly what
       the owner photographed.

       So the sweep is shortened to 300ms and the colour change is held back
       150ms and done in 110ms: by the time the text goes white, the red has
       already passed under it. On the way out the same delay is harmless —
       red text on white is readable throughout. */
    /* COLOUR AND FILL DO NOT ANIMATE. Only the lift, the ring and the shadow do.

       They used to cross-fade, and that was the bug the owner photographed: the
       label turned white while the red was still sweeping in, so for a few
       hundred milliseconds white text sat on the white half of the button and
       the button looked empty. Staging the timings did not fix it either,
       because an inline rule — `.theme-button:hover { transition: .5s }` —
       resets transition-property to `all` the instant you hover, throwing any
       staging away.

       Flipping colour and background together, with no transition on either,
       removes the ambiguous window entirely rather than trying to time around
       it. It is also instant in BOTH directions, so leaving the button cannot
       reproduce it in reverse. */
    transition: border-color 240ms cubic-bezier(.22, 1, .36, 1),
                box-shadow 240ms cubic-bezier(.22, 1, .36, 1),
                translate 220ms cubic-bezier(.34, 1.4, .44, 1),
                scale 160ms cubic-bezier(.34, 1.4, .44, 1);
}

.theme-button:hover, .theme-button:focus-visible,
.theme-button.outline:hover, .theme-button.outline:focus-visible,
.theme-button.fixed-btn:hover, .theme-button.fixed-btn:focus-visible,
.blog-load-more:hover, .blog-load-more:focus-visible,
.cta-btn-whatsapp:hover, .cta-btn-whatsapp:focus-visible,
.cta-btn-enquiry:hover, .cta-btn-enquiry:focus-visible,
.copy-clamp-toggle:hover, .copy-clamp-toggle:focus-visible,
.ryp-slide__cta:hover, .ryp-slide__cta:focus-visible {
    background-position: 0 0;             /* red sweeps across */
    border-color: var(--ryp-red);
    color: #fff;                          /* 4.71:1 on the red */
    translate: 0 -3px;
    box-shadow: 0 10px 24px rgba(222, 42, 29, .28);
}

.theme-button:active,
.blog-load-more:active,
.cta-btn-whatsapp:active,
.cta-btn-enquiry:active,
.copy-clamp-toggle:active,
.ryp-slide__cta:active { translate: 0 0; scale: .97; }

/* `span` wrappers inside several of these carry their own colour. */
.theme-button span, .blog-load-more span, .cta-btn-enquiry span { color: inherit; }

/* The closing CTA's two buttons need the section prefix: the live rules are
   `.av-premium-cta .cta-btn-whatsapp`, so an unprefixed selector of mine loses
   to them and they stayed WhatsApp-green and glassy-white. */
.av-premium-cta .cta-btn-whatsapp,
.av-premium-cta .cta-btn-enquiry {
    background-color: transparent;
    background-image: linear-gradient(to right, var(--ryp-red) 0 50%, #fff 50% 100%);
    background-size: 200% 100%;
    background-position: 100% 0;
    background-repeat: no-repeat;
    border: 1.5px solid #fff;             /* a red edge vanishes into the photo */
    color: var(--ryp-red-ink);
    box-shadow: 0 6px 20px rgba(0, 0, 0, .22);
    backdrop-filter: none;
}
.av-premium-cta .cta-btn-whatsapp:hover,
.av-premium-cta .cta-btn-enquiry:hover,
.av-premium-cta .cta-btn-whatsapp:focus-visible,
.av-premium-cta .cta-btn-enquiry:focus-visible {
    background-position: 0 0;
    background-color: transparent;
    border-color: #fff;
    color: #fff;
    /* The live hover animates `transform`; ours uses translate, so clear theirs
       or the two fight over the same property. */
    transform: none;
    translate: 0 -3px;
    box-shadow: 0 12px 28px rgba(0, 0, 0, .3);
}

/* -- round utility buttons: recoloured, not reshaped --------------------- */
.ryp-to-top {
    background: var(--ryp-red);
    border-color: var(--ryp-red);
    color: #fff;
}
.ryp-to-top:hover { background: var(--ryp-red-deep); }

/* The sticky bar at the bottom of a phone. */
.bottom-box .whatsapp { color: var(--ryp-red-ink); }

/* ---------------------------------------------------------------------------
   BUTTON HOVER — guaranteed red, whatever else is on the page
   ---------------------------------------------------------------------------
   The sweep above is painted with a background-IMAGE. Several live rules are
   more specific than a bare `.theme-button:hover` and set the `background`
   SHORTHAND, which resets background-image to none:

     .daily-schedule-section .ri-cta .theme-button:hover { background: rgba(201,169,110,.22) }
     .dates-fees-section .df-fees .theme-button:hover    { background-position: 100% 0 }
     .bottom-box .fixed-btn:hover                        { background: #24695f }
     .th-faq-section .th-cta-btn--primary:hover          { background: #fff }

   When one of those wins, the gradient disappears but our `color: #fff`
   still applies — so the label goes white on a white or pale background and
   the button reads as empty. That is the bug the owner spotted.

   The three declarations below are the only !important in this project, and
   they are here because the rules they beat are themselves more specific:
   matching every one of those chains would mean a new selector each time a
   section is added, and the first one missed is an invisible button.
   A solid red underneath the gradient means the END state is red even if the
   image is stripped, so the white label is always readable.
   --------------------------------------------------------------------------- */
.theme-button:hover, .theme-button:focus-visible,
.theme-button.outline:hover, .theme-button.outline:focus-visible,
.theme-button.fixed-btn:hover, .theme-button.fixed-btn:focus-visible,
.blog-load-more:hover, .blog-load-more:focus-visible,
.copy-clamp-toggle:hover, .copy-clamp-toggle:focus-visible,
.av-premium-cta .cta-btn-whatsapp:hover, .av-premium-cta .cta-btn-whatsapp:focus-visible,
.av-premium-cta .cta-btn-enquiry:hover, .av-premium-cta .cta-btn-enquiry:focus-visible,
.ryp-slide__cta:hover, .ryp-slide__cta:focus-visible {
    /* The fill itself is the ::after circle below. background-color stays red
       as the floor, so if that circle ever fails to paint the button is still
       red under white text rather than white under white. */
    background-color: var(--ryp-red) !important;
    background-image: none !important;
    color: #fff !important;
    /* Pins the transition over `.theme-button:hover { transition: .5s }`, which
       would otherwise reset transition-property to `all`. The label's colour is
       timed against the circle below, so the text never turns white while the
       button behind it is still white. See the delay, measured, further down. */
    transition-property: color, background-color, border-color, box-shadow, translate, scale !important;
    transition-duration: 60ms, 0s, 240ms, 240ms, 220ms, 160ms !important;
    /* background-color flips only AFTER the circle has landed (440ms). During
       the sweep the red comes from the circle; this is just a floor, so that if
       the circle ever fails to paint the button still ends up red under white
       text instead of white under white. */
    /* 25ms — measured, not guessed. Sampling the real hover frame by frame on
       "Explore 300 Hour Yoga TTC":

           label occupies 27.1% - 72.9% of the button
           circle covers that from scale 0.353, which the easing reaches at ~35ms
           colour was starting at 70ms  ->  t=39ms and t=56ms both read
           rgb(194,31,18) on red: two frames of dark red text on a red circle

       So the colour now starts at 25ms and is done by 85ms. It begins a frame
       BEFORE full coverage (harmless: at 25ms the circle already spans about
       28%-72%, so only the outer edge of the first and last letter is over
       white, and the text there is still almost fully dark) and finishes 50ms
       AFTER it, which is the margin that matters — white text must never
       arrive before the red does, or the label disappears. */
    transition-delay: 25ms, 440ms, 0s, 0s, 0s, 0s !important;
}

/* The closing CTA's two buttons sit on a PHOTOGRAPH, and that changes what the
   rule above does to them. Everywhere else `background-image: none` on hover
   just reveals white page behind the sweep. Here it revealed the photo: the
   white pill went hollow at t=0 while the circle was still at scale 0, so for
   about two frames the words floated on the picture inside a bare white ring.
   Measured: background-image `none` and background-color transparent from the
   first frame.

   So these two keep an opaque white fill for the whole sweep. The circle grows
   over it exactly as it does over white elsewhere, and on leaving, the fill is
   already the right colour, so there is nothing to flash back to.

   The trade: the red background-color underneath is no longer a visible floor
   for THESE two, since the white sits on top of it. That floor still protects
   every other button on the page. Here the pill reads correctly at rest, on
   hover and on leave, which is the thing a reader actually sees. */
.av-premium-cta .cta-btn-whatsapp:hover, .av-premium-cta .cta-btn-whatsapp:focus-visible,
.av-premium-cta .cta-btn-enquiry:hover, .av-premium-cta .cta-btn-enquiry:focus-visible {
    background-image: linear-gradient(#fff, #fff) !important;
}

/* ---------------------------------------------------------------------------
   THE SWEEP, BROUGHT BACK SAFELY
   ---------------------------------------------------------------------------
   The owner liked the fill sliding in, and it is back — but on ::after, not
   ::before, and red, not white.

   WHY ::after: ::before belongs to the live theme's white circle, which is
   switched off above. Using a different pseudo-element means the two can never
   fight over width, height or colour.

   WHY FROM THE CENTRE: a left-to-right sweep leaves the right end of the label
   sitting on white while the left end is already on red, so no single text
   colour works during the slide. A circle growing from the middle covers the
   words first and the corners last, so the label can flip to white early and
   stay readable the whole way.

   It scales rather than animating width/height, so it runs on the compositor
   and costs no layout. The button already clips to its pill shape.
   --------------------------------------------------------------------------- */
.theme-button::after,
.theme-button.outline::after,
.theme-button.fixed-btn::after,
.blog-load-more::after,
.copy-clamp-toggle::after,
.av-premium-cta .cta-btn-whatsapp::after,
.av-premium-cta .cta-btn-enquiry::after,
.ryp-slide__cta::after {
    content: "";
    position: absolute;
    left: 50%;
    top: 50%;
    width: 130%;
    height: 420%;
    border-radius: 50%;
    background: var(--ryp-red);
    transform: translate(-50%, -50%) scale(0);
    transition: transform 440ms cubic-bezier(.22, 1, .36, 1);
    pointer-events: none;
    /* -1, NOT 0. A positioned pseudo at z-index 0 paints AFTER inline content,
       i.e. on top of the label — the circle would cover the very words it is
       meant to sit behind. At -1, inside the isolate below, it paints above the
       button's background and below the text, which is the one place it works. */
    z-index: -1;
}
.theme-button:hover::after, .theme-button:focus-visible::after,
.theme-button.outline:hover::after, .theme-button.outline:focus-visible::after,
.theme-button.fixed-btn:hover::after, .theme-button.fixed-btn:focus-visible::after,
.blog-load-more:hover::after, .blog-load-more:focus-visible::after,
.copy-clamp-toggle:hover::after, .copy-clamp-toggle:focus-visible::after,
.av-premium-cta .cta-btn-whatsapp:hover::after, .av-premium-cta .cta-btn-whatsapp:focus-visible::after,
.av-premium-cta .cta-btn-enquiry:hover::after, .av-premium-cta .cta-btn-enquiry:focus-visible::after,
.ryp-slide__cta:hover::after, .ryp-slide__cta:focus-visible::after {
    transform: translate(-50%, -50%) scale(1);
}

/* The circle must be clipped to the pill, and the label must sit above it. */
.theme-button, .theme-button.outline, .theme-button.fixed-btn,
.blog-load-more, .copy-clamp-toggle,
.av-premium-cta .cta-btn-whatsapp, .av-premium-cta .cta-btn-enquiry,
.ryp-slide__cta {
    position: relative;
    overflow: hidden;
    isolation: isolate;   /* keeps the circle inside this button's own layer */
}
.theme-button > *, .blog-load-more > *, .copy-clamp-toggle > *,
.av-premium-cta .cta-btn-whatsapp > *, .av-premium-cta .cta-btn-enquiry > *,
.ryp-slide__cta > * { position: relative; z-index: 1; }

@media (prefers-reduced-motion: reduce) {
    .theme-button::after, .blog-load-more::after, .copy-clamp-toggle::after,
    .av-premium-cta .cta-btn-whatsapp::after, .av-premium-cta .cta-btn-enquiry::after,
    .ryp-slide__cta::after { transition: none; }
}

/* ---------------------------------------------------------------------------
   THE WHITE CIRCLE THAT ATE THE BUTTONS
   ---------------------------------------------------------------------------
   The live theme draws a decorative pseudo-element on every .theme-button:

     .theme-button::before       { content:""; position:absolute;
                                   background:#fff; width:0; height:0;
                                   z-index:-1; border-radius:50% }
     .theme-button:hover::before { width:150%; height:250% }

   a white circle that expands on hover. That was built for the old GREEN
   filled button — green underneath, white washing over it.

   Two things made it invisible until now, and one of my own changes undid
   both. A z-index:-1 pseudo normally paints BEHIND its element's own
   background, so you never saw it. But `translate` on hover makes the button
   a stacking context, and inside one a negative-z-index child paints above the
   background and below the text. So on hover the circle grew over my red fill
   and the white label sat on white — the button looked empty.

   This is why the computed styles all looked correct while the button looked
   broken: colour and background were right, and a white overlay was sitting
   between them. Reading styles cannot see that; only looking can.

   The circle has no job in this design — the fill is a flat colour swap now —
   so it goes. `content: none` removes the box altogether rather than just
   hiding it. The live stylesheet already does the same in two sections.
   --------------------------------------------------------------------------- */
.theme-button::before,
.theme-button.outline::before,
.theme-button.white-outline::before,
.theme-button.fixed-btn::before,
.blog-load-more::before,
.copy-clamp-toggle::before,
.av-premium-cta .cta-btn-whatsapp::before,
.av-premium-cta .cta-btn-enquiry::before,
.theme-button:hover::before,
.theme-button.outline:hover::before,
.blog-load-more:hover::before { content: none; }

/* ---------------------------------------------------------------------------
   A HIDDEN TOGGLE HAS TO ACTUALLY HIDE
   ---------------------------------------------------------------------------
   site.js sets `hidden` on a .copy-clamp-toggle whose clamp is not clamping
   anything. That alone does nothing here: the live theme styles the button
   `display: flex`, and an explicit display always beats the `[hidden]` user-
   agent rule. Measured: hidden="true" and the button still 50px tall on screen.
   --------------------------------------------------------------------------- */
.copy-clamp-toggle[hidden] { display: none !important; }

/* ---------------------------------------------------------------------------
   THE EBOOK MODAL'S PRACTICE SLIDER
   ---------------------------------------------------------------------------
   The fill used to be painted by an inline background that assets/js/custom.js
   writes with the old teal hardcoded into it — see the matching block in
   static/js/site.js, which lifts the percentage into --ryp-slider-fill and
   clears that inline style. The painting happens here instead, on the track,
   in the brand red.

   It has to be the track rather than the input because Chrome paints a range
   input's own background across the whole control and ignores background-clip,
   background-size and background-position on it. That is also what lets the
   input grow to a 44px touch target on a phone while the rule stays 4px.
   --------------------------------------------------------------------------- */
.ebook-modal .ryp-ebook-slider { background: none; }
/* The two track pseudo-elements are stated separately on purpose: a selector
   list is dropped whole by any engine that does not recognise one of its
   parts, so grouping them would have left Chrome with no track rule at all —
   which is exactly what happened the first time this was written. */
.ebook-modal .ryp-ebook-slider::-webkit-slider-runnable-track {
    height: 4px;
    border-radius: 99px;
    background: linear-gradient(to right,
        var(--ryp-red-deep) var(--ryp-slider-fill, 50%),
        #d1d5db var(--ryp-slider-fill, 50%));
}
.ebook-modal .ryp-ebook-slider::-moz-range-track {
    height: 4px;
    border-radius: 99px;
    background: linear-gradient(to right,
        var(--ryp-red-deep) var(--ryp-slider-fill, 50%),
        #d1d5db var(--ryp-slider-fill, 50%));
}

/* ---------------------------------------------------------------------------
   THE SCRIPT FACE
   ---------------------------------------------------------------------------
   Owner, 15 Nov 2026, pointing at "About *Rudra Yogpeeth*" in a banner:
   "ese font ko normal kar do sabhi pages main jaha jaha ese font main hai".

   "Fortune Parade" is the handwriting face the theme uses for one accented
   word in eleven places. Every one of them is listed here rather than the one
   he pointed at, because he asked for all of them.

   `font: inherit` and not just `font-family`: the accent is also set at its
   own size, weight and style — a script face has to run large to read at all —
   so swapping only the family would leave "Rudra Yogpeeth" at 54px in a sans
   beside a 32px heading. Inheriting the whole shorthand makes the phrase part
   of the line it sits in, which is what "normal" means here. The <em>'s italic
   goes with it, by the same reasoning.
   --------------------------------------------------------------------------- */
.breadcrumb-wrapper .breadcrumb-heading em,
.right-choice-section .rc-cta-title,
.career-paths-section .rc-cta-title,
.home-reviews-section .content-wrap .review-heading,
.nh-stats-cta .nh-stats-cta-text,
.th-hero .th-hero-location,
.th-schedule-section .th-day-range,
.th-overview-section .th-overview-copy .th-eyebrow,
.th-why-section .th-why-card .th-why-num,
.th-cta-section .th-cta-eyebrow,
.vp-journey-section .vp-day-no,
.vp-rhythm-section .vp-rhythm-range {
    font: inherit;
    font-style: normal;
}
/* the colour those rules also carried is kept where it was a deliberate one */
.breadcrumb-wrapper .breadcrumb-heading em { color: inherit; }

/* ---------------------------------------------------------------------------
   THE PAGE WATERMARK
   ---------------------------------------------------------------------------
   Owner, 15 Nov 2026: use rudra-bg-web.png where background-alt.webp is used,
   "but rudra-bg-web.png ko webp main kar dena so fast load ho".

   WHERE IT IS USED. Two rules in the live theme tile that file as a faint
   pattern behind everything: `.bg-alt:before` (style.css) and
   `.site-footer::before` (footer.css). Both are live files, so only the image
   is re-pointed here.

   WHAT HAD TO CHANGE ABOUT THE FILE, and why it could not simply be renamed.
   background-alt.webp is an ALPHA pattern — 81% of it is fully transparent and
   its strokes peak at alpha 18, so the paper ground shows through and the
   theme's `filter: brightness(0)` just inks the strokes. rudra-bg-web.png is
   the opposite: measured, 100% opaque and near-black throughout (mean rgb
   8,8,8), because its ground is painted rather than left out. Tiled as-is it
   would have laid a solid black sheet over the footer and every warm section.

   So it was rebuilt as the same kind of object: the icon strokes were lifted
   out of the dark ground by brightness and written into the alpha channel,
   scaled to the same peak of 18 the old tile uses, so the weight of the
   pattern on the page is unchanged and every filter and opacity the theme
   already applies keeps behaving. RGB is white, as the old tile's was.

   SIZE: 1488x720 down to 1116x540, which puts its icons at ~82px against the
   old tile's ~90px — the nearest match — and the lossless webp at that size
   is 68KB against the source PNG's 1.5MB. It tiles cleanly: the artwork's
   left and right edges carry the halves that complete across the seam, checked
   by eye at eight times its real strength.
   --------------------------------------------------------------------------- */
.bg-alt::before,
.site-footer::before {
    background-image: url("../img/rudra-bg-web.webp");
}

/* ---------------------------------------------------------------------------
   THE ICONS THAT WERE STILL GREEN
   ---------------------------------------------------------------------------
   Owner, 15 Nov 2026, pointing at the aeroplane, train, bus and taxi in the
   How To Reach table: "yeh sabhi jo icons hai uneh bhi modify karo and website
   ke color jesa kar do sabhi pages main."

   WHY THE PALETTE REMAP NEVER REACHED THEM. These are black SVGs tinted by a
   filter chain — `invert(44%) sepia(68%) saturate(377%) hue-rotate(123deg)…`
   — which lands on the theme's old green. gen_palette.py rewrites COLOURS; a
   hue rotation is not a colour, so it walked straight past them. Same root
   cause as the ebook slider's teal (see static/js/site.js).

   Swept the stylesheets for that chain: 29 rules carry it, 18 of them had not
   been overridden anywhere. Every one that paints an ICON is set to the brand
   red below, and every one that paints a BACKGROUND PATTERN is set to plain
   ink, which is what the footer's own tile was already doing.

   The one deliberate exception is .ycp-logo-wrapper .logo-img img: that is a
   partner's logo, and recolouring somebody else's mark is not a palette fix.
   --------------------------------------------------------------------------- */

/* -- icons: the brand red ------------------------------------------------- */
.reach-section .reach-mode-icon img,
#extra .extra-duration-icon,
.ashram-timeline-strip .ashram-timeline-card .atc-icon img,
.founders-section.is-light .founder-facts .founder-fact .founder-fact-icon,
.library-card .content .include-badge::before,
.partners-strip .ps-eyebrow::before,
.all-media .badge-cert::before,
.certified-section .cert-feature::before,
.certified-section .cert-feature::after,
.retreat-option-section .retreat-card .retreat-content .tags .tag .circle img,
.site-header .middle-box .box:nth-child(1) .top-contact-link .call-icon img,
.theme-button.outline .icon-wrap,
.theme-button:hover .icon-wrap,
.theme-button.white-outline:hover .icon-wrap {
    filter: brightness(0) saturate(100%) invert(22%) sepia(81%)
            saturate(5000%) hue-rotate(356deg) brightness(92%) contrast(97%);
}

/* -- background patterns: ink, and let their own opacity do the rest ------
   .bg-alt::before is the page watermark — the tile the owner replaced with
   rudra-bg-web.webp. It was being painted green by the same chain, which is
   why the icons behind every warm section read as sage rather than as the
   site's own ink. */
.bg-alt::before,
.bg-chakra::before,
.bg-chakra::after {
    filter: brightness(0);
}

/* ---------------------------------------------------------------------------
   THE "NOTE:" BOX
   ---------------------------------------------------------------------------
   Owner, 15 Nov 2026, pointing at the schedule note: "iska background website
   ke color jesa kar do sabhi pages main jaha yeh hai."

   It is the last of the theme's gold: a cream radial wash inside a
   rgba(201,169,110,.5) border with a gold ॐ watermark behind the words. The
   generated palette remap reached the TEXT colour and nothing else, because
   the gold was never part of the green family it maps.

   Now it reads like every other aside on the site: the paper ground, a red
   rule down its left edge instead of a box drawn all the way round, and the
   watermark in the faintest red rather than gold. It is on all eight pages
   that carry a daily schedule.
   --------------------------------------------------------------------------- */
.special-note {
    background: var(--ryp-red-tint);
    border: 0;
    border-left: 3px solid var(--ryp-red);
    border-radius: var(--ryp-img-radius);
    box-shadow: none;
    color: var(--ryp-ink-soft);
}
.special-note strong { color: var(--ryp-red-ink); }
/* Owner, 15 Nov 2026: the ॐ watermark behind the note is not to appear on any
   page. `content: none` would be the tidier way to drop a pseudo-element, but
   style.css sets the glyph on the same selector, so this matches it on content
   and wins there; !important because the theme's own rule is loaded from a
   file this redesign does not edit and the two are otherwise equal weight. */
.special-note::before {
    content: "" !important;
    display: none !important;
}

/* ---------------------------------------------------------------------------
   THE SECTION ORNAMENTS
   ---------------------------------------------------------------------------
   Owner, 16 Nov 2026: put his line-art drawing where chakra-pattern.webp is,
   in webp, on every page, visible on a phone, in the site's own colours.

   WHAT IT REPLACES. style.css hangs chakra-pattern.webp on both
   `.bg-chakra::before` and `.bg-chakra::after` — the same symmetrical mandala
   at the left and right edge of a section, each one half off the page.

   WHAT ARRIVED. One wide drawing holding TWO subjects: a dancer with a drum on
   the left and a hand in a mudra on the right. That is already a left ornament
   and a right ornament, so it is cut in two rather than repeated — measured,
   the ink falls in two clean runs with 200px of nothing between them, at
   x 321-804 and x 1007-1684.

   IT ARRIVED AS A SCREENSHOT, not as a transparent file: 100% opaque, with the
   editor's checkerboard baked into the pixels at ~201-203 and ~253-255. The
   alpha is rebuilt from darkness — nothing survives at or above 195, solid by
   45, so both checker tones clear and the soft end of every stroke is kept.
   Same repair the footer skyline needed; the owner's exports come this way.

   SIZE. The alpha is quantised to 17 levels before encoding. Dense
   cross-hatching is expensive to compress and at under a tenth opacity the
   other 239 levels cannot be seen: 166KB lossless became 78KB for the pair.

   COLOUR AND STRENGTH. Inked in the brand red rather than left on the theme's
   green filter chain, at .09 — a shade under the old .18/.20, because this
   drawing carries far more ink per square inch than the mandala it replaces
   and at the old strength it competed with the words.
   --------------------------------------------------------------------------- */
.bg-chakra::before,
.bg-chakra::after {
    width: clamp(210px, 30vw, 500px);
    opacity: .09;
    filter: brightness(0) saturate(100%) invert(22%) sepia(81%)
            saturate(5000%) hue-rotate(356deg) brightness(92%) contrast(97%);
}
.bg-chakra::before {
    background-image: url("../img/ornament-dancer.webp");
    aspect-ratio: 460 / 446;
    /* a quarter off the edge, not half: a mandala reads fine cut down the
       middle and a figure does not */
    transform: translate(-24%, -50%);
}
.bg-chakra::after {
    background-image: url("../img/ornament-mudra.webp");
    aspect-ratio: 520 / 472;
    transform: translate(24%, -50%);
}

/* style.css hangs the same mandala on .yttr-hero__footer as well, but no page
   in this redesign carries that class — checked — so there is no rule for it
   here. If that block ever appears, it will still show the old pattern and
   will want adding to the selectors above. */

@media (max-width: 61.99rem) {
    /* On a phone the ornaments were invisible, and `top: 50%` is why: the
       section's middle is where the full-width photo cards sit, and those are
       opaque, so a watermark behind them cannot be seen. Measured on the
       200-hour page — the section is 1775px tall and the ornaments landed at
       y≈887, squarely behind the stack.

       The foot is no good either: measured on the same section, the clear
       ground is 247px at the TOP and only 50px at the bottom — the last card
       runs almost to the section's edge. So both ornaments go in the top
       band, one at each side, small enough to leave the heading its middle:
       at 375px they occupy roughly the outer 110px on each side and the
       words keep the 150px between them. */
    .bg-chakra::before,
    .bg-chakra::after {
        top: 0;
        width: clamp(140px, 38vw, 190px);
    }
    .bg-chakra::before { transform: translate(-32%, 6%); }
    .bg-chakra::after  { transform: translate(32%, 6%); }
}
