aboutsummaryrefslogtreecommitdiff
path: root/content/posts
diff options
context:
space:
mode:
authorMartin Ashby <martin@ashbysoft.com>2022-10-15 22:51:00 +0100
committerMartin Ashby <martin@ashbysoft.com>2022-10-15 22:51:00 +0100
commitd4abe9e607e40f556077e99e35c85e7ce5c0f3df (patch)
tree7d16c2382b54b41ab48d6e60df329975e087c109 /content/posts
parentb55462fdcc57a5890108521749c467d23dabff12 (diff)
downloadmfashby.net-d4abe9e607e40f556077e99e35c85e7ce5c0f3df.tar.gz
mfashby.net-d4abe9e607e40f556077e99e35c85e7ce5c0f3df.tar.bz2
mfashby.net-d4abe9e607e40f556077e99e35c85e7ce5c0f3df.tar.xz
mfashby.net-d4abe9e607e40f556077e99e35c85e7ce5c0f3df.zip
second blogsite post
Diffstat (limited to 'content/posts')
-rw-r--r--content/posts/2022-10-15-blogsite2.md9
1 files changed, 9 insertions, 0 deletions
diff --git a/content/posts/2022-10-15-blogsite2.md b/content/posts/2022-10-15-blogsite2.md
new file mode 100644
index 0000000..6a26594
--- /dev/null
+++ b/content/posts/2022-10-15-blogsite2.md
@@ -0,0 +1,9 @@
+---
+title: "Blogsite 2"
+date: 2022-10-15T22:39:18+01:00
+draft: false
+---
+
+I made another [small experiment](https://blogsite2.mfashby.net/) [source](https://code.mfashby.net/martin/blogsite2) to do my blog yet another way; rather than using hugo static site generation, I can leverage Caddy server's built-in [template rendering](https://caddyserver.com/docs/caddyfile/directives/templates) and markdown support to serve markdown files 'directly' without a pre-build step.
+
+In the end though, I will probably stick with static site generation. It offers some performance and security improvements such as no templating time, no possibility of vulnerabilities in the templating engine, in return for a little extra complexity having a build-step.