Update
This commit is contained in:
+28
-15
@@ -1,26 +1,32 @@
|
||||
<main id="blog">
|
||||
<h1 id="mainHeading">$ mount /dev/blog</h1>
|
||||
<article>
|
||||
<h1 id="this-website">This website</h1>
|
||||
<h1 id="this-2024-02-13">*This (2024-02-13)</h1>
|
||||
<p>Naturally I devote the first blog post to the website. Let’s find out
|
||||
if I have any skills in writing such things.</p>
|
||||
if I’m any good in writing such things.</p>
|
||||
<h2 id="motivation">Motivation</h2>
|
||||
<p>The motivation for the website came 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="beliefs.html">beliefs()</a>
|
||||
pages, such that I have a public place to document what I’m doing and
|
||||
what I believe and have a corrective. I can’t 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.</p>
|
||||
pages. They provide me with a public place to document what I’m doing
|
||||
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.
|
||||
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 for once, it was the style
|
||||
at the time (be happy I don’t include a <code><marquee></code>
|
||||
tag. After all. Why not.) and for the second: I just suck at it. Deal
|
||||
with it :)</p>
|
||||
<p>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 and complexity over complexity nobody ever will ever understand.
|
||||
As such I just wanted a simple plain html+css stack, suppported by Linux
|
||||
programs.</p>
|
||||
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.</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">git()</a>. Beside HTML+CSS I wanted a bit
|
||||
of a template mechanism, but didn’t want it to be utterly complex.</p>
|
||||
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
|
||||
be utterly complex.</p>
|
||||
<h3 id="building-a-page">Building a page</h3>
|
||||
<p>As such I build this sites together with <code>cat</code>. To start
|
||||
the template I have a <code>start.html</code> which contains everything
|
||||
@@ -43,10 +49,17 @@ 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
|
||||
<code>pandoc -f markdown -t html *.md -o blog.html</code>. All of this
|
||||
also automated using markdown.</p>
|
||||
<h1 id="lol">lol</h1>
|
||||
<p>another test</p>
|
||||
<p>** with an even better english blogpost ** oO</p>
|
||||
<p>i dont care about this</p>
|
||||
<h2 id="future-work">Future Work</h2>
|
||||
<h3 id="blog-paging">Blog paging</h3>
|
||||
<p>I’m 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 in the
|
||||
standard!</p>
|
||||
<h3 id="references">References</h3>
|
||||
<p>I think I need some reference mechanism</p>
|
||||
<main id="blog">
|
||||
<h1 id="mainHeading">
|
||||
$ mount /dev/blog
|
||||
|
||||
Reference in New Issue
Block a user