Below you will find pages that mention the tag “meta-blog-maintenance”
I hope I’ve fixed my homepage deployment again now. I need to observe it for a bit.
More Feeds
📝 I’ve added a new page listing all the feeds and follow options for this page: Feeds / Subscribe. Inspired by the same page Jarrod Blundy made.
Looks like my DNS issue is resolved and my homepage should work again.
The keychain APIs from Apple are strange, but now I’ve updated my GitHub token and fixed a bug in my blogging app at the same time.
I just released a new subjection for my book reading log: Series. It still needs to be filled with all the content but that will take some time. 📚I hope this subpage allows me to better track which series I still need to finish reading.
Hugo is so strange, I’ve worked on a shortcode, and it just did not want to work.
{{- $matched := where $allSeries "Params.lostInterest" false -}}
It took me nearly an hour to find the issue! The culprit was the camelCase spelling of lostInterest. As soon as I changed it to all lower case, it worked fine. But the big catch is that for simple rendering, the value this works:
{{Params.lostInterest}}
But in the where statement, it needs to be written like this: Params.lostinterest.
Ok just did some more googling and found out now that custom parameters should always be lower case and should use snake case instead of camel case.
I love Hugo for its render speed, but the documentation could be better. Somehow I continuously run into issues that need quite convoluted solutions to solve. Today’s problem is to get absolute URLs for image links in the content part, so my images work correctly in the feeds. It looks like this is a solution Oo.
@V_ Thanks for that. I'll have to try it. I'd given up on images in the RSS feed because I really like the convenience of using relative URLs and keeping the post's assets in the same folder as the Markdown file.
by jack on
@jack You're welcome. I've also found this feature: gohugo.io/getting-s... It would allow for a nicer solution but only works with images. And you're right this would also allow me to move my assets back next to the md file as well.
by V_ on
It looks like Amazon changed their ebooks details page once again, and my scraping code does no longer work. It would be nice when they would just over an API.
Homepage History (v1-v6)
With the release of Version 7, it is time again to document my old homepage designs. So I don’t lose this information in the past. This post contains a list of all my homepage designs over time. I like to keep a log of how the homepage has changed since it’s inception. The list is complete, but between version five and six, there was quite a long gap where the homepage was not online at all.First post on the new Hugo based homepage. I hope everything works as expected.
@V_ Another webmention test the first one did not work :-(
by V_ on
@V_ the biggest complaint I constantly see about Hugo is the template engine being finicky and unintuitive. I considered it for my blog until I read about seasoned developers — which I’m not — having frustration with it. What has your experience been with Hugo?
by peterimoore on
@peterimoore I don't think it's any worse than any of the others, I just think the others are more similar to each other. The Hugo template engine is mostly just an extension of the golang templating stuff
by hjertnes on
@hjertnes is it hard for someone to learn with no golang experience, in your opinion? The appeal of Hugo over Jekyll is the build speed and single binary, and I’d be using a pre-made theme to start with. However, I’d still want to be able to tweak and make changes if needed.
by peterimoore on
@peterimoore, I think this: seasoned developers — which I’m not — having frustration with it summarizes my expericences pretty well. In the end I was able to solve nearly all of my issues, but the way to get there needs more energy then I think it should. And I don't think I had these issues with jekyllrb. But it is just to slow when you have more then five posts in you're blog :-( And I think in the end every system has it's quirks.
by V_ on
@V_ that’s my biggest issue and hesitation with Jekyll, quite honestly. Especially when I plan on heavily posting to my blog, even though I’d simply be committing to GitHub and having Netlify do the build. Right now I’m researching Zola as a candidate instead of Jekyll/Hugo.
by peterimoore on
@peterimoore you don't need to know any golang. In the same way you don't need any ruby to use jekyll
by hjertnes on
@peterimoore any speific reason which you like from Zola? I've only had a short look at the page right now it looks rather close to Hugo from what I've seen.
by V_ on
@V_ I like that it’s a single binary like Hugo, with fast build times from being written in Rust. I’ve read a couple of posts from people using it that its template engine is much friendlier, including one who ported a theme from Jekyll in a very short time due to similarities.
by peterimoore on
@peterimoore @V_ Did I also read it has no dependencies? That has a deep appeal. I tried to manage my own SSG site in the past and depency management meant I often was trying to fix something.
by toddgrotenhuis on
@toddgrotenhuis, yes, in this regard, it's the same as Hugo. And that is certainly an aspect I like of Hugo. I don't want to remember how many times I needed to fix my ruby gems with Jekyll Oo (until I moved it into Docker, but that made it still slower).
by V_ on
@toddgrotenhuis that’s correct, and you can use it with Netlify/Vercel for serverless deploy without downloading dependencies and risking breakage. My reading also showed it has a much cleaner folder structure (than Hugo especially). I’m going to try porting a Jekyll theme.
by peterimoore on