Well, it finally happened. My journey into managing this blog site with Grav has reached a new step. To date I have done everything with this site using nothing more than the Grav Admin Panel web interface. My goal was to see how long I could manage everything this way. That is, I have not had to resort to "going under the hood" to modify any files, etc. But this time I hit a wall.
This post could easily go by so many titles...
Stop Being So Anal
Let It Go, Dad!
(Yes, I am quoting Remi from the Pixar animation "Ratatouille". 😀)
How I Learned to Stop Worrying and Love the Bomb My Imperfections
the list goes on.
TL;DR
In short, it is about learning to know when it is time to consider something done.
Background
Not long ago, my family was sitting on the couch watching some YouTube clips by Mark Rober. (Yes, we are "cord cutters", currently using an AppleTV hooked up to the living room flat panel. Though we are more like "never been corded" types, as I have not had/paid for cable in over 20 years. But that's another story.)
TL;DR
For anyone who may just be starting in their network automation journey and is looking to simply get their head around things a bit, this page is a curation / summation / collection of notes regarding doing network DevOps work that in some form involves Python.
If it helps save at least one person time, whether in learning, figuring out what not to spend time on, etc., then it will have served its purpose. (It is also for myself as a refresher, as nothing helps one learn like having to write it down or teach it to someone else.)
Not long ago, I started this blog. I already wrote a post on how I researched CMSs and landed on using the Grav CMS for my own needs. But I would like to dig into this a bit deeper. With each passing day that I learn something new in this CMS, the more I love it.