It’s because we’re always telling folks to take their JS questions somewhere else!
Half-serious though: I hope we’re not making Hugo a less happy experience because we discourage JS folks here.
I hardly ever use JS myself. In fact, I’m working on an output format for
gemini, a protocol that takes fan-favorites from
http(s), in part because I just really like using Hugo for publishing documents. I like simple websites that I can read. JS has never been a large component of that.
Over in the meta Discourse instance (I’m apparently a FOSS groupie with too much time) I’m always running into folks integrating Discourse in other sites, and sometimes into Hugo, and they all get caught up in the JS portions. I let them know I just
getJSON posts in at build time, and it’s awesome.
When Hugo creates content pages from data sources I imagine a lot of JAMmers are gonna rethink their strategy (pfft, yeah right, the bright ones will).
Quick aside that kinda reinforces these ideas: my work with Hugo has informed my other efforts, including integrating WordPress with CDNs. Wanting to take advantage for static site reasons, CDNs, their uses and methods, have really opened my mind up to when and where web pages are being built. That in turn opened up more ideas on building Hugo sites and using data caches to build what are essentially “dynamic” static html sites.
No JS (or node, or Grunt, or…). Though I’m starting to see go (modules) as being part of my deploy stack. Is GAMstack a thing?