rhetenor/website
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Push before release

Browse Source
This commit is contained in:
Jonas Zeunert
2025-07-15 20:55:12 +02:00
parent 60daa40712
commit b9a403e9d9
3 changed files with 40 additions and 36 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
src/blog/1.md
View File

@@ -1,5 +1,5 @@
# *This (2024-02-13) # <a href="#2025-02-13" name="2025-02-13">*this (2025-02-13)</a>
Naturally I devote the first blog post to the website. 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. Let's find out if I'm any good in writing such things.
## Motivation ## Motivation
@@ -16,14 +16,14 @@ I just suck at it. Deal with it :)
Having programmed some time with modern JS/TS frameworks I'm a stark oppponent of this 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 - 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, nobody ever got any chance to understand. That's why I simply want a plain html+css website,
suppported by some GNU programs. suppported by some GNU programs.
## Technical details ## Technical details
You can find the whole source code of this in my [git()](https://git.rhetenor.de/rhetenor/website). You can find the whole source code of this in my [git()](https://git.rhetenor.de/rhetenor/website).
Beside HTML+CSS I wanted a bit of a template mechanism, but didn't want it to be utterly complex. Beside HTML+CSS I wanted some kind of template mechanism, but didn't want it to be utterly complex.
So I use `cat`, `make` to glue everything together and `pandoc` to translate Markdown to HTML for this So I use `cat`, `make` to glue everything together and `pandoc` to translate Markdown to HTML for this
blog. blog, because HTML is not too fun to write.
### Building a page ### Building a page
To start the template I have a `start.html` which contains everything from the start `<html>` tag, To start the template I have a `start.html` which contains everything from the start `<html>` tag,
@@ -51,7 +51,7 @@ I will need some paging mechanism and at one point maybe a search. But until I d
ignore it for now. ignore it for now.
### Marquee tag ### 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 ### References
I think I need some reference mechanism, to easilier include them, such that it is not that much of a hazzle. I think I need some reference mechanism, to easilier include them, such that it is not that much of a hazzle.

62
src/pages/blog.html
View File

@@ -1,9 +1,10 @@
<main id="blog"> <main id="blog">
<h1 id="mainHeading">$ mount /dev/blog</h1> <h1 id="mainHeading">$ mount /dev/blog</h1>
<article> <article>
<h1 id="this-2024-02-13">*This (2024-02-13)</h1> <h1 id="this-2025-02-13"><a href="#2025-02-13" name="2025-02-13">*this
<p>Naturally I devote the first blog post to the website. Let’s find out (2025-02-13)</a></h1>
if I’m any good in writing such things.</p> <p>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.</p>
<h2 id="motivation">Motivation</h2> <h2 id="motivation">Motivation</h2>
<p>The motivation for the website came from frustration with modern <p>The motivation for the website came from frustration with modern
sites and a bit of nostalgia. But mainly I wanted the <a sites and a bit of nostalgia. But mainly I wanted the <a
@@ -13,40 +14,42 @@ and what I believe and give me a correctiv. I can’t remember where I
read about it the first time, but I thought the idea was neat. 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 Especially as more of a private person, it motivates me to keep going
with things when I imagine people reading this.</p> with things when I imagine people reading this.</p>
<p>The design of this page is as bad as it is for once, it was the style <p>The design of this page is as bad as it is, because for once, it was
at the time (be happy I don’t include a <code>&lt;marquee&gt;</code> the style at the time (be happy I don’t include a
tag. After all. Why not.) and for the second: I just suck at it. Deal <code>&lt;marquee&gt;</code> tag. After all. Why not.) and secondly: I
with it :)</p> just suck at it. Deal with it :)</p>
<p>Having programmed quite some time with modern JS/TS frameworks I’m a <p>Having programmed some time with modern JS/TS frameworks I’m a stark
stark oppponent of this whole technology stack. It just adds layers and oppponent of this whole technology stack. It just adds - layers and
layers of complexity over complexity nobody ever has any chance to layers - of - complexity over complexity - nobody ever got any chance to
understand. That’s why I simply want a plain html+css stack, suppported understand. That’s why I simply want a plain html+css website,
by Linux programs.</p> suppported by some GNU programs.</p>
<h2 id="technical-details">Technical details</h2> <h2 id="technical-details">Technical details</h2>
<p>You can find the whole source code of this in my <a <p>You can find the whole source code of this in my <a
href="https://git.rhetenor.de/rhetenor/website">git()</a>. Beside href="https://git.rhetenor.de/rhetenor/website">git()</a>. Beside
HTML+CSS I wanted a bit of a template mechanism, but didn’t want it to HTML+CSS I wanted some kind of template mechanism, but didn’t want it to
be utterly complex.</p> 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> <h3 id="building-a-page">Building a page</h3>
<p>As such I build this sites together with <code>cat</code>. To start <p>To start the template I have a <code>start.html</code> which contains
the template I have a <code>start.html</code> which contains everything everything from the start <code>&lt;html&gt;</code> tag, the whole
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. <code>&lt;head&gt;</code> and the start <code>&lt;body&gt;</code> tag.
Then the <code>nav.html</code> with the navigation and the Then the <code>nav.html</code> and <code>side.html</code> are included
<code>side.html</code> with the sidebar gets included. Afterwards the with navigation and sidebar . Afterwards the actual
actual page gets included and at the end the <code>end.html</code> which <code>&lt;article&gt;</code> gets included and everything is closed
just closes the tags.</p> inside <code>end.html</code>.</p>
<p>So for example the <code>index.html</code> page is built using <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> <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> <h3 id="automating-using-make">Automating using make</h3>
<p>I automated this for a whole folder using a Makefile on which I don’t <p>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 want to elaborate too much, it’s just a “simple” Makefile. Makefiles are
and getting more cryptic as more one works on it. Probably the story of always simple when you start out and keep getting more cryptic as more
all Makefiles.</p> as you work on it.</p>
<h3 id="blog">Blog</h3> <h3 id="blog">Blog</h3>
<p>Since I’m not that much of a fan of writing HTML all the time, but <p>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 think Markdown is not that bad, I decided to use it for this blog. I
these posts as .md pages and convert them using pandoc with 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 <code>pandoc -f markdown -t html *.md -o blog.html</code>. All of this
also automated using markdown.</p> also automated using markdown.</p>
<h2 id="future-work">Future Work</h2> <h2 id="future-work">Future Work</h2>
@@ -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 mechanism and at one point maybe a search. But until I decide it is the
time, I will just ignore it for now.</p> time, I will just ignore it for now.</p>
<h3 id="marquee-tag">Marquee tag</h3> <h3 id="marquee-tag">Marquee tag</h3>
<p>Just joking it died with Internet Explorer and never was in the <p>Just joking it died with Internet Explorer and never was
standard!</p> standardized!</p>
<h3 id="references">References</h3> <h3 id="references">References</h3>
<p>I think I need some reference mechanism</p> <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"> <main id="blog">
<h1 id="mainHeading"> <h1 id="mainHeading">
$ mount /dev/blog $ mount /dev/blog

2
src/styles/aside.css
View File

@@ -4,7 +4,7 @@ aside {
width: 0; width: 0;
} }
min-height: 100%; min-height: 100%;
max-width: 14%; max-width: 20%;
height: 100%; height: 100%;
overflow: hidden; overflow: hidden;
margin-right: 1vw; margin-right: 1vw;