From a technical point of view, I have almost no critique for you. It scales well, everything works, and there is great beauty in simplicity. I'm not quite sure what you are want to use .spaced-line for, but if you want to keep it in line with the other sizing usages, you can convert px to em by dividing by 16 (in this specific case, because the default is 1em is 16px - it is not a general rule that 1em = 16px). So you could make it like this:

.spaced-line {
  margin: 6.25em 0;
  text-align: center;
}

Then .spaced-line will scale at the same rate as everything else if you do CTRL + or CTRL -.

That's a huge nitpick, but is the only thing I could really think of.

You write very well, I have no critique there. Making it bilingual is great.

I signed your guestbook. Lovely site!

Recently I added an English version to my WordPress-powered, 11+ years old blog, using a plugin called Polylang (the free version). It's quite nice! In the back-end, it's as if I had another blog, but sharing resources — layout, plugins, even assets like images used in posts —, all translatable and yet with minimal overhead.

It's way more complex than your solution, if anything else because it involves a self-manage CMS, but if you're serious about your blog, may worth the investment (of time, resources, and a little money).

I appreciate the speed of loading in the days of some web packager for every site (the jank, content shifts and, on storefronts, moving of a cursor in a search box make me wish for simpler sites).

The images are used well in the posts I checked and Noirvember was a fun read!

Nice blog! I’m a big fan of Bear, and might try setting one up at some point.

I think I like the separation via folders into the folders /br and /en. I like it better than appending the language at the end option.

There may be a way to setup redirects where you could link the old non-foldered English posts to the new ones under the /en folder, but I’m not sure how you’d set that up with Bear. I’m also not sure it’s really needed (other than for consistency), since you have the navbar set up to allow for filtering to just the English and Portuguese post lists.

I would just have new posts going forward sorted into the folders, and not worry about the old posts - to prevent breaking old links.

In regard to redirecting existing URLs, this is a good idea. You can add redirects to your .htaccess if you're using apache (if you don'tknow what you're using, it's probably apache). This is a decent article on it: https://www.semrush.com/blog/301-redirect-htaccess/

And chatgpt will understand how to write the specific rules so you see how that works. That, to me, is one of the excellent usecases for AI. :)

The blog itself: Incredibly simplistic. But those designs stand the test of time. Your goal is communication, and this design supports that. I support your design.

You may want to consider:

1. When users finish an article, they are at the bottom of your page, so you might wish to duplicate the navigation, or at least some elements of it, at the bottom. Or at least have a link back to the top of the page.
2. You may wish to link together articles where it makes sense to do so. Perhaps previoous/next links, or in specific cases if you write a series of articles, linking to the next/previous in that series (this would be done manually, of course)
3. A popular feature many blog softwares have would be some sort of "related posts" - to encourage people to find more blogs posts and make it easier for them to find them. There is a little bit of inertia that will prevent some from going back to the list of posts and choosing another.

But it's all about what makes sense to you, imho.

I have other preferences, but they are preferences - design choices - and you have made them and I think they are good. (For example, I prefer justified text, but there are arguments for and against it)