New Hugo themes resource


And that site itself is also built with Hugo.


This looks like a curated list based on the Hugo Themes website.

From a cursory look on GitHub I saw that @JugglerX is a contributor to this project.

I had a chat with Rob Austin in a Slack somewhere about it; I didn’t know that the project was built by Hugo, but it’s rather nice. I think the data model is more or less powered by taxonoies. He said he was going to write a blog article about it (and about the “Why Hugo” part).

I built Actually I work for now and this was a side project I led in house there which they loved. I’m really happy I could build it on Hugo. We will have some blog posts coming out in a few days, I’ll drop the link here when its done.

We’d love for Hugo Themes to help in any way on this project. Or I’m open to ideas on how I can help flow through people interested in Hugo back to this site. (I just added links to the each SSG’s official site on the taxonomy pages) -

Hugo was definitely up to the task. But I had to write some additional node scripts to fetch API data at build. This is an area the JS gens might have handled more elegantly and when I recommend Hugo I wish I could provide an option for this use case that remained inside of the Hugo framework. I think Hugo could draw some inspiration from this implementation in 11ty - It’s pretty tight.

1 Like

There are certainly improvements planned in the “API department”, but I suspect 11ty’s Stargazers example could be easily implemented by Hugo’s getJSON function.

How so? This is an API call that needs to be made using Fetch or Axios and it requires an authorization header with a Github Token. My understanding is getJSON can only fetch public URL’s.

I implemented a similar stargazers call for jamstackthemes, you can see the source here - - Can I do this with getJSON?

You can use Curl to access that API, so it’s pretty straight HTTP. I haven’t looked at it lately, but I think passing the Github token as a query parameter (which you can load via os env in Hugo) is still an option. It’s less secure than a header, but it’s certainly possible.

I quickly scrambled this together:

1 Like