From 82e7ac75954c973a5c59a02684788c0fb26e14dd Mon Sep 17 00:00:00 2001 From: Martin Ashby Date: Sat, 21 Dec 2024 22:18:18 +0000 Subject: Bump zine 0.3.0 -> 0.8.0 Fix a lot of associated breakage Fix broken rss.xml file as highlighted to me by Matthijs van der Wild (thanks!) --- content/posts/2022-10-14-blogsite.smd | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 content/posts/2022-10-14-blogsite.smd (limited to 'content/posts/2022-10-14-blogsite.smd') diff --git a/content/posts/2022-10-14-blogsite.smd b/content/posts/2022-10-14-blogsite.smd new file mode 100644 index 0000000..7b74c6a --- /dev/null +++ b/content/posts/2022-10-14-blogsite.smd @@ -0,0 +1,12 @@ +--- +.title = "Blogsite", +.author = "Martin Ashby", +.date = @date("2022-10-14T22:59:01+01:00"), +.layout = "single.shtml", +.custom = {"comments": true}, +--- + +I was thinking about this blog and how it's set up. I [covered](/posts/2021-10-01-blog/) the setup in a previous post, but it's quite simple: the site is generated from markdown files with [hugo](https://gohugo.io/) and published to git. The server pulls from git on a schedule, rebuilds it and copies it to the web server directory. + +I made a [little experiment](https://blogsite.mfashby.net/1-hello-new-blog) with a different approach [source](https://code.mfashby.net/martin/blogsite). Instead of statically generating the site, it's a Single Page Application which does the templating and routing on the client side. In theory this has a couple of upsides: if you visit multiple pages fewer bytes are transferred overall, and it totally removes the static site generation step; the folder is all just static content provided to the web server. This approach likely has some downsides too, like; requires javascript enabled client, no RSS feed or sitemap generation, and my implementation at least is relying on some fairly modern JS features like async/await and fetch API. + -- cgit v1.2.3-ZIG