3 ms·
I looked at the JS being loaded in the first place, and it's just two files: the entire JQuery package, and: $(document).ready(function() { $('nav'
by mynameismon 4y ago
I looked at the JS being loaded in the first place, and it's just two files: the entire JQuery package, and:
$(document).ready(function() {
$('nav').load('/nav.html');
});
That's...it.
- hombre_fatal 4y agoThere is a modern fervor over tech minimalism/purism where using even a little bit of Javascript, for example, is just a reminder that perhaps the answer all along was to just to use the trade-offs that work for you. Note, the people in the article were burned by wiki software that went unmaintained during its rewrite from Python 2.7 to Python 3 (afaict). Now they are editing HTML files on a production server. I'm sure getting let down like they did gave them a specific distaste for certain trade-offs that work for the rest of us, but you can also imagine the babies being thrown out with the bathwater like scaling out an article database without revision history. That said, it tends to be a good thing when you realize a vastly simple solution works for you.
- cestith 4y agoI'm kind of wondering why JQuery is needed for that, but I'm not curious enough to dig into nav.html to see why. The navigation looks simple enough. An at-home static site generator that literally replaces a custom tag with the contents of a file using sed would take less maintenance it seems to me than keeping JQuery updated.