This note is a reference for myself: what goes in a post, and how the site is put together. If you are reading the journal and wondering why every entry has the same shape, the answer is that a fixed shape is much easier to keep up with than a blank page.
What a post needs
| Field | What it is for |
|---|---|
title |
Shown on the card and as the page heading |
summary |
One sentence; used on cards, in RSS and in search results |
date |
Drives sorting. 2026-10-16 is fine, no time needed |
tags |
Group related notes. They are also the URLs of the tag pages |
draft |
true keeps it out of the published site |
Where it lives
Each language gets its own file, and the filename is the URL.
src/content/blog/
├── en/2026-10-16-why-i-built-this-site.md → /blog/2026-10-16-why-i-built-this-site/
└── ro/2026-10-16-why-i-built-this-site.md → /ro/blog/2026-10-16-why-i-built-this-site/
Keeping the two filenames identical is what makes the language switch jump straight to the translation instead of back to the front page.
Formulas and code
Because most of my courses are maths-heavy, the notes render real formulas. Something like a sine wave can be written inline, , or on its own line:
Code is highlighted the same way:
def rms(samples: list[float]) -> float:
return (sum(s * s for s in samples) / len(samples)) ** 0.5
Writing it
I write in Obsidian directly against these folders, so the note looks the same while I am writing it and after it is published. A task list works too:
- Write the note
- Add a diagram
- Read it again tomorrow with a clear head