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.
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
Le site du projet #ErgoL fait peau neuve : on est passé d’une page fixe en HTML à un joli site statique généré par #GoHugo. Enfin, « joli » toujours pas vu qu’on a gardé les mêmes feuilles de style (faites par moi), mais techniquement c’est magnifique ! :-)
Et on démarre donc un flux #RSS, qu’on fera vivre au fil des évolutions, événements, contributions. Enjoy !
Hugo uses Markdown to create the content, which is then parsed into static HTML. One of the features of Markdown are quotes. Multiline quotes (block quotes) are possible, but they are not very intuitive.
As someone who reads science fiction and occasionally updates my blog built with a static site generator... the #Hugo hashtag is a bit confusing these days. Maybe #HugoAwards and #GoHugo are less ambiguous?
If I had to name one thing I really dislike about #Hugo static website generator is that almost every theme has its own specific configuration, syntax and set of specific things.
Even for very standard things like copyright in the footer or social network links (I understand custom icons and where to render, not specific config), they need specific config 😕
This, added to the fact I really suck at frontend, is making my migration a real pain.
My mostly dead blog has been using self-hosted https://ghost.org as blogging platform for quite a while. Before Ghost I was using https://jekyllrb.com and then https://gohugo.io. Now I'm thinking of switching back to Hugo. Ghost is getting bloated with bunch of features I don’t need (memberships, newsletters etc).
I wonder if there are any other static site engines I should check or if anyone has recent experience with Hugo (have they ruined it)?
I finally did my reorganisation of my blog content. I've been wanting a nicer way of storing my blog files, but didnt want old post links etc to be broken.
I wrote a post describing how that process worked for me :)
I did some reorganisation on my #hugo site today, and I thought I was being so clever using aliases, and.... the aliases are not working. I'm scratching my head for why, and am really quite confused.
so how DOES federating work with old content anyway (or does it just not)?
I set up @sirtaptap.com@sirtaptap.com which should be a feed of all my website's articles...but it seems to have posted all my existing content before I federated so it's empty on .social
@SirTapTap Ahh. Yes, that's normal. Every post is a post in that blog's “instance”.
You then can follow it. And when you publish a new post, you should see it.
For the URL, I can't remember much about it since that last time I used #WordPress was in 2020; I migrated to #Hugo / #GoHugo late 2020.
But what I can remember, the plugin at that time will create a new post with your WP “summary” as the post content, then a link to back to your website for the full article. Something like a summary-only Atom / RSS feed.
To find the #ActivityPub link, I right-click on the date/time of the post it created and figured out how it creates the URLs.
I want to create book-esque website. So. it has chapters, cross-references, auto-numbering, bibliography and so on. I want this to generate per-chapter html files with next/prev links and a TOC. But I also want to generate a combined PDF and txt file.
This is not a task for markdown.
I was thinking of #groff/#troff, but it generates ugly HTML 4.1. HTML5 is a must - plus custom CSS.
I'm a bit afraid of jumping into #latex, but it looks like the best choice?
I'm currently using #gohugo. so a markdown output in place
Every time that I want to do anything with #gohugo it is so hard and requires so many hacks. I feel that it’s working against me, not with me.
Today’s rant inspired by wanting to add a table of content to a single article and that basically requiring that I apply a regex to the entire article content in order to do so.
The problem is that I already have a huge hack for something else (anchors in subtitles), and I’d need to pile the two do them together somehow.
I'm working on a new #hugo theme and while developing, I'm seeing this odd thing where changes to layouts/index.html is not triggering rebuild, so developing is hard.
anyone seen something like this before? layouts-wise I only have _defalt/[baseof, single, list, terms].html defined other than partials
So its done! I finally released a fairly easy to install (from scratch) Hugo based Static Site generator with full ActivityPub support.
It has step-by-step instructions on how to set it up for your own blog or static website.
One of the coolest features for me, other than having your static site blog posts show up as posts in the Fediverse is the support for interacting with those posts. Any replies you leave, likes, or boosts will show up in the "comments" section of the website on the page associated with the post. How cool is that!
To make it easier to combine the two, I added a shortcode that makes it easy to embed toots in any Hugo site. But of course I haven't thought of all the possible use cases, so feel free to comment and improve on my suggestion.
Did you know we're running our Tech Blog https://blog.zero-iee.com using Hugo, GitHub Actions and GitHub Pages? :github:
The content is composed using Markdown. Hugo (run via GitHub Actions) translates HTML templates and Markdown files to a collection of HTML files. GitHub Pages then displays the resulting HTML files and handles SSL.
All we need to do is write a new article in Markdown syntax and push it to our GitHub repository. HTML generation and publishing are fully automated.
While we could host a CICD pipeline and a web server ourselves, we prefer the current low-effort soultion. 😉
Thanks to the Index theme for GoHugo, I think I finally found the most efficient way to manage my (slowly) growing knowledge base: https://kindex.hugoblanc.com/
I ended up with a versioned and indexed version of it, quick and lightweight 🎉