Here Are the Finalists for the 2025 Hugo Awards https://reactormag.com/2025-hugo-finalists/

Hugo finalists announced - https://seattlein2025.org/wsfs/hugo-awards/2025-hugo-award-finalists/

Anyone familiar with #Hugo enough to tell me if I can get it to just make me a static site without any extra features? No blogging, no "featured" pages or whatever. I just want to stick a bunch of markdown files into a directory structure and have them rendered into HTML.

You know, the thing I did in 30 lines of C#, but with proper linking between pages. Heheh.

Why is it so hard to find a #Hugo theme that will just work for any sort of site that isn't incredibly complex and works with any slight modification of the example site?

Este domingo, HUGO vuelve a tierras madrileñas.
#OsNaufragosTeatro #Hugo #Autismo

https://www.diariodetorrejon.es/el-teatro-jose-maria-rodero-acoge-la-obra-hugo-en-el-dia-mundial-del-autismo/

It's weird... now that my site is based on #hugo - the excellent static site generator, I end up composing most of my blog posts inside my programming #ide, #vscodeOSS.

I can't say exactly why, but something about it feels strange.

If you're a web designer or developer, this might be just what you need! I've created a website showcasing the most beautiful and inspiring web designs. Check it out here: https://thecolophon.com/

And in my next act I will deploy the blog for #badgefed to #cloudfare and make it static with #hugo and still #federate with #activitypub using workers

https://github.com/tryvocalcat/badgefed-blog

Periodic update:
- graduated from my studio engineering program
- minor medical things
- more background on the song we released CC-BY-SA this week

https://venya.soundslike.pro/blog/2025/03/six-months/

I'm looking for a new comment system for my #Hugo blog, and I'm not seeing any clearly great options.

I've been using #Commento for #comments on my blog for a few years now, and it's about time to switch comment systems.

Commento has been effectively unmaintained for 4 years (see https://gitlab.com/commento/commento). Their (paid) hosted version has been continuing to work, but I've seen increasing numbers of errors lately, so it's time to move.

I'd really *love* something that could integrate semi-natively with #activitypub so new blog posts could show up in Mastodon and Mastodon replies would show up as comments, *but* I don't want to require a fediverse account for commenters; that rules out most (all?) of the embedded-Mastodon comment options.. After looking through Hugo's somewhat-outdated list of commenting options (https://gohugo.io/content-management/comments/), it looks like #Discourse is the only option that even *slightly* fits that, and it's a lot heavier-weight than I really want to run today. Hours-of-maintenance-per-comment should be less than 1, thanks.

Basic requirements:

- Either easy to self-host or has a cheap hosted option.
- Allows anonymous comments plus common external auth options.
- Possible to import comments from Commento, possibly requiring code on my part, but it needs to allow arbitrary names, etc.
- Works with static sites.
- Not a privacy disaster
- If self-hosted, ideally written in something sane -- Go, Rust, etc. *Ideally* it's a single binary that listens to HTTP and stores comments in Postgres.
- Supports Markdown.

Does anyone have anything that they're really happy with?

Wanting to get back to #blogging but also wanting to move my blog from wordpress to #hugo web framework seems to be a combo of too many steps that’s been stopping me from doing either.
I should probably start with the first, and move to the second only once I’ve gotten back to the groove of writing and publishing regularly regardless of the quality of the posts.

Hey #FediHelp

I am using quarto in different python projects.

I am using a different python environment for each of my projects.
And per project I am rendering them as HTML files.

How can I make a blog to aggregate my HTML files ?
Like one blog post per project ?

I would like to create a portfolio and I my open to alternatives to quarto

Thanks

I was recently having a conversation about "Mastodon hug of death" and how the type of site (static vs dynamic), caching, and page size all play a role in handling traffic. While I never expect to have to mitigate against that scenario, I wanted to take a look at my page size and my most recent post was 5.7 MB. That's pretty chonky, especially as I'm planning to self-host the site!!
That was enough motivation to finally just make a Hugo shortcode to insert images as resized figures (with full size images linked). That reduced my page size to 450 KB, a 12x reduction! That's the TL;DR, but here's the TL;PR.

I’m a wordy bastard. I really struggle with 500 characters. I’d struggle with 500 words sometimes. It's been hard to find a flow here (despite Mona's fantastic thread generator.)

I’m creating a #blog to house longer writings and share thoughts here without requiring anyone to visit platforms so many gathered here to avoid.

I'm using #Hugo instead of my usual #WordPress and dipping my toes into #Go and #TailwindCSS. I've only created the local structures, but so far, I dig it! It's #FOSS too!

Hey #indeweb, anyone with experience hosting (open-sourced) personal sites with media files (images, PDF) on #Codeberg? I aim to make use of a #Hugo pipeline from Codeberg to Codeberg Pages, like from Github to Github Pages / Netlify / Vercel. I don't want to test the limits of the terms of use though. Also considering #Cloudinary, bit unsure how to manage the upload automatically.

I ended up choosing #11ty over #Hugo.

Just posted a brief description of how I incorporated the HTML details disclosure element into my emacs to ox-hugo to hugo stream. Many who are more tech-savvy than I will find this obvious, but it might be helpful to some.

#emacs #hugo #oxhugo

https://johnrakestraw.com/post/using-the-html-details-disclosure-element/

Like many others, I post notes about my reading in my blog. Some of those notes are rather long, and some readers might stop scrolling and leave the page before noticing a book that they might find interesting. But TIL about the HTML details disclosure element. Now I have a short summary, and readers can click on the summary to reveal the entire note. Seems much cleaner to me. (And #emacs, #oxhugo, and #hugo make it very easy to do this.)

https://johnrakestraw.com/reading

#blogging @bookstodon