Compare commits

...

9 Commits

Author SHA1 Message Date
0b5411c6bd Fixed footer and license 2025-11-01 22:45:13 +01:00
e9e56da86c Fixed theme padding 2025-11-01 22:18:02 +01:00
d8b3064f13 Edited post Hugo workflow 2025-11-01 15:39:54 +01:00
e05401e20a Adjusted content updated theme and some other minor edits 2025-11-01 15:25:21 +01:00
5daa1e5f3a Updated theme 2025-11-01 15:24:35 +01:00
53cedfb96b Edited post Hugo workflow 2025-11-01 10:56:35 +01:00
129dc0889c Fixed tags on post Hugo workflow 2025-11-01 00:11:59 +01:00
8928f88b68 Updated page About 2025-11-01 00:07:22 +01:00
f2a88fbb60 Fixed link on page Emacs init.el.org 2025-11-01 00:06:55 +01:00
8 changed files with 75 additions and 34 deletions

View File

@@ -2,12 +2,12 @@
title = "About"
author = ["Anne"]
date = 2025-10-31T00:00:00+01:00
lastmod = 2025-10-31T23:52:43+01:00
lastmod = 2025-11-01T14:15:45+01:00
draft = false
url = "/about"
+++
Hi there --- and welcome!
## Hi there --- and welcome! {#hi-there-and-welcome}
You've stumbled upon my quiet spot online. I'm Anne (she/her), a DIY geek kind of girl living in the wonderful city of Amsterdam.
@@ -25,9 +25,8 @@ Thanks for stopping by --- stay curious!
x Anne
---
P.S. if you're wondering...
### P.S. if you're wondering... {#p-dot-s-dot-if-you-re-wondering-dot-dot-dot}
- you'll find the repo of this blog here: [git.minded.net/anne/blog.minded.net](<https://git.minded.net/anne/blog.minded.net>)
- my Emacs configuration: [init.el.org](<https://blog.minded.net/pages/emacs/init.el.org>)
- my literate Emacs configuration: [init.el.org](<https://blog.minded.net/pages/emacs/init.el.org>)

View File

@@ -2,7 +2,7 @@
title = "init.el.org"
author = ["Anne"]
date = 2025-10-31T00:00:00+01:00
lastmod = 2025-10-31T23:51:04+01:00
lastmod = 2025-11-01T00:03:32+01:00
tags = ["emacs"]
draft = false
+++
@@ -19,7 +19,7 @@ My Emacs repository: [git.minded.net/anne/emacs](https://git.minded.net/anne/ema
The source version of this file: [git.minded.net/anne/emacs/src/branch/main/init.el.org](https://git.minded.net/anne/emacs/src/branch/main/init.el.org?display=source)
Or view this file on my blog: [blog.minded.net/pages/emacs/init.el.org](https://blog.minded.net/pages/emacs)
Or view this file on my blog: [blog.minded.net/pages/emacs/init.el.org](https://blog.minded.net/pages/emacs/init.el.org)
### About me {#about-me}

View File

@@ -2,19 +2,19 @@
title = "Hello World!"
author = ["Anne"]
date = 2025-03-16T00:00:00+01:00
lastmod = 2025-10-31T23:30:47+01:00
lastmod = 2025-11-01T14:16:51+01:00
draft = false
summary = "Youve stumbled upon my quiet spot online. Probably you ended up here while figuring something out, just like I usually do. Hopefully you find a few answers here --- or at least some inspiration."
+++
Hi there --- and welcome!
## Hi there --- and welcome! {#hi-there-and-welcome}
Youve stumbled upon my quiet spot online. Probably you ended up here while figuring something out, just like I usually do.
Im [Anne](<mailto:anne@minded.net>) (she/her), a DIY geek kind of girl living in the wonderful city of Amsterdam. Some time ago, out of curiosity, I started building my own private server from collected scrap parts. I wanted to understand how the internet actually works. So I got myself a [domain name](<https://minded/net>) and figured out how to set up and manage my own mail server on Linux.
Im Anne (she/her), a DIY geek kind of girl living in the wonderful city of Amsterdam. Some time ago, out of curiosity, I started building my own private server from collected scrap parts. I wanted to understand how the internet actually works. So I got myself a [domain name](<https://minded/net>) and figured out how to set up and manage my own mail server on Linux.
I quickly discovered the joy of being independent --- and how empowering it is to understand things because youve built them yourself.
While tinkering, I learned a lot from others who shared their bits and pieces online. Thats exactly what this small corner of the web is about too. Hopefully you find a few answers here --- or at least some inspiration. Happy to help :-)
x Anne
x [Anne](<mailto:anne@minded.net>)

View File

@@ -1,27 +1,32 @@
+++
title = "The appeal of wysiwyg"
author = ["Anne"]
date = 2025-10-31T00:00:00+01:00
lastmod = 2025-10-31T23:29:54+01:00
date = 2025-11-01T00:00:00+01:00
lastmod = 2025-11-01T15:36:21+01:00
tags = ["hugo", "workflow"]
draft = false
summary = "For a DIY girl like me, [Hugo](https://gohugo.io) is awesome. Hugo is a static website generator that gives you complete control over its output --- right from the command line. What more could a girl wish for?"
+++
For a DIY kind of girl like me, [Hugo](<https://gohugo.io>) is the best. Hugo is a static website generator that gives you complete control of its output --- right from the command line. What more could a girl wish for?
## Hugo is awesome {#hugo-is-awesome}
<!--more-->
For a DIY girl like me, [Hugo](<https://gohugo.io>) is awesome. Hugo is a static website generator that gives you complete control over its output --- right from the command line. What more could a girl wish for?
Even better, you can use your [favorite text editor](<https://www.gnu.org/software/emacs/>) to write new content or tweak your theme. While I love the command line, I do understand the appeal of wysiwyg: it's nice to be able see how your content will look before publishing it online. But do you really need a full-blown content management system with all the bells and whistles for that? Nope, actually you don't. Hugo can help you out just as easily!
Even better, you can use your [favorite text editor](<https://www.gnu.org/software/emacs/>) to write new content or tweak your theme. While I love the command line, I do understand the appeal of wysiwyg: it's nice to be able see what your content will look before publishing it online. But do you really need a full-blown content management system with all the bells and whistles for that? Nope, actually you don't. Hugo can help you out just as easily!
## My workflow {#my-workflow}
### My workflow {#my-workflow}
So what does my workflow look like? In a nutshell: I create some new content on my laptop, check out how it renders locally in my browser, and when I'm satisfied, push it to [Gitea](<https://about.gitea.com/>) --- which automaticaly deploys it online.
So what does my workflow look like? In a nutshell: I create some new content on my laptop, check out how it renders in my browser locally, and when satisfied, push it to my server --- which automaticaly deploys it online.
Preferably, I write in Emacs, typing away on my laptop sitting somewhere cozy, with a cup of coffee within reach. On my laptop, I have a local repo clone of my blog. The git repository lives on Gitea on my private server, which also serves my blog to the world.
Preferably, I write in [Emacs Org Mode](<https://orgmode.org/>), typing away on my laptop sitting somewhere cozy, with a cup of coffee within reach. On my laptop, I have a local clone of my blog. The main git repository lives online on [Gitea](<https://about.gitea.com/>) on my private server, which also serves my blog to the world.
> Note to self: write a post about magically deploying a static website with Hugo, Gitea and webhooks.
Before I start writing, I `cd` into the root of my local copy of my blog's repository and fire up the Hugo web server:
```sh { linenos=false }
cd ~/projects/blog.minded.net
hugo server --buildDrafts --navigateToChanged
```
@@ -36,12 +41,14 @@ hugo new content posts/my-new-post.md
emacs content/posts/my-new-post.md
```
Every time I save my changes in Emacs, ox-hugo exports the org files to markdown files for Hugo. The Hugo server then renders the new content, so I can immediatly see what my writings look like in my browser. Wysiwyg enough for me!
Every time I save my changes, the Hugo embedded server renders the new content on the fly, so I can immediatly see what my writings look like in my browser. Wysiwyg enough for me!
> Hugo supports several [content formats](<https://gohugo.io/content-management/formats/>) out of the box. [Markdown](<https://www.markdownguide.org/tools/hugo/>) is the default format, but it also supports [Emacs Org Mode](<https://orgmode.org/>) and other formats. There are so many ways to get things done! Since I love Org Mode, I split up the technical stuff (i.e. my Hugo theme) and my content. When writing and editing posts and pages [ox-hugo](<https://github.com/kaushalmodi/ox-hugo>) helps to export my Org files to Markdown for Hugo. Maybe I'll circle back on that later in another post.
## Get it out there {#get-it-out-there}
### Get it out there {#get-it-out-there}
When I'm done writing, I commit and push my edits to the repository in Gitea:
When I'm done writing, I commit and push my edits to my main repository on Gitea:
```sh { linenos=false }
git add content/posts/my-new-post.md
@@ -51,6 +58,6 @@ git push
Gitea then automagically gets Hugo to rebuild my blog and publish it online. It really is that simple.
Note to self: don't forget about `draft = true` in the [front matter](<https://gohugo.io/content-management/front-matter/#draft>) of my new post :P
> One last note to self: don't forget about `draft = true` in the [front matter](<https://gohugo.io/content-management/front-matter/#draft>) of my new post :P
If you are curious, you can find the source code of this blog here: <https://git.minded.net/anne/blog.minded.net>.
If you are curious, you can find the repo of this blog here: [git.minded.net](<https://git.minded.net/anne/blog.minded.net>).

View File

@@ -5,7 +5,8 @@ html {
body {
line-height: 1.5;
max-width: 768px;
margin: 1rem;
margin: auto;
padding: 0 1rem 0 1rem;
font-family: Tahoma, Verdana, Arial, sans-serif;
color: lightgray;
}
@@ -38,12 +39,18 @@ nav ul li a {
color: violet;
}
div#tags div {
div#byline {
color: grey;
font-size: 0.9rem;
}
div#tags {
display: inline;
}
div#tags ul {
padding: 0;
padding-left: 0.5rem;
display: inline;
}
div#tags ul li {
@@ -59,6 +66,30 @@ a {
color: palevioletred;
}
h1, h2, h3, h4 {
padding-top: 1rem;
}
h1 {
color: palevioletred;
}
blockquote {
color: lightblue;
font-size: 0.9rem;
margin: 0;
padding-left: 0.5rem;
border-left: 0.4rem solid lightblue;
}
div#footer {
padding: 2rem 0 2rem 0;
}
div#footer p {
color: grey;
font-size: 0.9rem;
margin: 0;
}

View File

@@ -1 +1,4 @@
<p>Copyright {{ now.Year }}. All rights reserved.</p>
<div id="footer">
<p>&copy; {{ now.Year }} by <a href="mailto:anne@minded.net">Anne</a> is licensed under <a href="https://creativecommons.org/licenses/by-nc-sa/4.0/">CC BY-NC-SA 4.0</a><img src="https://mirrors.creativecommons.org/presskit/icons/cc.svg" alt="" style="max-width: 1em;max-height:1em;margin-left: .2em;"><img src="https://mirrors.creativecommons.org/presskit/icons/by.svg" alt="" style="max-width: 1em;max-height:1em;margin-left: .2em;"><img src="https://mirrors.creativecommons.org/presskit/icons/nc.svg" alt="" style="max-width: 1em;max-height:1em;margin-left: .2em;"><img src="https://mirrors.creativecommons.org/presskit/icons/sa.svg" alt="" style="max-width: 1em;max-height:1em;margin-left: .2em;"></p>
<p>Please feel free to share and reuse.</p>
</div>

View File

@@ -12,8 +12,7 @@ For a given taxonomy, renders a list of terms assigned to the page.
{{- with $page.GetTerms $taxonomy }}
{{- $label := (index . 0).Parent.LinkTitle }}
<div>
<div>{{ $label }}:</div>
<div id="tags">
<ul>
{{- range . }}
<li><a href="{{ .RelPermalink }}">{{ .LinkTitle }}</a></li>

View File

@@ -1,10 +1,12 @@
{{ define "main" }}
<h1>{{ .Title }}</h1>
{{ $dateMachine := .Date | time.Format "2006-01-02T15:04:05-07:00" }}
{{ $dateHuman := .Date | time.Format ":date_long" }}
<time datetime="{{ $dateMachine }}">{{ $dateHuman }}</time>
{{ $dateMachine := .Date | time.Format "2006-01-02" }}
{{ $dateHuman := .Date | time.Format "2006-01-02" }}
<div id="byline">
<time datetime="{{ $dateMachine }}">{{ $dateHuman }}</time>
{{ partial "terms.html" (dict "taxonomy" "tags" "page" .) }}
</div>
{{ .Content }}
{{ partial "terms.html" (dict "taxonomy" "tags" "page" .) }}
{{ end }}