1 files changed, 5 insertions, 8 deletions

diff --git a/posts/use-text-not-icons.md b/posts/use-text-not-icons.md
index aa10832..f505e24 100644
--- a/posts/use-text-not-icons.md
+++ b/posts/use-text-not-icons.md
@@ -1,6 +1,5 @@
-# Icons Should be Complementary - Text is Always Better
-
-2021-12-17
+[[!meta title="Icons Should be Complementary - Text is Always Better"]]
+[[!meta date="2021-12-17"]]
 
 Designing[^1] software is a complex thing. A great deal of real-world testing and user feedback is needed to create the best solution to the problem you are trying to fix. Obvious requirements are to keep things simple, make it easy to understand by *looking* at it, and build it to be headache-resistant for future updates. All these things are easier said than done. This is the challenge of a designer's dat-to-day.
 
@@ -48,8 +47,6 @@ I understand applications will have advanced or "pro" users that have full knowl
 
 As I stated above, try doing a quick design experiment by replacing all your existing iconography in your application with simple text. I assure you that at least you'll discover interesting design flaws in your system.
 
-## Refs
-
-1. By "design" I'm referring to visuals not programming or system engineering
-2. Early software programs did save to an external floppy disk. My point stands that many digital file storage applications copied this iconography blindly.
-3. Not to mention how rampant it is on plain ol' regular websites. If you're hiding five menu items behind a hamburger menu for "mobile users", you're doing it wrong.
+[^1]: By "design" I'm referring to visuals not programming or system engineering
+[^2]: Early software programs did save to an external floppy disk. My point stands that many digital file storage applications copied this iconography blindly.
+[^3]: Not to mention how rampant it is on plain ol' regular websites. If you're hiding five menu items behind a hamburger menu for "mobile users", you're doing it wrong.