Fixing center

Author: 4ZM

.python-version

@@ -0,0 +1 @@
+3.13

docs/custom.css

@@ -14,3 +14,10 @@
         width: 100%;
     }
 }
+
+.centered {
+    display: block;
+    margin-left: auto;
+    margin-right: auto;
+    text-align: center;
+}

docs/posts/2024-11-03-welcome-to-the-jungle/welcome-to-the-jungle.md

@@ -18,7 +18,7 @@ As a principal software architect and someone who cares deeply about how we deve
 
 If you are a senior developer, architect, tech lead, or CTO, I invite you on an excursion. We’ll travel winding paths through philosophy, biology, and social sciences to discover new ways of thinking about software development.
 
-<center>![Trekking through rainforest](trekking.jpeg){ width=80% }</center>
+![Trekking through rainforest](trekking.jpeg){ .centered width=80% }
 
 What is a software ecosystem? A global multitude of programs, libraries, and operating systems? A whirlpool of interactions between developers, teams, and organizations?
 
@@ -40,7 +40,7 @@ Removing the flaky character of tests will make the state of the trunk (main bra
 
 A careful, deliberate intervention in the environment by an experienced steward of the ecosystem can have a profound positive impact and make the ecology thrive and flourish.
 
-<center>![Architect in rainforest](architect.jpeg){ width=80% }</center>
+![Architect in rainforest](architect.jpeg){ .centered width=80% }
 
 Another lesson that we ought to have learned from biological ecology is that interventions into an environment can have catastrophic consequences. In some cases, we have witnessed how an ignorant action has led to a full collapse of the ecosystem.
 
@@ -68,7 +68,7 @@ These two approaches represent quite different ecological environments for devel
 
 When Darwin visited the Galápagos Islands in 1835, he noticed how finches had evolved differently on different islands. The isolation of the islands caused a heterogeneity of life forms. This is also true for poly-repo ecologies. They tend to exhibit variations in coding style, build systems, branching strategy, etc. Being isolated, they also exhibit favorable traits like internal cohesion, less complex dependencies, and security by segmentation.
 
-<center>![Paradise islands](islands.jpeg){ width=80% }</center>
+![Paradise islands](islands.jpeg){ .centered width=80% }
 
 A monorepo, on the other hand, is a vast rainforest. Life-forms abound and can always immediately interact with each other, especially in watering holes and other nodal points (e.g., the build system). A healthy monorepo is, however, always internally structured in components and parts — it’s not a giant ball of mud. In the jungle, some life forms inhabit the treetops and others the forest floor. In the monorepo, most developer teams spend their time in a niche, a fairly limited set of components and products.
 

docs/posts/2024-11-06-steal-this-class/steal-this-class.md

@@ -18,7 +18,7 @@ To make things worse, much of the advice on Stack Overflow and (LLM output train
 
 Since Ctrl-C, Ctrl-V is the de facto standard programming paradigm, and you are going to do it regardless, consider using these boilerplate classes. They are “copy-paste safe.” They have the right defaults, and they are not missing some essential piece that will get you into trouble later.
 
-<center>![Cute cat](take-this.jpg)</center>
+![Cute cat](take-this.jpg){ .centered }
 
 Of course, we have the [C++ Core Guidelines](https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines). These are all the defaults and best practices you *should* be using. But, be honest, you’re not going to read those, are you? These are the templates you have been looking for.
 
@@ -212,6 +212,6 @@ public:
 
 Now, before you get too worked up and start yelling at the screen. I know, there are exceptions to almost all of the recommendations in this post. But they are exceptions. What I have presented are the safe and sane defaults. Your starting point for modern C++.
 
-<center>![Hair of fire](hair-on-fire.jpeg)</center>
+![Hair of fire](hair-on-fire.jpeg){ .centered }
 
 <pre><p style="text-align: center; margin-top: 0px; margin-bottom: 4pt;">•  •  •</p></pre>

docs/posts/2024-12-01-control-is-an-Illusion-anyway/control-is-an-Illusion-anyway.md

@@ -92,7 +92,7 @@ Enforcing unconditional and automated formatting before merging is also key. If
 
 The Rosy Reviews process works well for us but it might not be for everyone. Our reviews latency is lower than in many other organization, but it still too high if you ask our developers. If you are curious about going down the eventual quality consistency route, here are some of the challenges we encountered. Consider if this is something that might need special attention in your organization.
 
-<center>![Clueless Revierer](clueless-reviewer.jpeg){ width=50% }</center>
+![Clueless Revierer](clueless-reviewer.jpeg){ .centered width=50% }
 
 It doesn't work without reliable tests. If you do "lazy" reviews without tests, you're back to yolo land. That's only fun until it breaks.
 

docs/posts/2024-12-18-git-beyond-the-basics/git-beyond-the-basics.md

@@ -18,11 +18,9 @@ For instance, if you are not using `git maintenance` or `worktree`, you are miss
 
 Much of the content in this post is straight out of the 2024 FOSDEM talk "So You Think You Know Git?" by the amazing Scott Chacon. Here is that talk and the follow-up "Part 2" from DevWorld 2024. I have cherry-picked the parts that I found most useful from his presentations and mixed them up with some of my own favorite Git features.
 
-<center>
-<iframe width="380" height="252" src="https://www.youtube.com/embed/aolI_Rz0ZqY?si=w-fTNQIOv5cjEjoc" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
-
-<iframe width="380" height="252" src="https://www.youtube.com/embed/Md44rcw13k4?si=aPogguUMXINligKV" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
-</center>
+<iframe class="centered" width="380" height="252" src="https://www.youtube.com/embed/aolI_Rz0ZqY?si=w-fTNQIOv5cjEjoc" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
+</br>
+<iframe class="centered" width="380" height="252" src="https://www.youtube.com/embed/Md44rcw13k4?si=aPogguUMXINligKV" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
 
 Before we get started, make sure you have the latest version of git installed: [https://git-scm.com/](https://git-scm.com/) Some of the things covered in this post are relatively new. If you haven't updated your Git installation for a few years, now is the time.
 
@@ -36,7 +34,7 @@ Let's start by setting up some nice log formatting and default arguments with a
 git config --global alias.l "log --pretty=format:'%C(#cccc00)%h %Cred%ad %Creset%<(60,trunc)%s%C(auto)%d %C(magenta)%<(15,trunc)%an' --date=format:'%y%m%d'"
 ```
 
-<center>![zlib gitlog color](git-log.png){ width=100% }</center>
+![zlib gitlog color](git-log.png){ .centered width=100% }
 
 With formatting out of the way, let's look at some other nice `git log` options.
 
@@ -108,7 +106,7 @@ While we're at it, let's add some color and a bit more context to the branch out
 git config --global alias.b "branch --format='%(color:#cccc00)%(objectname:short) %(color:red)%(committerdate:short) %(color:bold white)%(refname:short)'"
 ```
 
-<center>![branch alias](git-branch.png){ width=60% }</center>
+![branch alias](git-branch.png){ .centered width=60% }
 
 ## git push --force-with-lease
 
@@ -147,7 +145,7 @@ This problem is more common if you have long-lived feature branches or workflows
 
 If you are using Git from the terminal, you might consider adding a bit of ornamentation to your prompt. This is my favorite and it works well for bash.
 
-<center>![zlib gitlog color](git-prompt.png){ width=50% }</center>
+![zlib gitlog color](git-prompt.png){ .centered width=50% }
 
 ```
 git clone https://github.com/magicmonty/bash-git-prompt.git ~/.bash-git-prompt --depth=1
@@ -203,7 +201,7 @@ git commit -m "Adding a bar file"
 
 You then proceed to work and realize that what you are doing should be part of the first commit. You could try to remember this and fix it when you do your interactive rebase later. But you don't have to. You can do a fixup and stay in your development flow. Later, you autosquash the fixup commits and do any further interactive rebasing (if there is still something to do).
 
-<center>![fixup commit](fixup.png){ width=60% }</center>
+![fixup commit](fixup.png){ .centered width=60% }
 
 ```
 echo "fubar" >> foo
@@ -219,7 +217,7 @@ git rebase --autosquash
 
 Maybe the least useful advice in this blog post is also not a git native topic, but a GitHub specific one. But since I know this really trigger some people's OCD, I consider it a public health service. I'm referring to the GitHub language stats for you repo...
 
-<center>![github-linguist](linguist.png){ width=80% }</center>
+![github-linguist](linguist.png){ .centered width=80% }
 
 Some times, the tool that GitHub uses `github-linguist` (you can run it locally) need a little help. You can provide hints in a `.gitattributes` file.
 

docs/posts/2024-12-25-elf-shenanigans/elf-shenanigans.md

@@ -18,7 +18,7 @@ As hackers, we some times get a *"what if I just..."* moment. A delightful spark
 
 It turns out, that works like a charm and I have never seen a better looking symbol table!
 
-<center>![console](xmas.gif)</center>
+![console](xmas.gif){ .centered }
 
 The assembler complains about silly section names, but putting control characters in a linker script works just fine.
 

docs/posts/2025-03-31-low-level-talk/low-level.md

@@ -14,6 +14,4 @@ How low can you go? When it comes to embedded programming, the "full stack" star
 
 <pre><p style="text-align: center; margin-top: 0px; margin-bottom: 4pt;">•  •  •</p></pre>
 
-<center>
-<iframe width="560" height="315" src="https://www.youtube.com/embed/-uZRiTgqQRU?si=0mqLmcUe_uo1zuQb" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
-</center>
+<iframe class="centered" width="560" height="315" src="https://www.youtube.com/embed/-uZRiTgqQRU?si=0mqLmcUe_uo1zuQb" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>

docs/posts/2025-04-05-bitter-prediction/bitter-prediction.md

@@ -23,7 +23,7 @@ For a few days, I had a fantastic time. Then, I didn’t. It wasn’t that the t
 I recognized the feeling from a moment in my youth. Back then, I loved playing the game "UFO: Enemy Unknown." The game involved building a global defense network to ward off an alien invasion. Building bases, researching new technologies, and buying weapons were all part of the strategy mechanics. At the same time, I was beginning to explore how software was built. Using a hex editor and a disassembler, I would pick apart things to see how they worked. This was another kind of game that I thoroughly enjoyed. One day, it hit me: the amount of money I had in the game must somehow be stored in the save files! I could use my hex editor to change it.
 
 
-<center>![xcom](xcom.png){ width=60% }</center>
+![xcom](xcom.png){ .centered width=60% }
 
 Sure enough, my plan worked. I awarded myself a generous donation, and for a few hours, I was thrilled. I could buy all the cool stuff I couldn’t afford before and I had no problem fending off the pesky alien invasion. Aliens were no match for my hex editor.
 

docs/posts/2025-05-19-awesome-apis-talk/awesome-apis.md

@@ -14,14 +14,10 @@ I've recently delivered two talks on *API design best practices for libraries*.
 
 <pre><p style="text-align: center; margin-top: 0px; margin-bottom: 4pt;">•  •  •</p></pre>
 
-Here is a recording from the ACCU talk 2025 on Apr 3rd.
+Here is a recording from the ACCU talk 2025 on Apr 3rd. It's a shorter 20min version.
 
-<center>
-<iframe width="560" height="315" src="https://www.youtube.com/embed/crQQjdOARCQ?si=uaF_j_VZqs9FlFzo" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
-</center>
+<iframe class="centered" width="560" height="315" src="https://www.youtube.com/embed/crQQjdOARCQ?si=uaF_j_VZqs9FlFzo" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
 
-Here is a recording from the Stockholm C++ Meetup on May 8th. This is a longer version of the talk with a lot of interaction and participation from the audience. 
+Here is a recording from the Stockholm C++ Meetup on May 8th. This is a longer version of the talk with a lot of interaction and participation from the audience. Unfortunately the audio of audience comments is a bit lacking.
 
-<center>
-<iframe width="560" height="315" src="https://www.youtube.com/embed/myoXUpnvfeA?si=hzjJTk2C6f6n4jr0" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
-</center>
+<iframe class="centered" width="560" height="315" src="https://www.youtube.com/embed/myoXUpnvfeA?si=hzjJTk2C6f6n4jr0" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>