Lessons from Neovim configurations and 11ty website templates
This weekend, I changed my neovim configuration from nvchad to kickstart nvim. The primary reason was that the level of abstraction in nvchad was a bit too much, and I wanted a single init.lua file in which I could comfortably add plugins through lazy.nvim. I hadn’t recognized it up until now, but not fully appreciating the structure for the config was presenting a significant barrier to further making my setup my own. Not only was kickstart neovim incredibly easy to setup, I have been able to tweak so many things that I had put off of the past year because I now have a much better handle on how to implement those changes. Throughout this experience, I learned more about the trade-offs of complexity, and reflected on how my neovim adventures differed from revamping my website with 11ty. In one instance I was building from the top down — I took a template and began to strip away and tweak the components I didn’t need. In the other, I removed most of the complexity and started from a more bare bones configuration to build off of.