/* Root baseline only for CKEditor's design view - everything else (h1-h6, p,
   tables, lists, etc) used to be duplicated here too, .ck-content-prefixed,
   but that meant this file's rules always outranked a template's own CSS:
   @scope(.ck-content) (which contentEditor.js's window.contentEditorInjectStyles
   uses to inject a template's saved style, per document, into the designer)
   does NOT add the scope root to a selector's specificity, so a template's
   own bare `h1 { ... }` (specificity 0,0,1) always lost to this file's
   `.ck-content h1 { ... }` (0,1,1), regardless of cascade order - a plain
   class on an h1 couldn't win either. Every one of those rules already has
   an equivalent in wwwroot/script/pwd/pamphletMgr.js's _defaultDesignCss
   (the single canonical copy of a new template's default CSS, injected the
   same @scope way as any other saved style), so removing them here just lets
   that already-present, already-injected content style through - the
   Designer now renders new templates exactly as pamphletMgr.js declares them,
   and a template's own overrides finally take effect over the default. Only
   this root rule is left, since .ck-content itself is CKEditor's own class,
   not something a template's saved CSS would ever target directly - keeping
   a baseline here (rather than nothing) means a template with NO style
   content at all (or before any document has loaded) still gets sane
   defaults instead of raw browser styles. Prefix .ck-content beats AdminLTE
   element/single-class rules. */
.ck-content {
    font-family: sans-serif;
    font-size: 12pt;
    font-weight: normal;
    font-style: normal;
    color: #000;
    line-height: 1.4;
    text-decoration: none;
    margin: 10pt 20pt;
}

.content-fields .ck-content {
    margin: 0;
}