@skyfaller I have thought about this in the past. I know there are CMSses designed to work with static sites, like this one for #jekyll, though I’ve never evaluated any.
There’s got to be something similar for #hugo, though cost may be a concern if it’s an enterprise focused tool.
Spent a week trying to improve the RSS on my new test Hugo site, because the one they give you is second class, and I had no luck. I broke it 3 times, made it worse twice, somehow erased it completely, so I finally thought hey there's far better nerds than me out there so I looked around, found this, and forked it! https://gist.github.com/LorenDB/2faa2bb78885806c8d4c914d01130e1e#Hugo#RSS
#Hugo docs state that the "root" of your resultant website is /static, and anything in there can be referenced as the root, and they're lying, and I'll set them on fire in front of their families.
@webology Using #hugo the last couple of days I asked myself what the difference is between the assets and static folder? And I wasn't the first. So assets hosts files that can/must be processed and static contains files that are used as is. For #Django I think it is more obvious what the purpose of those two directories are by naming them static/src and static/public as suggested by @josh.
💡 My personal website used to run with a static site generator that I created on my own. Even though I had a fully customized site generator, I switched to #Hugo. This article explains why I would do such a thing. https://www.mattlayman.com/blog/2018/tale-two-site-generators/
trying out #Hugo atm, i have a feeling that this framework might be more suitable for me than Astrojs from #javascript since i only care for writing contents in markdown...
I was looking at some discussion of static site generators and whether one could be used for blogs since it was designed for documentation.
FFS. A blog is just text with a date at the top, and optionally hyperlinks to whatever you're talking about. Bonus points for an index of titles and dates.
I keep thinking that all the crap we've layered on top of web pages is hostile and anti-democratic, that it's all gatekeeping, that the original point was to make it easy to publish text and share it.
@foolishowl That’s so odd - even a cursory look at something like #hugo / #GoHugo reveals a ton of themes that are for documentation OR blogs. (I found fewer themes for SSG for small service-oriented businesses, which surprised me because it seems so obviously suited for that niche.)
Agree about your hostile comment tho. A lot out there is way more complex than it needs to be.
Part 6 of "A Guide to Implementing ActivityPub in a Static Site (or Any Website)" is now out.
Sorry about the delay, this is the part that not many people will like, I assume. I try to explain how to implement the inbox, which by nature is dynamic non-static.
I need advice or a hint from @gohugoio users. I want to make a fairly simple static webpage for a small restaurant, but the complex part is that they need to be able to edit this week’s menu. If I were the one editing the menu, that would be a no-brainer: SSH into my dev machine, edit the MD file, and do a simple git push. However, I need to make it simple for them, the restaurant staff. Please ping me if you have ideas.
I fancy using #Mastodon as a comment system for my blog but the solutions I found were made for #Hugo. How bad would it be if I reused them in my #Quarto blog?
Making a getting started guide for screen reader users that want to try a Static Site Generator and I was sad to discover that #11ty is not in any Windows package manager I can find. If this isn’t correct let me know so I can get this right. For now, looks like the guide will be for Hugo #GoHugo#Hugo#SSG#StaticSiteGenerator
Since I've gotten exactly one webmention for my blog, I obviously had to put some work in to display this webmention on my blog. 😄 Had to do some reading to figure out how to make Hugo download external resources, but otherwise it was pretty smooth sailing. Much thanks to https://webmention.io/. Still not implemented sending webmentions yet though.
Check your #Hugo#Markdown postings for a number of common problems and issues before publishing a post.
Each part is configurable. Probably works with tools like #Jekyll too. Works standalone, or as #git pre-commit check. And comes with a suite of tests if you want to add new checks.
My list of talks is a #Hugo data template for a while now. That's now enriched with metadata, especially coordinates. And the website got a map showing all the locations.