Documenting code, one commit at a time.
A cluttered navigation bar is the digital equivalent of a messy entryway: it’s the first thing visitors see, and if it's misaligned, the entire professional impression suffers. Recently, while working on my personal portfolio, I found that small inconsistencies in the navbar layout and language toggle were creating unnecessary visual noise.
In my work on the Darwinhamiltonc/my-portfolio project, I recently reached a point where the codebase felt heavy. It is easy to fall into the trap of thinking that once a feature is shipped, the code is static. But as I revisited my portfolio, I realized that maintenance isn't just about adding features—it is about pruning the garden.
We often leave code alone
As my portfolio project grew, inconsistent spacing between sections began to create a disjointed visual experience. Elements felt crowded in some areas and oddly isolated in others, leading to a loss of rhythm that distracted from the core content.
To restore balance, I moved away from hard-coded, case-by-case margin adjustments and transitioned toward a
