,
* because a theme that resets `em { font-style: normal }` would otherwise take
* the italic away and leave weight doing the work alone. Both properties are
* stated so neither depends on what the site happens to say.
*/
#dcf-search .dcf-search-desc em,
#dcf-invitation p em {
font-weight: 600;
font-style: italic;
}
/**
* The last line before the textarea, and now literally against it.
*
* Quiet on purpose. It is a caution, not a pitch, and anything loud here would
* compete with the very thing it is asking the visitor to do.
*
* Lives OUTSIDE #dcf-container since it moved inside the form, so like
* .dcf-postsubmit below it repeats the few tokens it needs instead of
* inheriting them — there is no container to inherit from, and an em font-size
* out here would be measured against whatever the theme sets on the form.
* 13px is the same size the em version resolved to inside the panel.
*/
.dcf-presubmit {
margin: 0 0 0.5em;
padding: 0;
font-size: 13px;
line-height: 1.45;
text-align: center;
color: #6c655b;
}
/**
* The save-this-page notice. Lives outside #dcf-container — it is rendered after
* the form, not in the panel — so it repeats the tokens it needs rather than
* inheriting them.
*
* The accent wash rather than the plain surface. It was chosen when this only
* appeared in answer to a submission and had to read as an acknowledgement;
* it is now on the page from first paint (2026-08-05) and the wash is what
* keeps it from being read as part of the form it sits under. Kept for the
* second reason, not the first.
*/
.dcf-postsubmit {
margin: 0.9em 0;
padding: 0.85em 1em;
font-size: 15px;
line-height: 1.5;
text-align: center;
color: #23201c;
background: #eff6f5;
border: 1px solid #a9c8c4;
border-radius: 8px;
}
.dcf-postsubmit p {
margin: 0;
padding: 0;
font-size: inherit;
line-height: inherit;
color: inherit;
}
/**
* Copy the link. A full reset, not a tweak — themes style bare `button` hard
* (heatmap-adaptive sets font-size, line-height, border, background and radius;
* Astra adds padding and letter-spacing), and this one sits in theme territory
* outside #dcf-container with nothing of ours between it and them.
*
* Outlined rather than solid: the notice it lives in is already an
* acknowledgement, and the real next action is the visitor bookmarking or
* sharing the page. This offers help with that, it does not demand a click.
*
* text-transform: none for the same reason as the panel's button — Turkish
* dotted and dotless i do not survive CSS uppercasing across 28 installs, and
* 'Bağlantıyı kopyala' is exactly the phrase that would break.
*/
.dcf-postsubmit .dcf-copy-button {
display: inline-block;
margin: 0.7em 0 0;
padding: 0.5em 1.1em;
font-family: inherit;
font-size: 14px;
font-weight: 600;
font-style: normal;
line-height: 1.3;
letter-spacing: normal;
text-align: center;
text-transform: none;
text-decoration: none;
color: #14655e;
background: #ffffff;
border: 1px solid #a9c8c4;
border-radius: 6px;
box-shadow: none;
cursor: pointer;
-webkit-appearance: none;
appearance: none;
transition: background-color 0.15s ease, border-color 0.15s ease;
}
.dcf-postsubmit .dcf-copy-button:hover,
.dcf-postsubmit .dcf-copy-button:focus {
background: #eff6f5;
border-color: #14655e;
}
/* Focus has to survive the reset above, because removing an outline without
replacing it is how a keyboard user loses their place. */
.dcf-postsubmit .dcf-copy-button:focus-visible {
outline: 2px solid #14655e;
outline-offset: 2px;
}
/* Confirmed. Green rather than the accent, matching the presence dot's meaning
of 'yes, this happened' — and it is a state, not a second action, so the
border goes with it. */
.dcf-postsubmit .dcf-copy-button.is-done {
color: #1d7a4a;
background: #ffffff;
border-color: #2f9e63;
cursor: default;
}
@media (prefers-reduced-motion: reduce) {
.dcf-postsubmit .dcf-copy-button {
transition: none;
}
}
@media (prefers-reduced-motion: reduce) {
#dcf-container #dcf-load,
#dcf-container .dcf-chevron {
transition: none;
}
}
/**
* Narrow phones: keep the three abreast — stacking them would put the reply time
* below the fold, which is the whole reason the panel moved here — but give the
* dividers and padding back their room.
*
* Only the container's font-size moves. Every label, definition and the button
* scale from it in one step, which is the payoff for banning rem: there is
* exactly one number to turn.
*/
@media (max-width: 420px) {
#dcf-container {
font-size: 15px;
}
#dcf-container .dcf-cards {
padding: 0.75em 0.125em;
}
#dcf-container .dcf-card {
padding: 0 0.3em;
}
}
/* =========================================================================
wpDiscuz overrides — NOT the panel
=========================================================================
Everything above this line is ours, scoped under #dcf-container, and uses no
!important. Everything below is the opposite on both counts, deliberately:
these target wpDiscuz's own markup, which is outside our container and comes
with its own stylesheet, so there is nothing of ours to scope to and no way
to win on specificity alone against rules we do not control and cannot
anticipate across four theme families.
Why they are here at all: this exact set was maintained by hand in 26
separate per-site files under wp-content/uploads/custom-css-js/ — mycss.css,
10000045.css, r-p.css, so_css.css, 2149424.css and a dozen more names. Same
intent, sixteen filenames, no way to change it once. Consolidating them here
is the point.
The per-site file stays the place for anything genuinely per-site. This
section is only for rules that should be true on every site.
========================================================================= */
/* Identity fields. The network never asks a dreamer for an email address or a
website, and the two are removed rather than restyled.
PRECONDITION: the field must NOT be required in the wpDiscuz form (Comment
Forms → the form → the field). Hiding a required input makes the browser
refuse to submit and then fail to explain why, because it cannot focus a
display:none field to show the message. All 26 sites already carry
required=0 on the email field; verify before adding a site. */
.wc_email-wrapper,
.wc_website-wrapper {
display: none !important;
}
/* Account furniture. These sites have no reader accounts — the only logged-in
user is the interpreter — so a log-in link and a user-settings panel offer
a door that opens onto nothing. */
.wpd-login,
.wpdiscuz-user-settings {
display: none;
}
/* Replies to a dream are the interpreter's job, not the crowd's. Hiding the
reply button on top-level comments only: nested replies keep theirs, so a
dreamer can still answer inside their own thread. */
div.wpd_comment_level-1 > div.wpd-comment-wrap > div.wpd-comment-right > div.wpd-comment-footer > div.wpd-reply-button {
display: none !important;
}
/* The thread toggle is the control that reveals an interpretation, so it is
sized and coloured to be found rather than left at wpDiscuz's default. */
.wpd-toggle i {
font-size: 20px !important;
color: #0088cc !important;
}
span.wpd-view-replies-text {
font-size: 16px !important;
font-weight: 600;
}
/* A dream takes more than two lines to tell. Three times the 48px wpDiscuz gives
the box, so it invites the whole thing rather than a sentence the visitor then
has to scroll inside.
The live selector is the plain textarea. **Quill is off on all five deployed
sites** — measured in a browser, 2026-08-03: every one renders
`#wpdcom.wpd-layout-2` with a `textarea.wc_comment` and no `.ql-editor` node at
all. Reading the page source is not enough to tell: `ql-editor` appears there
as CSS text whether or not the editor is ever instantiated, which is exactly
how the first attempt at this rule went to the wrong element.
`min-height` rather than `height` on purpose. wpDiscuz sets `height: 48px`
(`#wpdcom.wpd-layout-2 .wpd-form .wpdiscuz-textarea-wrap textarea`) and grows
it from JS as the visitor types; min-height beats both an explicit height and
an inline one, so the floor holds without fighting the auto-grow.
The .ql-editor selector rides along for the case where someone turns the rich
editor back on in wpDiscuz's settings — it costs one line and otherwise the box
would silently drop to 65px. */
#wpdcom .wpd-form .wpdiscuz-textarea-wrap textarea,
#wpdcom .ql-editor {
min-height: 144px !important;
}
/* wpDiscuz's per-thread meta line (vote/date/count strip above a thread) adds
nothing next to the panel's own counters, so it is hidden. !important matches
the rest of this block — wpDiscuz's own rules are ID-scoped. */
.wpd-thread-info {
display: none !important;
}
/* The house rule, a custom HTML field in the wpDiscuz form. wpDiscuz renders it
inside .wpd-form-col-right (49%, floated right, text-align:right) directly
under the Send button, so it is already positioned as a footnote to that
button — this only makes it read like one. Nothing in wpDiscuz, Blocksy or
the other three theme families targets .comment-rules, so #wpdcom is enough
specificity and no !important is needed: unlike the rest of this block, the
markup is ours.
The is where the size lives because the field's stored HTML puts it
there; setting it on the alone would be overridden by the theme's own
`small { font-size: 80% }`.
#6c655b is --dcf-ink-mute from the panel above, hardcoded because these custom
properties are declared on #dcf-container and do not reach inside the form.
5.6:1 on white, which passes AA at 12px. */
#wpdcom .comment-rules {
margin: 12px 0 0;
line-height: 1.45;
}
#wpdcom .comment-rules small {
font-size: 12px;
font-style: italic;
color: #6c655b;
}
/* The comment section's own background.
wpDiscuz has a Custom CSS box in its settings, and on this fleet it was used
to paint the whole comment area — alemimenam.com carries
`.comments-area{width:auto;background-color:#f0ffe6;padding:10px}`, printed
inline as wpdiscuz-frontend-css-inline-css. It is per-site data in the
wpDiscuz options rather than code, and the colour is not the same on every
site.
Removed here rather than by editing each site's setting, for two reasons.
Editing wpDiscuz options means a read-modify-write on serialised data, which
has already broken a comment form on this network once. And a per-site fix is
exactly what this section exists to stop: the whole point of consolidating 26
files was that a rule true everywhere should be written once.
`transparent`, not a colour of our own. The section then shows whatever the
page behind it shows, which is the site's real background — the blocks above
the form inherit their type from the theme and now sit on the theme's own
surface too, instead of on a tint chosen years ago in a settings box.
The padding is deliberately left alone. It is spacing, not colour, and with
no background to define an edge it costs nothing to keep. */
.comments-area {
background-color: transparent !important;
}