add refactor-argent blog post and updated favicon

2 files changed, 48 insertions, 24 deletions

diff --git a/site_root/blog/announcing_honeysuckle.lua b/site_root/blog/announcing_honeysuckle.lua
index 5fb97fb..f078585 100644
--- a/site_root/blog/announcing_honeysuckle.lua
+++ b/site_root/blog/announcing_honeysuckle.lua
@@ -3,35 +3,35 @@ return {
    layout='blog',
    date='2021-05-23',
    markdown=[[
-As I’ve been working on various projects for the past couple of years 
-I have continued to find that a combination of C and Lua is my favorite 
-way to write code. The ongoing development of [my game engine honey](https://honey3d.org/)
-uses that pair and I’m planning on using it (whenever I get around to it) for my [dream 
-atlas project](https://sanine.net/projects/dream-atlas). But, and I’ll be the first
-to admit this, the C API is a little clunky. 
-I don’t generally mind that all too much (after all, one of my favorite things about 
-both C and Lua is that they’re languages you can carry around in your head, and having
-a very explicit API means you only need to understand the fundamental concepts to use it)
+as i’ve been working on various projects for the past couple of years 
+i have continued to find that a combination of c and lua is my favorite 
+way to write code. the ongoing development of [my game engine honey](https://honey3d.org/)
+uses that pair and i’m planning on using it (whenever i get around to it) for my [dream 
+atlas project](https://sanine.net/projects/dream-atlas). but, and i’ll be the first
+to admit this, the c api is a little clunky. 
+i don’t generally mind that all too much (after all, one of my favorite things about 
+both c and lua is that they’re languages you can carry around in your head, and having
+a very explicit api means you only need to understand the fundamental concepts to use it)
 but it does mean that dev work goes a bit slower.
 
-I did a good bit of work streamlining the process of writing Lua bindings in C when
-tinkering with honey and ever since then I’ve found myself peeking back at that code
-and re-implementing it in other projects. A colleague of mine once said that the time
+i did a good bit of work streamlining the process of writing lua bindings in c when
+tinkering with honey and ever since then i’ve found myself peeking back at that code
+and re-implementing it in other projects. a colleague of mine once said that the time
 to write a library is when you’ve done something once, you’re doing it now, and you
-re pretty sure you’ll do it again, and I think I’ve quite handily cleared that condition
-So! I’m splitting that code out and refactoring it into its own library which, due
-to its historical roots, I’ve chosen to call honeysuckle.
+re pretty sure you’ll do it again, and i think i’ve quite handily cleared that condition
+so! i’m splitting that code out and refactoring it into its own library which, due
+to its historical roots, i’ve chosen to call honeysuckle.
 
-honeysuckle is still under development – the API is a bit different from the one I
+honeysuckle is still under development – the api is a bit different from the one i
 came up with when working on honey and imo is easier to use – but when it’s ready
-it will provide a whole host of helpful functions that make integrating Lua scripting
-into C applications simple and fast. I am (attempting) to employ readme-driven development
-so I’ve written up a readme for honeysuckle. Any feedback on the proposed API and
-features would be much appreciated! As of writing, honeysuckle is planned to include
-functions for parsing arguments to C functions from Lua, creating and processing tables
-throwing and handling Lua errors, using the Lua registry, and creating printf-formatted strings.
+it will provide a whole host of helpful functions that make integrating lua scripting
+into c applications simple and fast. i am (attempting) to employ readme-driven development
+so i’ve written up a readme for honeysuckle. any feedback on the proposed api and
+features would be much appreciated! as of writing, honeysuckle is planned to include
+functions for parsing arguments to c functions from lua, creating and processing tables
+throwing and handling lua errors, using the lua registry, and creating printf-formatted strings.
 
-I’ve already created a repository for honeysuckle. There’s just a README in there
-for now, but that will probably have changed even just later today, since I’m planning
+i’ve already created a repository for honeysuckle. there’s just a readme in there
+for now, but that will probably have changed even just later today, since i’m planning
 on working on it more this afternoon. :p
 ]]}
diff --git a/site_root/blog/refactor-argent.lua b/site_root/blog/refactor-argent.lua
new file mode 100644
index 0000000..6b7ca4d
--- /dev/null
+++ b/site_root/blog/refactor-argent.lua
@@ -0,0 +1,24 @@
+local md = [[
+hey there!  you might be noticing that things look a little... different around here. 
+that's because i've refactored this site to use my custom static site generator, [argent].
+i used to use jekyll, but i wanted to be able to do more *direct programming* in building my
+pages, and i wanted to be able to do that in lua. i tried looking at some of the other 
+static site generators out there using lua (and python too) but so many of them rely on
+packages that no longer exist, or language features from seven versions ago, or similar
+types of problems, that i wanted to have a site generator that *just works*.
+
+so i wrote one! i called it argent because (a) it sounds kinda cool and (b) argent, as a
+silver-white color, is used in heraldry to represent the moon, and i like the oblique reference
+to lua. it relies on posix filesystem calls (sorry windows users, you'll need msys or something
+to run it) but otherwise is totally standalone -- it packages its own lua interpreter, so language
+version (ideally) will never change.
+
+[argent]: /git/argent
+]]
+
+return {
+   title = 'refactor: argent',
+   date = '2022-01-13',
+   layout = 'blog',
+   markdown = md,
+}