Some tasks are just too thorny (or annoying) for plain ol' HTML, and blogging is one of them. Add that to the never ending to-do list of ways to improve the site.Īnd now, with my tail between my legs, I'm crawling back to the Javascript ecosystem to help me out of a bind. Ideally that would include removing all my 3rd party dependencies, and I'm not there yet. I wanted to get as close to 100% native browser technologies as possible.
That's why I removed all the JS dependencies in a fit of frustration and defiance 6 months ago. I imagine the same is true for any other form of engineering or art. To create something that lasts, though, you need to carefully consider the tools and materials you use to build it. There are a limitless number of problems to be solved, bugs to be squashed, new toys to try out. In fact, it's part of what makes web development so exciting. It's just a matter of time! The few things that don't break should be considered exceptions to the rule and can be counted on two hands (kudos, Space Jam).īut don't misunderstand me! This is not all bad. If you build something and then simply wait. The entire web is in a constant state of decay, some parts degrading more quickly than others. If you're new to web development, let me disabuse you of any misconceptions to the contrary: this is par for the course. I'm just biding my time until it fails again. But even now, completely rebuilt, it's a ticking time bomb.
#NVM INSTALL NODE PERMISSION DENIED UPDATE#
It was easier to rebuild the entire thing from scratch than to update all the dependencies and libraries. The same thing happened with a small Rails app that I built around the same time. I left it alone and one day POOF it stopped working. At some point the compilation totally broke and I didn't feel like investing the time to figure out why. An earlier version of this site was built in 2015 using Jade for templating and Grunt for compiling the assets.
Truth be told, I am genuinely apprehensive about updating the tech stack of my portfolio site. Follow along as I try to get step 1 of the Eleventy docs working, but instead spend an entire night installing Node. Two posts per year isn't quite the clip I was hoping for! So my new plan is to make it so easy to write, publish, and manage content that I have no excuse but to do it more often. Moving my blog to Eleventy, Part 1: Installing Node with NVM tl:dr Īpparently writing my first blog post wasn't enough to kick my butt into high blogging gear. Moving my blog to Eleventy, Part 1: Installing Node with NVM
0 kommentar(er)
