Jekyll2026-04-24T01:59:44+00:00https://osnibjunior.dev/feed.xmlOsni B. JuniorPersonal blog by Osni B. Junior — technical and non-technical writing about software, work, and life.Osni B. JuniorHello, world — again2026-04-22T10:00:00+00:002026-04-22T10:00:00+00:00https://osnibjunior.dev/2026/04/hello-worldThis page used to be a small collection of social-media buttons — a glorified link-in-bio. It served its purpose, but it never felt like mine. A website should say something.

So I’m turning it into a blog. Nothing fancy: minimal layout, dark mode, markdown posts. A place to write about the things I work on, the things I learn, and — occasionally — things that have nothing to do with code.

A few ground rules I’m setting for myself:

  • Publish even when it’s imperfect.
  • Keep posts short unless they truly need to be long.
  • Write in English, but don’t stress about sounding native.
  • Link to the source. Always.

If you’re reading this and something resonates (or doesn’t), the links at the bottom of every page will get you to me. See you in the next one.

]]>Osni B. JuniorNotes on shipping small static sites in 20262026-04-15T09:00:00+00:002026-04-15T09:00:00+00:00https://osnibjunior.dev/2026/04/sample-technical-postStatic sites are having a quiet renaissance. Not the kind that trends on Hacker News every six months, but the kind where people who just want a personal site keep reaching for the same small set of tools — and it mostly Just Works.

Why Jekyll, still

GitHub Pages builds Jekyll natively. That’s the whole pitch. No CI to configure, no Node toolchain to keep alive, no lockfile drama. You write Markdown, push to main, and a few seconds later the site is live.

There are faster builders (Hugo), prettier DX stories (Astro), and friendlier plugin ecosystems (11ty). All true. But for a personal blog — where the build runs once a week and nobody cares if it takes four seconds — the “zero moving parts” story is hard to beat.

The pieces that matter

A personal blog really only needs:

  1. A layout system so the header and footer don’t live in every file.
  2. A post list that reverses itself automatically.
  3. A tag system — optional, but nice to have.
  4. Dark mode — table stakes at this point.

Everything else is polish.

A dark-mode detail worth knowing

The one trap with dark mode is the flash of wrong theme on first paint. The fix is a small inline script in the <head> that applies data-theme before the CSS loads:

<script>
  var stored = localStorage.getItem('theme');
  var prefersDark = matchMedia('(prefers-color-scheme: dark)').matches;
  document.documentElement.setAttribute(
    'data-theme',
    stored || (prefersDark ? 'dark' : 'light')
  );
</script>

That’s it. Render-blocking, yes, but it’s 200 bytes and it saves you the eye-searing white flash every time someone with dark mode enabled lands on your site.

Closing thought

Boring tools for boring problems, fancy tools for fancy problems. A personal blog is a boring problem — and that’s a feature.

]]>Osni B. Junior