FAQ
Frequently asked questions about the site, the content, and the person behind it.
Published January 27, 2024
Frequently Asked Questions
Common questions about the site, what is on it, how it is built, and who I am.
About the Site
What is this site about?
It is a personal knowledge base and blog — a place where I write down things I am learning, document projects I am building, and occasionally think out loud about technology.
Topics include web development, infrastructure, networking, homelabbing, virtualisation, and the occasional detour into music technology or something I encountered outdoors.
Who is this for?
Honestly, it started as notes for myself. But if you are a developer, hobbyist, or curious person who finds something useful here, that is a very welcome outcome.
How often is content updated?
When I have something worth writing. There is no publishing schedule. Some weeks I write several things. Some months nothing new appears. Quality over cadence.
Can I use content from this site?
For personal and educational use, yes — please attribute and link back to the source. For anything commercial, ask me first. See the Terms of Service for full details.
About Me
What is your background in technology?
Long story, gladly told. I have been around computers since the HCL Beanstalk and Pentium era — watched the whole arc from bare-metal Windows installs to containers and cloud infrastructure.
I started with HTML and was immediately hooked. Perl and PHP on a LAMP stack followed. Java and JavaScript became my main languages for a long time. These days I am picking up Python, which I should have done years ago.
Virtualisation is a genuine love of mine — hypervisors, homelabs, spinning environments up and tearing them down. There is something deeply satisfying about that.
Do you only write about technology?
Mostly, yes. But context leaks in. I spend a lot of time outdoors — hiking, exploring places with no cell signal — and that perspective shapes how I approach problems. Music and music technology are also constants in my life.
Why do you blog / build a public wiki?
Writing forces clarity. If I cannot explain something simply, I probably do not understand it well enough yet. Publishing raises the bar — knowing someone else might read it makes me think harder before hand-waving past the details.
Technical Questions
What technology powers this site?
- Next.js 16 with the App Router
- MDX for content with React component support
- Tailwind CSS v4 for styling
- Shiki for syntax highlighting via rehype-pretty-code
- Vercel for hosting
How is the wiki structured?
Pages live as MDX files in content/pages/. Directories become sections, files become pages.
The sidebar is generated automatically from the filesystem — no config required.
Add a file, it appears. See the wiki overview for more.
Something is broken. What do I do?
Tell me. Seriously. I would rather fix it than have something broken and not know about it. A brief description and the page URL is all I need.
Still Have a Question?
If something is not answered here, get in touch. Chances are if you are wondering, someone else will too — and I will add it here.