🇳🇱
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!
@paul I found it to be a arelatively simple static site engine overall. But it does take some time to learn the language. If there is something in particular that confuses you just let me know.
$ hugo new content posts/my-first-post.md
Error: failed to resolve "content" to a archetype template
(Just following the first site steps on https://gohugo.io/getting-started/quick-start/ )
Did you run into this as well?
$ hugo new content/post/filename.md
works a lot better.
@paul I would follow the instructions on the git for fedipage rather than hugo if your trying to setup fedipage: https://git.qoto.org/fedipage/fedipage
@paul You doing this in a new project or as part of fedipage?
First I want to get a bit of a feel for it. If it's easy enough, I may examine if there is a way to import my various existing (static site) sites into Hugo, through some converter or so. Those have hundreds of articles and pages, so I'm not typing them in again 😉
Also I'm not going to put a lot of time into it every day. My workdays are long enough. 😉
I moved over from middleman static site generator. The pages moved over without a hitch for me. Any markdown based source should be relatively easy to convert.
Keep in mind Hugo wont give you fediverse/activityPub access on its own. Its just another (nice) static site generator. The ability to integrate with the fediverse is entirely a fedipage thing.
This does not sound like an easy transfer, then. Thank you for the information.
I'm not focussing on the Fedipage part for anything at the moment. If I can't make Hugo work for me 'as is' (including importing my existing sites), then that route is not happening.
It might be interesting for a new site I could set up. But that's not in the books yet.
@paul Going from raw html will be more difficult.
You might need some additional effort.
When you write your journal entries then you are writing them in raw HTML? If not what markup language do you write your articles in?
See image of Publii's post editor:
You will probably start crying now. Sorry.
@paul Ohhh its a wysiwig... yea sadly unless you can find a way to convert it you may be in for some trouble. Personally this is why i dont use blogging tools that dont use open standard formats like markdown to begin with.
Hugo does support html markup but you'd likely have to heavily edit that format since it would have to be an html fragment without all the header and styling stuff.
@paul Wonderful to hear that!
<pre>
</pre>
So that's very Zen but not what I am looking for. 🤣
@paul haha its fairly automatic if you have the right directory structure and settings. Can be hard to do from scratch though if you dont know the right settings.
Because I couldn't get the example to work on the quickstart page (the error is still there after all those years), I went for Publii. I'd have no problem writing some Python to convert the wordpest XML backup into markdown.