/* ============================================================
   PLAIN PAGES — the two policies and Контакти, loaded only for
   a page on the default template (inc/enqueue.php). The Eurovision
   hub has its own template and its own stylesheet, and /spisak/
   and /kviz/ are rewrite rules, not pages, so none of them reach
   this file.

   The problem it solves: page.php gave a legal document a bare
   title and a column of grey text on the page background, with
   nothing to say where the document started or ended. It read as
   unstyled rather than as plain.

   Everything here is container and rhythm. The prose itself —
   headings with the accent tick, links, lists, the contact card —
   is entry.css and is not touched, so a page still reads like the
   rest of the site.
   ============================================================ */

/* ------------------------------------------------------------
   1. Title band

   The short accent rule under the title is the same motif the
   footer and the h2 headings use: one solid tick in the accent.
   It gives the page a top edge without a graphic or a photo,
   which these pages do not have and should not be given.

   The title still takes the 900px cap entry.css sets — only the
   panel below lost its own on 20.09.2026. Nothing shows it today:
   „Политика за бисквитките“, „Политика за поверителност“ and
   „Контакти“ all fit on one line well short of it. A longer page
   title would wrap at 900 above a panel running to 1368, and that
   is the point to take the cap off here too.
   ------------------------------------------------------------ */
.entry-header__inner::after {
    content: "";
    display: block;
    width: 56px;
    height: 4px;
    margin-top: 20px;
    border-radius: 2px;
    background: var(--c-accent);
}

/* ------------------------------------------------------------
   2. The document panel

   A page is one column of continuous prose with no picture and no
   sidebar, so the card is what gives it edges. Surface over the
   page background is the same treatment the article cards and the
   place card use — in light mode the border does most of the work,
   in dark mode the two surfaces separate on their own.

   The panel takes the full width of .entry-body, which stops at
   1480px and pads. No width cap here: it was asked for on
   20.09.2026, the same call as the article header. On a wide
   screen that puts the prose on a long line — if it ever reads
   too long, cap the paragraphs rather than the panel, so the panel
   keeps its edges and the text keeps its measure.
   ------------------------------------------------------------ */
.entry-body {
    padding-top: clamp(20px, 3vw, 32px);
}

.entry-body .entry-content {
    padding: clamp(22px, 4vw, 48px);
    border: 1px solid var(--c-border);
    border-radius: var(--radius-lg);
    background: var(--c-surface);
    box-shadow: 0 2px 16px var(--c-shadow);
}

/* The panel supplies the top padding, so whatever the editor put
   first must not add its own margin on top of it. */
.entry-content > *:first-child {
    margin-top: 0;
}

.entry-content > *:last-child {
    margin-bottom: 0;
}

/* ------------------------------------------------------------
   3. The opening paragraph

   Both policies start with one sentence that says what the
   document is for. It carries the page, so it is set larger and
   in the full ink rather than the softened body colour.
   ------------------------------------------------------------ */
.entry-content > p:first-child {
    font-size: 1.16rem;
    line-height: 1.65;
    color: var(--c-ink);
}

/* ------------------------------------------------------------
   4. Section rhythm

   A policy is mostly h2 sections one after another. Inside a panel
   the generic 2.1em top margin runs them together, so each section
   after the first gets a hairline above it — the separation these
   documents actually need, and cheaper than boxing every section.
   ------------------------------------------------------------ */
.entry-content h2 {
    margin-top: 2em;
    padding-top: 1.6em;
    border-top: 1px solid var(--c-border);
}

.entry-content > h2:first-child,
.entry-content > p:first-child + h2 {
    margin-top: 1.4em;
    padding-top: 0;
    border-top: 0;
}

/* ------------------------------------------------------------
   5. The consent panel

   [cmplz-manage-consent] renders Complianz's own button, and the
   cookie policy is the only place on the site that offers a way to
   withdraw consent — the privacy policy promises it, so it must not
   disappear into the prose. It is given room and left otherwise
   alone: the markup is the plugin's and will change under us.
   ------------------------------------------------------------ */
.entry-content .cmplz-manage-consent,
.entry-content .cmplz-manage-consent-container {
    display: block;
    margin: 1.8em 0;
}

/* ------------------------------------------------------------
   6. Narrow screens

   The panel keeps its radius but loses most of its inset, so the
   text measure does not collapse on a phone.
   ------------------------------------------------------------ */
@media (max-width: 600px) {
    .entry-body {
        padding-right: 14px;
        padding-left: 14px;
    }

    .entry-body .entry-content {
        padding: 20px 16px;
    }
}