Hello, world
This is the first entry — a template more than a post. I'm setting up a place to write weekly about a project I'm working on: a small lead-generation system for my dad's taekwondo school. The point of publishing the work isn't to teach anyone yet. It's to make sure I actually finish the thing.
Every future post will be a copy of this file. I'll change the title, the date, and the body, and that's it. No CMS, no build step, no database. Just a folder of plain HTML files I can read and edit by hand five years from now without help.
What this section is for
Subheadings break long entries into scannable chunks. Use them when a post crosses a natural seam — a new topic, a shift from problem to solution, the start of a numbered series. Don't use them just to decorate.
Write the obvious thing first. The clever version can come in the edit, if it comes at all.
Lists are useful when the items don't have a connecting argument between them — when the prose would just be a string of "and" clauses. A few examples of when to reach for one:
- Listing the exact steps to reproduce a bug.
- Enumerating the constraints I'm designing against.
- Showing the shortlist of options I considered before picking one.
Code shows up in two flavors. Short references go inline, like
npm install or a path like ~/Documents/mysite.
Longer snippets get their own block:
// A code block. Multi-line, monospaced, scrolls horizontally if it needs to.
function greet(name) {
return `Hello, ${name}.`;
}
console.log(greet('world'));
When I want to point at something elsewhere, I use a plain link. Underline shows up on hover only — it's there when you reach for it, gone when you don't.
That's every element this site knows how to render. If a future post needs something not on this list, I'll add it here first so the styling stays in one place.