summaryrefslogtreecommitdiff
path: root/posts/wp-enqueue-for-beginners.md
diff options
context:
space:
mode:
authorbt <bt@web>2023-11-28 13:35:21 -0500
committerIkiWiki <ikiwiki.info>2023-11-28 13:35:21 -0500
commitc94f7876da9b8658fd2566a5f40e89307712111e (patch)
tree6321b28fefca103290a38857cce0e454d71bf8eb /posts/wp-enqueue-for-beginners.md
parente07cec12f358678483bbd7825167159980b64d2d (diff)
Diffstat (limited to 'posts/wp-enqueue-for-beginners.md')
-rw-r--r--posts/wp-enqueue-for-beginners.md5
1 files changed, 2 insertions, 3 deletions
diff --git a/posts/wp-enqueue-for-beginners.md b/posts/wp-enqueue-for-beginners.md
index 2d5667f..8257625 100644
--- a/posts/wp-enqueue-for-beginners.md
+++ b/posts/wp-enqueue-for-beginners.md
@@ -1,6 +1,5 @@
-# WP Enqueue for Beginners
-
-2020-05-05
+[[!meta title="WP Enqueue for Beginners"]]
+[[!meta date="2020-05-05"]]
Throughout my career designing, developing and auditing WordPress themes, I've come across many that include their custom styles / scripts as static HTML elements inside their respective `header` and `footer` templates. This is perfectly _fine_, but there is a cleaner way to include these files.