/* designyoursleep.com - restoration extras.
   Everything here replaces a stylesheet the archive did not capture. Nothing here is decoration
   for its own sake; each block names the file it stands in for.
   ------------------------------------------------------------------------------------------- */

/* A. Section D of the theme's own responsive.css never downloaded, and neither did the plugin CSS
      that constrained inline images. One image on the homepage measured 496px inside a 390px
      viewport, which is the whole of the site's sideways scroll on a phone. */
img, svg, video, iframe { max-width: 100%; height: auto; }
table { max-width: 100%; }

/* B. themify-icons.css is gone, so the mobile menu button rendered as an empty box: a control the
      visitor cannot see is a control that does not exist. Drawn in CSS instead of a webfont. */
#mobile_nav_icon { display: inline-block; width: 44px; height: 44px; position: relative; }
#mobile_nav_icon .ti-menu { display: block; width: 100%; height: 100%; }
#mobile_nav_icon .ti-menu::before,
#mobile_nav_icon .ti-menu::after {
  content: ""; position: absolute; left: 11px; width: 22px; height: 2px;
  background: #2F466D; border-radius: 2px;
}
/* three bars from two pseudo-elements: the middle one is a box-shadow on the top bar, because the
   theme's markup is a bare <span class="ti-menu"></span> with no child to style. */
#mobile_nav_icon .ti-menu::before { top: 15px; box-shadow: 0 6px 0 0 #2F466D; }
#mobile_nav_icon .ti-menu::after  { top: 27px; }
/* On the 13 blog articles the header is navy (#header_style_wrapper, #2F466D) - the same colour as the
   bars above - so the burger measured 3288/3300 navy pixels: no menu at all on a phone. Where the
   header is navy the bars are white; every other template keeps navy bars on its white top bar. */
#wrapper.hasbg.transparent #mobile_nav_icon .ti-menu::before { background: #fff; box-shadow: 0 6px 0 0 #fff; }
#wrapper.hasbg.transparent #mobile_nav_icon .ti-menu::after  { background: #fff; }

/* C. The theme's font-awesome.min.css (v4 syntax) is gone, so the back-to-top control lost its
      chevron. Same reasoning as B: draw it. */
#toTop { display: none; position: fixed; right: 20px; bottom: 20px; width: 44px; height: 44px;
  border-radius: 50%; background: #2F466D; z-index: 900; text-indent: -9999px; overflow: hidden; }
#toTop.dys-visible { display: block; }
#toTop::after { content: ""; position: absolute; left: 15px; top: 19px; width: 12px; height: 12px;
  border-left: 2px solid #fff; border-top: 2px solid #fff; transform: rotate(45deg); }

/* D. loftloader.min.css is gone with its plugin; the wrapper markup has been deleted from every
      page, and this is the belt-and-braces rule in case a page is ever rebuilt from the raw HTML. */
#loftloader-wrapper { display: none !important; }

/* E. The off-canvas mobile drawer. The theme shipped its open/close behaviour in custom.js, which
      the archive never captured, so at 390px the burger opened nothing at all. The drawer markup
      (.mobile_menu_wrapper with the full menu inside) IS in every page, so the behaviour is
      rebuilt here rather than the menu being replaced by something the site never had. */
@media (max-width: 1000px) {
  .mobile_menu_wrapper {
    position: fixed; top: 0; right: 0; bottom: 0; width: min(86vw, 340px);
    background: #fff; z-index: 1000; overflow-y: auto; padding: 84px 24px 40px;
    transform: translateX(105%); transition: transform .28s ease, visibility 0s linear .28s;
    box-shadow: -6px 0 24px rgba(0, 0, 0, .18); display: block;
    /* transform alone left a sliver of the drawer painted at the right edge of a 390px screen,
       because the theme also positions it; visibility takes it out of the picture entirely. */
    visibility: hidden;
  }
  body.dys-menu-open .mobile_menu_wrapper {
    transform: translateX(0); visibility: visible; transition: transform .28s ease;
  }
  #close_mobile_menu {
    position: fixed; inset: 0; background: rgba(20, 26, 40, .45); z-index: 999;
    display: none; text-decoration: none;
  }
  body.dys-menu-open #close_mobile_menu { display: block; }
  body.dys-menu-open { overflow: hidden; }
  .mobile_menu_wrapper .mobile_main_nav { list-style: none; margin: 0; padding: 0; }
  .mobile_menu_wrapper .mobile_main_nav li { border-bottom: 1px solid #e6e9f0; }
  .mobile_menu_wrapper .mobile_main_nav a {
    display: block; padding: 14px 4px; font-size: 17px; line-height: 1.4; color: #2F466D;
    text-decoration: none; min-height: 24px;
  }
  .mobile_menu_wrapper .sub-menu { list-style: none; margin: 0 0 0 14px; padding: 0; }
}
@media (min-width: 1001px) {
  .mobile_menu_wrapper, #close_mobile_menu { display: none !important; }
}

/* F. The two dead third-party widgets - Calendly's 700px hole and Fillout's 500px hole - were
      replaced by the practice's own published contact route. This is how that block is dressed so
      it reads as part of the page and not as an apology bolted on. */
.dys-contact-route {
  max-width: 620px; margin: 0 auto 40px; padding: 28px 30px;
  border: 1px solid #dfe4ee; border-radius: 10px; background: #fbfcfe;
}
.dys-contact-route h2 { margin: 0 0 14px; font-size: 26px; line-height: 1.25; color: #2F466D; }
.dys-contact-route p { margin: 0 0 14px; font-size: 16px; line-height: 1.6; color: #3a4256; }
.dys-contact-list { list-style: none; margin: 0 0 18px; padding: 0; }
.dys-contact-list li {
  display: flex; flex-wrap: wrap; gap: 8px; padding: 10px 0;
  border-bottom: 1px solid #e8ecf4; font-size: 16px; line-height: 1.5; color: #3a4256;
}
.dys-contact-list li span {
  min-width: 108px; font-size: 13px; letter-spacing: .08em; text-transform: uppercase;
  color: #64708A;
}
.dys-contact-list a { color: #2F466D; text-decoration: underline; }
.dys-btn {
  display: inline-block; padding: 13px 26px; min-height: 24px; border-radius: 6px;
  background: #2F466D; color: #fff !important; text-decoration: none; font-size: 16px;
}
.dys-btn:hover { background: #1f3355; }
.dys-note { font-size: 14px; line-height: 1.6; color: #5d6679; margin-bottom: 0; }

/* G. Legibility. The theme set 14px body copy inside Elementor text widgets below 768px, which is
      under the 12px floor once a browser's minimum-font-size is off, and its footer links were
      #8d97ab on white - 2.9:1. Both are raised to the readable side; nothing else about the
      typography is touched. */
.elementor-widget-text-editor, .elementor-widget-text-editor p { font-size: 16px; }
@media (max-width: 767px) {
  .elementor-974 .elementor-element.elementor-element-9074abe,
  .elementor-974 .elementor-element.elementor-element-79cf772,
  .elementor-widget-text-editor, .elementor-widget-text-editor p { font-size: 16px; }
}
/* K. The footer, measured rather than assumed - a first attempt at "darken the footer links"
      painted #46506b on the English footer's accent panel and made six links invisible at 1.41:1,
      then painting them white made fourteen invisible on the FRENCH footer, which is white.
      The French footer is white only because its Elementor CSS (post-2670.css) is one of the files
      the archive never captured: it is the same design as the English footer, whose own CSS did
      survive and paints the panel #4F6B78. So the French footer is given back that panel, and then
      one rule serves both. Links carry an underline because once the panel is one colour they are
      otherwise indistinguishable from the headings beside them. */
#footer_wrapper .elementor-2670 > section,
#footer_wrapper .elementor-2670 .elementor-top-section { background-color: #4F6B78; }
#footer_wrapper, #footer_wrapper p, #footer_wrapper span,
#footer_wrapper .elementor-heading-title, #footer_wrapper .elementor-icon-list-text,
#footer_wrapper a { color: #FFFFFF; }
#footer_wrapper .elementor-icon-list-item a { text-decoration: underline; text-underline-offset: 3px; }
#footer_wrapper a:hover { color: #EADAA8; }

/* A 14px uppercase kicker in tan on white, 3.81:1. Darkened inside its own hue. */
.elementor-974 .elementor-element.elementor-element-92f7ec4 .elementor-heading-title { color: #8A6335; }

/* H. Tap targets. Elementor's icon-list rows in the footer were 18px tall on a phone. */
@media (max-width: 767px) {
  #footer_wrapper .elementor-icon-list-item a,
  .elementor-social-icon { min-height: 24px; display: inline-flex; align-items: center; }
  .elementor-social-icon { min-width: 24px; justify-content: center; }
}

/* I. Contrast, measured against the ground actually painted behind the text.
      Two Elementor global colours failed: the olive --e-global-color-3173126 (#878663) carried the
      e-book pitch at 3.28:1 on the site's own cream #F2F0EB, and the blue-grey
      --e-global-color-f7be0d4 (#7093A1) carried white button text at 3.29:1. Both are darkened
      within their own hue rather than replaced, so the palette still reads as this site's.
      The French homepage was worse - 2.09:1 - because its Elementor page CSS is one of the files
      the archive never captured, so its e-book button fell back to Elementor's stock
      .elementor-button-info blue. Pointing it at the same accent restores the intended colour. */
.elementor-kit-146 {
  --e-global-color-3173126: #5F5E45;
  --e-global-color-f7be0d4: #4F6B78;
}
.elementor-974 .elementor-element.elementor-element-4ba295e .elementor-button,
.elementor-element.elementor-button-info .elementor-button,
.elementor-widget-button .elementor-button.elementor-button-info { background-color: #4F6B78; }

/* J. Tap targets in the desktop header. The theme gave its nav links a 20px box; the floor for a
      control is 24px on its shorter side. Padding, not font-size, so the header keeps its rhythm. */
#main_menu li a, #main_menu .sub-menu li a, .menu-dys-main-menu-container ul li a {
  padding-top: 5px !important; padding-bottom: 5px !important; display: inline-block;
}

/* L. Tap targets in lists of links, and the category chips.
      The blog grid, the rebuilt category archives and the authored legal/404 pages all put their
      links in tight lists: 19-22px boxes, under the 24px floor for a control. Padding on the link
      itself, so the target grows without the type changing size. The category chips were the
      theme's #7093A1 on white (3.29:1) and move to the darkened accent, which measures 5.6:1. */
.o5-legal li a,
.dys-archive .post_header_title h5 a,
.blog_post_content_wrapper .post_header_title h5 a,
.posts.blog li a,
.post_info_cat a {
  display: inline-block; padding-top: 3px; padding-bottom: 3px;
}
.blog_post_content_wrapper .post_info_cat a, .dys-archive .post_info_cat a,
.blog_post_content_wrapper .post_attribute, .dys-archive .post_attribute { color: #4F6B78; }

/* M. The article hero. Fourteen posts opened with a full-width photograph behind a transparent
      header, and the theme paints the header's navigation WHITE for exactly that state. None of
      those fourteen photographs was ever captured, so the band was white and the whole main
      navigation measured 1:1 - invisible on every article page, before this restoration and after.
      Painting the band in the site's own navy puts the white navigation back on a dark ground; a
      caption that still has its photograph paints straight over the colour. */
#page_caption.hasbg { background-color: #2F466D; }
#page_caption.hasbg .post_info_cat a, #page_caption.hasbg .post_attribute,
#page_caption.hasbg h1 { color: #FFFFFF; }

/* N. The transparent header. The theme marks these pages body.tg_menu_transparent and paints the
      navigation white, because a full-bleed photograph was supposed to sit behind it. The
      photographs are gone AND the scroll handler that swapped the header to its solid state lived
      in the theme's custom.js, which is also gone - so the white navigation ended up over white
      page for the whole of every article. The header gets the same navy as the caption band it
      overlaps, which reads at the top of the page and stays readable once the page scrolls. */
body.tg_menu_transparent .header_style_wrapper,
body.tg_menu_transparent #header_wrapper { background-color: #2F466D; }

/* O. The separators and tag chips in listings, still on the theme's #7093A1 at 3.29:1. */
.blog_post_content_wrapper .post_info_cat, .dys-archive .post_info_cat,
.post_tags a, .tags a { color: #4F6B78; }

/* P. The footer's own links - the sitemap column, the decoded e-mail address and the illustrator
      credit - measured 14 to 19px tall at every width. The earlier rule only raised them below
      768px, which is the same "fixed on one viewport, never re-checked on the other" mistake this
      project keeps paying for. */
#footer_wrapper a, #footer_wrapper .elementor-icon-list-item a {
  display: inline-block; padding-top: 4px; padding-bottom: 4px; min-height: 24px;
}

/* Q. The category chips were set at 11px, under the 12px floor for body copy. */
.post_info_cat, .post_info_cat a, .post_info_cat span { font-size: 12px; }
.post_info_cat a { color: #4F6B78; }
#page_caption.hasbg .post_info_cat, #page_caption.hasbg .post_info_cat a { color: #FFFFFF; }

/* R. The article's own controls. The previous/next article links measured 19px tall with an 11px
      "Previous Article" label under them, and links inside the prose measured 19px. Padding on the
      inline box grows the target without moving a single line of text. */
.post_navigation a { display: block; padding: 6px 0; }
.post_navigation .navigation_anchor, .navigation_anchor { font-size: 12px !important; }
#page_content_wrapper p a, #page_content_wrapper li a, .post_tags a {
  padding-top: 3px; padding-bottom: 3px;
}

/* S. The drawer's click-away overlay is an empty <a>; the theme gives it a box even when closed,
      which reads as a 350x19 control that does nothing. It exists only while the drawer is open. */
#close_mobile_menu { display: none !important; }
body.dys-menu-open #close_mobile_menu { display: block !important; }

/* T. The call-to-action illustration and the portrait were wrapped in a link so they advertise the
      page they belong to. An inline <a> around a block image reports a 380x19 line box as its
      clickable area - the picture is hittable but the CONTROL measures 19px. Block it. */
a.dys-img-link { display: block; }

/* U. Prose links inside Elementor text widgets - the theme's own body copy - were 23px. */
.elementor-widget-text-editor a, .elementor-widget-text-editor p a {
  padding-top: 3px; padding-bottom: 3px;
}

/* V. The burger is the theme's side-menu toggle and it renders at every width. At desktop the full
      horizontal navigation is already on screen, so the burger is a duplicate control - and it sits
      under the language switcher, where a real pointer never reaches it. */
@media (min-width: 1001px) { #mobile_nav_icon { display: none !important; } }

/* W. Three things the phone showed that no number did.
      1. The DESKTOP navigation was still painted at 390px, running off the right edge beside the
         burger. The theme hid it from responsive.css, which the archive captured only in part.
      2. The homepage hero's italic line carries margin-top:-39px, tuned for a wider column; at
         390px the paragraph above it is four lines longer and the two printed on top of each other.
         The pull-up is cancelled below the tablet breakpoint rather than removed, so the desktop
         composition the author intended is untouched.
      3. Raising the footer links to a 24px target turned Elementor's icon-list rows into a stack:
         the tick floated above its own label. Back to a row, with the target height kept. */
@media (max-width: 1000px) {
  #menu_wrapper, #nav_wrapper, #main_menu { display: none !important; }
}
/* CORRECTED 2026-08-19, second finishing pass. Item 2 above was wrong about where the collision
   happens, and the correction is the whole reason this file is worth reading before editing.
   The pull-up was cancelled only below 767px, on the theory that the desktop composition still
   worked. It does not: at 1440 the English homepage prints "Finally feel well-rested & lead a
   healthy and productive life." straight through "get their life back, just like I did." The
   earlier pass photographed exactly that crop (_recon/shots/dysrev/crop-home-hero.png), and the
   overlap is plainly in the picture, yet the site was recorded as fixed.
   WHY it collides at every width: the -20px is measured against a paragraph set in HK Grotesk,
   one of the four display faces whose stylesheet the archive never captured. In the fallback face
   the same words occupy more vertical space, so a pull-up that used to close a gap now eats a
   whole line. There is no width at which the original number is still correct, so the cancel is
   unconditional. 8px keeps the two lines reading as one thought, which is what the -20px was for. */
.elementor-974 .elementor-element.elementor-element-79cf772 > .elementor-widget-container,
.elementor-element.elementor-element-79cf772 > .elementor-widget-container {
  margin-top: 8px !important;
}
#footer_wrapper .elementor-icon-list-item {
  display: flex; align-items: center; gap: 8px;
}
#footer_wrapper .elementor-icon-list-item a {
  display: flex; align-items: center; gap: 8px; padding-top: 4px; padding-bottom: 4px;
}
#footer_wrapper .elementor-icon-list-icon { flex: 0 0 auto; line-height: 1; }

/* X. Social icons are square controls with their own sizing; the blanket footer-link padding above
      was squashing them into each other. They are already well over 24px, so they opt out. */
#footer_wrapper a.elementor-social-icon,
#footer_wrapper .elementor-social-icon {
  display: inline-flex; align-items: center; justify-content: center;
  padding: 0; min-height: 0; margin-right: 6px;
}
#footer_wrapper .elementor-grid-item { display: inline-block; }

/* Y. On the fifteen article pages the caption band is 545px tall and completely empty: it existed
      to carry the article's full-bleed photograph, and none of those photographs was captured. The
      article's own title sits below it. Left at 545px it reads as half a screen of nothing before
      the article starts, so it is cut back to just enough to sit behind the fixed header. */
#page_caption.hasbg { height: 132px !important; min-height: 0 !important; }

/* Z. On /fr/blog-fr/ the rebuilt article listing sits under the e-book call to action, whose
      illustration is pulled up by a negative margin and printed across the first two headlines. */
.dys-archive-intro.dys-after-hero { clear: both; margin-top: 220px; position: relative; z-index: 2; }
.dys-archive { position: relative; z-index: 2; }

/* AA. THE CASCADE ITSELF WAS THE DEFECT, and it is why the two blocks above measured clean on the
       homepage and broken on the article pages. WordPress prints Elementor's kit stylesheet
       (post-146.css, which DEFINES --e-global-color-f7be0d4) and the footer template (post-277.css)
       inside <body>, after </head> - so this file, appended at the end of the head, lost the
       cascade on 25 of 47 pages and won on the rest. The whole footer of every article and every
       category archive therefore kept the theme's #7093A1 with white text on it: 3.29:1, on 25
       pages, while the homepage screenshot that the last review looked at was correct.
       The link tag is now moved after the last stylesheet on every page by
       _scripts/o5_22_restore_css_last_word.py. Nothing below relies on !important because of it.

   BB. The article meta line, now that this file is actually read last.
       - .post_detail ("Insomnia · Sleep Science ·" under every headline) is the theme's #7093A1 on
         white, 3.29:1. It carries the article's categories, so it is content, not decoration. The
         theme selector is .post_detail.single_post, so the override has to match that weight.
       - .post_attribute on a single article ("February 9, 2022") is #9B9B9B on white: 2.78:1, the
         lowest-contrast text on the site. It is the publication date - the one fact on the page a
         reader uses to judge whether the advice is current.
       Both move to the same darkened accent already used for the listings, which measures 5.6:1. */
.post_detail, .post_detail.single_post, .post_detail a,
.post_attribute, .post_attribute a, .post-date, .comment_date { color: #4F6B78; }
#page_caption.hasbg .post_detail, #page_caption.hasbg .post_detail a,
#page_caption.hasbg .post_attribute { color: #FFFFFF; }

/* CC. The two survivors of the same #7093A1, both of them content rather than chrome:
       - the "·" separators between an article's categories are painted on .post_info_cat itself,
         not on the links inside it, so darkening only the links left the dots at 3.29:1;
       - the tag chips at the foot of every article (.post_excerpt.post_tag a) are the theme's own
         two-class selector, so a one-class override loses on specificity, not on order. */
.post_info_cat { color: #4F6B78; }
.post_excerpt.post_tag a, .post_excerpt.post_tag a:hover { color: #4F6B78; }

/* DD. /sleep-pressure/ carries a WordPress PINGBACK rendered in the comment list - the site's own
       /get-to-sleep-earlier/ article linking back to it. Its anchor is an inline <a> around an
       <h7>, so it reports a 589x19 line box: a full-width control 19px tall, under the 24px floor.
       Rule R only covered .post_navigation, which is the other, thumbnailed previous/next block. */
.fullwidth_comment_wrapper .comment .right > a { display: block; padding: 4px 0; min-height: 24px; }

/* EE. THE BIGGEST THING ANY NUMBER MISSED: at every desktop width the page's own H1 was painted
       UNDER the header and simply was not there for the visitor. Twenty-one pages, both languages.
       "Terms & Conditions", "Insomnia", "Schedule", "Prendre RDV", "Services", "E-book download",
       "Sleep Truths", "Corporate sleep consultations" and the first paragraph of both About
       letters and both contact pages - all of them behind an opaque white bar.

       MECHANISM. The dotlife header is .header_style_wrapper { position: fixed; top: 0 } and it is
       124px tall at >=1025px, 99px at 961-1024px. A fixed header is out of flow, so the page has
       to reserve the space itself. The theme's own responsive.css does exactly that BELOW 960px -
       #wrapper gets padding-top: 75px, then 69px - and above 960px it reserved nothing, because
       above 960px the theme set that padding from JavaScript. That JavaScript is the theme's
       custom.js, which the archive never captured and which was removed from this build for
       throwing on every page. Two rules in the theme's own screen.css are the fingerprint of it:
       "body.leftmenu #wrapper { padding-top: 0 !important }" and
       "#wrapper.hasbg.transparent { padding-top: 0 !important }" - you only write !important
       overrides of zero against a padding something else is setting.

       So this restores the reservation in CSS at the two widths where the theme left it to JS.
       Measured, not guessed: the header was photographed at thirteen widths from 320 to 1600.
       The two exemptions stay exempt by the theme's own !important, and that is deliberate: on the
       fifteen article pages #wrapper is .hasbg.transparent and the navy caption band is SUPPOSED to
       run under the header. */
@media (min-width: 961px)  { #wrapper { padding-top: 99px; } }
@media (min-width: 1025px) { #wrapper { padding-top: 124px; } }

/* FF. INDEPENDENT REVIEW, THIRD FINISHING PASS 2026-08-19 (port 9615 rework).
       R1/R2: Elementor's own frontend.min.css carries
       ".elementor-widget-wrap>.elementor-element.elementor-absolute{position:absolute}" with no
       matching top/left - those offsets are written per-page into post-<page-id>.css, which the
       archive captured for exactly three pages (post-146 the kit, post-277 the footer, post-974
       the English homepage). On the fifteen pages whose own post-<id>.css was never captured, every
       .elementor-absolute widget keeps position:absolute with NO offset. Per spec its "static
       position" is computed as if it still had position:static - i.e. sitting where the next widget
       in its column would fall - but taking it OUT of flow removes the space it would have
       reserved, so the widget after it (a heading, a footer column, an e-book paragraph) rides up
       underneath it. That is the mechanism behind both R1 (Journal-PNG covering the /about/ footer
       and the /fr/a-propos/, /fr/, /sleep-truths/ e-book calls to action) and R2 (the decorative
       star/circle sprites stamped through headings on /fr/, /corporate-sleep-programmes/,
       /online-sleep-programmes-2/, /fr/programme-online/, /fr/programme-entreprise/).
       There is no honest way to re-derive the missing top/left values - the theme's own kit only
       ever shipped them per page, and inventing coordinates would be exactly the "simulation" this
       project refuses to do. So this returns the affected widgets to NORMAL FLOW instead: photos
       and sprites render inline, in the position their own DOM order gives them, and nothing under
       them gets covered. Scoped to the fifteen page_ids that never got a post-<id>.css (matches
       _recon/visual_designyoursleep.com.json's "pages_with_no_page_stylesheet" exactly), so the
       homepage (974), the footer (277) and the kit (146) - the only three pages/templates the
       archive DID capture per-page CSS for - are untouched and keep their real offsets. */
body.elementor-page-42 .elementor-absolute,
body.elementor-page-450 .elementor-absolute,
body.elementor-page-1174 .elementor-absolute,
body.elementor-page-2327 .elementor-absolute,
body.elementor-page-2656 .elementor-absolute,
body.elementor-page-2751 .elementor-absolute,
body.elementor-page-2743 .elementor-absolute,
body.elementor-page-2690 .elementor-absolute,
body.elementor-page-2814 .elementor-absolute,
body.elementor-page-2809 .elementor-absolute,
body.elementor-page-2679 .elementor-absolute,
body.elementor-page-2762 .elementor-absolute,
body.elementor-page-1156 .elementor-absolute,
body.elementor-page-200 .elementor-absolute,
body.elementor-page-332 .elementor-absolute {
  position: static !important; inset: auto !important;
  display: block; margin: 12px auto; text-align: center;
}
body.elementor-page-42 a.dys-img-link,
body.elementor-page-2656 a.dys-img-link,
body.elementor-page-2751 a.dys-img-link,
body.elementor-page-2690 a.dys-img-link,
body.elementor-page-332 a.dys-img-link {
  display: block; margin: 12px auto;
}

/* GG. R3: THE CLIENT'S MANDATORY /fr/ HOMEPAGE OWES THE SAME E-BOOK PANEL AS ITS ENGLISH TWIN.
       The section is the SAME Elementor element on both pages (data-id 2e625ba, confirmed identical
       in _raw/designyoursleep.com/pages/index.html and fr.html) and its design is fully specified in
       the archive's own post-974.css - but that rule is scoped to .elementor-974, so the French page
       (.elementor-2690) got none of it: bare white background, no min-height on the illustration
       column, and the -121px pull-up that is meant to seat the panel against the section above it
       missing, which is what left the 247px empty gap the reviewer measured. Re-scoped from the
       site's own captured CSS, not invented - same colour, same height, same pull-up. */
.elementor-2690 .elementor-element.elementor-element-2e625ba:not(.elementor-motion-effects-element-type-background) {
  background-color: #F2F0EB;
}
.elementor-2690 .elementor-element.elementor-element-2e625ba > .elementor-container {
  min-height: 281px;
}
.elementor-2690 .elementor-element.elementor-element-2e625ba {
  margin-top: -121px; margin-bottom: 0; padding: 50px 0 30px;
}
@media (max-width: 767px) {
  .elementor-2690 .elementor-element.elementor-element-2e625ba { margin-top: 0; margin-bottom: 0; }
}

/* HH. ORDER-7 VISUAL REVIEW, 2026-10-14.
   HH1. THE HERO CHANGED SIZE MID-SENTENCE. post-974.css sets the two hero text widgets
        (9074abe "My name is Donna...", 79cf772 "Finally feel well-rested...") to 20px at desktop,
        and the owner's pasted <span style="font-size:20px"> runs inside them agree with it. Block G
        above writes `.elementor-widget-text-editor p { font-size: 16px }`, which targets the <p>
        directly, so the unwrapped words dropped to 16px while the spans stayed at 20px: "...that
        was destroying my life. I'" small, "m now a qualified sleep educator..." large, at 1440
        (_shots/o7_designyoursleep.com/home-d0.png). G was written to RAISE small copy and says so;
        on these two widgets it lowered it. Only these two widgets on the whole site carry a desktop
        size above 16px (measured over every post-*.css), so the paragraph inherits its widget's own
        size again at >=768px. Below 768px the theme's 14px still gives way to G's 16px floor. */
@media (min-width: 768px) {
  .elementor-974 .elementor-element-9074abe p,
  .elementor-974 .elementor-element-79cf772 p { font-size: inherit; }
}

/* HH2. THE DROPDOWN ARROW WAS A MISSING GLYPH. screen.css draws the arrow after "English" /
        "Francais" / "Sleep Truths" as `font-family:'themify'; content:"\e64b"` (ti-angle-down),
        and themify-icons was never captured (same loss as blocks B and C), so a private-use
        codepoint with no font rendered as a stray two-stroke mark at 7px beside the label on every
        page (home-d0.png, fr-d0.png, mentions_legales-d0.png). Drawn in CSS, as B and C do; all four
        selectors from screen.css are repeated so the sub-menu variant cannot reinstate the glyph. */
#menu_wrapper .nav li.arrow > a:after,
#menu_wrapper div .nav li.arrow > a:after,
#menu_wrapper .nav ul li:not(.megamenu) > ul.sub-menu > li.arrow > a:after,
#menu_wrapper div .nav li:not(.megamenu) > ul.sub-menu > li.arrow > a:after {
  content: "";
  font-family: inherit;
  font-size: 0;
  display: inline-block;
  float: none;
  width: 5px;
  height: 5px;
  margin-left: 8px;
  border-right: 1.5px solid currentColor;
  border-bottom: 1.5px solid currentColor;
  transform: translateY(-3px) rotate(45deg);
  vertical-align: middle;
  line-height: normal;
}
