aboutsummaryrefslogtreecommitdiff
path: root/build/posts/wp-enqueue-for-beginners/index.html
diff options
context:
space:
mode:
Diffstat (limited to 'build/posts/wp-enqueue-for-beginners/index.html')
-rw-r--r--build/posts/wp-enqueue-for-beginners/index.html103
1 files changed, 103 insertions, 0 deletions
diff --git a/build/posts/wp-enqueue-for-beginners/index.html b/build/posts/wp-enqueue-for-beginners/index.html
new file mode 100644
index 0000000..a74b8c1
--- /dev/null
+++ b/build/posts/wp-enqueue-for-beginners/index.html
@@ -0,0 +1,103 @@
+<!doctype html>
+<html lang="en">
+<head>
+ <meta charset="utf-8">
+ <meta name="viewport" content="width=device-width, initial-scale=1">
+ <meta name="color-scheme" content="dark light">
+ <link rel="icon" href="data:,">
+ <title>WP Enqueue for Beginners</title>
+ <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;}blockquote{background:rgba(0,0,0,0.1);border-left:4px solid;padding-left:5px;}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>
+</nav>
+
+<main>
+<h1 id="wp-enqueue-for-beginners">WP Enqueue for Beginners</h1>
+<p>2020-05-05</p>
+<p>Throughout my career designing, developing and auditing WordPress themes, I&#8217;ve come across many that include their custom styles &#47; scripts as static HTML elements inside their respective <code>header</code> and <code>footer</code> templates. This is perfectly <em>fine</em>, but there is a cleaner way to include these files.</p>
+<p>This post is purposefully catered for WordPress beginners, so if this seems overly simple, then you&#8217;re probably already developing WordPress themes that utilize these techniques. (Which is awesome!)</p>
+<h2 id="introducing-wp-enqueue">Introducing WP Enqueue</h2>
+<p>The description of Wp Enqueue from the WordPress documentation:</p>
+<p>In a nutshell: Placing a <code>wp_enqueue_script</code> or <code>wp_enqueue_style</code> script in the <code>functions.php</code> of your custom theme tells WordPress to pull external files into the header or footer of your website. Best practice being: <em>styles into the header, scripts into the footer</em>.</p>
+<p>I suggest you read the official documentation for more details: <a href="https://developer.wordpress.org/reference/functions/wp_enqueue_script/">wp_enqueue_script</a> and <a href="https://developer.wordpress.org/reference/functions/wp_enqueue_style/">wp_enqueue_style</a>.</p>
+<h2 id="enqueue-stylesheets">Enqueue Stylesheets</h2>
+<p>The default script to enqueue a CSS stylesheet:</p>
+<pre><code>wp_enqueue_style( $handle, $src, $deps, $ver, $media );
+</code></pre>
+<ul>
+<li><code>$handle</code> - the name associated with your stylesheet</li>
+<li><code>$src</code> - URL pointing to the directory of the stylesheet itself</li>
+<li><code>$deps</code> - An array of any other stylesheets needed as dependencies</li>
+<li><code>$ver</code> - The version number of the stylesheet (used for cache busting)</li>
+<li><code>$media</code> - Specify media type (<code>all</code>, <code>print</code>, <code>screen</code>, etc.)</li>
+</ul>
+<p>So, with all those parameters in mind, here is what a standard default enqueue of a CSS stylesheet looks like:</p>
+<pre><code>wp_enqueue_style( &#39;google-fonts&#39;, &#39;https:&#47;&#47;fonts.googleapis.com&#47;css?family=Montserrat:200,300,300i,400,600,700,800,900&#39;, &#39;&#39;, &#39;1.0&#39;, &#39;&#39;);
+</code></pre>
+<p>In this example we have rendered the following:</p>
+<ul>
+<li><code>$handle</code>: google-fonts</li>
+<li><code>$src</code>: <a href="https://fonts.googleapis.com/css?family=Montserrat:200,300,300i,400,600,700,800-">https:&#47;&#47;fonts.googleapis.com&#47;css?family=Montserrat:200,300,300i,400,600,700,800-</a> 0</li>
+<li><code>$deps</code>: Null (left blank)</li>
+<li><code>$ver</code>: 1.0</li>
+<li><code>$media</code>: Null (left blank)</li>
+</ul>
+<p><strong>Important:</strong> Keep in mind that the <code>wp_enqueue_style</code> script will render the stylesheet link into the WordPress header automatically.</p>
+<h2 id="enqueue-scripts">Enqueue Scripts</h2>
+<p>The default script to enqueue an external JS file:</p>
+<pre><code>wp_enqueue_script( $handle, $src, $deps, $ver, $in_footer );
+</code></pre>
+<ul>
+<li><code>$handle</code> - the name associated with your script</li>
+<li><code>$src</code> - URL pointing to the directory of the script itself</li>
+<li><code>$deps</code> - An array of any other scripts needed as dependencies</li>
+<li><code>$ver</code> - The version number of the script (used for cache busting)</li>
+<li><code>$in_footer</code> - Set whether the script is loaded in the <code>&#60;head&#62;</code> or just before the <code>&#60;&#47;body&#62;</code></li>
+</ul>
+<p>With all those parameters in mind, here is what a standard default enqueue of a Javascript file looks like:</p>
+<pre><code>wp_enqueue_script( &#39;bxslider&#39;, get_template_directory_uri() . &#39;&#47;js&#47;bxslider.js&#39;, array(&#39;jquery&#39;), &#39;1.0.0&#39;, true );
+</code></pre>
+<p>In this example we have rendered the following:</p>
+<ul>
+<li><code>$handle</code>: bxslider</li>
+<li><code>$src</code>: get_template_directory_uri() . &#47;js&#47;bxslider.js&#8217;</li>
+<li><code>$deps</code>: array(jquery&#8217;)</li>
+<li><code>$ver</code>: 1.0.0</li>
+<li><code>$in_footer</code>: True (<em>places script before closing body tag</em>)</li>
+</ul>
+<h2 id="packaging-everything-together">Packaging Everything Together</h2>
+<p>Now that we have the custom stylesheet and script ready to be loaded into our custom WordPress theme, we just need to properly package them together as a function in our <code>functions.php</code> file:</p>
+<pre><code>&#47;&#47; Add styles and scripts to the header&#47;footer
+function custom_enqueue_scripts() {
+ wp_enqueue_style( &#39;google-fonts&#39;, &#39;https:&#47;&#47;fonts.googleapis.com&#47;css?family=Montserrat:200,300,300i,400,600,700,800,900&#39;);
+ wp_enqueue_script( &#39;bxslider&#39;, get_template_directory_uri() . &#39;&#47;js&#47;bxslider.js&#39;, array(&#39;jquery&#39;), &#39;1.0.0&#39;, true );
+}
+
+add_action( &#39;wp_enqueue_scripts&#39;, &#39;custom_enqueue_scripts&#39;);
+</code></pre>
+<p>That&#8217;s it! Hopefully this helps prevent WordPress newbies from statically rendering their external CSS and JS files directly in template files. Let WordPress do that for you!</p>
+<footer role="contentinfo">
+ <h2>Menu Navigation</h2>
+ <ul id="menu">
+ <li><a href="/">Home</a></li>
+ <li><a href="/projects">Projects</a></li>
+ <li><a href="/uses">Uses</a></li>
+ <li><a href="/wiki">Wiki</a></li>
+ <li><a href="/resume">Resume</a></li>
+ <li><a href="/colophon">Colophon</a></li>
+ <li><a href="/now">Now</a></li>
+ <li><a href="/donate">Donate</a></li>
+ <li><a href="/atom.xml">RSS</a></li>
+ <li><a href="#top">&uarr; Top of the page</a></li>
+ </ul>
+ <small>
+ Built with <a href="https://git.sr.ht/~bt/barf">barf</a>. <br>
+ Maintained with ♥ for the web. <br>
+ Proud supporter of <a href="https://usefathom.com/ref/DKHJVX">Fathom</a> &amp; <a href="https://nextdns.io/?from=74d3p3h8">NextDNS</a>. <br>
+ The content for this site is <a href="https://creativecommons.org/licenses/by-sa/2.0/">CC-BY-SA</a>.<br> The <a href="https://git.sr.ht/~bt/bt.ht">code for this site</a> is <a href="https://git.sr.ht/~bt/bt.ht/tree/master/item/LICENSE">MIT</a>.
+ </small>
+</footer> \ No newline at end of file