feat: add new Experience

Reviewed-on: #2

.gitea/workflows/build-container-image.yaml

@@ -0,0 +1,64 @@
+name: Build and Deploy
+run-name: ${{ gitea.actor }} is building container
+on:
+  push:
+    tags:
+      - "*"
+jobs:
+  Build-Container-Image:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Docker meta
+        id: meta
+        uses: docker/metadata-action@v5
+        with:
+          images: |
+            git.dev-null.rocks/alexohneander/alexohneander-zola
+          tags: |
+            type=schedule,pattern={{date 'YYYYMMDDHHMM'}}
+            type=semver,pattern={{version}}
+            type=semver,pattern={{major}}.{{minor}}
+            type=semver,pattern={{major}}
+            type=sha
+
+      - name: Set up Docker Context for Buildx
+        id: buildx-context
+        run: |
+          export DOCKER_HOST=tcp://docker:2376/
+          export DOCKER_TLS_CERTDIR="/certs"
+          export DOCKER_TLS_VERIFY=1
+          export DOCKER_CERT_PATH="/certs/client"
+          docker context create builders
+
+      - name: Setup Docker Buildx
+        id: buildx
+        uses: docker/setup-buildx-action@v3
+        with:
+          # buildkitd-flags: --debug
+          endpoint: builders
+        env:
+          DOCKER_HOST: "tcp://docker:2376/"
+          DOCKER_TLS_CERTDIR: "/certs"
+          DOCKER_TLS_VERIFY: 1
+          DOCKER_CERT_PATH: "/certs/client"
+
+      - name: Login to Gitea
+        uses: docker/login-action@v3
+        with:
+          registry: git.dev-null.rocks
+          username: ${{ gitea.actor }}
+          password: ${{ secrets.GA_TOKEN }}
+
+      - name: Build and push the image
+        uses: docker/build-push-action@v5
+        with:
+          file: Dockerfile
+          platforms: linux/amd64
+          push: true
+          tags: ${{ steps.meta.outputs.tags }}
+          labels: ${{ steps.meta.outputs.labels }}
+        env:
+          DOCKER_HOST: "tcp://docker:2376/"
+          DOCKER_TLS_CERTDIR: "/certs"
+          DOCKER_TLS_VERIFY: 1
+          DOCKER_CERT_PATH: "/certs/client"

.gitea/workflows/config.js

@@ -0,0 +1,8 @@
+module.exports = {
+    "endpoint": "https://git.dev-null.rocks/api/v1", // replace it with your actual endpoint
+    "gitAuthor": "Renovate Bot <renovate-bot@dev-null.rocks>",
+    "platform": "gitea",
+    "onboardingConfigFileName": "renovate.json",
+    "autodiscover": true,
+    "optimizeForDisabled": true,
+};

.gitea/workflows/renovate.yaml

@@ -0,0 +1,20 @@
+name: renovate
+
+on:
+  schedule:
+    - cron: "@daily"
+  push:
+    branches:
+      - main
+
+jobs:
+  renovate:
+    runs-on: ubuntu-latest
+    container: ghcr.io/renovatebot/renovate:39.207.2
+    steps:
+      - uses: actions/checkout@v4
+      - run: renovate
+        env:
+          RENOVATE_CONFIG_FILE: ".gitea/workflows/config.js" # replace it with your config.js path
+          LOG_LEVEL: "debug"
+          RENOVATE_TOKEN: ${{ secrets.RENOVATE_TOKEN }} # your Revonate bot token

.github/CODEOWNERS

@@ -1,2 +0,0 @@
-* @welpo
-i18n/ar.toml @TheAwiteb

.github/FUNDING.yml

@@ -1 +0,0 @@
-github: welpo

.github/ISSUE_TEMPLATE/2_bug_report.yml

@@ -1,62 +0,0 @@
-name: "🐛 Bug report"
-description: "Did you run into an issue while using tabi?"
-labels: ["bug"]
-body:
-- type: textarea
-  attributes:
-      label: "System information"
-      description: |
-          Please provide the following information:
-          - Zola version: Run `zola --version`
-          - tabi version or commit hash
-      placeholder: |
-          Zola version: 
-          tabi version or commit: 
-  validations:
-      required: true
-
-- type: textarea
-  attributes:
-      label: "Expected behaviour"
-      description: "Tell us what should have happened."
-      placeholder: "Describe what you expected tabi to do…"
-  validations:
-      required: true
-
-- type: textarea
-  attributes:
-      label: "Actual behaviour"
-      description: "Tell us what happens instead of the expected behavior."
-      placeholder: "Describe what actually happened…"
-  validations:
-      required: true
-
-- type: textarea
-  attributes:
-      label: "Steps to reproduce"
-      description: "Please provide detailed steps to reproduce the issue."
-      placeholder: |
-          1. Set up `config.toml` with these settings: …
-          2. Create content with this structure: …
-          3. Run Zola with these arguments: …
-          4. See the following error: …
-  validations:
-      required: true
-
-- type: textarea
-  attributes:
-      label: "Additional context"
-      description: >
-          Please provide any relevant configuration files, error messages, or screenshots that might help us understand the issue.
-          You can drag and drop files here to attach them.
-  validations:
-      required: false
-
-- type: checkboxes
-  attributes:
-      label: "Final checklist"
-      options:
-          - label: "I've checked that the issue isn't already reported."
-            required: true
-          - label: "I've tested with the latest version of tabi to check if the issue has already been fixed."
-            required: true

.github/ISSUE_TEMPLATE/3_feature_request.yml

@@ -1,34 +0,0 @@
-name: "✨ Feature request"
-description: "Suggest an idea for tabi"
-labels: ["enhancement"]
-body:
-- type: textarea
-  attributes:
-      label: "Summary and motivation"
-      description: "Briefly describe the feature and why it would be valuable for tabi users."
-      placeholder: |
-          Describe:
-          - What the feature is
-          - Why it would be useful
-          - Any examples from other projects
-  validations:
-      required: true
-
-- type: textarea
-  attributes:
-      label: "Implementation details"
-      description: "Share any ideas you have about how this could be implemented."
-      placeholder: "Technical suggestions, potential approaches, or specific requirements."
-  validations:
-      required: false
-
-- type: checkboxes
-  attributes:
-      label: "Checklist"
-      options:
-          - label: "I've searched existing issues to make sure this feature hasn't already been requested."
-            required: true
-          - label: "This feature aligns with tabi's philosophy (minimal JS, accessible…)"
-            required: true
-          - label: "I'm willing to contribute to the implementation of this feature."
-            required: false

.github/ISSUE_TEMPLATE/config.yml

@@ -1,5 +0,0 @@
-blank_issues_enabled: false
-contact_links:
-  - name: 💬 tabi discussions
-    url: https://github.com/welpo/tabi/discussions
-    about: If you have questions or need help, feel free to ask here~

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,67 +0,0 @@
-<!--
-  Thank you for contributing to tabi!
-
-  This template is designed to guide you through the pull request process.
-  Please fill out the sections below as applicable.
-
-  Don't worry if your PR is not complete or you're unsure about something;
-  feel free to submit it and ask for feedback. We appreciate all contributions, big or small!
-
-  Feel free to remove any section or checklist item that does not apply to your changes.
-  If it's a quick fix (for example, fixing a typo), a Summary is enough.
--->
-
-## Summary
-
-<!-- Please provide a brief description of the changes made in this PR -->
-
-### Related issue
-
-<!-- Mention any relevant issues like #123 -->
-
-## Changes
-
-<!-- Please provide some more detail regarding the changes.
-Add any additional information, configuration, or data that might be necessary for the review -->
-
-### Accessibility
-
-<!-- Have you taken steps to make your changes accessible? This could include:
-- Semantic HTML
-- ARIA attributes
-- Keyboard navigation
-- Voiceover or screen reader compatibility
-- Colour contrast
-Please elaborate on the actions taken.
-If you need help, please ask! -->
-
-### Screenshots
-
-<!-- If applicable, add screenshots to help explain the changes made. Consider if a before/after is helpful -->
-
-### Type of change
-
-<!-- Mark the relevant option with an `x` like so: `[x]` (no spaces) -->
-
-- [ ] Bug fix (fixes an issue without altering functionality)
-- [ ] New feature (adds non-breaking functionality)
-- [ ] Breaking change (alters existing functionality)
-- [ ] UI/UX improvement (enhances user interface without altering functionality)
-- [ ] Refactor (improves code quality without altering functionality)
-- [ ] Documentation update
-- [ ] Other (please describe below)
-
----
-
-## Checklist
-
-- [ ] I have verified the accessibility of my changes
-- [ ] I have tested all possible scenarios for this change
-- [ ] I have updated `theme.toml` with a sane default for the feature
-- [ ] I have updated `config.toml` in [tabi-start](https://github.com/welpo/tabi-start)
-- [ ] I have made corresponding changes to the documentation:
-  - [ ] Updated `config.toml` comments
-  - [ ] Updated `theme.toml` comments
-  - [ ] Updated "Mastering tabi" post in English
-  - [ ] (Optional) Updated "Mastering tabi" post in Spanish
-  - [ ] (Optional) Updated "Mastering tabi" post in Catalan

.github/renovate.json

@@ -1,29 +0,0 @@
-{
-  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
-  "extends": ["config:recommended", ":automergeMinor", ":disableDependencyDashboard"],
-  "commitMessagePrefix": "⬆️",
-  "commitMessageAction": "chore(deps): update",
-  "commitMessageTopic": "{{{depName}}}",
-  "labels": ["dependencies"],
-  "git-submodules": {
-    "enabled": true
-  },
-  "packageRules": [
-    {
-      "updateTypes": ["pin"],
-      "commitMessagePrefix": "📌"
-    },
-    {
-      "updateTypes": ["major", "minor", "patch", "digest", "bump"],
-      "commitMessagePrefix": "⬆️"
-    },
-    {
-      "updateTypes": ["rollback"],
-      "commitMessagePrefix": "⬇️"
-    },
-    {
-      "matchFileNames": ["scripts/release/**"],
-      "automerge": true
-    }
-  ]
-}

.github/workflows/cd.yml

@@ -1,36 +0,0 @@
-name: Continuous Deployment
-
-on:
-  push:
-    tags:
-      - 'v*.*.*'
-
-jobs:
-  deploy:
-    name: Deploy and release
-    runs-on: ubuntu-24.04
-    permissions:
-      contents: write
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-
-      - name: Generate the changelog
-        uses: orhun/git-cliff-action@main
-        id: git-cliff
-        with:
-          config: cliff.toml
-          args: --latest --strip all
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          OUTPUT: CHANGES.md
-
-      - name: Create GitHub release
-        run: |
-          gh release create ${{ github.ref_name }} \
-            --title "Release ${{ github.ref_name }}" \
-            --notes-file CHANGES.md
-        env:
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/ci.yml

@@ -1,44 +0,0 @@
-name: Build Site
-
-on:
-  push:
-    branches:
-      - main
-  pull_request:
-    branches:
-      - main
-
-jobs:
-  check_and_build_pr:
-    name: Check and Build for Pull Requests
-    runs-on: ubuntu-latest
-    if: github.event_name == 'pull_request'
-    steps:
-      - name: Checkout Code
-        uses: actions/checkout@v4
-
-      - name: Zola Build
-        uses: shalzz/zola-deploy-action@v0.19.2
-        env:
-          BUILD_ONLY: true
-
-      - name: Zola Check
-        uses: shalzz/zola-deploy-action@v0.19.2
-        env:
-          BUILD_ONLY: true
-          CHECK_LINKS: true
-
-  build_and_deploy:
-    name: Build and Deploy on Main Push
-    runs-on: ubuntu-24.04
-    if: github.event_name == 'push' && github.ref == 'refs/heads/main'
-    steps:
-      - name: Checkout Code
-        uses: actions/checkout@v4
-
-      - name: Build and Deploy
-        uses: shalzz/zola-deploy-action@v0.19.2
-        env:
-          PAGES_BRANCH: gh-pages
-          TOKEN: ${{ secrets.TOKEN }}
-          BUILD_THEMES: false

.github/workflows/git-sumi.yml

@@ -1,24 +0,0 @@
-name: Lint pull request title
-
-on:
-  pull_request:
-    types:
-      - opened
-      - edited
-      - synchronize
-      - ready_for_review
-
-permissions:
-  pull-requests: read
-
-jobs:
-  main:
-    name: Run git-sumi
-    runs-on: ubuntu-24.04
-    steps:
-      - name: Set header length for dependency updates
-        if: contains(github.event.pull_request.title, 'chore(deps)')
-        run: echo "GIT_SUMI_MAX_HEADER_LENGTH=80" >> $GITHUB_ENV
-      - uses: welpo/git-sumi-action@main
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/upgrade-deps.yml

@@ -1,89 +0,0 @@
-name: Dependency upgrade
-on:
-  workflow_dispatch:
-    inputs:
-      dependency:
-        description: 'Dependency to upgrade'
-        required: true
-        type: choice
-        options:
-          - all
-          - mermaid
-          - katex
-  schedule:
-    - cron: '32 4 * * *'
-
-jobs:
-  upgrade-dependency:
-    name: Upgrade dependency
-    runs-on: ubuntu-24.04
-    permissions:
-      contents: write
-      pull-requests: write
-    strategy:
-      matrix:
-        dependency: ${{ github.event_name == 'schedule' && fromJson('["mermaid", "katex"]') || fromJson(format('["{0}"]', github.event.inputs.dependency)) }}
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-
-      - name: Set up environment
-        run: |
-          sudo apt-get update
-          sudo apt-get install -y jq npm curl git
-          npm install uglify-js -g
-          uglifyjs --version
-
-      - name: Configure GPG key
-        run: |
-          echo -n ${{ secrets.GPG_PRIVATE_KEY }} | base64 --decode | gpg --import
-
-      - name: Configure Git
-        run: |
-          git config --global user.signingkey 33EACFE956484C3940BFEEDCE4EC28F8DFB57474
-          git config --global commit.gpgsign true
-          git config --global user.name "welpo"
-          git config --global user.email "welpo@users.noreply.github.com"
-
-      - name: Check for existing branch
-        id: check_branch
-        run: |
-          if git ls-remote --heads origin deps/upgrade-${{ matrix.dependency }} | grep -q deps/upgrade-${{ matrix.dependency }}; then
-            echo "branch_exists=true" >> $GITHUB_OUTPUT
-          else
-            echo "branch_exists=false" >> $GITHUB_OUTPUT
-          fi
-
-      - name: Handle existing branch
-        if: steps.check_branch.outputs.branch_exists == 'true'
-        run: |
-          echo "Branch deps/upgrade-${{ matrix.dependency }} already exists."
-          echo "Skipping upgrade as there's already an open PR"
-          exit 0
-
-      - name: Create and switch to new branch
-        run: |
-          git checkout -b deps/upgrade-${{ matrix.dependency }}
-
-      - name: Run upgrade script
-        shell: bash
-        run: |
-          if [[ "${{ matrix.dependency }}" == "all" ]]; then
-            bash scripts/upgrade-deps --all
-          else
-            bash scripts/upgrade-deps --${{ matrix.dependency }}
-          fi
-
-      - name: Push changes and create PR
-        shell: bash
-        run: |
-          if git diff --quiet HEAD origin/main; then
-            echo "No changes to push for ${{ matrix.dependency }}"
-            exit 0
-          fi
-          git push -u origin deps/upgrade-${{ matrix.dependency }}
-          gh pr create --fill --base main --head deps/upgrade-${{ matrix.dependency }} --label "dependencies"
-        env:
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}

CODE_OF_CONDUCT.md

@@ -1,128 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-We as members, contributors, and leaders pledge to make participation in our
-community a harassment-free experience for everyone, regardless of age, body
-size, visible or invisible disability, ethnicity, sex characteristics, gender
-identity and expression, level of experience, education, socio-economic status,
-nationality, personal appearance, race, religion, or sexual identity
-and orientation.
-
-We pledge to act and interact in ways that contribute to an open, welcoming,
-diverse, inclusive, and healthy community.
-
-## Our Standards
-
-Examples of behavior that contributes to a positive environment for our
-community include:
-
-* Demonstrating empathy and kindness toward other people
-* Being respectful of differing opinions, viewpoints, and experiences
-* Giving and gracefully accepting constructive feedback
-* Accepting responsibility and apologizing to those affected by our mistakes,
-  and learning from the experience
-* Focusing on what is best not just for us as individuals, but for the
-  overall community
-
-Examples of unacceptable behavior include:
-
-* The use of sexualized language or imagery, and sexual attention or
-  advances of any kind
-* Trolling, insulting or derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or email
-  address, without their explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Enforcement Responsibilities
-
-Community leaders are responsible for clarifying and enforcing our standards of
-acceptable behavior and will take appropriate and fair corrective action in
-response to any behavior that they deem inappropriate, threatening, offensive,
-or harmful.
-
-Community leaders have the right and responsibility to remove, edit, or reject
-comments, commits, code, wiki edits, issues, and other contributions that are
-not aligned to this Code of Conduct, and will communicate reasons for moderation
-decisions when appropriate.
-
-## Scope
-
-This Code of Conduct applies within all community spaces, and also applies when
-an individual is officially representing the community in public spaces.
-Examples of representing our community include using an official e-mail address,
-posting via an official social media account, or acting as an appointed
-representative at an online or offline event.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported to the community leaders responsible for enforcement at
-tabi@osc.garden.
-All complaints will be reviewed and investigated promptly and fairly.
-
-All community leaders are obligated to respect the privacy and security of the
-reporter of any incident.
-
-## Enforcement Guidelines
-
-Community leaders will follow these Community Impact Guidelines in determining
-the consequences for any action they deem in violation of this Code of Conduct:
-
-### 1. Correction
-
-**Community Impact**: Use of inappropriate language or other behavior deemed
-unprofessional or unwelcome in the community.
-
-**Consequence**: A private, written warning from community leaders, providing
-clarity around the nature of the violation and an explanation of why the
-behavior was inappropriate. A public apology may be requested.
-
-### 2. Warning
-
-**Community Impact**: A violation through a single incident or series
-of actions.
-
-**Consequence**: A warning with consequences for continued behavior. No
-interaction with the people involved, including unsolicited interaction with
-those enforcing the Code of Conduct, for a specified period of time. This
-includes avoiding interactions in community spaces as well as external channels
-like social media. Violating these terms may lead to a temporary or
-permanent ban.
-
-### 3. Temporary Ban
-
-**Community Impact**: A serious violation of community standards, including
-sustained inappropriate behavior.
-
-**Consequence**: A temporary ban from any sort of interaction or public
-communication with the community for a specified period of time. No public or
-private interaction with the people involved, including unsolicited interaction
-with those enforcing the Code of Conduct, is allowed during this period.
-Violating these terms may lead to a permanent ban.
-
-### 4. Permanent Ban
-
-**Community Impact**: Demonstrating a pattern of violation of community
-standards, including sustained inappropriate behavior,  harassment of an
-individual, or aggression toward or disparagement of classes of individuals.
-
-**Consequence**: A permanent ban from any sort of public interaction within
-the community.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage],
-version 2.0, available at
-https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
-
-Community Impact Guidelines were inspired by [Mozilla's code of conduct
-enforcement ladder](https://github.com/mozilla/diversity).
-
-[homepage]: https://www.contributor-covenant.org
-
-For answers to common questions about this code of conduct, see the FAQ at
-https://www.contributor-covenant.org/faq. Translations are available at
-https://www.contributor-covenant.org/translations.

CONTRIBUTING.md

@@ -1,122 +0,0 @@
-# Contributing to tabi
-
-Halló!
-
-Thanks for contributing to [tabi](https://github.com/welpo/tabi). Before implementing new features and changes, please [submit an issue](https://github.com/welpo/tabi/issues/new) so that we can discuss it.
-
-We welcome contributions in many forms, including:
-
-- Bug reports;
-- New translations;
-- Improvements to existing translations;
-- Feature requests;
-- Code patches;
-- Documentation improvements;
-- UI/UX suggestions.
-
-If you're not sure how to contribute or need help with something, please don't hesitate to reach out via the [issue tracker](https://github.com/welpo/tabi/issues) or [mail](mailto:tabi@osc.garden?subject=[GitHub]%20tabi).
-
-## Pull Requests
-
-Working on your first Pull Request? You can learn how from this free video series:
-
-[**How to Contribute to an Open Source Project on GitHub**](https://egghead.io/courses/how-to-contribute-to-an-open-source-project-on-github)
-
-Please make sure the following is done when submitting a pull request:
-
-1. **Keep your PR small**. Small pull requests are much easier to review and more likely to get merged. Make sure the PR does only one thing, otherwise please split it.
-2. **Use descriptive titles**. It is recommended to follow this [commit message style](#conventional-commit-messages-with-gitmoji).
-3. **Test your changes**. Make sure to test different configurations that might affect your changes.
-4. **Fill the PR template**. The template will guide you through the process of submitting a PR.
-
-### Conventional Commit Messages with Gitmoji
-
-See how a minor change to your commit message style can make you a better programmer.
-
-Format: `<gitmoji> <type>(<scope>): <description>`
-
-`<gitmoji>` is an emoji from the [gitmoji](https://gitmoji.dev/) list. It makes it easier to visually scan the commit history and quickly grasp the purpose of changes.
-
-`<scope>` is optional. If your change affects a specific part of the codebase, consider adding the scope. Scopes should be brief but recognizable, e.g. `config`, `feed`, or `search`.
-
-The various types of commits:
-
-- `feat`: a new API or behaviour **for the end user**.
-- `fix`: a bug fix **for the end user**.
-- `style`: changes to the visual appearance of the theme, e.g. CSS, fonts, images…
-- `docs`: a change to the website or other Markdown documents.
-- `refactor`: a change to code that doesn't change behaviour, e.g. splitting files, renaming internal variables, improving code style…
-- `chore`: upgrading dependencies, releasing new versions… Chores that are **regularly done** for maintenance purposes.
-- `misc`: anything else that doesn't change production code, yet is not `chore`. e.g. updating GitHub actions workflow.
-
-The commits within your PR don't need to follow this convention (we'll [squash them](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests)). However, the PR title should be in this format. If you're not sure about the title, don't worry, we'll help you fix it. Your code is more important than conventions!
-
-Example:
-
-```text
-🐛 fix(i18n): localise date in single taxonomy listing
-^  ^-^^----^  ^--------------------------------------^
-|  |  |       |
-|  |  |       +-> Description in imperative and lowercase.
-|  |  |
-|  |  +-> The scope of the change.
-|  |
-|  +-------> Type: see above for the list we use.
-|
-+----------> A valid gitmoji.
-```
-
-## Coding Style Guidelines
-
-While we don't enforce a strict coding style, we appreciate it when contributions follow the existing code style of the project (e.g. indenting with 4 spaces). This makes the codebase easier to read and maintain. If you are making significant changes or additions, please try to maintain consistency with the current coding patterns and idioms.
-
-For JavaScript files, we use [Prettier](https://prettier.io/) to format the code.
-
-The CSS properties are sorted following [Concentric-CSS](https://github.com/brandon-rhodes/Concentric-CSS). If you use VSCode, the [Sort CSS](https://marketplace.visualstudio.com/items?itemName=piyushsarkar.sort-css-properties) extension makes this super easy.
-
-## Pre-commit Githook
-
-### Introduction
-
-We use a pre-commit githook to maintain code and file quality. [This script](https://github.com/welpo/tabi/blob/main/.githooks/pre-commit) performs a series of checks and updates before a commit is made.
-
-### Setting Up
-
-To use the pre-commit githook, run the following command from the root of the repository to configure the git hooks path and make the script executable:
-
-```bash
-git config core.hooksPath .githooks
-chmod +x .githooks/pre-commit
-```
-
-### Features
-
-The pre-commit githook performs the following actions:
-
-#### Automatic Updates
-
-- **Front Matter in Markdown Files**: Automatically updates the "updated" field in the front matter of `.md` files.
-- **PNG Compression**: Compresses PNG files using either [`oxipng`](https://github.com/shssoichiro/oxipng) or [`optipng`](https://optipng.sourceforge.net/), whichever is available on your system.
-- **Font Subsetting**: Runs `subset_font` if `config.toml` has been modified.
-
-#### Commit Checks
-
-The script prevents you from committing if:
-
-- The `.md` file is marked as a draft.
-- Any file contains a "TODO".
-- A JavaScript file is being committed without a corresponding minified version.
-- A minified JavaScript file is not as small as it could be. Requires installing [UglifyJS](https://github.com/mishoo/UglifyJS) and/or [terser](https://github.com/terser/terser).
-- `config.toml` and `theme.toml` have different numbers of lines in their `[extra]` sections.
-
-These checks are in place to ensure code quality and consistency throughout the project.
-
-## Code of Conduct
-
-We expect all contributors to follow our [Code of Conduct](./CODE_OF_CONDUCT.md). Please be respectful and professional when interacting with other contributors.
-
-## License
-
-The code is available under the [MIT license](./LICENSE).
-
-Thank you for your contributions!

Dockerfile

@@ -0,0 +1,9 @@
+FROM ghcr.io/getzola/zola:v0.20.0 as zola
+
+COPY . /project
+WORKDIR /project
+RUN ["zola", "build"]
+
+FROM ghcr.io/static-web-server/static-web-server:2
+WORKDIR /
+COPY --from=zola /project/public /public

LICENSE

@@ -1,21 +0,0 @@
-MIT License
-
-Copyright (c) 2023 Óscar Fernández
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.

README.md

@@ -1,243 +1,6 @@
 <p align="center">
-    <a href="CONTRIBUTING.md#pull-requests">
+    <a href="https://git.dev-null.rocks/alexohneander/alexohneander-zola/actions">
-        <img src="https://img.shields.io/badge/PRs-welcome-0?style=flat-square&labelColor=202b2d&color=087e96" alt="PRs welcome"></a>
+        <img src="https://git.dev-null.rocks/alexohneander/alexohneander-zola/actions/workflows/build-container-image.yaml/badge.svg?branch=main" alt="Build status"></a>
-    <a href="https://github.com/welpo/tabi/graphs/contributors">
-        <img src="https://img.shields.io/github/contributors/welpo/tabi?style=flat-square&labelColor=202b2d&color=087e96" alt="Contributors"></a>
-    <a href="https://github.com/welpo/tabi/forks">
-        <img src="https://img.shields.io/github/forks/welpo/tabi?style=flat-square&labelColor=202b2d&color=087e96" alt="Forks"></a>
-    <a hfref="https://github.com/welpo/tabi/commits/main/">
-        <img src="https://img.shields.io/github/last-commit/welpo/tabi?style=flat-square&labelColor=202b2d&color=087e96" alt="Last commit"></a>
-    <br>
-    <a href="https://github.com/welpo/tabi/releases">
-        <img src="https://img.shields.io/github/v/release/welpo/tabi?style=flat-square&labelColor=202b2d&color=087e96" alt="Latest release"></a>
-    <a href="https://welpo.github.io/tabi/blog/mastering-tabi-settings/">
-        <img src="https://img.shields.io/website?url=https%3A%2F%2Fwelpo.github.io%2Ftabi&style=flat-square&label=docs&labelColor=202b2d" alt="Documentation"></a>
-    <a href="https://github.com/welpo/tabi/blob/main/LICENSE">
-        <img src="https://img.shields.io/github/license/welpo/tabi?style=flat-square&labelColor=202b2d&color=087e96" alt="License"></a>
-    <a href="https://github.com/welpo/git-sumi">
-        <img src="https://img.shields.io/badge/clean_commits-git--sumi-0?style=flat-square&labelColor=202b2d&color=087e96" alt="Clean commits"></a>
-    <a href="https://isitmaintained.com/project/welpo/tabi">
-        <img src="https://isitmaintained.com/badge/resolution/welpo/tabi.svg" alt="Average time to resolve an issue"></a>
-    <a href="https://isitmaintained.com/project/welpo/tabi">
-        <img src="https://isitmaintained.com/badge/open/welpo/tabi.svg" alt="Percentage of issues still open"></a>
 </p>
 
-# 🌱 tabi
+# 🌱 alexohneander
-
-An accessible [Zola](https://www.getzola.org) theme with [search](https://welpo.github.io/tabi/blog/mastering-tabi-settings/#search), [multi-language support](https://welpo.github.io/tabi/blog/faq-languages/), [optional JavaScript](https://welpo.github.io/tabi/blog/javascript/), a perfect Lighthouse score, and [comprehensive documentation](https://welpo.github.io/tabi). Crafted for personal websites and blogs.
-
-> [!TIP]
-> Want to start blogging right away? Use the [tabi-start template](https://github.com/welpo/tabi-start) to get a complete site up and running in minutes.
-
-See a live preview (and the theme's documentation) [here](https://welpo.github.io/tabi).
-
-Explore the [Sites Using tabi section](#sites-using-tabi) to see real-world applications.
-
-> tabi (旅, /<span title="/t/: 't' in 'sty'">t</span><span title="/ɐ/: a sound between 'a' in 'sofa' and 'u' in 'nut'">ɐ</span><span title="/ˈ/: primary stress mark, indicating that the following syllable is pronounced with greater emphasis">ˈ</span><span title="/b/: 'b' in 'cab'">b</span><span title="/i/: 'i' in 'fleece'">i</span>/): Journey.
-
-![tabi](https://github.com/welpo/tabi/raw/main/light_dark_screenshot.png)
-
-tabi has a perfect score on Google's Lighthouse audit:
-
-![lighthouse](https://raw.githubusercontent.com/welpo/tabi/main/lighthouse_score.png)
-
-## Features
-
-- [X] [Set any language as default](https://welpo.github.io/tabi/blog/faq-languages/#how-do-i-set-a-default-language-for-my-site). Set your base site to Chinese, Spanish, French, Hindi… or any [other supported language](/i18n). The theme's interface will be translated accordingly.
-- [X] [Integration with remote repositories](https://welpo.github.io/tabi/blog/mastering-tabi-settings/#git-repository-integration) on GitHub, GitLab, Gitea & Codeberg for commit history and showing the site source.
-- [X] [Series support](https://welpo.github.io/tabi/blog/series/) for creating sequential content like tutorials, courses, and multi-part stories.
-- [X] Dark and light themes. Defaults to the OS setting, with a switcher in the navigation bar.
-- [X] Thorough documentation. See [Mastering tabi Settings: A Comprehensive Guide](https://welpo.github.io/tabi/blog/mastering-tabi-settings/).
-- [X] Perfect Lighthouse score (Performance, Accessibility, Best Practices and SEO).
-- [X] [Comprehensive multi-language support](https://welpo.github.io/tabi/blog/faq-languages/#how-does-tabi-handle-multilingual-support). Add as many languages as you wish.
-- [X] Support for [comments using giscus, utterances, Hyvor Talk, or Isso](https://welpo.github.io/tabi/blog/comments/).
-- [X] Code syntax highlighting with colours based on [Catppuccin](https://github.com/catppuccin/catppuccin) Frappé.
-- [X] [Mermaid support](https://welpo.github.io/tabi/blog/shortcodes/#mermaid-diagrams) to create diagrams and charts with text.
-- [X] [Local search](https://welpo.github.io/tabi/blog/mastering-tabi-settings/#search) with an accessible, multi-lingual interface.
-- [X] [Custom Twitter card](https://welpo.github.io/tabi/blog/mastering-tabi-settings/#social-media-cards) and automatic Open Graph tags.
-- [X] [KaTeX](https://katex.org/) support for mathematical notation.
-- [X] [Stylized and human readable Atom feed](https://welpo.github.io/tabi/atom.xml).
-- [X] [Stylized and human readable sitemap](https://welpo.github.io/tabi/sitemap.xml).
-- [X] [Mail encoding](https://welpo.github.io/tabi/blog/mastering-tabi-settings/#encoded-email) for spam protection.
-- [X] All JavaScript can be [fully disabled](https://welpo.github.io/tabi/blog/javascript/).
-- [X] [Customizable Table of Contents](https://welpo.github.io/tabi/blog/toc/).
-- [X] [Customizable secure headers](https://welpo.github.io/tabi/blog/security/).
-- [X] [Copy button for code blocks](https://welpo.github.io/tabi/blog/mastering-tabi-settings/#copy-button-on-code-blocks).
-- [X] [Quick navigation buttons](https://welpo.github.io/tabi/blog/mastering-tabi-settings/#quick-navigation-buttons).
-- [X] [Custom copyright notice](https://welpo.github.io/tabi/blog/mastering-tabi-settings/#copyright).
-- [X] [Custom canonical URLs](https://welpo.github.io/tabi/blog/mastering-tabi-settings/#canonical-url).
-- [X] [Custom shortcodes](https://welpo.github.io/tabi/blog/shortcodes/).
-- [X] [Customizable skins](https://welpo.github.io/tabi/blog/customise-tabi/).
-- [X] [Social media cards](https://welpo.github.io/tabi/blog/mastering-tabi-settings/#social-media-cards).
-- [X] Responsive design.
-- [X] [Projects page](https://welpo.github.io/tabi/projects/).
-- [X] [Archive page](https://welpo.github.io/tabi/archive/).
-- [X] [Pinned posts](https://welpo.github.io/tabi/blog/mastering-tabi-settings/#pinning-posts).
-- [X] [Social links](https://welpo.github.io/tabi/blog/mastering-tabi-settings/#social-media-icons).
-- [X] [Tags](https://welpo.github.io/tabi/blog/mastering-tabi-settings/#tags).
-
-## Installation
-
-> [!NOTE]
-> The fastest way to create a new site is to use the [tabi-start template](https://github.com/welpo/tabi-start). This gives you a complete blog setup with all the essential configuration ready to go.
-
-### Manual installation
-
-To add tabi to you existing Zola site:
-
-0. Initialize a Git repository in your project directory (if you haven't already):
-
-```
-git init
-```
-
-1. Add the theme as a git submodule:
-
-```
-git submodule add https://github.com/welpo/tabi.git themes/tabi
-```
-
-Or clone the theme into your themes directory:
-
-```
-git clone https://github.com/welpo/tabi.git themes/tabi
-```
-
-### Required configuration
-
-2. Enable the theme in your `config.toml`:
-
-```
-theme = "tabi"
-```
-
-3. Set a `title` in your `config.toml`:
-
-```
-title = "Your Site Title"
-```
-
-4. Configure code block highlighting in your `config.toml`:
-
-```toml
-[markdown]
-highlight_code = true
-highlight_theme = "css"
-```
-
-5. Create a `content/_index.md` file. This file controls how your home page looks and behaves. Choose one of the following options:
-
-   **Option A: Serve posts from `/`**:
-
-   ```
-   +++
-   title = "Home"
-   paginate_by = 5  # Show 5 posts per page.
-   +++
-   ```
-
-   - This will display posts in `content/` with pagination.
-
-   **Option B: Serve posts from a different path (e.g., `blog/`)**:
-
-   ```
-   +++
-   title = "Home"
-   # Note we're not setting `paginate_by` here.
-
-   [extra]
-   section_path = "blog/_index.md"  # Where to find your posts.
-   max_posts = 5  # Show 5 posts on the home page.
-   +++
-   ```
-
-    - This will display the latest 5 posts from the `blog/` section.
-    - Do not set `paginate_by` if you choose this option.
-    - Use the full path to the section's `_index.md` file. Using `section_path = "blog/"` will not work.
-
-> [!WARNING]
-> Do not set both `paginate_by` and `section_path` in `content/_index.md`.
->
-> These settings are mutually exclusive and using both may result in no posts being displayed.
-
-1. If you want an introduction section (see screenshot above), add these lines to `content/_index.md`:
-
-```
-[extra]
-header = {title = "Hello! I'm tabi~", img = "img/main.webp", img_alt = "Your Name" }
-```
-
-The content outside the front matter will be rendered between the header title and the posts listing. In the screenshot above, it's the text that reads "tabi is a fast, lightweight, and modern Zola theme…".
-
-7. If you want a multilingual site, you will need to set up each language. In `config.toml`, set the title and taxonomies for each language, like:
-
-```toml
-[languages.es]
-title = "~/tabi"
-taxonomies = [{name = "tags", feed = true}]
-```
-
-You will need an `_index.{language_code}.md` per language for each section (e.g. /blog or /projects) that you want to enable in that language.
-
-The same is true for individual posts, which should have the exact same name as the default language, with an extra `.{code}` before the extension (e.g. the Spanish version of `security.md` would be `security.es.md`).
-
-This configuration allows the language switcher to take the user to the translation of the current URL. If a translation doesn't exist, the 404 page will be displayed, with an explanation in each language set in the config.
-
-To learn more about multilingual support, see the [Frequently Asked Questions](https://welpo.github.io/tabi/blog/faq-languages/).
-
-### Updating tabi
-
-If you added the theme as a git submodule, run:
-
-```bash
-git submodule update --remote themes/tabi
-```
-
-If you cloned it:
-
-```bash
-cd themes/tabi
-git pull
-```
-
-## Sites using tabi
-
-| Website | Creator | Description  | Site Source   |
-| - | - | - | - |
-| [osc.garden](https://osc.garden) | Óscar Fernández ([welpo](https://github.com/welpo)) | Data science, psychology, and Zola | [Source](https://github.com/welpo/osc.garden) |
-| [sandip.live](https://sandip.live) | Sandip G ([sandman](https://github.com/sandman)) | Startups, tech and the good life | [Source](https://github.com/sandman/sandman.github.io) |
-| [seadve.github.io](https://seadve.github.io/) | Dave Patrick Caberto ([SeaDve](https://github.com/SeaDve/)) | Personal blog and portfolio with custom CSS | [Source](https://github.com/SeaDve/seadve.github.io) |
-| [mikufan.page](https://mikufan.page) | [Nadia](https://github.com/nyadiia) | Personal blog | [Source](https://github.com/nyadiia/mikufan.page) |
-| [tim-boettcher.online](https://tim-boettcher.online/) | [Tim Böttcher](https://codeberg.org/Tim-Boettcher/) | Insights and ramblings of a deafblind programmer | [Source](https://codeberg.org/Tim-Boettcher/tim-boettcher-online/) |
-| [www.richtman.au](https://www.richtman.au) | [Ariel Richtman](https://github.com/arichtman) | Personal tech blog | [Source](https://github.com/arichtman/www.richtman.au) |
-| [Ponderosa Games](https://ponderosagames.com/) | John Burak ([JVimes](https://github.com/jvimes)) | A friendly indie game company | &mdash; |
-| [jmbhughes.com](https://jmbhughes.com/) | Marcus Hughes ([jmbhughes](https://github.com/jmbhughes)) | Personal blog | [Source](https://github.com/jmbhughes/jmbhughes.github.io) |
-| [szabolcs.me](https://szabolcs.me) | Szabolcs Fazekas ([szabolcsf](https://github.com/szabolcsf)) | Personal blog | [Source](https://github.com/szabolcsf/szabolcs.me) |
-
-
-Using tabi? Feel free to create a PR and add your site to this list.
-
-## Inspiration
-
-This theme was inspired by:
-- [shadharon](https://github.com/syedzayyan/shadharon) — tabi started as a fork of [syedzayyan](https://github.com/syedzayyan)'s theme
-- [tailwind-nextjs-starter-blog](https://github.com/timlrx/tailwind-nextjs-starter-blog)
-- [abridge](https://github.com/Jieiku/abridge)
-
-## Support
-
-Something not working? Have an idea? Let us know!
-
-- Questions? → [Start a discussion](https://github.com/welpo/tabi/discussions)
-- Found a bug? → [Report it here](https://github.com/welpo/tabi/issues/new?&labels=bug&template=2_bug_report.yml)
-- Feature request? → [Tell us more!](https://github.com/welpo/tabi/issues/new?&labels=feature&template=3_feature_request.yml)
-
-## Contributing
-
-Please do! We appreciate bug reports, improvements to translations or documentation (however minor), feature requests…
-
-Take a look at the [Contributing Guidelines](/CONTRIBUTING.md) to learn more.
-
-## License
-
-The code is available under the [MIT license](./LICENSE).

cliff.toml

@@ -1,148 +0,0 @@
-# git-cliff ~ default configuration file
-# https://git-cliff.org/docs/configuration
-#
-# Lines starting with "#" are comments.
-# Configuration options are organized into tables and keys.
-# See documentation for more information on available options.
-
-[remote.github]
-owner = "welpo"
-repo = "tabi"
-
-[changelog]
-# changelog header
-header = """
-# Changelog
-
-Welcome to the changelog for tabi. This document aims to provide a comprehensive list of all notable changes made to the project, organised chronologically by release version.
-
-We use Semantic Versioning (SemVer) for our version numbers, formatted as MAJOR.MINOR.PATCH. Major version changes involve significant (breaking) changes, minor versions introduce features and improvements in a backward compatible manner, and patch versions are for bug fixes and minor tweaks.\n
-"""
-# template for the changelog body
-# https://keats.github.io/tera/docs/#introduction
-body = """
-{%- macro remote_url() -%}
-  https://github.com/{{ remote.github.owner }}/{{ remote.github.repo }}
-{%- endmacro -%}
-{% if version %}\
-    {% if previous.version %}\
-        ## [{{ version | trim_start_matches(pat="v") }}]({{ self::remote_url() }}/compare/{{ previous.version }}..{{ version }}) - {{ timestamp | date(format="%Y-%m-%d") }}
-    {% else %}\
-        ## {{ version | trim_start_matches(pat="v") }} - {{ timestamp | date(format="%Y-%m-%d") }}
-    {% endif %}\
-{% else %}\
-    ## unreleased
-{% endif %}\
-
-{% macro commit(commit, in_breaking_section=false) -%}
-    - {% if commit.scope %}*({{ commit.scope }})* {% endif %}{% if commit.breaking and not in_breaking_section %}[**‼️BREAKING‼️**] {% endif %}\
-        {{ commit.message | upper_first }}\
-        {% if not commit.remote.pr_number %} ([{{ commit.id | truncate(length=7, end="") }}]({{ self::remote_url() }}/commit/{{ commit.id }})){%- endif -%}{% if commit.remote.username %} by @{{ commit.remote.username }} \
-        {%- set co_authors = commit.footers | filter(attribute="token", value="Co-authored-by") | map(attribute="value") -%}
-        {%- set number_of_co_authors = co_authors | length -%}
-        {%- for co_author in co_authors -%}
-            {%- if not loop.last %}, {% else %} and {% endif %}@{{ co_author | split(pat=" <") | first | trim }}
-        {%- endfor -%}
-        {%- endif -%}
-{% endmacro -%}
-
-{%- set breaking_header_shown = false -%}
-{% for commit in commits -%}
-    {% if commit.breaking and not breaking_header_shown -%}
-        {% raw %}\n### 💥 BREAKING CHANGES 💥\n{% endraw %}
-        {%- set_global breaking_header_shown = true -%}
-    {%- endif -%}
-    {%- if commit.breaking %}
-        {{ self::commit(commit=commit, in_breaking_section=true) -}}
-    {% endif -%}
-{%- endfor -%}
-{%- if breaking_header_shown == true -%}
-    {% raw %}\n{% endraw %}\
-{%- endif -%}
-
-{% for group, commits in commits | group_by(attribute="group") %}
-    ### {{ group | striptags | trim | upper_first }}
-    {% for commit in commits
-    | filter(attribute="scope")
-    | sort(attribute="scope") %}
-        {{ self::commit(commit=commit) }}
-    {%- endfor -%}
-    {% raw %}\n{% endraw %}\
-    {%- for commit in commits %}
-        {%- if not commit.scope -%}
-            {{ self::commit(commit=commit) }}
-        {% endif -%}
-    {% endfor -%}
-{% endfor %}
-
-{%- if github.contributors | filter(attribute="is_first_time", value=true) | length != 0 -%}
-  {% raw %}\n{% endraw %}### 👥 New contributors
-  {% raw -%}\n{% endraw -%}
-{% for contributor in github.contributors | filter(attribute="is_first_time", value=true) %}
-  🫶 @{{ contributor.username }} made their first contribution
-    {%- if contributor.pr_number %} in \
-      [#{{ contributor.pr_number }}]({{ self::remote_url() }}/pull/{{ contributor.pr_number }}) \
-    {%- endif %}
-{% endfor %}
-{%- endif %}
-{% raw -%}\n{% endraw -%}
-"""
-
-# remove the leading and trailing whitespace from the template
-trim = true
-# changelog footer
-footer = """
-<!-- generated by git-cliff -->
-"""
-# postprocessors
-postprocessors = [
-    # { pattern = " @([a-zA-Z0-9](?:[a-zA-Z0-9]+-?)*[a-zA-Z0-9])", replace = " [@$1](https://github.com/$1)"}, # add link to GitHub usernames (done in release script instead)
-]
-
-[git]
-# parse the commits based on https://www.conventionalcommits.org
-conventional_commits = true
-# filter out the commits that are not conventional
-filter_unconventional = true
-# process each line of a commit as an individual commit
-split_commits = false
-# regex for preprocessing the commit messages
-commit_preprocessors = [
-    # Replace the issue number with the link.
-    { pattern = "\\(#([0-9]+)\\)", replace = "([#${1}](https://github.com/welpo/tabi/issues/${1}))" },
-    # Remove trailing whitespace.
-    { pattern = ' +$', replace = "" },
-    # Replace multiple spaces with a single space.
-    { pattern = ' +', replace = " " },
-    # Remove gitmoji, both actual UTF emoji and :emoji:
-    { pattern = ' *(:\w+:|[\p{Emoji_Presentation}\p{Extended_Pictographic}](?:\u{FE0F})?\u{200D}?) *', replace = "" },
-]
-# regex for parsing and grouping commits
-commit_parsers = [
-    { message = "^feat", group = "<!-- 0 -->✨ Features" },
-    { message = "^fix", group = "<!-- 1 -->🐛 Bug fixes" },
-    { message = "^style", group = "<!-- 2 -->💄 Styling" },
-    { message = "^doc", group = "<!-- 3 -->📝 Documentation" },
-    { message = "^refactor", group = "<!-- 4 -->♻️ Refactor" },
-    { message = "^test", group = "<!-- 5 -->✅ Testing" },
-    { message = "^misc", group = "<!-- 6 -->🔧 Miscellaneous tasks" },
-    { message = "^deprecate", group = "<!-- 7 -->🗑️️ Deprecations" },
-    { message = "^chore", skip = true },
-]
-# protect breaking changes from being skipped due to matching a skipping commit_parser
-protect_breaking_commits = true
-# filter out the commits that are not matched by commit parsers
-filter_commits = true
-# regex for matching git tags
-tag_pattern = "v[0-9].*"
-
-# regex for skipping tags
-skip_tags = "v0.1.0-beta.1"
-# regex for ignoring tags
-ignore_tags = ""
-# sort the tags topologically
-topo_order = false
-# sort the commits inside sections by oldest/newest order
-sort_commits = "newest"
-# limit the number of commits included in the changelog.
-# limit_commits = 42

config.toml

@@ -101,10 +101,10 @@ stylesheets = []
 # Remote repository for your Zola site.
 # Used for `show_remote_changes` and `show_remote_source` (see below).
 # Supports GitHub, GitLab, Gitea, and Codeberg.
-remote_repository_url = "https://github.com/alexohneander/alexohneander-zola"
+remote_repository_url = "https://git.dev-null.rocks/alexohneander/alexohneander-zola"
 # Set this to "auto" to try and auto-detect the platform based on the repository URL.
 # Accepted values are "github", "gitlab", "gitea", and "codeberg".
-remote_repository_git_platform = "auto"  # Defaults to "auto".
+remote_repository_git_platform = "gitea"  # Defaults to "auto".
 # Branch in the repo hosting the Zola site.
 remote_repository_branch = "main"  # Defaults to "main".
 # Show a link to the commit history of updated posts, right next to the last updated date.

content/blog/use-real-servers-again/index.md

@@ -0,0 +1,30 @@
++++
+title = "Use real Servers again"
+date = 2025-03-18
+updated = 2025-03-18
+description = "Is the cloud really the ultimate solution? This post questions the current cloud-first mentality, arguing for a return to 'real' servers and discussing the hidden costs, dependency, and political vulnerabilities of relying solely on the cloud."
+
+[taxonomies]
+tags = ["baremetal", "cloud", "google", "aws", "cloud"]
+
+[extra]
+toc = false
+pinned = true
+quick_navigation_buttons = true
++++
+
+![Private Cluster](https://preview.redd.it/k3pj0bjpr7s61.jpg?width=1080&crop=smart&auto=webp&s=8f1cee3bfc17c36c165e9e7dd7d5fafda6c943c6)
+
+## The Case for Bringing Back "Real" Servers: Why the Cloud Isn't Always King
+
+For years now, the narrative has been clear: the cloud is the future. Businesses big and small have flocked to platforms like Google Cloud and AWS, lured by promises of scalability, flexibility, and cost savings. But lately, I've been thinking: is this headlong rush to the cloud truly the best path? I believe it's time we seriously consider a return to "real" servers and acknowledge the limitations and potential pitfalls of relying solely on these tech giants.
+
+Let's be honest, the cloud providers aren't doing anything magical. At their core, Google, Amazon, and the rest are simply running massive data centers filled with… you guessed it… servers. They've built impressive infrastructure and offer a wide range of services on top, but fundamentally, "they also just cook with water," as the saying goes. The perceived complexity and innovation can sometimes mask the underlying reality.
+
+One of the biggest issues I've encountered, and I know many others have too, is the often-opaque pricing structure of cloud services. While the initial allure might be pay-as-you-go flexibility, the reality can be a tangled web of instance types, storage tiers, network egress fees, and a host of other charges that can quickly balloon your monthly bill. These "hidden costs" can be difficult to predict and manage, often negating the promised cost savings compared to the more predictable expenses of owning and maintaining your own hardware.
+
+Furthermore, the increasing reliance on a handful of major cloud providers creates a significant dependency. We are essentially entrusting critical data and infrastructure to these companies, making ourselves vulnerable to their pricing changes, service outages, and even their long-term strategic decisions. This lack of control is a worrying trend, especially when considering the potential for vendor lock-in, where migrating away from a specific cloud platform becomes prohibitively expensive and complex.
+
+Beyond the technical and economic considerations, the current political landscape adds another layer of risk to our cloud dependency. Imagine a scenario where political tensions rise, and a country like the United States, under a potential future administration, decides to impose tariffs on cloud services. Someone like Trump, for example, has shown a willingness to use tariffs as a political tool. If such tariffs were levied on cloud usage, businesses relying heavily on these platforms would face significant and potentially crippling cost increases. This geopolitical uncertainty makes the idea of having more control over our own infrastructure increasingly appealing.
+
+In conclusion, while the cloud offers undeniable benefits in certain situations, it's crucial to have a more balanced perspective. We need to recognize that "real" servers still hold significant value, offering greater control, potentially more predictable costs, and insulation from the unpredictable nature of both cloud pricing and international politics. It's time to re-evaluate our cloud-first mentality and consider whether bringing some workloads back in-house, or at least diversifying our infrastructure, might be a more resilient and ultimately more cost-effective strategy in the long run.

content/blog/why-docker-isnt-always-a-good-idea/index.md

@@ -2,7 +2,7 @@
 title = "Why Docker isn't always a good idea Part 1"
 date = 2022-09-15
 updated = 2022-09-15
-description = "To briefly explain the situation. We have a **HAProxy** running on a Debian server as a Docker container. This is the entrance node to a **Docker Swarm** cluster."
+description = "To briefly explain the situation. We have a HAProxy running on a Debian server as a Docker container. This is the entrance node to a Docker Swarm cluster."
 
 [taxonomies]
 tags = ["docker", "network", "haproxy"]

content/pages/experience/index.md

@@ -53,9 +53,19 @@ Agency for internet and design founded in 1998, established in Kastellaun in the
 
 ## Projects
 
+### DevOps Engineer, AEF AgIN Common-Connector
+
+The Common-Connector is being developed by the Agricultural Industry Electronics Foundation (AEF) as part of their Agricultural Interoperability Network (AgIN) initiative. In my role as a DevOps engineer, I supported the tender and contributed to the development of the MVP. Our team developed a Java Spring Boot application to facilitate seamless data exchange between platforms.
+
+- Conception and Development of a Dev Cluster based on AWS EKS (IaC)
+- Setting up build and deployment pipelines (GitLab)
+- Development of a test concept (Playwright, Testcontainers)
+- Development and integration of the operator pattern in a Java Spring Boot application
+- Development of the security pipelines (SonarQube, Mend, SAST)
+
 ### DevOps Engineer, Cofinity-X
 
-**since 2023**
+**until 2024**
 
 Cofinity-X is the first operator of the Catena-X network, connecting automotive partners at every level of the value chain. As a DevOps engineer, I was responsible for the enablement services.
 
@@ -85,3 +95,4 @@ Just right for your pharmacy! amamed is the only digital solution on the market
 - Design and operation of Kubernetes clusters (3 locations)
 - Management of automated pipelines via Bitbucket Pipelines (continuous integration)
 - IT administration for 6 individuals (SysOps)
+

content/projects/cert-fixer/index.md

@@ -0,0 +1,36 @@
++++
+title = "cert-fixer"
+description = "Watch k8s Resources to fix self propagation check for clusters behind NAT."
+weight = 30
+
+[taxonomies]
+tags = ["Rust", "Kubernetes", "CoreDNS", "BareMetal" ]
+
+[extra]
+local_image = "projects/cert-fixer/zutsu_logo.webp"
+social_media_card = "social_cards/projects_doteki.jpg"
+canonical_url = "https://alexohneander.de/projects/rustysearch/"
+add_src_to_code_block = true
++++
+
+### Why does this project exist?
+
+If you run a Kubernetes cluster behind a NAT and want to create certificates with the **Cert-Manager**, you quickly run into the problem that the Self Propagation check fails. This issue can be fixed with a simple line of code in the **CoreDNS** config. But now you don't want to adjust the **CoreDNS** Config for every Ingress and restart the Pod afterwards. The **cert-fixer** is supposed to be a quick remedy for this.
+
+### How does it work?
+
+The **cert-fixer** is a simple **Kubernetes** Pod that checks continuously if some Ingresses have been created or deleted. If this is the case, the **CoreDNS** ConfigMap should be updated and the **CoreDNS** Pod should be restarted.
+
+### How to use it?
+
+```bash
+kubectl apply -f https://raw.githubusercontent.com/alexohneander/cert-fixer/main/deployment/deployment.yaml
+```
+
+### How to configure it?
+
+The **cert-fixer** is configured via environment variables. The following variables are available:
+
+| Variable | Description | Default |
+| --- | --- | --- |
+| INGRESS_SERVICE | The name of the Ingress Controller Service | ingress-nginx-controller.ingress-nginx.svc.cluster.local |

deploy/deployment.yaml

@@ -0,0 +1,22 @@
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: alexohneander-zola-deployment
+  namespace: websites
+  labels:
+    app: alexohneander-zola
+spec:
+  replicas: 1
+  selector:
+    matchLabels:
+      app: alexohneander-zola
+  template:
+    metadata:
+      labels:
+        app: alexohneander-zola
+    spec:
+      containers:
+        - name: alexohneander-zola
+          image: git.dev-null.rocks/alexohneander/alexohneander-zola:0.1.3
+          ports:
+            - containerPort: 80

deploy/ingress.yaml

@@ -0,0 +1,59 @@
+apiVersion: networking.k8s.io/v1
+kind: Ingress
+metadata:
+  name: alexohneander-zola-ingress
+  namespace: websites
+  annotations:
+    cert-manager.io/cluster-issuer: letsencrypt-prod
+    kubernetes.io/ingress.class: nginx
+    kubernetes.io/tls-acme: "true"
+spec:
+  ingressClassName: nginx
+  tls:
+    - hosts:
+        - alexohneander.de
+        - wellnitz-alex.de
+        - www.alexohneander.de
+        - www.wellnitz-alex.de
+      secretName: alexohneander-tls
+  rules:
+    - host: www.wellnitz-alex.de
+      http:
+        paths:
+          - path: /
+            pathType: Prefix
+            backend:
+              service:
+                name: alexohneander-zola-service
+                port:
+                  number: 80
+    - host: www.alexohneander.de
+      http:
+        paths:
+          - path: /
+            pathType: Prefix
+            backend:
+              service:
+                name: alexohneander-zola-service
+                port:
+                  number: 80
+    - host: wellnitz-alex.de
+      http:
+        paths:
+          - path: /
+            pathType: Prefix
+            backend:
+              service:
+                name: alexohneander-zola-service
+                port:
+                  number: 80
+    - host: alexohneander.de
+      http:
+        paths:
+          - path: /
+            pathType: Prefix
+            backend:
+              service:
+                name: alexohneander-zola-service
+                port:
+                  number: 80

deploy/service.yaml

@@ -0,0 +1,12 @@
+apiVersion: v1
+kind: Service
+metadata:
+  name: alexohneander-zola-service
+  namespace: websites
+spec:
+  selector:
+    app: alexohneander-zola
+  ports:
+    - protocol: TCP
+      port: 80
+      targetPort: 80

renovate.json

@@ -0,0 +1,9 @@
+{
+  "extends": ["config:recommended"],
+  "packageRules": [
+    {
+      "matchUpdateTypes": ["minor", "patch", "pin", "digest"],
+      "automerge": true
+    }
+  ]
+}

sass/main.scss

@@ -55,7 +55,7 @@
         --bg-2: #fefefe;
         --bg-3: #d8dcdd;
         --hover-color: white;
-        --primary-color: #ff6b01;
+        --primary-color: #00d183;
         --divider-color: #d7d7d7;
         --text-color: #222226;
         --text-color-high-contrast: #313333;
@@ -73,7 +73,7 @@
         --bg-2: #171717;
         --bg-3: #535555;
         --hover-color: black;
-        --primary-color: #ff6b01;
+        --primary-color: #00d183;
         --divider-color: #4a4a4a;
         --text-color: #D4D4D4;
         --text-color-high-contrast: #eceeef;

sumi.toml

@@ -1,57 +0,0 @@
-# git-sumi ~ configuration file
-# Config: https://sumi.rs/docs/configuration
-# Rules: https://sumi.rs/docs/rules
-
-# Suppresses progress messages.
-quiet = false
-
-# Displays parsed commit message.
-display = true
-
-# Sets display format: cli, json, table, toml.
-format = "cli"
-
-# Processes each non-empty line as an individual commit.
-split_lines = false
-
-# Rule: Include one valid Gitmoji.
-# See https://gitmoji.dev/.
-gitmoji = true
-
-# Rule: Description must start with the specified case.
-# Options: 'any', 'lower', 'upper'.
-description_case = "lower"
-
-# Rule: Use the imperative mood in the description.
-# Example: 'Fix bug' instead of 'Fixed bug'.
-imperative = true
-
-# Rule: Do not end commit header with a period.
-no_period = true
-
-# Rule: Header length limit.
-# A value of 0 disables the rule.
-max_header_length = 55
-
-# Rule: Body line length limit.
-# A value of 0 disables the rule.
-max_body_length = 80
-
-# Rule: No leading, trailing, or consecutive spaces.
-whitespace = true
-
-# Rule: Follow Conventional Commits format.
-# See https://www.conventionalcommits.org/.
-conventional = true
-
-# Rule: List of allowed commit scopes.
-# An empty list allows all scopes. Example: ["docs", "cli"].
-scopes_allowed = []
-
-# Rule: List of allowed commit types.
-# An empty list allows all types. Example: ["feat", "fix", "docs"].
-types_allowed = ["feat", "fix", "docs", "refactor", "test", "chore", "misc", "style"]
-
-# Rule: Header must match regex pattern.
-# Example: '^JIRA-\d+:'.
-header_pattern = '^([\p{Emoji_Presentation}\p{Extended_Pictographic}](?:\u{FE0F})?\u{200D}?) \w' # The first character must be an emoji.

templates/partials/footer.html

@@ -103,8 +103,7 @@
 
                 {# Shows "Powered by Zola & tabi" notice #}
                 {{ macros_translate::translate(key="powered_by", default="Powered by", language_strings=language_strings) }}
-                <a rel="{{ rel_attributes }}" {{ blank_target }} href="https://www.getzola.org">Zola</a>
+                  <a rel="{{ rel_attributes }}" {{ blank_target }} href="https://www.getzola.org">Zola</a> and running on real <a {{ blank_target }} href="/blog/use-real-servers-again">Servers</a>
-
                 {# Shows link to remote repository #}
                 {%- if config.extra.remote_repository_url and config.extra.show_remote_source | default(value=true) -%}
                 {{ separator }}