diff --git a/Makefile b/Makefile index 0ea7508..9259b04 100644 --- a/Makefile +++ b/Makefile @@ -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 > $@ diff --git a/src/blog/1.md b/src/blog/1.md index d7ba74f..7d9ee2a 100644 --- a/src/blog/1.md +++ b/src/blog/1.md @@ -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 `` 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 `` tag, -the whole `` and the start `` 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 `` and the start `` tag. Then the `nav.html` and `side.html` are included +with navigation and sidebar . Afterwards the actual `
` 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. diff --git a/src/pages/beliefs.html b/src/pages/beliefs.html index c8b0f0a..a9b5188 100644 --- a/src/pages/beliefs.html +++ b/src/pages/beliefs.html @@ -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. +

General

+

Writing

+

+ Better have to many dates in your document than to less. It is cumbersome to find out if information is outdated. +

+ However unimportant a citation might seem, always cite as much as possible. Others will thank you if they are interested. +

+

Programming

Premature optimization

diff --git a/src/pages/blog.html b/src/pages/blog.html index 9e9b1af..1f1d7fd 100644 --- a/src/pages/blog.html +++ b/src/pages/blog.html @@ -1,26 +1,32 @@

$ mount /dev/blog

-

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.

+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() and the beliefs() -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.

+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.

+

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 <marquee> +tag. After all. Why not.) and for the second: I just suck at it. Deal +with it :)

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.

+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.

Technical details

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.

+href="https://git.rhetenor.de/rhetenor/website">git(). Beside +HTML+CSS I wanted a bit of a template mechanism, but didn’t want it to +be utterly complex.

Building a page

As such I build this sites together with cat. To start the template I have a start.html 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 pandoc -f markdown -t html *.md -o blog.html. All of this also automated using markdown.

-

lol

-

another test

-

** with an even better english blogpost ** oO

-

i dont care about this

+

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

$ mount /dev/blog diff --git a/src/side.html b/src/side.html index a01c310..24754e9 100644 --- a/src/side.html +++ b/src/side.html @@ -3,17 +3,25 @@

Updates

    +
  • +

    2025-02-13

    +
      +
    • updated Style
      • +
    • add blog()
      • +
    • add beliefs()
      • +
    • add content
      • +
    +

  • 2024-05-08:

      -
    • Updated Style
      • -
    • main() Content
      • -
    • More links()
      • -
    • Added Misc
      • +
    • updated style
      • +
    • main() content
      • +
    • more links()
    • -

  • 2024-04-28:

    Website created
    • +

  • 2024-04-28:

    website created
diff --git a/src/styles/style.css b/src/styles/style.css index 1a53b14..9cb80bf 100644 --- a/src/styles/style.css +++ b/src/styles/style.css @@ -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,