My SSG for generating my website/blog content, which is deployed on branch 'pages'. https://maze88.dev
  • HTML 42.3%
  • CSS 34.3%
  • Shell 10.4%
  • JavaScript 7.6%
  • Makefile 5.4%
Find a file
Michael Zeevi 24e34db53f
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
add family news and some self-judgement to homepage
Signed-off-by: Michael Zeevi <[email protected]>
2025-12-10 11:59:38 +02:00
assets add assets (used to be res) from old pages-ssg repository 2024-12-25 02:53:13 +02:00
src add family news and some self-judgement to homepage 2025-12-10 11:59:38 +02:00
template removed pgp, keyoxide, and omg.lol from footer/social section; changed email to match publicly listed one on codeberg 2025-10-11 02:26:09 +03:00
.gitignore rename output directory to _dist 2024-12-26 00:18:06 +02:00
.woodpecker.yaml move woodpecker CI back to repo root 2025-10-11 02:09:14 +03:00
build.sh add gitignore for draft blog post dir 2025-08-11 02:25:28 +03:00
LICENSE add license from old pages-ssg repository 2024-12-23 01:39:40 +02:00
Makefile remove unimportant line from makefile 2025-04-25 09:31:36 +03:00
README.md minor reword in readme and testing CI fix 2025-06-30 02:42:46 +03:00

status-badge

maze88.dev Static site & generator

Overview

This repository contains the sources and static files (on branches main and pages, respectfully) for generating my website/blog https://maze88.dev using my SSG. Deployment is with Codeberg pages.

Input preparation

  1. All content should be written in markdown and put in the src/ directory.

    Note: Do not create a src/blog.md file, since the build will overwrite it when generating the blog index.

  2. Blog posts should be placed in the src/posts/ directory, with filenames that are arranged chronologically by prefix (using numbers and dashes only), such as:

    00-writing-markdown.md
    01-generating-html.md
    

    or

    2022-01-11-writing-markdown.md
    2022-02-22-generating-html.md
    
  3. Each post should contain the following YAML in its frontmatter:

    ---
    title: Generating HTML with Pandoc
    date: 2022-03-11
    author: Michael Zeevi  # optional
    keywords:  # optional
    - markdown
    - html
    ---
    
  4. Additional resources and media (CSS, images, PGP public key, etc.) can be put in the assets/ directory, which will be copied to _dist/assets/ during build.

Usage

Local development and testing

  1. Build by running make (which wraps the ./build.sh script) - this will clean and then produce the output in the directory _dist/.

  2. One can test by opening the output locally in their web browser.

Publishing (deploying)

  1. Run make publish - this will first build and then commit & push the output to the pages branch.

    Note: The pages branch must pre-exist in the remote repository.

  2. One can test by going to the website with their browser.

    Note: A .domains file must also exist on the pages branch.