brycewray.comBryce Wray’s website | Observations, opinions, geekiness2018-09-14T00:00:00-05:00https://www.brycewray.com/Bryce Wrayhttps://www.brycewray.com/bw@brycewray.comMixed nuts #182026-06-03T14:27:00-05:00Bryce Wrayhttps://www.brycewray.com/bw@brycewray.comhttps://www.brycewray.com/posts/2026/06/mixed-nuts-18/AVIF support in Hugo, hashes in action(s), floaters, and clankers.<em>AVIF support in Hugo, hashes in action(s), floaters, and clankers.</em><hr />For no major reason other than that I feel like writing about a few odds and ends which have recently occupied my mind, here’s <a href="https://www.brycewray.com/posts/2026/03/mixed-nuts-17/">yet another</a> “Mixed nuts” post.<hr><p><em>To get posts’ <strong>full</strong> content in your reader, you can subscribe to <a href="https://www.brycewray.com/index.xml">this feed</a>.</em></p>A “new normal” update2026-05-04T15:29:00-05:00Bryce Wrayhttps://www.brycewray.com/bw@brycewray.comhttps://www.brycewray.com/posts/2026/05/new-normal-update/Improving my scripting following hvm’s recent changes.<em>Improving my scripting following hvm’s recent changes.</em><hr /><a href="https://www.brycewray.com/posts/2025/12/new-normal-starting-hugo-0.153.x/">Late last year</a>, I had to adapt this website’s repository to accommodate a change in how <a href="https://gohugo.io" rel="noopener">Hugo</a>’s macOS version is packaged. In short, I started to use the <a href="https://github.com/jmooring/hvm/" rel="noopener">hvm (Hugo Version Manager) app</a> to manage my computer’s use of the Hugo binary. More recently, after a change to hvm itself, I made a further adaptation. Fortunately for me, as in the case of that earlier post, Hugo maintainer and hvm creator <a href="https://github.com/jmooring" rel="noopener">Joe Mooring</a> gave me help in overcoming, as I described to him, “my embarrassing lack of <a href="https://english.stackexchange.com/questions/47694/when-did-things-like-fu-start-to-spread" rel="noopener">scripting-fu</a>.”<hr><p><em>To get posts’ <strong>full</strong> content in your reader, you can subscribe to <a href="https://www.brycewray.com/index.xml">this feed</a>.</em></p>Hugo’s new CSS powers2026-04-02T12:19:00-05:00Bryce Wrayhttps://www.brycewray.com/bw@brycewray.comhttps://www.brycewray.com/posts/2026/04/hugos-new-css-powers/A recent update can make it easier than ever to style your site, depending on how you want to do that styling.<em>A recent update can make it easier than ever to style your site, depending on how you want to do that styling.</em><hr />As I mentioned in my <a href="https://www.brycewray.com/posts/2026/03/mixed-nuts-17/">previous post</a>, I was intrigued when the release of <a href="https://gohugo.io" rel="noopener">Hugo</a> <a href="https://github.com/gohugoio/hugo/releases/tag/v0.158.0" rel="noopener">v.0.158.0</a> introduced its <a href="https://gohugo.io/functions/css/build/#article" rel="noopener"><code>css.Build</code></a> function. The new powers that resulted are worth a look when you consider all the aspects of styling a site you’ve built, or plan to build, on Hugo. Still, the enhancements have certain limitations of which you’ll also want to be aware.<hr><p><em>To get posts’ <strong>full</strong> content in your reader, you can subscribe to <a href="https://www.brycewray.com/index.xml">this feed</a>.</em></p>Mixed nuts #172026-03-16T16:46:00-05:00Bryce Wrayhttps://www.brycewray.com/bw@brycewray.comhttps://www.brycewray.com/posts/2026/03/mixed-nuts-17/A new name for Eleventy, trying CachyOS, some new powers for Hugo, and other folderol from my noggin.<em>A new name for Eleventy, trying CachyOS, some new powers for Hugo, and other folderol from my noggin.</em><hr />Here we go <a href="https://www.brycewray.com/posts/2025/09/mixed-nuts-16/">once again</a> with an entry in my “Mixed nuts” series of posts, each of which contains musings on multiple topics that have recently occupied my semi-reasonable facsimile of a brain.<hr><p><em>To get posts’ <strong>full</strong> content in your reader, you can subscribe to <a href="https://www.brycewray.com/index.xml">this feed</a>.</em></p>Browsing tips2026-02-19T16:00:00-06:00Bryce Wrayhttps://www.brycewray.com/bw@brycewray.comhttps://www.brycewray.com/posts/2026/02/browsing-tips/Some suggestions for making websites easier to read — in more ways than one.<em>Some suggestions for making websites easier to read — in more ways than one.</em><hr /><p>If you spend lots of hours per week perusing content on one or more web browsers as I’ve been doing since, oh, the mid-1990s, there are ways you can tailor that activity somewhat more to your liking. Many of you probably already know about the potential solutions I’ll mention in this post but, on the off-chance that you don’t, here are some tips for improving your browsing experience. Specifically, this is about: (1.) adjusting how the browsers actually render web pages; and (2.) filtering out ads and certain other content types that interfere with one’s browsing pleasure. To be sure, there’s a certain degree of interaction between those two, but I’ve found that they require two different sets of solutions.</p>
<p><em>(This is almost entirely about browsing from a computer, not from within a phone or tablet, particularly since the vast majority of my readers still view my content from their computers rather than their other devices. However, I still will have a few comments about browsing with the latter.)</em></p><hr><p><em>To get posts’ <strong>full</strong> content in your reader, you can subscribe to <a href="https://www.brycewray.com/index.xml">this feed</a>.</em></p>Three items of note2026-01-21T16:57:00-06:00Bryce Wrayhttps://www.brycewray.com/bw@brycewray.comhttps://www.brycewray.com/posts/2026/01/three-items-note/The Cloudflare acquihire of Astro, visited links of a not-different color, and a 1Password syntax highlighting bug.<em>The Cloudflare acquihire of Astro, visited links of a not-different color, and a 1Password syntax highlighting bug.</em><hr />Since I last wrote herein, three events have piqued my nerdy curiosity, suggesting some appropriate musings on them. The first affects the web development business; the second has to do with a change in how visited links look in some web browsers; and the third concerns a browser extension bug which, for a few weeks, fouled up code blocks in some websites (including this one).<hr><p><em>To get posts’ <strong>full</strong> content in your reader, you can subscribe to <a href="https://www.brycewray.com/index.xml">this feed</a>.</em></p>My “new normal,” starting with Hugo 0.153.x2025-12-26T10:29:00-06:00Bryce Wrayhttps://www.brycewray.com/bw@brycewray.comhttps://www.brycewray.com/posts/2025/12/new-normal-starting-hugo-0.153.x/Switching to hvm and converting my scripts to work with Hugo’s packaging for macOS.<em>Switching to hvm and converting my scripts to work with Hugo’s packaging for macOS.</em><hr />Until a few days ago, those who use the <a href="https://gohugo.io" rel="noopener">Hugo</a> static site generator on macOS have had to deal with Apple’s <a href="https://eclecticlight.co/2021/12/11/explainer-quarantine/" rel="noopener">quarantine feature</a> each time they downloaded a new Hugo version. With the recent release of Hugo <a href="https://github.com/gohugoio/hugo/releases/tag/v0.153.0" rel="noopener">0.153.0</a>, that ceased to be the case. For most Hugo-on-macOS users, that’s a good thing. For nerds like me who’ve been managing their Hugo-on-macOS workflows through scripting, it was . . . complicated. However, with major help from one of Hugo’s key personnel, I was able to make this “new normal” a good thing for me, too.<hr><p><em>To get posts’ <strong>full</strong> content in your reader, you can subscribe to <a href="https://www.brycewray.com/index.xml">this feed</a>.</em></p>From Pages to Workers (again): revisited2025-11-24T14:44:00-06:00Bryce Wrayhttps://www.brycewray.com/bw@brycewray.comhttps://www.brycewray.com/posts/2025/11/pages-workers-again-revisited/Getting the straight story from one who definitely knows what’s what at Cloudflare.<em>Getting the straight story from one who definitely knows what’s what at Cloudflare.</em><hr />Earlier this year, I had <a href="https://www.brycewray.com/posts/2025/05/pages-workers-again/">some</a> <a href="https://www.brycewray.com/posts/2025/07/hugo-sites-cloudflare-workers-or-not/">things</a> to say about a <a href="https://blog.cloudflare.com/full-stack-development-on-cloudflare-workers/" rel="noopener">Cloudflare announcement</a> concerning its Cloudflare Workers (CFW) platform and, more to the points I was making, the Cloudflare Pages (CFP) product on which this site had lived for a good while. It now turns out that I may have misunderstood things at the time, so this post is my attempt to fix things somewhat.<hr><p><em>To get posts’ <strong>full</strong> content in your reader, you can subscribe to <a href="https://www.brycewray.com/index.xml">this feed</a>.</em></p>Getting HTTP/3 on Cloudflare with Firefox2025-10-30T12:28:00-05:00Bryce Wrayhttps://www.brycewray.com/bw@brycewray.comhttps://www.brycewray.com/posts/2025/10/getting-http3-cloudflare-firefox/There are two paths to the goal, although I can use only one.<em>There are two paths to the goal, although I can use only one.</em><hr />After wondering for a good while about a Firefox-specific weirdness I was seeing on Cloudflare-hosted sites, I finally found that there are two solutions. Only thing is, I am able to use only one of those two. That said, I’ll describe the problem and how I found the answers — or, in my particular case, <em>answer</em>, singular.<hr><p><em>To get posts’ <strong>full</strong> content in your reader, you can subscribe to <a href="https://www.brycewray.com/index.xml">this feed</a>.</em></p>Mixed nuts #162025-09-26T12:12:00-05:00Bryce Wrayhttps://www.brycewray.com/bw@brycewray.comhttps://www.brycewray.com/posts/2025/09/mixed-nuts-16/The Google ruling, Netlify’s pricing changes, and other tales of interest.<em>The Google ruling, Netlify’s pricing changes, and other tales of interest.</em><hr /><a href="https://www.brycewray.com/posts/2025/06/mixed-nuts-15/">Yet again</a>, I’ll indulge myself in commenting on a variety of topics stemming from the nerdy stuff to which I pay attention. I’d originally intended for this latest post to be focused on just one of them — I’ll leave it to you to guess which — but, the longer I procrastinated, the greater number of happenings that I wanted to discuss. It’s not a desirable habit, but it’s <em>Moi</em>, folks. Let’s have at it.<hr><p><em>To get posts’ <strong>full</strong> content in your reader, you can subscribe to <a href="https://www.brycewray.com/index.xml">this feed</a>.</em></p>