*This (2024-02-13)
-Naturally I devote the first blog post to the website. Let’s find out -if I’m any good in writing such things.
+*this +(2025-02-13)
+Naturally I devote the first blog post to the creation of this +website. Let’s find out if I’m any good in writing such things.
Motivation
The motivation for the website came from frustration with modern
sites and a bit of nostalgia. But mainly I wanted the
- The design of this page is as bad as it is for once, it was the style
-at the time (be happy I don’t include a Having programmed quite some time with modern JS/TS frameworks I’m a
-stark oppponent of this whole technology stack. It just adds layers and
-layers of complexity over complexity nobody ever has any chance to
-understand. That’s why I simply want a plain html+css stack, suppported
-by Linux programs. The design of this page is as bad as it is, because for once, it was
+the style at the time (be happy I don’t include a
+ Having programmed some time with modern JS/TS frameworks I’m a stark
+oppponent of this whole technology stack. It just adds - layers and
+layers - of - complexity over complexity - nobody ever got any chance to
+understand. That’s why I simply want a plain html+css website,
+suppported by some GNU programs. You can find the whole source code of this in my git(). Beside
-HTML+CSS I wanted a bit of a template mechanism, but didn’t want it to
-be utterly complex.<marquee>
-tag. After all. Why not.) and for the second: I just suck at it. Deal
-with it :)<marquee> tag. After all. Why not.) and secondly: I
+just suck at it. Deal with it :)Technical details
cat, make to glue
+everything together and pandoc to translate Markdown to
+HTML for this blog, because HTML is not too fun to write.
Building a page
-As such I build this sites together with cat. To start
-the template I have a start.html which contains everything
-from the start <html> tag, the whole
+
To start the template I have a start.html which contains
+everything from the start <html> tag, the whole
<head> and the start <body> tag.
-Then the nav.html with the navigation and the
-side.html with the sidebar gets included. Afterwards the
-actual page gets included and at the end the end.html which
-just closes the tags.
nav.html and side.html are included
+with navigation and sidebar . Afterwards the actual
+<article> gets included and everything is closed
+inside end.html.
So for example the index.html page is built using
cat start.html nav.html side.html index.html end.html
Same applies to every other page.
Automating using make
I automated this for a whole folder using a Makefile on which I don’t -want to elaborate, it’s just a standard Makefile. Simple at the start -and getting more cryptic as more one works on it. Probably the story of -all Makefiles.
+want to elaborate too much, it’s just a “simple” Makefile. Makefiles are +always simple when you start out and keep getting more cryptic as more +as you work on it.Blog
Since I’m not that much of a fan of writing HTML all the time, but
-quite some fan of Markdown, I decided to use it for this blog. I write
-these posts as .md pages and convert them using pandoc with
+think Markdown is not that bad, I decided to use it for this blog. I
+write these posts as .md pages and convert them using pandoc with
pandoc -f markdown -t html *.md -o blog.html. All of this
also automated using markdown.
Future Work
@@ -56,10 +59,11 @@ more content here it will become confusing. I will need some paging mechanism and at one point maybe a search. But until I decide it is the time, I will just ignore it for now.Marquee tag
-Just joking it died with Internet Explorer and never was in the -standard!
+Just joking it died with Internet Explorer and never was +standardized!
References
-I think I need some reference mechanism
+I think I need some reference mechanism, to easilier include them, +such that it is not that much of a hazzle.