<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Cms on D. Sébastien Taggart</title>
    <link>https://www.sebastientaggart.com/tags/cms/</link>
    <description>Recent content in Cms on D. Sébastien Taggart</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sun, 04 Oct 2026 22:13:05 -0400</lastBuildDate>
    <atom:link href="https://www.sebastientaggart.com/tags/cms/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Building the Ultimate Content Editor Experience in a CMS</title>
      <link>https://www.sebastientaggart.com/writing/building-the-ultimate-content-editor-experience-in-a-cms/</link>
      <pubDate>Tue, 02 Jul 2024 21:15:54 -0400</pubDate>
      <guid>https://www.sebastientaggart.com/writing/building-the-ultimate-content-editor-experience-in-a-cms/</guid>
      <description>Principles and feature buckets that keep a rich text editor trustworthy for authors, aligned with the live site, and usable under Section 508.</description>
      <content:encoded><![CDATA[<p>Most CMS projects treat the editor as a checkbox. Pick CKEditor or TinyMCE, wire a media library if you are lucky, and call it done. Then the help desk tickets start: &ldquo;Why does my table look different on the page?&rdquo; &ldquo;I pasted from Word and the whole section broke.&rdquo; &ldquo;Screen reader users say the accordion is unreadable.&rdquo; I have been on both sides of that (the person filing the ticket and the person explaining why WYSIWYG is a lie). The editor is where content quality and accessibility are won or lost before anything ships.</p>
<p>Here is how I think about building an editor experience that authors will actually use without breaking the site, and that auditors will not torch in a 508 review.</p>
<h2 id="principles-that-actually-constrain-design">Principles that actually constrain design</h2>
<p><strong>Simplicity</strong> sounds obvious until you add every toolbar button a power user asked for in a requirements workshop. My bias: default to a short toolbar and progressive disclosure. If a control does not apply to most pages, it belongs in a secondary panel or a structured field, not next to Bold. Fewer choices means fewer wrong choices.</p>
<p><strong>Impossible to break</strong> is not literal (authors are creative), but the goal is valid output. That usually means constraining the schema: allowed tags, allowed classes, sanitization on save, and patterns that map cleanly to your theme. If someone can paste arbitrary HTML from a random website and have it stick, you do not have an editor; you have a footgun with a blinking cursor.</p>
<p><strong>Perfect previews</strong> are the hardest item on the list. &ldquo;What you see is what you get&rdquo; is only honest if the iframe (or live preview route) loads the same CSS, typography, spacing tokens, and component markup as production. If preview runs against a stripped admin theme, you are training authors to distrust the tool. I treat preview parity as a build pipeline problem, not a nice-to-have.</p>
<p><strong>Familiarity</strong> is cheaper than novelty. Bold looks like bold, lists look like lists, link dialogs look like the link dialogs people know from Google Docs or Word. Custom iconography for standard actions is how you get &ldquo;where is underline?&rdquo; in every training session.</p>
<p><strong>508 compliance</strong> is not a bolt-on color contrast pass at the end. It is keyboard operability for every control in the chrome, visible focus, text alternatives for images at insert time, table headers that survive round-trips, and collapsible regions that expose state to assistive tech. If your accordion widget relies on click-only divs with no role or name, you have built technical debt that WCAG will find.</p>
<h2 id="image-management-and-embedding">Image management (and embedding)</h2>
<p>Authors need crop, resize, focal point, and alt text in the flow where they insert the image, not in a separate &ldquo;fix accessibility later&rdquo; queue. Drag-and-drop is fine if the same fields appear for uploads and library picks. Lazy loading and <code>srcset</code> should be automatic; the author should not hand-edit attributes.</p>
<p>I also like forcing a decision on decorative images (empty alt with a real checkbox) so people do not default to filename-as-alt-text, which is a classic 508 fail in the wild.</p>
<h2 id="file-management-and-embedding">File management (and embedding)</h2>
<p>PDFs and Office files are where CMSs quietly become file shares. If you allow arbitrary uploads from the body field, you get duplicate assets, stale versions, and broken links after migrations. A dedicated media or document entity with a stable URL, virus scanning if you are in a regulated environment, and a picker that inserts a shortcode or structured link beats &ldquo;attach whatever.&rdquo;</p>
<p>For federal-ish work, think about whether the file should open in a new tab, whether you need a file type and size label next to the link, and whether the title text is meaningful (not <code>FINAL_v7_really.pdf</code>).</p>
<h2 id="tables-sortable-interactive-compliant">Tables (sortable, interactive, compliant)</h2>
<p>Tables are the #1 source of &ldquo;looks fine in the editor&rdquo; grief. Authors merge cells because Excel trained them to; then responsive CSS and screen readers suffer.</p>
<p>My hierarchy: (1) simple data tables with explicit header rows and no layout tables in the body, (2) optional sorting or filtering only if you have a component that preserves <code>&lt;th scope&gt;</code> relationships and does not rely on hover alone, (3) if you need pivot-level behavior, that is probably not inline rich text; it is a block, a view, or an embed.</p>
<p>Interactive tables also need a plan for mobile (horizontal scroll with a visible cue, or reflow) and for keyboard users (sort controls must be focusable buttons, not mystery clicks on <code>&lt;th&gt;</code>).</p>
<h2 id="accordions-and-collapsible-content">Accordions and collapsible content</h2>
<p>Collapsible sections are great for long policy pages and terrible when implemented as anonymous divs with a chevron image. Use a pattern with <code>button</code> triggers, <code>aria-expanded</code>, and an associated region id. Keyboard support should mirror disclosure widgets in the ARIA authoring practices guide.</p>
<p>From an editor UX angle, treat accordion as a structured block (Gutenberg-style, Layout Builder section, whatever your stack supports) instead of free-form HTML. That keeps markup consistent and previews honest.</p>
<h2 id="formatting-and-cleanup">Formatting and cleanup</h2>
<p>Bold, italic, underline, links, headings, lists, blockquote: ship the boring set first. &ldquo;Clear formatting&rdquo; and &ldquo;paste as plain text&rdquo; (or paste filtering) save more production bugs than another alignment option. Paste from Word is a product feature; test it with real government templates and tables.</p>
<p>If you support subscript or strikethrough for legal or scientific content, expose them; if you do not need them, hide them so authors do not build layouts out of character-level styling.</p>
<h2 id="pre-styled-body-content-callouts-boxes-div-based-patterns">Pre-styled body content (callouts, boxes, div-based patterns)</h2>
<p>Callout boxes (&ldquo;blue half-width note,&rdquo; warning panels, pull quotes) should not be &ldquo;paste this div from the wiki.&rdquo; They should be either (a) a small set of allowed wrapper classes your CSS documents, inserted through a dropdown the editor understands, or (b) custom components with their own fields. Half-width layouts need a grid or breakpoint story on small screens (usually full width below a breakpoint), or mobile users eat the cost.</p>
<p>Whatever you do, avoid unbounded class names in the body. Whitelist classes, map them to components, and validate on save. That is how you keep the experience &ldquo;impossible to break&rdquo; without turning authors into front-end developers.</p>
<p>The editor worth shipping is not the one with the most buttons. It is the one where authors recognize the interface, the preview matches what visitors see, and the output is boring enough for automated checks and screen readers to handle. I am still looking for a stack that nails all of that without custom glue; if you have one, I would like to hear about it.</p>
]]></content:encoded>
    </item>
  </channel>
</rss>
