...and why I should simply write one that gets it right from the get go

-snip-

I unearthed some bespoke site I made back in 2022 that used the cgit
layout from some other site I've long forgotten in Framagit, a GitLab
host run by Framasoft, which used GitLab Pages.

Had the awful idea of writing a CI pipeline to build the site with a
static site generator no one knows of, to boot.

Basically made the site structure as I'd always do on my computer, and
then the insanity went full throttle for five failed attempts, a half
successful one, and two successful ones, because holy classified
information.

It all went to 'download a random binary off the Internet', but hey, it
worked.

Shouldn't be hard to adapt on GitHub Pages or something, Gitea on the
other hand, tough luck, if I remember correctly, you can't build sites
and the pages server doesn't handle such cases beyond just uploading the
already built content with Git, which is a pain.

You can see the result here <https://minazukimidnight.frama.io>

```
image: alpine:3.23

before_script:
  - apk update
  - apk add --no-cache wget
  - wget -O /usr/bin/aya https://novaburst.bsd.tilde.team/archive/aya-linux-amd64
  - chmod 0755 /usr/bin/aya

test:
  stage: test
  script:
    - /usr/bin/aya version

pages:
  stage: deploy
  script:
    - /usr/bin/aya build
    - mv .pub public
  artifacts:
    paths:	
      - public
  only:
    - master
```