Files
website/src/pages/blog.html
T
2026-05-04 21:58:16 +02:00

76 lines
3.7 KiB
HTML
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
<main id="blog">
<h1 id="mainHeading">$ mount /dev/blog</h1>
<article>
<h1 id="this-2025-02-13"><a href="#2025-02-13" name="2025-02-13">*this
(2025-02-13)</a></h1>
<p>Naturally I devote the first blog post to the creation of this
website.</p>
<h2 id="motivation">Motivation</h2>
<p>The motivation came of course from frustration with modern sites and
a bit of nostalgia. But mainly I wanted the <a href="now.html">now()</a>
and the <a href="about.html">about()</a> pages. They provide me with a
public place to document what Im on and what I believe and give me a
corrective. I cant remember where I read about it the first time, but I
thought the idea was neat. Especially as more of a private person, it
motivates me to keep going with things when I imagine people reading
this.</p>
<p>The design of this page is as bad as it is, because for once, it was
the style at the time (be happy I dont include a
<code>&lt;marquee&gt;</code> tag. Worst loss of the net…) and secondly:
I just suck at it. Deal with it :)</p>
<p>Having programmed some time with modern JS/TS frameworks Im 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. Thats why I simply want a plain html+css website,
suppported by some GNU programs.</p>
<h2 id="technical-details">Technical details</h2>
<p>You can find the whole source code of this in my <a
href="https://git.rhetenor.de/rhetenor/website">git()</a>. Beside
HTML+CSS I wanted some kind of template mechanism, but didnt want it to
be utterly complex. So I use <code>cat</code>, <code>make</code> to glue
everything together and <code>pandoc</code> to translate Markdown to
HTML for this blog, because HTML is not too fun to write.</p>
<h3 id="building-a-page">Building a page</h3>
<p>To start the template I have a <code>start.html</code> which contains
everything from the start <code>&lt;html&gt;</code> tag, the whole
<code>&lt;head&gt;</code> and the start <code>&lt;body&gt;</code> tag.
Then the <code>nav.html</code> and <code>side.html</code> are included
with navigation and sidebar . Afterwards the actual
<code>&lt;article&gt;</code> gets included and everything is closed
inside <code>end.html</code>.</p>
<p>So for example the <code>index.html</code> page is built using
<code>cat start.html nav.html side.html index.html end.html</code></p>
<p>Same applies to every other page.</p>
<h3 id="automating-using-make">Automating using make</h3>
<p>I automated this for a whole folder using a Makefile on which I dont
want to elaborate too much, its just a “simple” Makefile. Makefiles are
always simple when you start out and keep getting more cryptic as more
as you work on it.</p>
<h3 id="blog">Blog</h3>
<p>Since Im not that much of a fan of writing HTML all the time, but
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
<code>pandoc -f markdown -t html *.md -o blog.html</code>. All of this
also automated using markdown.</p>
<h2 id="future-work">Future Work</h2>
<h3 id="blog-paging">Blog paging</h3>
<p>Im pretty sure this is simple for the moment but if I add more and
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.</p>
<h3 id="marquee-tag">Marquee tag</h3>
<p>Just joking it died with Internet Explorer and never was
standardized!</p>
<h3 id="references">References</h3>
<p>I think I need some reference mechanism, to easilier include them,
such that it is not that much of a hazzle.</p>
<main id="blog">
<h1 id="mainHeading">
$ mount /dev/blog
</h1>
<article>
</article>
</main>
</article>
</main>