The author seems adamant that blog.domain.com is a worse setup than domain.com/blog - I've seen this argument go back and forth a lot, with both sides claiming advantages and disadvantages. I am interested to hear the consensus from HN users as to which is better, and why.
As he said, a sub domain is often considered a separate domain when it comes to SEO. His other arguments about naming seems rather hand-wavy, though.
Security-wise, a subdomain can also be a different origin. Which is often positive, so a flaw in your blogging software doesn't allow someone to extract cookies or so from the main site.
Are Hugo really substantially better than say pelican or Nikola or all the other 'established' SSG?
not really. although hugo is pretty established, too. for a personal blog, i'd just pick one and run with it. getting stuff out is more important than the "right" generator.
(that said, personally, i prefer the runtime hackability of pelican, and i don't find the speed of generation to matter much under 200 posts)
I keep wanting to use Hugo, and I have made a few attempts. Moving away from Wordpress and its problems would be good. I do think a few features are missing that I find valuable: * Search (you can add it as an external service I haven't found one I trust and like yet. * Comments, there are several third-party comment providers that I can use, I tried out Disqus for a while but I didnt like nor trust them. I look at u…
I use commento[1] on my site, running on my own server so no third party has access. I do not get many comments though so I don't know how it handles higher load.
I used hugo for a while, but found myself struggling against it more often than I liked. I have since moved on to using other options.
What other options?
(Not OP)Shameless plug: Please take a look at Wemebox CMS https://wemebox.com. I created this because I wanted a dead simple CMS for the websites I create for my clients.I believe it is much simpler than Hugo. Will be open sourcing the source code in a couple of months.
The author seems adamant that blog.domain.com is a worse setup than domain.com/blog - I've seen this argument go back and forth a lot, with both sides claiming advantages and disadvantages. I am interested to hear the consensus from HN users as to which is better, and why.
I have some reasons to prefer domain.com/thing now : - You don't have to add and manage subdomain - You don't have to stop and restart the reverse-proxy of your VPS - Only one cert to deal with (I use traefik w/ automatic LE renewal but that implied more things to set up on the chain) But I still use blog.domain.com because I find it prettier. And when I need to type it in the URL bar it's just $service .domain . Now…
Those three concerns are one-off operations with minimal time investment, even if you don't automate most of the process.
I like the idea of static blogs. However, I didn't accomplish to find a great workflow to use hugo from my android phone while traveling. Using git on a phone is a pain
I found an app called Teddy Hyde[0] which is designed to make this workflow easier. It's focused around Jekyll but perhaps it's flexible enough for Huge also? Ultimately I couldn't get myself to write anything regularly so I gave up with the whole idea, but the app seemed decent.
I keep wanting to use Hugo, and I have made a few attempts. Moving away from Wordpress and its problems would be good. I do think a few features are missing that I find valuable: * Search (you can add it as an external service I haven't found one I trust and like yet. * Comments, there are several third-party comment providers that I can use, I tried out Disqus for a while but I didnt like nor trust them. I look at u…
Well, as long as Hugo remains a static site generator, it won't be able to support these features "out of the box". E.g. comments are simply not possible just with HTML + JS, so you'll either have to integrate a third-party service (Disqus, Staticman etc.), or move away from the "static site" concept.
Similar issues from my side. Cryptic documentation, bad dissorganized forum and configuration,... I love the hugo idea but to find one detail you will get into chaos of strange wording and noise. I am using it but I try to configure as small amount as possible as I always get into some undesired behaviour. It seems like it was from begining build with idea and then continued by patch over patch over patch. Cant recom…
I decided I would make a static site the old fashioned way on neocities.org and happily got started. And then I remembered all the double work you have to do linking and making lists and repeating headers/footers (or use frames) and so on. Now I'm back to looking for some simple script that can output static sites without having to spend a month learning a new tool...
I have a site like that on Tilde Town. It's much smaller than my blogs or other sites, though, so managing links and repeating code is not that big of a deal.
I like the idea of static blogs. However, I didn't accomplish to find a great workflow to use hugo from my android phone while traveling. Using git on a phone is a pain
Yes this is where I got blocked on this too. I like using the WP Android app to upload photos when travelling. Obviously a static site by its very nature cannot interact with a phone app, so this seems like a difficult/intractable problem.
I have the same use case and have been wondering about solutions too. I'm hosting on Netlify, and when I push to my gitlab repository, Netlify's CI fetches, builds and deploys the site. I've wondered if I can run a script somewhere that periodically checks a private Instagram account (so not my main one), and when it sees a new post, it would download the photo and caption, creates a Markdown post and pushes everything into the git repo.