#+TITLE: martensteppat's journal
#+NICK: martensteppat
#+DESCRIPTION: German Webdesigner, Author (Fantasy + Science Fiction), Human Design Coach. I love Emacs, Org Mode, org-node and Star Trek.
#+AVATAR: https://martensteppat.de/images/Marten-Steppat.jpg
#+CONTACT: mail@martensteppat.de
#+CONTACT: https://martensteppat.de
#+GROUP: Emacs https://relay.org-social.org
#+GROUP: Org Social https://relay.org-social.org
#+GROUP: Org Mode https://relay.org-social.org
#+FOLLOW: https://org-social.org/social.org
#+FOLLOW: https://andros.dev/static/social.org
#+FOLLOW: nickanderson https://cmdln.org/social.org

* Posts
** 2026-02-27T19:32:17+0100
:PROPERTIES:
:TAGS: :org-node:notes:
:CLIENT: org-social.el
:MOOD: 
:END:

On my notes and zettelkasten journey, I found *denote* and thought, I would stick to it forever.

A year later I found a new god and switched to *org-node.*

Why?

Denote taught me to name my files meaningful. Its naming conventions showed me what is needed to keep my files showing up for the keywords I would use later. Identifier, title, tags. But it also forced me to do so.

Some files I expect to find alphabetically. Getting away a bit from the zettelkasten philosophy to use one file per information, I wanted some file names to just be "emacs.org" or "org-mode.org". I wanted to store more information in those files, but at the same time jump quickly to the exact information I was looking for.

Org-node was the game changer.

I could name my files like I wanted, keeping in mind what I learned from denote. I can store them wherever I want, since I can order org-node to watch this and that folder, while others can be excluded.

Org-node uses the ID from Org Mode instead of denote using its own Identifier, so it feels more native to me.

And finally, org-node can put IDs on any org heading (node). The interactive search will show me, in which file the information is, I am looking for.

Backlinks are supported, but (at least with my configuration) are stored away in a drawer.

In the end, it feels more natural for me, simpler but at the same time more powerful.

I would like to hear your thoughts about denote vs. org-node, if you tried both.

** 2026-03-02T18:50:58+0100
:PROPERTIES:
:TAGS: 
:CLIENT: org-social.el
:REPLY_TO: https://www.matem.unam.mx/~omar/social.org#2026-02-22T01:54:12-0600
:MOOD: 
:END:

I just started with Hugo. My search engine told me, for building websites I could use Hugo, but I could also use org-mode to export into Hugo's markdown which would finally export into HTML. I chose markdown.

From my point of knowledge, Hugo comes with some pre-defined themes to download, pre-configured elements like header, footer, menu, lists of your articles, automatically sorting at the right place by category, tags or as an overall summary. There is a central config file, in which you can define the general behaviour of your website. If you want to enhance your SEO, you find possabilities.

Hugo has quite some docs explaining all the possibilities on several sites, which gives me the expression, if you know how it works, it's so fast and easy as it can get.

On the other side, the descriptions of chapter 14 "Publishing" on [[orgmode.org]] seem rather short and all the listed properties aren't explained.

So my impression is still, that Hugo offers more out of the box to config a new website to your likings, as long as you want to stick to some standards.

I will check org-publish again for another project soon.