<?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>Digital Tools on D. Sébastien Taggart</title>
    <link>https://www.sebastientaggart.com/categories/digital-tools/</link>
    <description>Recent content in Digital Tools 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/categories/digital-tools/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>
    <item>
      <title>Search Without Being Tracked with Searx</title>
      <link>https://www.sebastientaggart.com/writing/search-without-being-tracked-with-searx/</link>
      <pubDate>Tue, 08 Jun 2021 21:10:29 +0000</pubDate>
      <guid>https://www.sebastientaggart.com/writing/search-without-being-tracked-with-searx/</guid>
      <description>&lt;p&gt;Searx has garnered attention as a robust solution for privacy-conscious users. As the documentation aptly states:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Searx is a free internet metasearch engine that aggregates results from more than 70 search services. Users are neither tracked nor profiled. Additionally, Searx can be used over Tor for online anonymity.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Even if privacy isn’t your primary concern, the search experience Searx offers is refreshingly superior to that of ad-driven giants like Google. Today, we&amp;rsquo;re going to set up Searx in a way that respects your privacy while providing a seamless search experience.&lt;/p&gt;</description>
      <content:encoded><![CDATA[<p>Searx has garnered attention as a robust solution for privacy-conscious users. As the documentation aptly states:</p>
<blockquote>
<p>Searx is a free internet metasearch engine that aggregates results from more than 70 search services. Users are neither tracked nor profiled. Additionally, Searx can be used over Tor for online anonymity.</p>
</blockquote>
<p>Even if privacy isn’t your primary concern, the search experience Searx offers is refreshingly superior to that of ad-driven giants like Google. Today, we&rsquo;re going to set up Searx in a way that respects your privacy while providing a seamless search experience.</p>
<h3 id="setting-up-searx">Setting Up Searx</h3>
<p>Let’s lay out a few foundational assumptions:</p>
<ul>
<li>We’ll be self-hosting Searx using Docker and Docker Compose.</li>
<li>The Searx container will run behind a reverse proxy that’s already configured.</li>
</ul>
<p>The official Docker Compose example offers a good starting point, but we’ll simplify it for our purposes. The following configuration avoids unnecessary complexity:</p>
<pre tabindex="0"><code>version: &#39;3.7&#39;

services:

  searx:
    image: searx/searx:1.0.0-151-c5d63a5c
    container_name: searx
    restart: unless-stopped
    ports:
      - &#39;8086:8080&#39;
    volumes:
      - &#39;./data/searx:/etc/searx&#39;
    environment:
      - BASE_URL=https://search.YOURDOMAIN.com/
    cap_drop:
      - ALL
    cap_add:
      - CHOWN
      - SETGID
      - SETUID
      - DAC_OVERRIDE
</code></pre><p>Notice we specify the actual image tag (<code>1.0.0-151-c5d63a5c</code>) rather than using <code>latest</code>. This practice ensures deliberate upgrades and reduces the risk of unexpected changes. Additionally, adjust the port <code>8086</code> to align with your reverse proxy configuration.</p>
<p>After executing <code>docker-compose up -d</code>, you can customize your Searx settings by editing <code>./data/searx/settings.yml</code>. Here are a few key configurations to consider:</p>
<ul>
<li>Change <code>instance_name: &quot;searx&quot;</code> to a name that resonates with you.</li>
<li>Set <code>enable_stats: True</code> to activate a nifty stats page—just be aware that it may inadvertently leak usage data.</li>
<li>Update the <code>secret_key:</code> value to something unique and secure.</li>
<li>Modify <code>method: &quot;GET&quot;</code> to ensure compatibility with Firefox’s address bar searches. Note that changing this in the GUI alone won&rsquo;t suffice.</li>
</ul>
<p>After saving your changes, run <code>docker-compose down &amp;&amp; docker-compose up -d</code> to apply them. You should now have your private search page up and running!</p>
<h3 id="integrating-searx-with-firefox">Integrating Searx with Firefox</h3>
<p>To streamline your search experience, add your new Searx instance as a default search engine in Firefox:</p>
<ol>
<li>Navigate to settings and select “Search.”</li>
<li>Click “Add search engine” and provide the following details:
<ul>
<li>Name: <code>searx</code> (or your preferred label)</li>
<li>Search string: <code>https://search.YOURDOMAIN.com/search?q=%s</code></li>
</ul>
</li>
<li>Save your new search engine (look for the checkmark icon) and set it as the default.</li>
</ol>
<p>Similar steps apply for Chromium and other browsers, ensuring a unified search experience across platforms.</p>
<h3 id="the-benefits-of-searx">The Benefits of Searx</h3>
<p>After using Searx for a few days, I was pleasantly surprised by how enjoyable the user experience can be without the profit motive. Unlike Google and others, which often prioritize ad revenue over user needs, Searx focuses solely on delivering relevant information.</p>
<p>Of course, there is a trade-off: search results may take 2-3 seconds to load, compared to Google’s sub-second speed. However, this is a small price to pay for the wealth of benefits it offers:</p>
<ul>
<li><strong>Granular Control</strong>: Under <code>preferences</code>, you can customize categories, themes, behaviors, and much more.</li>
<li><strong>Unfiltered Results</strong>: Unlike Google, which tailors results based on a user profile, Searx allows you to dictate your search experience.</li>
<li><strong>Category Filtering</strong>: The ability to filter results by categories (General, Files, Images, etc.) is incredibly powerful. It’s a feature you didn’t realize you needed until you experience it.</li>
</ul>
<p>To put it simply: obtaining unfiltered results on a platform I control feels like liberation after a long confinement. It’s a refreshing experience.</p>
<h3 id="the-bigger-picture">The Bigger Picture</h3>
<p>I firmly believe that every individual should actively resist the gradual erosion of privacy. In an online landscape dominated by monopolies, there exists immense pressure to monetize every digital footprint. This loss of privacy occurs incrementally, often unnoticed, making it essential to reclaim it piece by piece wherever possible.</p>
<p>Online search serves as the gateway to a vast array of information and services. It’s a critical first step in regaining control over your digital life and ensuring your privacy. By choosing Searx, you take a meaningful step toward a more private and empowered online experience.</p>
]]></content:encoded>
    </item>
    <item>
      <title>Taming Google Search Results With uBlock Origin</title>
      <link>https://www.sebastientaggart.com/writing/taming-google-search-results-with-ublock-origin/</link>
      <pubDate>Mon, 04 Mar 2019 13:19:50 -0500</pubDate>
      <guid>https://www.sebastientaggart.com/writing/taming-google-search-results-with-ublock-origin/</guid>
      <description>&lt;p&gt;Web advertising has become an unwieldy beast. What began as a means to support quality content has morphed into a cumbersome, privacy-invading presence that often detracts from the ideals of the internet. Fortunately, we have powerful tools at our disposal to combat this trend. Enter &lt;strong&gt;uBlock Origin&lt;/strong&gt;, a versatile content blocker that excels at more than just blocking ads.&lt;/p&gt;
&lt;p&gt;At its core, uBlock Origin allows you to customize your browsing experience by blocking any content on a site of your choosing. For instance, when you fire up a Google search, the default view may include distractions like embedded ads and extraneous suggestions. Let’s explore how uBlock can help streamline your search results for a cleaner, more focused experience.&lt;/p&gt;</description>
      <content:encoded><![CDATA[<p>Web advertising has become an unwieldy beast. What began as a means to support quality content has morphed into a cumbersome, privacy-invading presence that often detracts from the ideals of the internet. Fortunately, we have powerful tools at our disposal to combat this trend. Enter <strong>uBlock Origin</strong>, a versatile content blocker that excels at more than just blocking ads.</p>
<p>At its core, uBlock Origin allows you to customize your browsing experience by blocking any content on a site of your choosing. For instance, when you fire up a Google search, the default view may include distractions like embedded ads and extraneous suggestions. Let’s explore how uBlock can help streamline your search results for a cleaner, more focused experience.</p>
<h3 id="the-challenge-with-google-search">The Challenge with Google Search</h3>
<p>Take a look at the default Google search page. You might find the &ldquo;People also search for&rdquo; suggestions cluttering your results.</p>
<p><img alt="Before uBlock Origin" loading="lazy" src="images/Taming-Google-Search-Results-with-uBlock-Origin-bf77a783.png"></p>
<p>This feature can disrupt the flow of information. Not only does it often pop up in unexpected locations, but I’ve personally never found these suggestions helpful — and I suspect you might feel the same way.</p>
<h3 id="a-solution-with-ublock-origin">A Solution with uBlock Origin</h3>
<p>The good news is that uBlock Origin allows you to block these pesky features. Here’s how to tidy up your Google search results:</p>
<ol>
<li>
<p>Open the uBlock Origin settings.</p>
<p><img alt="uBlock Origin Settings" loading="lazy" src="images/Taming-Google-Search-Results-with-uBlock-Origin-09.png"></p>
</li>
<li>
<p>Click on &ldquo;My Filters.&rdquo;</p>
<p><img alt="My Filters" loading="lazy" src="images/Taming-Google-Search-Results-with-uBlock-Origin-a082544b.png"></p>
</li>
<li>
<p>Add the following code to your filters:</p>
<pre tabindex="0"><code>! https://www.google.com/search
www.google.com##.exp-outline
www.google.com##[style=&#34;display: block; opacity: 1;&#34;]
www.google.com##[data-hveid]&gt;div:style(height: auto !important)
</code></pre></li>
</ol>
<p>And just like that, the &ldquo;People also search for&rdquo; feature is gone!</p>
<h3 id="bonus-blocking-people-also-ask">Bonus: Blocking &ldquo;People Also Ask&rdquo;</h3>
<p>If you&rsquo;re looking for an even cleaner experience, you can easily block the &ldquo;People also ask&rdquo; section as well by adding this line:</p>
<pre tabindex="0"><code>www.google.com##div:has(&gt;div&gt;div&gt;div&gt;h2:has-text(People also ask))
</code></pre><h3 id="the-result">The Result</h3>
<p>With these adjustments, your Google search results will resemble a simpler, more straightforward format reminiscent of the mid-2000s — a time when the internet felt less cluttered.</p>
<p><img alt="After uBlock Origin" loading="lazy" src="images/Taming-Google-Search-Results-with-uBlock-Origin-c11bc11a.png"></p>
<h3 id="conclusion">Conclusion</h3>
<p>In a world where our attention is constantly being pulled in multiple directions, tools like uBlock Origin empower us to reclaim our browsing experience. By eliminating distractions, we can focus on what truly matters: finding the information we seek.</p>
<p>So, take a moment to explore uBlock Origin’s capabilities. You might just find that a cleaner digital landscape enhances not only your productivity but also your overall online experience. Happy searching!</p>
]]></content:encoded>
    </item>
  </channel>
</rss>
