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

Update

Browse Source
This commit is contained in:
Jonas Zeunert
2025-05-03 14:43:58 +02:00
parent 356de5f9dd
commit 60daa40712
6 changed files with 93 additions and 47 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
Makefile
View File

@@ -26,8 +26,9 @@ template: $(SRC_DIR)/start.html $(SRC_DIR)/nav.html $(SRC_DIR)/side.html | mkdis
cat $(SRC_DIR)/start.html $(SRC_DIR)/nav.html $(SRC_DIR)/side.html > dist/template.html
$(PAGES_DIR)/blog.html: $(BLOG_PAGES) $(BLOG_DIR)/start_blog.html $(BLOG_DIR)/end_blog.html
pandoc -f markdown -t html $^ -o $@
cat $(BLOG_DIR)/start_blog.html $@ $(BLOG_DIR)/end_blog.html | tee $@
pandoc -f markdown -t html $^ -o $@.tmp
cat $(BLOG_DIR)/start_blog.html $@.tmp $(BLOG_DIR)/end_blog.html > $@
rm $@.tmp
$(DIST_DIR)/%.html: $(PAGES_DIR)/%.html | template mkdist
cat $(DIST_DIR)/template.html $(PAGES_DIR)/$*.html $(SRC_DIR)/end.html > $@

52
src/blog/1.md
View File

@@ -1,41 +1,57 @@
# This website
# *This (2024-02-13)
Naturally I devote the first blog post to the website.
Let's find out if I have any skills in writing such things.
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 [now()](now.html) and the [beliefs()](beliefs.html) pages, such that I
have a public place to document what I'm doing and what I believe and have a corrective.
But mainly I wanted the [now()](now.html) and the [beliefs()](beliefs.html) 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.
Especially as more of a private person, it motivates me to keep going with things when I
imagine people reading this.
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.
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 `<marquee>` tag. After all. Why not.) and secondly:
I just suck at it. Deal with it :)
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 has any chance to understand. That's why I simply want a plain html+css stack,
suppported by some GNU programs.
## Technical details
You can find the whole source code of this in my [git()](https://git.rhetenor.de).
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.
So I use `cat`, `make` to glue everything together and `pandoc` to translate Markdown to HTML for this
blog.
### 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 `<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.
the whole `<head>` and the start `<body>` tag. Then the `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.
I automated this for a whole folder using a Makefile on which I don't 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
Since I'm 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
`pandoc -f markdown -t html *.md -o blog.html`. All of this also automated using markdown.
## Future Work
### Blog paging
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.
### Marquee tag
Just joking it died with Internet Explorer and never was in the standard!
### References
I think I need some reference mechanism, to easilier include them, such that it is not that much of a hazzle.

8
src/pages/beliefs.html
View File

@@ -3,6 +3,14 @@
A page with my beliefs. I will try to update it from time to time, and strike out what has changed.
<h2>General</h2>
<h2>Writing</h2>
<p>
Better have to many dates in your document than to less. It is cumbersome to find out if information is outdated.
<p>
However unimportant a citation might seem, always cite as much as possible. Others will thank you if they are interested.
</p>
<h2>Programming</h2>
<h3>Premature optimization</h3>
<p>

43
src/pages/blog.html
View File

@@ -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>&lt;marquee&gt;</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

18
src/side.html
View File

@@ -3,17 +3,25 @@
<h1 id="updates_heading">Updates</h1>
<ul class="outer_list">
<li>
<h2>2025-02-13</h2>
<ul class="inner_list">
<li>updated Style</li>
<li>add blog()</li>
<li>add beliefs()</li>
<li>add content</li>
</ul>
</li>
<li>
<h2>2024-05-08:</h2>
<ul class="inner_list">
<li>Updated Style</li>
<li>main() Content</li>
<li>More links()</li>
<li>Added Misc</li>
<li>updated style</li>
<li>main() content</li>
<li>more links()</li>
</ul>
</li>
<li><h2>2024-04-28:</h2>Website created</li>
<li><h2>2024-04-28:</h2>website created</li>
</ul>
</section>

14
src/styles/style.css
View File

@@ -21,20 +21,20 @@ body {
linear-gradient(
60deg,
#000123 7.2%,
white 7.3% 7.35%,
red 7.3% 7.35%,
#000 7.45%
),
linear-gradient(
-20deg,
#181a1b 38%,
-10deg,
#181a1b 48%,
red 38.2% 38.3%,
#000 38.5%
),
linear-gradient(
12deg,
#181a1b 14%,
green 14.3% 14.5%,
#000 14.8%
11deg,
#181a1b 14.2%,
green 14.3% 14.4%,
#000 14.5%
),
linear-gradient(
11deg,