diff options
| author | bt <bt@btxx.org> | 2024-06-08 13:22:19 -0400 |
|---|---|---|
| committer | bt <bt@btxx.org> | 2024-06-08 13:22:19 -0400 |
| commit | dcfb172704f3afb68a30425029ec834be2883274 (patch) | |
| tree | 02ac480745db802d7af03f3213a0c568322170e3 /build/lazy-dev-dark-mode/index.html | |
| parent | e146f8a64c793c337999ce316b16ebe5fe6f2dab (diff) | |
More content porting, on-going markdown changes for lowdown support
Diffstat (limited to 'build/lazy-dev-dark-mode/index.html')
| -rw-r--r-- | build/lazy-dev-dark-mode/index.html | 46 |
1 files changed, 31 insertions, 15 deletions
diff --git a/build/lazy-dev-dark-mode/index.html b/build/lazy-dev-dark-mode/index.html index f73276f..65d075f 100644 --- a/build/lazy-dev-dark-mode/index.html +++ b/build/lazy-dev-dark-mode/index.html @@ -1,42 +1,58 @@ <!doctype html> -<html lang="en" id="top"> +<html lang="en"> <head> <meta charset="utf-8"> <meta name="viewport" content="width=device-width, initial-scale=1"> <link rel="icon" href="data:,"> <title>The Lazy Developer's Dark Mode</title> - <link href="https://bt.ht/atom.xml" type="application/atom+xml" rel="alternate" title="Atom feed for blog posts" /> - <style>*{box-sizing:border-box;}body{font-family:sans-serif;margin:0 auto;max-width:650px;padding:1rem;}img{max-width:100%;}pre{overflow:auto;}table{text-align:left;width:100%;}</style> + <link href="/atom.xml" type="application/atom+xml" rel="alternate" title="Atom feed for blog posts" /> + <link href="/rss.xml" type="application/rss+xml" rel="alternate" title="RSS feed for blog posts" /> +<style>*{box-sizing:border-box;}body{font-family:sans-serif;line-height:1.33;margin:0 auto;max-width:650px;padding:1rem;}img{max-width:100%;}pre{border:1px solid;overflow:auto;padding:5px;}table{text-align:left;width:100%;}.footnotes{font-size:90%;}</style> </head> <nav> - <a href="#menu">Menu ↓</a> + <a href="#menu">Menu ↓</a> </nav> <main> -<h1>The Lazy Developer's Dark Mode</h1> +<h1 id="the-lazy-developers-dark-mode">The Lazy Developer’s Dark Mode</h1> + <p>2021-04-12</p> + <p>After recently jumping back to Jekyll for my personal blog, I decided to take a closer look at how I was supporting <code>dark mode</code> for my visitors. I was using the proper CSS query to target those who had system-wide dark mode enabled, but I found that the code had far too many caveats and targeted too many custom classes.</p> -<p>So I thought to myself, "There <em>has</em> to be a simpler way..."</p> -<h2>Introducing Dark Mode - The Lazy Way</h2> -<p>Here is the default dark mode for my current website in all it's glory:</p> + +<p>So I thought to myself, “There <em>has</em> to be a simpler way…”</p> + +<h2 id="introducing-dark-mode---the-lazy-way">Introducing Dark Mode - The Lazy Way</h2> + +<p>Here is the default dark mode for my current website in all it’s glory:</p> + <pre><code>@media (prefers-color-scheme: dark) { body{background:#2d2d2d;filter:invert(1);} img,.cp_embed_wrapper,pre{filter:invert(1);} } </code></pre> -<p>Not much to look at, eh? Well, let's still break it down.</p> -<p>First we set the <code>body</code> to use a nice dark background color (avoid using <code>#000000</code> directly since that can cause some minor eye strain). Next we tell the browser to invert all the child elements by using <code>filter:invert(1)</code>. At this point, you could consider your work done - but there are some edge case elements...</p> -<h2>Images, CodePens & Code - Oh My!</h2> -<p>Most of my articles on this site will include either an image(s), embedded CodePen examples or code snippets directly in the page. For these elements we probably <em>don't</em> want to invert their color/text etc. All we need to do is run the filter property on these a second time (<em>after</em> the main <code>body</code> attribute):</p> + +<p>Not much to look at, eh? Well, let’s still break it down.</p> + +<p>First we set the <code>body</code> to use a nice dark background color (avoid using <code>#000000</code> directly since that can cause some minor eye strain). Next we tell the browser to invert all the child elements by using <code>filter:invert(1)</code>. At this point, you could consider your work done - but there are some edge case elements…</p> + +<h2 id="images-codepens-code---oh-my">Images, CodePens & Code - Oh My!</h2> + +<p>Most of my articles on this site will include either an image(s), embedded CodePen examples or code snippets directly in the page. For these elements we probably <em>don’t</em> want to invert their color/text etc. All we need to do is run the filter property on these a second time (<em>after</em> the main <code>body</code> attribute):</p> + <pre><code>@media (prefers-color-scheme: dark) { img,.cp_embed_wrapper,pre{filter:invert(1);} } </code></pre> + <p>Of course, YMMV depending on what other custom elements you want to avoid inverting.</p> -<h2>Minor Caveats</h2> -<p>I should mention that since my website doesn't use any custom coloring for anchor links, inverting <code>ahref</code> elements works out of the box. Certain projects might still require some custom overrides if the inverted version of a certain custom color looks poor.</p> -<p>That's it - enjoy being lazy!</p> + +<h2 id="minor-caveats">Minor Caveats</h2> + +<p>I should mention that since my website doesn’t use any custom coloring for anchor links, inverting <code>ahref</code> elements works out of the box. Certain projects might still require some custom overrides if the inverted version of a certain custom color looks poor.</p> + +<p>That’s it - enjoy being lazy!</p> <footer role="contentinfo"> <h2>Menu Navigation</h2> <ul id="menu"> |