Tag: blog

  • Long overdue & my first Firefox addon

    Long overdue – another blog overhaul. It’s building again, now based on the blowfish theme, and if all goes well I will get a better editing experience than this <censored> “open-editor-new-file-add-front-matter” process, which is, frankly, shit. The last theme lasted two full posts. One if you don’t count the one announcing it. Wow.

    Apart from that – I start being a half-fan of “AI”. The possibilities opening up are quite nice.

    For me, that was a successor of a Firefox addon I heavily rely on (“Containerise“), which seemed no longer maintained, and also super cumbersome to use for 2026. Also, ugly.

    So here’s my first Firefox addon: “Container Dispatcher”. You can find more information now on the new project page, and my dispatcher site.

  • New theme, again

    Every now and then I get that idiotic idea that I would succeed in doing any kind of web / theme design. So the page was in a truly desolate state for a while now, which I now freely admit, and (hopefully) corrected.

    I found the theme Hinode, which seemed kinda nice, and does all I need – for now. Maybe I’ll switch again, maybe not, but I truly and desperately hope that I will never attempt to do this myself – it’s just a waste of time.

    So here we go, an actually working theme again, have fun.

  • Hugo: index vs. _index

    I renamed ./content/about.md to ./content/index.md, and poof! … all tags gone, all blog postings gone.

    What?!

    It makes sense, if you think about it.

    index.md is a special file, which automatically marks the directory it is in as a so-called “leaf-bundle“, which then makes all the files and directories and all directories become “irrelevant” – a leaf bundle has no children.

    So, what I actually wanted to do was to rename it to _index.md, which marks ./content as what it is – a branch bundle.

    Or in short: don’t put index.md files in ./content. If you want to update your home page, use _index.md.

    Sources:

  • Flypenguin Theme …

    The blog gets a new theme: The flypenguin theme.

    The old one (Cactus) served me well, but I wanted to do something on my own. Sometimes you just have to part ways.

    This theme will be mine and mine alone, it will not be designed for re-use, and I hope I will not totally suck in designing it.

    Let’s see.

  • remark42 comments

    This is a test post. There should be a comment box below, powered by the pretty cool and really well documented remark42 commenting engine.

    Let’s see … 🙂

  • GOPATH and GOROOT

    go has some unique concepts, one of them is a system-wide (user-wide) central go directory where things “happen” (e.g. modules being downloaded, etc.). For example, if you perform hugo mod get you essentially perform go mod get, which then downloads required modules … into your $GOPATH. Or $GOROOT/something, I really don’t quite get it, and I don’t care unless it stops working. Which it did.

    You often read “Just look into $GOPATH and see if it’s there”. Unfortunately I never set the value so there is no environment variable. The default of $HOME/go does not exist on my mac. Now what?

    Thanks to 0x434d53 I now know to do this, which prints the values used by go:

    go env
    
  • Hugo migration experiences

    The goal was to switch to hugo as a static blogging engine. My reasons were:

    • super easy hosting (planned was S3 & CloudFront, it is now Netlify – which is insanely easy and I don’t need my homepage-builder image any longer)
    • no database any more, everything in git, including git push deployments
    • super quick page loads

    While trying this I found a couple of drawbacks, mainly …

    • way less themes than WordPress (well, big surprise), in by far not the same quality
    • theme switching is, if it gets improved a lot, still a PITA (right now let’s just not talk about it)
    • it is insanely hard to debug your page if something does not work
    • currently no comment engine

    It is a double-edged sword. During the migration process I often wished for a quick WYSIWYG “new blog post” editor like in WordPress, at the same time I loved the security git gave me – it’s nearly impossible to lose images, posts, whatever in your blog, it will always be “somewhere” in git. But there are already ways to get around that (it seems forestry.io is exactly that).

    So, here we are now. The state is:

    • currently, no comments available
    • cause I hate ads and don’t want to introduce ad-supported Disqus, and I also don’t want to pay for it
    • the plan is to add a self-hosted commenting engine though
    • all posts transferred, including all images (as far as I can tell)
    • a somewhat final theme (50:50 that this will be changed again)

    … and all of this took WAY longer that I expected.

  • Syntax highlighting with wordpress

    This is just a test for syntax highlighting. Which I really really really wanted to have. Even if it’s WordPress and not something cool like hugo.

    So, let’s try:

    import random
    
    class RndTest:
        def __init__(self):
            print("Oy! 'this is python!")
            self.rnd_seed = random.random()
    
        @classmethod
        def do_nothing(cls, nothing):
            print("Doing {} now ;)".format(nothing))
    

    That doesn’t look so bad, right?

    How to do this

    • install the crayon syntax highlight plugin
    • when writing posts, your toolbar will have a new icon looking like this: <>
    • press it, and an “add code” dialog will open
    • do your thing
    • save
    • done

    Like.

    Dislikes

    • I don’t know which JS engine this thing uses (if any public one in particular)
    • I like highlight.js

    (So, none really)

    Alternative plugins (untested)

    To be honest, the only real contender in installation base and features seems to be Syntax Highlighter Evolved. I have not tried it, but if you don’t like crayon, that looks like the one to go.