.blue-btn:hover,
.blue-btn:active,
.blue-btn:focus,
.blue-btn {
    background: transparent;
    border: solid 1px #27a9e0;
    border-radius: 3px;
    color: #27a9e0;
    font-size: 16px;
    margin-bottom: 20px;
    outline: none !important;
    padding: 10px 20px;
}

.fileUpload {
    position: relative;
    overflow: hidden;
    height: 43px;
    margin-top: 0;
}

.fileUpload input.uploadlogo {
    position: absolute;
    top: 0;
    right: 0;
    margin: 0;
    padding: 0;
    font-size: 20px;
    cursor: pointer;
    opacity: 0;
    filter: alpha(opacity=0);
    width: 100%;
    height: 42px;
}

/*Chrome fix*/
input::-webkit-file-upload-button {
    cursor: pointer !important;
    height: 42px;
    width: 100%;
}
.seo-snippet {
    padding: 0px !important;
}

.seo-snippet small{
    color:#1a0dab !important;
}

.seo-snippet h5 {
    color: #1a0dab !important;
}

.seo-snippet p {
    color:#3C4043 !important;
}

/* =====================================================================
   THE FRONT DOOR'S COLOURS — the five screens on administrator.layouts.login

   WHERE THESE CAME FROM. Until 2026-09-13 the login layout carried two
   inline <style> blocks of its own: `body { background-color: 1c8642 }`
   and the whole of `.btn-theme`, which is defined NOWHERE ELSE in this
   project. Five views extend that layout — administrator/auth/{login,
   forgot,set-password,change-password} and the branch chooser
   administrator/tenants/select-tenancy — so the way into the product was
   painted by a blade rather than by a stylesheet, and nothing could reuse
   or review it.

   WHAT WAS MEASURED, before deciding anything, against the four committed
   stylesheets this layout already loads:
     #00803F  2x in bootstrap.min.css, 1x in app.min.css  -> the panel's own green
     #00632F  0x anywhere                                 -> invented, here only
      1c8642  0x anywhere                                 -> invented, here only

   THE DECISIONS, so that no colour here is one nobody chose:

   1. --bif-admin-green is #00803F, unchanged. It is measurably the
      panel's green, so the button the volunteer presses to sign in is the
      same green as the buttons they meet once inside.

   2. THE BACKGROUND IS NOW THAT SAME GREEN. 1c8642 (no hash: it is gone) was rgb(28,134,66)
      against #00803F's rgb(0,128,63) — a near-miss nobody could have
      chosen on purpose and nobody can see the difference of. The door
      stays green, as it has for years; it is now the product's green.

   3. --bif-admin-green-dark keeps #00632F. It is the only darker shade
      this button has ever shipped, changing it would alter what every
      administrator in 37 branches sees at the front door for a reason
      nobody could name, and a derived value (color-mix) would fail open
      on a browser that does not support it — on the ONE screen that must
      never be wrong. It is a chosen colour now, named, where colours
      live, rather than an anonymous literal inside a blade.

   Scoped to `.admin-auth`, which the login layout puts on <body>, so a
   screen that loads this sheet for its other rules does not inherit a
   green page.
   ===================================================================== */
:root {
    --bif-admin-green: #00803F;
    --bif-admin-green-dark: #00632F;
}

body.admin-auth {
    background-color: var(--bif-admin-green);
}

body.admin-auth footer {
    width: 100%;
    position: fixed;
    bottom: 15px;
}

.btn-theme {
    background-color: var(--bif-admin-green);
    border-color: var(--bif-admin-green);
    color: #ffffff;
}

.btn-theme:hover {
    background-color: var(--bif-admin-green-dark);
    border-color: var(--bif-admin-green-dark);
    color: #ffffff;
}

.btn-theme:focus {
    background-color: var(--bif-admin-green-dark);
    box-shadow: none;
}

.btn-theme:active {
    background-color: var(--bif-admin-green-dark) !important;
    border-color: var(--bif-admin-green-dark) !important;
    color: #ffffff !important;
}
