aboutsummaryrefslogtreecommitdiff
path: root/build/menu-toggle-css
diff options
context:
space:
mode:
Diffstat (limited to 'build/menu-toggle-css')
-rw-r--r--build/menu-toggle-css/index.html106
1 files changed, 58 insertions, 48 deletions
diff --git a/build/menu-toggle-css/index.html b/build/menu-toggle-css/index.html
index fb941a8..3bb096e 100644
--- a/build/menu-toggle-css/index.html
+++ b/build/menu-toggle-css/index.html
@@ -1,62 +1,67 @@
<!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>Menu Toggle with Pure CSS</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 &darr;</a>
+ <a href="#menu">Menu &darr;</a>
</nav>
<main>
-<h1>Menu Toggle with Pure CSS</h1>
+<h1 id="menu-toggle-with-pure-css">Menu Toggle with Pure CSS</h1>
+
<p>2020-10-19</p>
+
<p>When thinking through navigation designs for mobile devices sometimes the best option is to store away the content behind a toggle button. This button would then display the menu items upon interaction. Let me show you how to create such an element with only CSS - no need for JavaScript today!</p>
-<h2>Before we begin</h2>
-<p>I would like to point out that the concept of "toggling" the main menu (even for mobile) is not always the best solution. If you're interested, you can take a look at a previous article I wrote explaining why: <a href="/hamburger-menu-alternative.html">Using Hamburger Menus? Try Sausage Links</a></p>
-<p>Now that we have mentioned possible pitfalls of relying so heavily on toggle menus, let's build one!</p>
-<h2>Our Final Product</h2>
+
+<h2 id="before-we-begin">Before we begin</h2>
+
+<p>I would like to point out that the concept of &#8220;toggling&#8221; the main menu (even for mobile) is not always the best solution. If you&#8217;re interested, you can take a look at a previous article I wrote explaining why: <a href="/hamburger-menu-alternative.html">Using Hamburger Menus? Try Sausage Links</a></p>
+
+<p>Now that we have mentioned possible pitfalls of relying so heavily on toggle menus, let&#8217;s build one!</p>
+
+<h2 id="our-final-product">Our Final Product</h2>
+
<p><img src="/public/images/menu-toggle-css.png" alt="Menu toggle made from pure CSS" /></p>
+
<p><a href="https://codepen.io/bradleytaunt/pen/mdEEvEX">Live CodePen Example</a></p>
-<h2>The HTML</h2>
-<p>To implement this design you really don't need much in terms of HTML:</p>
+
+<h2 id="the-html">The HTML</h2>
+
+<p>To implement this design you really don&#8217;t need much in terms of HTML:</p>
+
<ul>
-<li>A single <code>checkbox</code> input</li>
-<li>A <code>label</code> that corresponds to the <code>checkbox</code></li>
-<li>A <code>nav</code> element to house our unordered list items</li>
+<li><p>A single <code>checkbox</code> input</p></li>
+<li><p>A <code>label</code> that corresponds to the <code>checkbox</code></p></li>
+<li><p>A <code>nav</code> element to house our unordered list items</p>
+
+<p>Menu</p></li>
</ul>
-<pre><code>&lt;!-- The checkbox input &amp; label partner --&gt;
-&lt;input type=&quot;checkbox&quot; id=&quot;menu-toggle&quot;&gt;
-&lt;label for=&quot;menu-toggle&quot;&gt;Menu&lt;/label&gt;
-
-&lt;!-- The navigation we wish to toggle --&gt;
-&lt;nav&gt;
- &lt;ul&gt;
- &lt;li&gt;&lt;a href=&quot;&quot;&gt;Home&lt;/a&gt;&lt;/li&gt;
- &lt;li&gt;&lt;a href=&quot;&quot;&gt;About&lt;/a&gt;&lt;/li&gt;
- &lt;li&gt;&lt;a href=&quot;&quot;&gt;Articles&lt;/a&gt;&lt;/li&gt;
- &lt;li&gt;&lt;a href=&quot;&quot;&gt;Colophon&lt;/a&gt;&lt;/li&gt;
- &lt;li&gt;&lt;a href=&quot;&quot;&gt;Contact&lt;/a&gt;&lt;/li&gt;
- &lt;/ul&gt;
-&lt;/nav&gt;
-</code></pre>
-<p>That's it!</p>
-<h2>The CSS</h2>
-<p>The first thing we need to do is "hide" the <code>checkbox</code> input element. It's important to avoid using <code>display: none</code> or <code>visibility: hidden</code> in order to achieve this. Those CSS properties can negatively impact accessibility (specifically screen readers). So we will be relying on the <code>position</code>, <code>z-index</code> and <code>opacity</code> properties to help us out.</p>
-<pre><code>/* Set the input position to absolute, send it off screen with zero opacity */
-input[type=&quot;checkbox&quot;] {
+
+<p>That&#8217;s it!</p>
+
+<h2 id="the-css">The CSS</h2>
+
+<p>The first thing we need to do is &#8220;hide&#8221; the <code>checkbox</code> input element. It&#8217;s important to avoid using <code>display: none</code> or <code>visibility: hidden</code> in order to achieve this. Those CSS properties can negatively impact accessibility (specifically screen readers). So we will be relying on the <code>position</code>, <code>z-index</code> and <code>opacity</code> properties to help us out.</p>
+
+<pre><code>&#47;* Set the input position to absolute, send it off screen with zero opacity *&#47;
+input[type="checkbox"] {
left: -9999px;
opacity: 0;
position: absolute;
}
</code></pre>
+
<p>Then we give our corresponding <code>label</code> a minor face-lift to make it appear more button-like:</p>
-<pre><code>/* Minor visual styling to make the label more button-y */
+
+<pre><code>&#47;* Minor visual styling to make the label more button-y *&#47;
label {
border: 1px solid currentColor;
border-radius: 4px;
@@ -64,26 +69,31 @@ label {
padding: 10px;
}
</code></pre>
-<p>For our main <code>nav</code> element, we want to set it's position to <code>absolute</code> in order to avoid any janky page rendering issues that might occur when toggling the menu:</p>
+
+<p>For our main <code>nav</code> element, we want to set it&#8217;s position to <code>absolute</code> in order to avoid any janky page rendering issues that might occur when toggling the menu:</p>
+
<p>`
-</p>
-<pre><code>/* Set nav to absolute (avoids odd page rendering space pop-in) */
-nav {
- opacity: 0;
- position: absolute;
- z-index: -2;
-}
-</code></pre>
+ &#47;* Set nav to absolute (avoids odd page rendering space pop-in) *&#47;
+ nav {
+ opacity: 0;
+ position: absolute;
+ z-index: -2;
+ }</p>
+
<p>The last step is to actually <em>show</em> the menu if the user toggles the <code>checkbox</code>:</p>
-<pre><code>/* Show nav when checkbox is checked */
-input[type=&quot;checkbox&quot;]:checked ~ nav {
+
+<pre><code>&#47;* Show nav when checkbox is checked *&#47;
+input[type="checkbox"]:checked ~ nav {
opacity: 1;
z-index: 1;
}
</code></pre>
+
<p>It might not look like much, but you now have a fully functional menu toggle - <strong>made with pure CSS</strong>! </p>
-<h2>With Great Power...</h2>
-<p>Although this design is very simple to implement, please remember to use these types of menus wisely. Just because you <em>can</em> do something, doesn't always mean you <em>should</em>.</p>
+
+<h2 id="with-great-power">With Great Power&#8230;</h2>
+
+<p>Although this design is very simple to implement, please remember to use these types of menus wisely. Just because you <em>can</em> do something, doesn&#8217;t always mean you <em>should</em>.</p>
<footer role="contentinfo">
<h2>Menu Navigation</h2>
<ul id="menu">