git.privacynerd.de/blog.privacynerd.de
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fixed problem in german about page; fixed wrong usage of quotation marks in the english articles

Browse Source
This commit is contained in:
BlueFox
2025-04-13 20:18:30 +02:00
parent 8da401dc8f
commit 1f6167c9f2
4 changed files with 11 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
public/de/about/index.html
View File

@@ -247,7 +247,7 @@ Dies ist mein persönlicher Blog (den ich in meiner Freizeit betreibe, all das i
<h1 class="post-title">
<a href="https://blog.privacynerd.de/de/about/">Über</a>
</h1>
<div class="post-meta"><time class="post-date">2025-04-13</time><span class="post-reading-time">3 Minuten Lesezeit (248 Wörter)</span></div>
<div class="post-meta"><time class="post-date">2025-04-13</time><span class="post-reading-time">3 Minuten Lesezeit (246 Wörter)</span></div>
@@ -267,7 +267,7 @@ Dies ist mein persönlicher Blog (den ich in meiner Freizeit betreibe, all das i
</ul>
<p>Schau dich doch <a href="/de/">einfach mal um</a>, und vielleicht findest du ja etwas Interessantes!</p>
<h2 id="the-logo">Das Logo<a href="#the-logo" class="hanchor" ariaLabel="Anchor">#</a> </h2>
<p>Das Logo für diesen Blog ist entstanden, als mir irgendwann mal langweilig war. Es gefiel mir einfach, und seitdem verwende ich es regelmäßig für meine Projekte. Um genau zu sein, habe ich es gezeichnet, als ich vielleicht 11 Jahre alt war, und das erste Mal wurde es in einem <code>Django + Python</code>-Projekt von mir verwendet, das sich „PiFi“ nannte - was jetzt auch der Name eines High-Speed-Wifi-Nachrüstsatzes und eines HiFi-Systems ist, die beide auf Raspberry Pi&rsquo;s basieren (aber diese sind völlig unabhängig voneinander und konnten meine Namensgebung nicht kennen). Wie auch immer.</p>
<p>Das Logo für diesen Blog ist entstanden, als mir irgendwann mal langweilig war. Es gefiel mir einfach, und seitdem verwende ich es regelmäßig für meine Projekte. Um genau zu sein, habe ich es gezeichnet, als ich vielleicht 11 Jahre alt war, und das erste Mal wurde es in einem <code>Django + Python</code>-Projekt von mir verwendet, das sich „PiFi“ nannte - was jetzt auch der Name eines High-Speed-Wifi-Nachrüstsatzes und eines HiFi-Systems ist, die beide auf Raspberry Pi&rsquo;s basieren (aber diese sind völlig unabhängig voneinander und konnten meine Namensgebung nicht kennen). Naja.</p>
<h2 id="the-story-behind-it">Die Geschichte dahinter (und noch mehr)<a href="#the-story-behind-it" class="hanchor" ariaLabel="Anchor">#</a> </h2>
<p>Der erste Post in diesem Blog verrät viel über die Geschichte und wie es zu der Idee für diesen Blog kam. Wen es interessiert, der kann es <a href="https://blog.privacynerd.de/de/posts/how-it-all-began/">hier</a> nachlesen.</p>

8
public/en/posts/how-it-all-began/index.html
View File

@@ -328,7 +328,7 @@
</figcaption>
</figure>
<p>Things got even more hardware-oriented with my first ESP32 - new ideas emerged and with them new projects. A self-built safe (super safe made of wood!) with my own <a href="https://git.privacynerd.de/BlueFox/ESafeP">software</a> was just as much a part of it as my own <a href="https://git.privacynerd.de/NetSpeaker/NetSpeaker">MP3 (and much more) player</a>. The 3D printer was also used time and again, as it is common in the DIY space - for example for the housing for my battery-powered <a href="https://git.privacynerd.de/BlueFox/losungepaper">ePaper showing the german “Tageslosung“ - a verse from the bible for every day</a>.</p>
<p>Things got even more hardware-oriented with my first ESP32 - new ideas emerged and with them new projects. A self-built safe (super safe made of wood!) with my own <a href="https://git.privacynerd.de/BlueFox/ESafeP">software</a> was just as much a part of it as my own <a href="https://git.privacynerd.de/NetSpeaker/NetSpeaker">MP3 (and much more) player</a>. The 3D printer was also used time and again, as it is common in the DIY space - for example for the housing for my battery-powered <a href="https://git.privacynerd.de/BlueFox/losungepaper">ePaper showing the german ”Tageslosung“ - a verse from the bible for every day</a>.</p>
<figure><img src="/files/how-it-all-began/netspeaker.jpg"
alt="Image of a finished, self-made NetSpeaker in housing - which is (not) just MP3 player."><figcaption>
<p>A NetSpeaker</p>
@@ -336,7 +336,7 @@
</figure>
<figure><img src="/files/how-it-all-began/losung-epaper.jpg"
alt="Image of the finished ePaper, which displays the current daily verse of the bibel (german “Tageslosung“)"><figcaption>
alt="Image of the finished ePaper, which displays the current daily verse of the bibel (german ”Tageslosung“)"><figcaption>
<p>Losungs-ePaper (showing a biblical verse of the day)</p>
</figcaption>
</figure>
@@ -346,7 +346,7 @@
<p>Well, not much has changed since then. At some point, self-hosting got a thing for me, and I also got to know wood as an exciting material (as already mentioned above). It&rsquo;s so cool to see what you can host yourself: your own file synchronization service, your <a href="https://git.privacynerd.de/">own Github</a>, media servers, and so on. Initially, everything ran on the aforementioned Raspberry Pi. Later, however, access from outside the home network was required, and since then many services have been running on a rented server.</p>
<figure><img src="/files/how-it-all-began/gitea-a-self-hosted-github.png"
alt="Screenshot of my self-hosted instance of Gitea"><figcaption>
<p>„A self-hosted Github“</p>
<p>”A self-hosted Github“</p>
</figcaption>
</figure>
@@ -357,7 +357,7 @@
</figcaption>
</figure>
<p>So, I sat down and looked for ways to create a blog. Of course, it had to be self-hosted, and maybe even a bit self-made. This led me to <a href="https://gohugo.io/">Hugo</a> (Jekyll was also a consideration), a relatively simple (and very fast) static site generator that can generate websites from Markdown (among other things) and is therefore actually perfect for a blog. When choosing a theme, I initially wavered between “create it myself” and “use an existing one”. Due to a lack of time and for reasons of simplicity, I ended up using an existing one, more precisely <a href="https://themes.gohugo.io/themes/hugo-theme-terminal/">Terminal</a>. Adapted to my needs, the blog itself was already finished relatively quickly<sup id="fnref:3"><a href="#fn:3" class="footnote-ref" role="doc-noteref">3</a></sup>. Now it&rsquo;s just waiting to be filled with content.</p>
<p>So, I sat down and looked for ways to create a blog. Of course, it had to be self-hosted, and maybe even a bit self-made. This led me to <a href="https://gohugo.io/">Hugo</a> (Jekyll was also a consideration), a relatively simple (and very fast) static site generator that can generate websites from Markdown (among other things) and is therefore actually perfect for a blog. When choosing a theme, I initially wavered between ”create it myself“ and ”use an existing one“. Due to a lack of time and for reasons of simplicity, I ended up using an existing one, more precisely <a href="https://themes.gohugo.io/themes/hugo-theme-terminal/">Terminal</a>. Adapted to my needs, the blog itself was already finished relatively quickly<sup id="fnref:3"><a href="#fn:3" class="footnote-ref" role="doc-noteref">3</a></sup>. Now it&rsquo;s just waiting to be filled with content.</p>
<h2 id="planned-content">Planned content<a href="#planned-content" class="hanchor" ariaLabel="Anchor">#</a> </h2>
<p>What you plan at the beginning is rarely implemented in exactly the same way in the end - and that will probably also be the case with this blog, and that&rsquo;s a good thing. After all, everything evolves. But I&rsquo;m still going to write down what I plan to write on this blog in the future - because I do have a rough idea.</p>
<ul>