update

config.toml

@@ -14,5 +14,5 @@ nav_links = [
     { url = "/", text = "home" },
     { url = "/pages/about", text = "about" },
     { url = "/pages", text = "all pages" },
-    { url = "https://git.iptq.io/michael", text = "projects »" },
+    { url = "/projects", text = "projects »" },
 ]

content/2019-03-04-server-analogy.md

@@ -1,10 +1,12 @@
 +++
-title = "interesting cs analogies"
+title = "accept server analogy"
+date = 2019-03-04
+
+[taxonomies]
+tags = []
 +++
 
-stupid analogies i think of in my free time
-
-## socket server + multiple clients analogy
+This is just something stupid I thought of recently, but decided to write about it anyway.
 
 If you think about it, a server waiting for clients is kind of like the host at the front of a restaurant leading guests to tables. They don't actually take orders or serve food, they just stand at the front and wait for new guests to arrive. Then there's another waiter that's specifically assigned to take that table's orders.
 

content/pages/setup.md

@@ -78,7 +78,7 @@ And a slew of other non-free apps that have pretty specific uses, though I think
 
 The stack for this website looks like:
 
-- The [source code](https://git.iptq.io/michael/blog) is written as a set of Gutenberg config files.
+- The [source code](https://iptq.io/projects/blog) is written as a set of Gutenberg config files.
 - This is then transpiled into static HTML + resources using [Zola](https://getzola.org/), a static site generator written with Rust.
 - Changes are deployed using Git hooks.
 - Static files are served from a web root using [nginx](https://nginx.org/en/) through a virtual host.