Comment on [Debian Stable] Which Static Blog Generator: blag, Jekyll, Hugo, Lektor, Pelican, staticsite?

OmegaLemmy@discuss.online ⁨3⁩ ⁨weeks⁩ ago

• A_norny_mousse@feddit.org ⁨3⁩ ⁨weeks⁩ ago

  That’s usually fixable with templating. What sort of comment integration? Some third party I guess?

  source

  • OmegaLemmy@discuss.online ⁨3⁩ ⁨weeks⁩ ago

    Self host and third party exists. You probably could use Lemmy as a shoddy way to make comments too

    source

    • A_norny_mousse@feddit.org ⁨3⁩ ⁨weeks⁩ ago

      Self host

      On a static site generator? Can you link me to that please?

      What about Hugo’s templating language? It’s been said to be daunting:

      • “It gets admittedly more complex if you’re wanting to write your own theme though.”
      • “But as soon as you do want to customize it, you’re stuck learning one of the most esoteric languages that wasn’t meant as a joke.”
      • “The documentation is unclear and there’s a chicken and egg problem about how to learn Hugo.”

      source

      • moonpiedumplings@programming.dev ⁨3⁩ ⁨weeks⁩ ago

        Alright, this is gonna be long.

        Firstly, yes, different static site generators have different templating langauges. But just like normal programming languages, it is easy to transition from one templating langauge to another. If you take a look at the syntax:

        • Pelian: pypi.org/project/Jinja2/
        • Hugo: pkg.go.dev/text/template, pkg.go.dev/html/template

        Not drastically different, but reading the docs, they are all similar enough, and easy to learn.

        I wouldn’t call go’s templating language “esoteric”, but it should be noted that jinja2 is has other uses, most notably it is the templating engine that Ansible uses.

        As for the docs… This could probably be a blog post by itself.

        Firstly, take a look at this website: killedbygoogle.com . Google has created and then killed 296 projects, many of which were actively used and working. Why?

        This is because, internally at Google, you get promoted if you either A: write software, or B: add more features to software. So what happens is people write software, get promoted, and then realize they don’t get paid more if they actually maintain that software, so they just kill it. Also, they forget to write documentation (because it doesn’t pay more or get you promoted).

        Hugo, is by a Google Engineer, and it shows (or at least, it used to). Software by Google has two distinct characteristics (actually 3 if we count being written in Go).

        • It has every feature you could ever want, even stuff you haven’t heard of
        • And it’s poorly documented. Or not at all lmao.

        But, “being poorly documented” is not a permanent fixture of this software, but instead something that mostly persists for as long as it’s Google software. Often, these projects get “adopted” by the wider community, who fixes up their documentation. Looking at hugo’s docs, it doesn’t seem be nightmarishly bad, especially for the core, main set of features. Like the setup docs appear to be clear (although a more complex process than alternatives).

        But like, for search options: gohugo.io/tools/search/ . That google software pattern continues. There are like 10 options on the page, and no docs from hugo on their usage/installation lol.

        Anyway, I would recommend eithier Pelican or Jekyll, given your requirements. But because everything you write is in markdown, it will be fairly easy to move from one static site generator to another, even if you are dissatisfied.

        Also, kinda sorta relevant:

        Image

        (source)

        But the point I’m trying to make is the same. Don’t sweat the setup too much.

        source

        • -> View More Comments
      • OmegaLemmy@discuss.online ⁨3⁩ ⁨weeks⁩ ago

        I was fighting with my linter tbh still have no clue how to write html in go like its php

        And, for the comments part, I haven’t looked into it, it’s likely just a JavaScript file that connects to your server or an external one and pulls all data and whatever, its the single dynamic part and it’s done with js

        source