chore: converted Emoji version 16 (#2018)

* add language support for Comment

* docs: let users know they can customize their language preference

.github/dependabot.yml

@@ -1,11 +1,20 @@
-# To get started with Dependabot version updates, you'll need to specify which
-# package ecosystems to update and where the package manifests are located.
-# Please see the documentation for all configuration options:
-# https://docs.github.com/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file
-
 version: 2
 updates:
   - package-ecosystem: "npm"
     directory: "/"
     schedule:
       interval: "weekly"
+    groups:
+      production-dependencies:
+        applies-to: "version-updates"
+        patterns:
+          - "*"
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    groups:
+      ci-dependencies:
+        applies-to: "version-updates"
+        patterns:
+          - "*"

.github/workflows/build-preview.yaml

@@ -0,0 +1,43 @@
+name: Build Preview Deployment
+
+on:
+  pull_request:
+    types: [opened, synchronize]
+  workflow_dispatch:
+
+jobs:
+  build-preview:
+    if: ${{ github.repository == 'jackyzha0/quartz' }}
+    runs-on: ubuntu-latest
+    name: Build Preview
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Setup Node
+        uses: actions/setup-node@v4
+        with:
+          node-version: 22
+
+      - name: Cache dependencies
+        uses: actions/cache@v4
+        with:
+          path: ~/.npm
+          key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}
+          restore-keys: |
+            ${{ runner.os }}-node-
+
+      - run: npm ci
+
+      - name: Check types and style
+        run: npm run check
+
+      - name: Build Quartz
+        run: npx quartz build -d docs -v
+
+      - name: Upload build artifact
+        uses: actions/upload-artifact@v4
+        with:
+          name: preview-build
+          path: public

.github/workflows/ci.yaml

@@ -7,6 +7,7 @@ on:
   push:
     branches:
       - v4
+  workflow_dispatch:
 
 jobs:
   build-and-test:
@@ -18,17 +19,17 @@ jobs:
     permissions:
       contents: write
     steps:
-      - uses: actions/checkout@v3
+      - uses: actions/checkout@v4
         with:
           fetch-depth: 0
 
       - name: Setup Node
-        uses: actions/setup-node@v3
+        uses: actions/setup-node@v4
         with:
-          node-version: 18
+          node-version: 22
 
       - name: Cache dependencies
-        uses: actions/cache@v3
+        uses: actions/cache@v4
         with:
           path: ~/.npm
           key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}
@@ -44,25 +45,25 @@ jobs:
         run: npm test
 
       - name: Ensure Quartz builds, check bundle info
-        run: npx quartz build --bundleInfo
+        run: npx quartz build --bundleInfo -d docs
 
   publish-tag:
-    if: ${{ github.repository == 'jackyzha0/quartz' }}
+    if: ${{ github.repository == 'jackyzha0/quartz' && github.ref == 'refs/heads/v4' }}
     runs-on: ubuntu-latest
     permissions:
       contents: write
     steps:
-      - uses: actions/checkout@v3
+      - uses: actions/checkout@v4
         with:
           fetch-depth: 0
       - name: Setup Node
-        uses: actions/setup-node@v3
+        uses: actions/setup-node@v4
         with:
-          node-version: 18
+          node-version: 22
       - name: Get package version
         run: node -p -e '`PACKAGE_VERSION=${require("./package.json").version}`' >> $GITHUB_ENV
       - name: Create release tag
-        uses: pkgdeps/git-tag-action@v2
+        uses: pkgdeps/git-tag-action@v3
         with:
           github_token: ${{ secrets.GITHUB_TOKEN }}
           github_repo: ${{ github.repository }}

.github/workflows/deploy-preview.yaml

@@ -0,0 +1,37 @@
+name: Upload Preview Deployment
+on:
+  workflow_run:
+    workflows: ["Build Preview Deployment"]
+    types:
+      - completed
+
+permissions:
+  actions: read
+  deployments: write
+  contents: read
+  pull-requests: write
+
+jobs:
+  deploy-preview:
+    if: ${{ github.repository == 'jackyzha0/quartz' && github.event.workflow_run.conclusion == 'success' }}
+    runs-on: ubuntu-latest
+    name: Deploy Preview to Cloudflare Pages
+    steps:
+      - name: Download build artifact
+        uses: actions/download-artifact@v4
+        id: preview-build-artifact
+        with:
+          name: preview-build
+          path: build
+          github-token: ${{ secrets.GITHUB_TOKEN }}
+          run-id: ${{ github.event.workflow_run.id }}
+
+      - name: Deploy to Cloudflare Pages
+        uses: AdrianGonz97/refined-cf-pages-action@v1
+        with:
+          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
+          accountId: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
+          githubToken: ${{ secrets.GITHUB_TOKEN }}
+          projectName: quartz
+          deploymentName: Branch Preview
+          directory: ${{ steps.preview-build-artifact.outputs.download-path }}

.github/workflows/docker-build-push.yaml

@@ -0,0 +1,88 @@
+name: Docker build & push image
+
+on:
+  push:
+    branches: [v4]
+    tags: ["v*"]
+  pull_request:
+    branches: [v4]
+    paths:
+      - .github/workflows/docker-build-push.yaml
+      - quartz/**
+  workflow_dispatch:
+
+jobs:
+  build:
+    if: ${{ github.repository == 'jackyzha0/quartz' }} # Comment this out if you want to publish your own images on a fork!
+    runs-on: ubuntu-latest
+    steps:
+      - name: Set lowercase repository owner environment variable
+        run: |
+          echo "OWNER_LOWERCASE=${OWNER,,}" >> ${GITHUB_ENV}
+        env:
+          OWNER: "${{ github.repository_owner }}"
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 1
+      - name: Inject slug/short variables
+        uses: rlespinasse/github-slug-action@v5.1.0
+      - name: Set up QEMU
+        uses: docker/setup-qemu-action@v3
+      - name: Set up Docker Buildx
+        uses: docker/setup-buildx-action@v3
+        with:
+          install: true
+          driver-opts: |
+            image=moby/buildkit:master
+            network=host
+      - name: Install cosign
+        if: github.event_name != 'pull_request'
+        uses: sigstore/cosign-installer@v3.8.2
+      - name: Login to GitHub Container Registry
+        uses: docker/login-action@v3
+        if: github.event_name != 'pull_request'
+        with:
+          registry: ghcr.io
+          username: ${{ github.actor }}
+          password: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Extract metadata tags and labels on PRs
+        if: github.event_name == 'pull_request'
+        id: meta-pr
+        uses: docker/metadata-action@v5
+        with:
+          images: ghcr.io/${{ env.OWNER_LOWERCASE }}/quartz
+          tags: |
+            type=raw,value=sha-${{ env.GITHUB_SHA_SHORT }}
+          labels: |
+            org.opencontainers.image.source="https://github.com/${{ github.repository_owner }}/quartz"
+      - name: Extract metadata tags and labels for main, release or tag
+        if: github.event_name != 'pull_request'
+        id: meta
+        uses: docker/metadata-action@v5
+        with:
+          flavor: |
+            latest=auto
+          images: ghcr.io/${{ env.OWNER_LOWERCASE }}/quartz
+          tags: |
+            type=semver,pattern={{version}}
+            type=semver,pattern={{major}}.{{minor}}
+            type=semver,pattern={{major}}.{{minor}}.{{patch}}
+            type=raw,value=latest,enable=${{ github.ref == format('refs/heads/{0}', github.event.repository.default_branch) }}
+            type=raw,value=sha-${{ env.GITHUB_SHA_SHORT }}
+          labels: |
+            maintainer=${{ github.repository_owner }}
+            org.opencontainers.image.source="https://github.com/${{ github.repository_owner }}/quartz"
+
+      - name: Build and push Docker image
+        id: build-and-push
+        uses: docker/build-push-action@v6
+        with:
+          push: ${{ github.event_name != 'pull_request' }}
+          build-args: |
+            GIT_SHA=${{ env.GITHUB_SHA }}
+            DOCKER_LABEL=sha-${{ env.GITHUB_SHA_SHORT }}
+          tags: ${{ steps.meta.outputs.tags || steps.meta-pr.outputs.tags }}
+          labels: ${{ steps.meta.outputs.labels || steps.meta-pr.outputs.labels }}
+          cache-from: type=gha
+          cache-to: type=gha

.node-version

@@ -0,0 +1 @@
+v22.16.0

Dockerfile

@@ -1,23 +1,11 @@
-FROM python:latest as convert
-WORKDIR /usr/src/app
-COPY content/ ./
-COPY custom/convert-furigana/program/convert-furigana.py ./
-COPY custom/convert-usage/program/convert-usage.py ./
-ENV PIP_ROOT_USER_ACTION=ignore
-RUN python -m pip install --upgrade pip
-RUN python -m pip install beautifulsoup4
-RUN python convert-furigana.py .
-RUN python convert-usage.py .
-
-FROM node:20-slim as builder
+FROM node:22-slim AS builder
 WORKDIR /usr/src/app
 COPY package.json .
 COPY package-lock.json* .
 RUN npm ci
 
-FROM node:20-slim
+FROM node:22-slim
 WORKDIR /usr/src/app
 COPY --from=builder /usr/src/app/ /usr/src/app/
 COPY . .
-COPY --from=convert /usr/src/app/ /usr/src/app/content/
 CMD ["npx", "quartz", "build", "--serve"]

content/.gitignore

@@ -1,2 +0,0 @@
-.obsidian/workspace.json
-0- Do-Not-Commit

content/.obsidian/app.json

@@ -1,4 +0,0 @@
-{
-  "alwaysUpdateLinks": true,
-  "showInlineTitle": false
-}

content/.obsidian/appearance.json

@@ -1,11 +0,0 @@
-{
-  "accentColor": "",
-  "theme": "moonstone",
-  "enabledCssSnippets": [
-    "usage",
-    "spacing",
-    "highlight-color"
-  ],
-  "cssTheme": "AnuPpuccin",
-  "showViewHeader": true
-}

content/.obsidian/community-plugins.json

@@ -1,6 +0,0 @@
-[
-  "obsidian-markdown-furigana",
-  "obsidian-style-settings",
-  "obsidian42-brat",
-  "obsidian-opener"
-]

content/.obsidian/core-plugins-migration.json

@@ -1,30 +0,0 @@
-{
-  "file-explorer": true,
-  "global-search": true,
-  "switcher": true,
-  "graph": true,
-  "backlink": true,
-  "canvas": true,
-  "outgoing-link": true,
-  "tag-pane": true,
-  "properties": false,
-  "page-preview": true,
-  "daily-notes": true,
-  "templates": true,
-  "note-composer": true,
-  "command-palette": true,
-  "slash-command": false,
-  "editor-status": true,
-  "bookmarks": true,
-  "markdown-importer": false,
-  "zk-prefixer": false,
-  "random-note": false,
-  "outline": true,
-  "word-count": true,
-  "slides": false,
-  "audio-recorder": false,
-  "workspaces": false,
-  "file-recovery": true,
-  "publish": false,
-  "sync": false
-}

content/.obsidian/core-plugins.json

@@ -1,20 +0,0 @@
-[
-  "file-explorer",
-  "global-search",
-  "switcher",
-  "graph",
-  "backlink",
-  "canvas",
-  "outgoing-link",
-  "tag-pane",
-  "page-preview",
-  "daily-notes",
-  "templates",
-  "note-composer",
-  "command-palette",
-  "editor-status",
-  "bookmarks",
-  "outline",
-  "word-count",
-  "file-recovery"
-]

content/.obsidian/graph.json

@@ -1,22 +0,0 @@
-{
-  "collapse-filter": true,
-  "search": "",
-  "showTags": false,
-  "showAttachments": false,
-  "hideUnresolved": false,
-  "showOrphans": true,
-  "collapse-color-groups": true,
-  "colorGroups": [],
-  "collapse-display": true,
-  "showArrow": false,
-  "textFadeMultiplier": 0,
-  "nodeSizeMultiplier": 1,
-  "lineSizeMultiplier": 1,
-  "collapse-forces": true,
-  "centerStrength": 0.518713248970312,
-  "repelStrength": 10,
-  "linkStrength": 1,
-  "linkDistance": 250,
-  "scale": 1,
-  "close": false
-}

content/.obsidian/plugins/obsidian-markdown-furigana/manifest.json

@@ -1,10 +0,0 @@
-{
-	"id": "obsidian-markdown-furigana",
-	"name": "Markdown Furigana",
-	"version": "1.3.0",
-	"minAppVersion": "0.9.12",
-	"description": "Simple Markdown to Furigana Rendering Plugin for Obsidian.",
-	"author": "Steven Kraft",
-	"authorUrl": "https://github.com/steven-kraft/obsidian-markdown-furigana",
-	"isDesktopOnly": false
-}

content/.obsidian/plugins/obsidian-opener/main.js

@@ -1,377 +0,0 @@
-/*
-THIS IS A GENERATED/BUNDLED FILE BY ESBUILD
-if you want to view the source, please visit the github repository of this plugin
-*/
-
-var __defProp = Object.defineProperty;
-var __getOwnPropDesc = Object.getOwnPropertyDescriptor;
-var __getOwnPropNames = Object.getOwnPropertyNames;
-var __hasOwnProp = Object.prototype.hasOwnProperty;
-var __export = (target, all) => {
-  for (var name in all)
-    __defProp(target, name, { get: all[name], enumerable: true });
-};
-var __copyProps = (to, from, except, desc) => {
-  if (from && typeof from === "object" || typeof from === "function") {
-    for (let key of __getOwnPropNames(from))
-      if (!__hasOwnProp.call(to, key) && key !== except)
-        __defProp(to, key, { get: () => from[key], enumerable: !(desc = __getOwnPropDesc(from, key)) || desc.enumerable });
-  }
-  return to;
-};
-var __toCommonJS = (mod) => __copyProps(__defProp({}, "__esModule", { value: true }), mod);
-
-// main.ts
-var main_exports = {};
-__export(main_exports, {
-  default: () => Opener
-});
-module.exports = __toCommonJS(main_exports);
-var import_obsidian2 = require("obsidian");
-
-// node_modules/monkey-around/mjs/index.js
-function around(obj, factories) {
-  const removers = Object.keys(factories).map((key) => around1(obj, key, factories[key]));
-  return removers.length === 1 ? removers[0] : function() {
-    removers.forEach((r) => r());
-  };
-}
-function around1(obj, method, createWrapper) {
-  const original = obj[method], hadOwn = obj.hasOwnProperty(method);
-  let current = createWrapper(original);
-  if (original)
-    Object.setPrototypeOf(current, original);
-  Object.setPrototypeOf(wrapper, current);
-  obj[method] = wrapper;
-  return remove;
-  function wrapper(...args) {
-    if (current === original && obj[method] === wrapper)
-      remove();
-    return current.apply(this, args);
-  }
-  function remove() {
-    if (obj[method] === wrapper) {
-      if (hadOwn)
-        obj[method] = original;
-      else
-        delete obj[method];
-    }
-    if (current === original)
-      return;
-    current = original;
-    Object.setPrototypeOf(wrapper, original || Function);
-  }
-}
-
-// settings.ts
-var import_obsidian = require("obsidian");
-var OpenerSettingTab = class extends import_obsidian.PluginSettingTab {
-  display() {
-    const { containerEl } = this;
-    const plugin = this.plugin;
-    containerEl.empty();
-    new import_obsidian.Setting(containerEl).setName("New Tab Default").setDesc(
-      "Enable to open new files in a new tab (or existing tab, if it was previously opened). Disable for default Obsidian behavior."
-    ).addToggle(
-      (toggle) => toggle.setValue(plugin.settings.newTab).onChange((value) => {
-        plugin.settings.newTab = value;
-        plugin.saveSettings();
-      })
-    );
-    new import_obsidian.Setting(containerEl).setName("PDF Default App").setDesc(
-      "Enable to open pdfs with system viewer app. Disable for default behavior (open pdfs in Obsidian)."
-    ).addToggle(
-      (toggle) => toggle.setValue(plugin.settings.PDFApp).onChange((value) => {
-        plugin.settings.PDFApp = value;
-        plugin.saveSettings();
-      })
-    );
-    new import_obsidian.Setting(containerEl).setName("Default app only when Ctrl/Cmd-Key is held").setDesc(
-      "Open in default app only when Ctrl/Cmd-Key is held. Disable to always\u201A open with system viewer."
-    ).addToggle(
-      (toggle) => toggle.setValue(plugin.settings.extOnlyWhenMetaKey).onChange((value) => {
-        plugin.settings.extOnlyWhenMetaKey = value;
-        plugin.saveSettings();
-      })
-    );
-    new import_obsidian.Setting(containerEl).setName("Open everything outside of Obsidian").setDesc(
-      "Enable to open all obsidian supported extensions with system viewer instead. Disable for default behavior (open within Obsidian). Defaults supported extensions are 'png', 'webp', 'jpg', 'jpeg', 'gif', 'bmp', 'svg', 'mp3', 'webm', 'wav', 'm4a', 'ogg','3gp', 'flac', 'mp4', 'ogv', 'mov', 'mkv'."
-    ).addToggle(
-      (toggle) => toggle.setValue(plugin.settings.allExt).onChange((value) => {
-        plugin.settings.allExt = value;
-        plugin.saveSettings();
-      })
-    );
-    new import_obsidian.Setting(containerEl).setName("Open Outside Obsidian: Manual List").setDesc("This shouldn't be necessary, but you can manually enable custom extensions here.").addToggle(
-      (toggle) => toggle.setValue(plugin.settings.custExt).onChange((value) => {
-        plugin.settings.custExt = value;
-        plugin.saveSettings();
-        this.display();
-      })
-    );
-    if (plugin.settings.custExt) {
-      new import_obsidian.Setting(containerEl).setName("Manual List").setDesc("Enter extension names (without the dot, ie, just docx separated by newlines).").addTextArea((textArea) => {
-        textArea.inputEl.rows = 5;
-        textArea.setValue(plugin.settings.custExtList.join("\n")).onChange(async (value) => {
-          plugin.settings.custExtList = value.split("\n");
-          plugin.saveSettings();
-        });
-      }).settingEl.style.borderTop = "none";
-    }
-  }
-};
-
-// constants.ts
-var DEFAULT_SETTINGS = {
-  newTab: true,
-  PDFApp: true,
-  extOnlyWhenMetaKey: true,
-  allExt: false,
-  custExt: false,
-  custExtList: []
-};
-
-// main.ts
-var Opener = class extends import_obsidian2.Plugin {
-  constructor() {
-    super(...arguments);
-    this.isMetaKeyHeld = null;
-    this.sameTabOnce = false;
-    // Meta key listeners
-    // arrow syntax to preserve `this` context
-    this.keyDownHandler = (e) => {
-      if (e.key === "Meta" || e.key === "Control") {
-        this.isMetaKeyHeld = true;
-      }
-    };
-    this.keyUpHandler = (e) => {
-      if (e.key === "Meta" || e.key === "Control") {
-        this.isMetaKeyHeld = false;
-      }
-    };
-    // Mouse handler is needed because the key handler will not fire if the app is out of focus
-    this.mouseDownHandler = (e) => {
-      if (e.metaKey || e.ctrlKey) {
-        this.isMetaKeyHeld = true;
-      } else {
-        this.isMetaKeyHeld = false;
-      }
-    };
-  }
-  async onload() {
-    console.log("loading " + this.manifest.name + " plugin");
-    await this.loadSettings();
-    this.addSettingTab(new OpenerSettingTab(this.app, this));
-    this.updateMetaKeyListeners();
-    this.monkeyPatchOpenFile();
-    this.addCommands();
-    this.addMenuItem();
-  }
-  onunload() {
-    this.uninstallMonkeyPatchOpenFile && this.uninstallMonkeyPatchOpenFile();
-    this.removeMetaKeyListeners();
-    console.log("unloading " + this.manifest.name + " plugin");
-  }
-  async loadSettings() {
-    const data = await this.loadData();
-    this.settings = Object.assign({}, DEFAULT_SETTINGS, data);
-  }
-  async saveSettings() {
-    await this.saveData(this.settings);
-    this.updateMetaKeyListeners();
-  }
-  addCommands() {
-    this.addCommand({
-      id: "same-tab-once",
-      name: "Open next file in same tab (Obsidian default behavior)",
-      checkCallback: (checking) => {
-        if (checking) {
-          return this.settings.newTab;
-        }
-        this.sameTabOnce = true;
-        new import_obsidian2.Notice("Next file will open in same tab");
-      }
-    });
-    this.addCommand({
-      id: "enable-new-tab",
-      name: "Enable new tab for all files",
-      checkCallback: (checking) => {
-        if (checking) {
-          return !this.settings.newTab;
-        }
-        this.settings.newTab = true;
-        this.saveSettings();
-        new import_obsidian2.Notice("Opener: New tab for all files enabled");
-      }
-    });
-    this.addCommand({
-      id: "disable-new-tab",
-      name: "Disable new tab for all files",
-      checkCallback: (checking) => {
-        if (checking) {
-          return this.settings.newTab;
-        }
-        this.settings.newTab = false;
-        this.saveSettings();
-        new import_obsidian2.Notice("Opener: New tab for all files disabled");
-      }
-    });
-    this.addCommand({
-      id: "enable-pdf",
-      name: "Enable open all PDFs with default app",
-      checkCallback: (checking) => {
-        if (checking) {
-          return !this.settings.PDFApp;
-        }
-        this.settings.PDFApp = true;
-        this.saveSettings();
-        new import_obsidian2.Notice("Opener: Open all PDFs with default app enabled");
-      }
-    });
-    this.addCommand({
-      id: "disable-pdf",
-      name: "Disable open all PDFs with default app",
-      checkCallback: (checking) => {
-        if (checking) {
-          return this.settings.PDFApp;
-        }
-        this.settings.PDFApp = false;
-        this.saveSettings();
-        new import_obsidian2.Notice("Opener: Open all PDFs with default app disabled");
-      }
-    });
-    this.addCommand({
-      id: "open-graph-view-in-new-tab",
-      name: "Open Graph View in new tab",
-      callback: () => {
-        this.app.commands.executeCommandById("workspace:new-tab");
-        this.app.commands.executeCommandById("graph:open");
-      }
-    });
-  }
-  // add command to right-click menu
-  addMenuItem() {
-    this.registerEvent(
-      this.app.workspace.on("file-menu", (menu, file, source, leaf) => {
-        if (file instanceof import_obsidian2.TFile) {
-          menu.addItem((item) => {
-            item.setSection("open");
-            item.setTitle("Open in same tab").onClick(() => {
-              this.sameTabOnce = true;
-              this.app.workspace.getLeaf().openFile(file);
-            });
-          });
-        }
-      })
-    );
-  }
-  addMetaKeyListeners() {
-    if (this.isMetaKeyHeld !== null)
-      return;
-    this.isMetaKeyHeld = false;
-    document.addEventListener("keydown", this.keyDownHandler);
-    document.addEventListener("keyup", this.keyUpHandler);
-    document.addEventListener("mousedown", this.mouseDownHandler, { capture: true });
-  }
-  removeMetaKeyListeners() {
-    if (this.isMetaKeyHeld === null)
-      return;
-    document.removeEventListener("keydown", this.keyDownHandler);
-    document.removeEventListener("keyup", this.keyUpHandler);
-    document.removeEventListener("mousedown", this.mouseDownHandler, { capture: true });
-    this.isMetaKeyHeld = null;
-  }
-  updateMetaKeyListeners() {
-    if (this.settings.extOnlyWhenMetaKey) {
-      this.addMetaKeyListeners();
-    } else {
-      this.removeMetaKeyListeners();
-    }
-  }
-  monkeyPatchOpenFile() {
-    const parentThis = this;
-    this.uninstallMonkeyPatchOpenFile = around(import_obsidian2.WorkspaceLeaf.prototype, {
-      openFile(oldOpenFile) {
-        return async function(file, openState) {
-          var _a, _b, _c, _d, _e, _f, _g, _h;
-          const defaultBehavior = () => {
-            return oldOpenFile.apply(this, [file, openState]);
-          };
-          const preparedEmptyLeave = ((_a = this.getViewState()) == null ? void 0 : _a.type) == "empty";
-          if (((_b = openState == null ? void 0 : openState.state) == null ? void 0 : _b.mode) && preparedEmptyLeave) {
-            return defaultBehavior();
-          }
-          if (file.path == ((_c = app.workspace.getActiveFile()) == null ? void 0 : _c.path) && ((_d = openState == null ? void 0 : openState.eState) == null ? void 0 : _d.subpath)) {
-            return defaultBehavior();
-          }
-          if (parentThis.sameTabOnce) {
-            parentThis.sameTabOnce = false;
-            return defaultBehavior();
-          }
-          const ALLEXT = ["png", "webp", "jpg", "jpeg", "gif", "bmp", "svg", "mp3", "webm", "wav", "m4a", "ogg", "3gp", "flac", "mp4", "ogv", "mov", "mkv"];
-          const OBSID_OPENABLE = ALLEXT.concat(["md", "canvas", "pdf"]);
-          if (parentThis.settings.PDFApp && file.extension == "pdf" || parentThis.settings.allExt && ALLEXT.includes(file.extension) || parentThis.settings.custExt && parentThis.settings.custExtList.includes(file.extension)) {
-            if (!parentThis.settings.extOnlyWhenMetaKey || parentThis.isMetaKeyHeld) {
-              new import_obsidian2.Notice("Opening external file with default app (Opener Plugin)");
-              if (preparedEmptyLeave) {
-                this.detach();
-              }
-              parentThis.app.openWithDefaultApp(file.path);
-              return;
-            } else {
-              new import_obsidian2.Notice("Opener Tip: Hold Cmd/Ctrl key to open with default app");
-            }
-          }
-          if (!parentThis.settings.newTab) {
-            return defaultBehavior();
-          }
-          if (this.group) {
-            new import_obsidian2.Notice("Opener: This is a Linked Tab! Opening in same tab therefore.");
-            return defaultBehavior();
-          }
-          const matchingLeaves = [];
-          const pushLeaveIfMatching = (leaf) => {
-            var _a2;
-            if (((_a2 = leaf.getViewState().state) == null ? void 0 : _a2.file) == file.path) {
-              matchingLeaves.push(leaf);
-            }
-          };
-          app.workspace.iterateRootLeaves(pushLeaveIfMatching);
-          (_g = (_f = (_e = app.workspace.getLayout()) == null ? void 0 : _e.floating) == null ? void 0 : _f.children) == null ? void 0 : _g.forEach((win) => {
-            var _a2;
-            if ((win == null ? void 0 : win.type) !== "window")
-              return console.log("Opener-Plugin: Strange floating object found (no window)", win);
-            (_a2 = win.children) == null ? void 0 : _a2.forEach((tabs) => {
-              var _a3;
-              if ((tabs == null ? void 0 : tabs.type) !== "tabs")
-                return console.log("Opener-Plugin: Strange floating object found (no tabs)", tabs);
-              (_a3 = tabs.children) == null ? void 0 : _a3.forEach((leaf) => {
-                if ((leaf == null ? void 0 : leaf.type) !== "leaf")
-                  return console.log("Opener-Plugin: Strange floating object found (no leaf)", leaf);
-                pushLeaveIfMatching(app.workspace.getLeafById(leaf.id));
-              });
-            });
-          });
-          if (matchingLeaves.length) {
-            if (preparedEmptyLeave) {
-              new import_obsidian2.Notice(`File is now open in ${matchingLeaves.length + 1} Tabs`);
-              return defaultBehavior();
-            } else {
-              return oldOpenFile.apply(matchingLeaves[0], [file, openState]);
-            }
-          }
-          if (preparedEmptyLeave) {
-            return defaultBehavior();
-          }
-          if (!((_h = parentThis.app.viewRegistry) == null ? void 0 : _h.getTypeByExtension(file.extension))) {
-            return defaultBehavior();
-          }
-          return oldOpenFile.apply(app.workspace.getLeaf("tab"), [
-            file,
-            openState
-          ]);
-        };
-      }
-    });
-  }
-};

content/.obsidian/plugins/obsidian-opener/manifest.json

@@ -1 +0,0 @@
-{"id":"obsidian-opener","name":"Opener","minAppVersion":"0.15.9","description":"Open links in new/existing tabs by default. Open PDFs in System App by default. Can open other file formats in System Apps if desired.","author":"Aidan Gibson","authorUrl":"https://github.com/aidan-gibson","isDesktopOnly":false,"version":"2.1.2"}

content/.obsidian/plugins/obsidian-style-settings/data.json

@@ -1,5 +0,0 @@
-{
-  "anuppuccin-theme-settings@@anuppuccin-theme-light": "ctp-latte",
-  "anuppuccin-theme-settings@@anuppuccin-light-theme-accents": "ctp-accent-light-lavender",
-  "anuppuccin-theme-settings@@anuppuccin-theme-accents": "ctp-accent-lavender"
-}

content/.obsidian/plugins/obsidian-style-settings/manifest.json

@@ -1,10 +0,0 @@
-{
-	"id": "obsidian-style-settings",
-	"name": "Style Settings",
-	"version": "1.0.8",
-	"minAppVersion": "0.11.5",
-	"description": "Offers controls for adjusting theme, plugin, and snippet CSS variables.",
-	"author": "mgmeyers",
-	"authorUrl": "https://github.com/mgmeyers/obsidian-style-settings",
-	"isDesktopOnly": false
-}

content/.obsidian/plugins/obsidian42-brat/data.json

@@ -1,16 +0,0 @@
-{
-  "pluginList": [
-    "aidan-gibson/obsidian-opener"
-  ],
-  "pluginSubListFrozenVersion": [],
-  "themesList": [],
-  "updateAtStartup": true,
-  "updateThemesAtStartup": true,
-  "enableAfterInstall": true,
-  "loggingEnabled": false,
-  "loggingPath": "BRAT-log",
-  "loggingVerboseEnabled": false,
-  "debuggingMode": false,
-  "notificationsEnabled": true,
-  "personalAccessToken": ""
-}

content/.obsidian/plugins/obsidian42-brat/manifest.json

@@ -1,15 +0,0 @@
-{
-	"id": "obsidian42-brat",
-	"name": "BRAT",
-	"version": "1.0.1",
-	"minAppVersion": "1.4.16",
-	"description": "Easily install a beta version of a plugin for testing.",
-	"author": "TfTHacker",
-	"authorUrl": "https://github.com/TfTHacker/obsidian42-brat",
-	"helpUrl": "https://tfthacker.com/BRAT",
-	"isDesktopOnly": false,
-	"fundingUrl": {
-		"Buy Me a Coffee": "https://bit.ly/o42-kofi",
-		"Visit my site": "https://tfthacker.com"
-	}
-}

content/.obsidian/plugins/obsidian42-brat/styles.css

@@ -1,3 +0,0 @@
-.brat-modal .modal-button-container {
-  margin-top: 5px !important;
-}

content/.obsidian/snippets/highlight-color.css

@@ -1,3 +0,0 @@
-.cm-s-obsidian span.cm-formatting-highlight, .cm-s-obsidian span.cm-highlight, .markdown-rendered mark {
-    --text-highlight-bg: #e6cee7;
-}

content/.obsidian/snippets/spacing.css

@@ -1,3 +0,0 @@
-.cm-s-obsidian .cm-line.HyperMD-header {
-    padding-top: 0;
-}

content/.obsidian/snippets/usage.css

@@ -1,34 +0,0 @@
-.usage {
-    display:flex;
-    flex-direction: row;
-    align-items: center;
-}
-
-.usage p {
-    margin:0;
-}
-
-.usage .box {
-    border: 1px solid black;
-    border-radius: 0.5rem;
-    padding: 0.2rem 0.3rem 0.2rem 0.3rem;
-    display: inline-block;
-    width: fit-content;
-    margin: 0.2rem;
-}
-
-.usage .left {
-    padding-right: 1.7rem;
-
-    background-image: linear-gradient(black, black), linear-gradient(black, black);
-    background-repeat: no-repeat;
-    background-size: 8px 2px;
-    background-position: top right, bottom right;
-
-    border-right: solid black;
-    border-width: 0 2px;
-}
-
-.usage .right {
-    padding-left: 1rem;
-}

content/.obsidian/themes/AnuPpuccin/manifest.json

@@ -1,7 +0,0 @@
-{
-  "name": "AnuPpuccin",
-  "version": "1.4.5",
-  "minAppVersion": "0.16.0",
-  "author": "Anubis",
-  "authorUrl": "https://github.com/AnubisNekhet"
-}

content/2- Conjugation/2- TeF - basics.md

@@ -1,230 +0,0 @@
-# 2- Te-Form - basics
-
-## Rule
-
-### Verbs
-
-The easiest way to identify whether to use て or で is by looking at the preceding kana.
-If the plain (dictionary) form of the verb finishes in ぐ, ぬ, ぶ, or む, then で will be used.
-る-Verbs never use で.
-
-| Ending              | Ending Te-Form | Verb           | Te-Form                       | Hiragana            |
-| ------------------- | -------------- | -------------- | ----------------------------- | ------------------- |
-| **る verbs**         |                |                |                               |                     |
-| (い・え)る              | て              | 食べる            | 食べ==て==                       | たべて                 |
-| **う verbs**         |                |                |                               |                     |
-| う<br>つ<br>る         | <br>って<br>     | 歌う<br>打つ<br>座る | 歌==って==<br>打==って==<br>座==って== | うたって<br>うって<br>すわって |
-| む<br>ぶ<br>ぬ         | <br>んで         | 休む<br>飛ぶ<br>死ぬ | 休==んで==<br>飛==んで==<br>死==んで== | やすんで<br>とんで<br>しんで  |
-| く                   | いて             | 歩く             | 歩==いて==                       | あるいて                |
-| ぐ                   | いで             | 泳ぐ             | 泳==いで==                       | およいで                |
-| す                   | して             | 話す             | 話==して==                       | はなして                |
-| **Irregular Verbs** |                |                |                               |                     |
-|                     |                | する             | し==て==                        |                     |
-|                     |                | 行く             | 行==って==                       | いって                 |
-|                     |                | 来る             | 来==て==                        | きて                  |
-
-### Adjectives and nouns
-
-| Form                 | Word  | Word Te-Form |
-| -------------------- | ----- | ------------ |
-| **いA** + ~~い~~ く + て | おもしろい | おもしろ==くて==   |
-| **なA** + で           | しずか   | しずか==で==     |
-| **N** + で            | 猫     | 猫==で==       |
-
-### Song
-
-A common way to remember this form is by a song. Here is one sung by Hatsune Miku.
-
-![Te Song](https://www.youtube.com/watch?v=Cj-P-nEPoe0)
-
-| Ending | Te-Form |
-| ------ | ------- |
-| う・つ・る  | って      |
-| む・ぶ・ぬ  | んで      |
-| く      | いて      |
-| ぐ      | いで      |
-| いく     | いって     |
-| くる     | きて      |
-| する     | して      |
-| す      | して      |
-
-## Basic functions
-
-### Connection
-
-The most basic function of the Te-Form: form connection between **verbs**.
-
-> [!info] Example
-> 食べ==て=={寝|ね}る。
-> To eat, then sleep.
-
-This also works with **いA**, **なA**, and **nouns**.
-
-> [!info] Example
-> あの{自転車|じてんしゃ}は{便利|べんり}==で=={軽|かる}い。
-> That bicycle is useful and light.
-
-### Reasons
-
-Used primarily for reasons beyond control of the speaker.
-
-> [!info] Example
-> 大雨==で==バスが止まりました。
-> The bus stopped with rain. (the reason is the rain)
-
-### Manners
-
-Highlights something being used, whether a tool, a circumstance, a situation, etc.
-
-> [!info] Examples
-> 私はご{飯|はん}を{急|いそ}い==で==食べる。
-> I eat food in a hurry.
-> 
-> ハサミ==で=={野菜|やさい}を{切|き}ります。
-> I cut my vegetables using scissors.
-
-## Sequence and non-sequence
-
-Only for **verbs**.
-
-### て sequence
-
-Used to list a sequence of events that happen one after another. Must be used for ordered sequence of what is being said!
-
-> [!info] Example
-> パンを買==って==、食べた。
-> I bought some bread, then ate it.
-
-### て non-sequence
-
-The particle can also contrast things that have some sort of relationship. It can mean something like "and" or "while", but is not really similar to "but": it always has the same weight in the sentence, as opposed to expressions like けど・のに, etc.
-
-> [!info] Examples
-> 朝は雨が{降|ふ}==って=={夕方|ゆう|がた}は{晴|は}れた。
-> It rained this morning, **and** then it cleared up in the afternoon. (there is no particular emphasis on either event).
->
-> 朝は雨が降った==けど==夕方は晴れた。
-> It rained this morning, **but then** it cleared up in the afternoon. (there is emphasis on the fact that it stopped raining).
-
-### てから
-
-Used to say that something will happen after something else : "after doing (A), (B)".
-Only for **verbs**.
-
-> [!info] Example
-> {洗濯|せん|たく}をし==てから==、出かける。
-> After doing the laundry, I will go out.
-
-⚠ Simple present (るから) and past (たから) have a meaning closer to "because" or "since".
-
-## States
-
-### ている form
-
-| Plain | Polite |
-| ----- | ------ |
-| ている   | ています   |
-| てる    | てます    |
-
-ている is often shortened to てる. This applies to all tenses, including てる, てて, てた, and even てます.
-Only for **verbs**.
-
-Sometimes ている can become しとる (like in manga).
-
-#### 1/ State of existence: is being done
-
-Used to convey a constant state of the verb being done, executed, etc. It is continuing to exist in a specific state.
-
-> [!info] Example
->今ラーメンを食べ==ています==。
->I am eating ramen now.
-
-#### 2/ State of existence: has been done
-
-Expresses "existing in a of state of having been done".
-In English, a different tense would have been used, but in Japanese it is also Te-form.
-
-> [!info] Examples
-> お前はもう死==んでいる==。
-> You are already dead.
-> 
-> クラスは始ま==っている==。
-> The class has already started. (existing in the state of having started)
-> 
-> お母さんは今買い物に行==っています==。
-> My mom went out to go shopping. (existing in the state of having gone)
-> 
-> 先生がめちゃ{怒|おこ}==っている==。
-> My teacher is very angry. (existing in the state of having gotten angry)
-
-Then, how to differentiate from the past form? Think about if the action can happen twice. For example, something cannot start twice, so it will use ている. The same applies for dying. This will not work for all verbs, but for the majority.
-
-> [!info] Example
-> ピアノが{落|お}ち==ている==。
-> The piano has fallen. (existing in the state of having fallen)
-> Something has fallen and is already on the ground, so it cannot fall again. ている will be used.
-
-#### 3/ State of existence: frequent and repeated action
-
-Used for the repetition of common activities. They are not continuing per se, but are occurring at such a frequency that they are considered to be continuous.
-For example: going to work, having a hobby, doing sports, etc.
-
-You can see it as "continuing to exist in a specific state".
-Expression of time are often used with this meaning.
-
-> [!info] Examples
-> 私は毎日ギターを{弾|ひ}い==ている==。
-> I play my guitar everyday (hobby).
-> 
-> {毎晩|まい|ばん}９時に{寝|ね}==ている==。
-> I sleep at 9 every night (habit).
-> 
-> {彼|かれ}は学校で{働|はたら}い==ている==。
-> He works at a school (regular activity).
-
-### ていた・ていました
-
-Means that something was happening, someone was doing something. If an object has changed state and is still in the state, it can also be used, for example a broken window.
-Only for **verbs**.
-
-ていた can be shortened to てた, and ていました to てました.
-
-> [!info] Example
-> {勉強|べんきょう}をし==ていた==けど、今は{休|やす}んでいる。
-> I was studying but am taking a break right now.
-
-### てある
-
-Shares with ている the meaning of being in an ongoing state, meaning that something has been done. It is also similar to a simple past form. However, the nuance is that this form is only used with transitive verbs on inanimate objects, meaning either:
-* the action has been done intentionally (focuses on a person's intention),
-* the focus is the resulting state of the action.
-
-> [!info] Examples
-> 明日の{弁当|べん|とう}はもう作==ってある==。
-> Tomorrow's lunch has already been prepared.
-> 
-> ドアが{開|あ}け==てある==。
-> The door has been left open (intentionally).
-
-Only for **transitive verbs**.
-
-### ておく
-
-Means to do something in advance, to complete something in preparation for something.
-If used in past form ておいた, means that the completed action was in preparation for the current situation.
-Only for **verbs**.
-
-Can be shortened as とく.
-
-> [!info] Example
-> メロンパンを買==っておく==。
-> I'll buy a melon pan (in preparation for a something, for example a picnic).
-
-### まだ～ていません
-
-This means "still have not done something". 
-Only for **verbs**.
-
-> [!info] Example
-> このゲームは==まだ==し==ていない==。
-> I haven't played this game yet.

content/2- Conjugation/3- TeF - manner - give receive.md

@@ -1,118 +0,0 @@
-# 3- Te-Form - manner of doing - give & receive
-
-## Manner of doing
-
-### てしまう
-
-<div class="usage">
-<div>
-	<p><span class="box">Vて</span> + しまう</p>
-	<p><span class="box">V<strike>て</strike></span> + ちゃう</p>
-	<p><span class="box">V<strike>で</strike></span> + じゃう</p>
-</div>
-</div>
-
-This means "by accident, unfortunately" or "completely".
-Only for **verbs**.
-
-> [!info] Examples
-> {宿題|しゅく|だい}もうや==ってしまいました==。
-> I've already finished my homework.
-> 
-> もう{全部|ぜん|ぶ}食べ==ちゃった==。。。
-> I've already eaten everything...
-
-### てみる
-
-Used to express the meaning of trying something, usually something new.
-Can also be used to suggest to someone to try something.
-Used in past tense, it implies a successful attempt.
-Only for **verbs**.
-
-> [!info] Example
-> これを食べ==てみる==か？
-> Do you want to try this food?
-
-### ていく・てくる
-
-ていく combines the Te-form with the verb 行く.
-てくる combines the Te-form with the verb 来る. 
-Both can be used when representing time or a physical place. Kanji and hiragana can be used, and they can be conjugated.
-Only for **verbs**.
-
-The first meaning is the following:
-* ていく means to go and do something.
-* てくる means to do and come back.
-
-> [!info] Examples
-> 家で食べ==ていく==か？
-> Want to go and eat at my home?
-> 
-> {晩御飯|ばんごはん}を買==ってきた==。
-> I brought tonight's dinner. (bought and came with).
-
-The second meaning is:
-* ていく means to start doing something with your own agency.
-* てくる on the contrary, is when something comes to the listener without agency from them.
-
-> [!info] Examples
-> 彼は駅まで歩い==ていきます==。
-> He walk to the station.
-> 
-> 雨が{降|ふ}==ってきた==。
-> It started raining.
-
-## Give and receive
-
-Extends the common forms of あげる, くれる, and もらう, but what is received or given is now a verb, instead of a noun.
-
-### てあげる
-
-Expresses that someone is doing or did something for someone else.
-The person that received the favor is followed by the に particle.
-Only for **verbs**.
-
-> [!info] Example
-> 母にケーキを買==ってあげた==。
-> I bought a cake for my mother.
-> 
-
-### てくれる
-
-Used to ask a favor from someone or to say that something was done to the speaker.
-The person that received the favor (usually oneself and thus omitted) is followed by the に particle.
-Only for **verbs**.
-
-> [!info] Example
-> {友達|とも|だち}がギターを{教|おし}え==てくれる==。
-> My friend will teach me the guitar.
-
-#### てくれてありがとう
-
-This form expresses gratitude for something that benefited the speaker. It is not used for something expected.
-Only for **verbs**.
-
-> [!info] Example
-> 今日来==てくれてありがとう==！
-> Thank you for coming today!
-
-### てもらう
-
-This form expresses gratitude for a favor that the recipient generally requested for, or where gratitude is the focus.
-Only for **verbs**.
-
-> [!info] Example
-> {友達|とも|だち}が手伝==ってもらった==。
-> My friend helped me (and I owe him / because I asked him and I am grateful)
-
-### てくれない・てもらえない
-
-Used as a mean to ask for a favor like "would you, could you?". Used in a similar form to じゃないか.
-Only for **verbs**.
-
-> [!info] Example
-> {電気|でん|き}をつけ==てもらえない==か。
-> Could you please turn on the lights?
-> 
-> 電気をつけ==ないでもらえない==か。
-> Could you please turn off the light?

content/2- Conjugation/4- TeF - even if.md

@@ -1,69 +0,0 @@
-# 4- Te-Form - even if
-
-For **verbs**, **adjectives** and **nouns**.
-
-## Even if: ても・でも
-
-Works by adding も to the Te-Form.
-
-> [!info] Example
-> 安==くても==、買いません。
-> Even if it's cheap, I won't buy it.
-> 
-> 好き==でも==、買えなかった。
-> Even if I liked it, I didn't bought it.
-
-### てもいい
-
-Means that something is "alright". Frequently used for questions.
-
-> [!info] Example
-> ここに{座|すわ}==ってもいい==？
-> Is it okay if I sit here?
-> 
-> {冷|つめ}たい==でもいい==。
-> It's okay even if it's cold.
-
-### ても～なくても
-
-Means "whether or not". A form a bit strange, where the verb is repeated two times in the following manner: VてもVなくても.
-
-> [!info] Example
-> 食べ==ても==食べ==なくても==、{構|かま}いません。
-> It doesn't matter whether you eat it orb not.
-
-### ても構わない・てもかまわない
-
-Means that it doesn't matter or that the speaker doesn't mind.
-
-> [!info] Example
-> 雨が{降|ふ}==っても構わない==。
-> I don't mind if it rains.
-
-### ても始まらない・てもはじまらない
-
-Means that even if you do it, it will never start: that it's no use.
-Only for **verbs**.
-
-> [!info] Example
-> この時間に会==っても始まらない==。
-> There's no point meeting at this time of the day.
-
-### いくら～ても・どんなに～ても
-
-Means "no matter how much".
-
-> [!info] Example
-> ==いくら==好き==でも==、買えません。
-> No matter how much you like it, I won't buy it for you.
-> 
-> ==どんなに==高==くても==、買います。
-> No matter how expensive, I'll buy it.
-
-### たとえ〜ても
-
-Used to make a supposition. Would translate to something like "even if... is the case".
-
-> [!info] Example
-> ==たとえ=={新幹線|しん|かん|せん}==でも==、１時間かかる。
-> Even if you take the Shinkansen, it will take one hour.

content/index.md

@@ -1,48 +0,0 @@
-# Japanese Grammar
-
-Welcome to my Japanese Grammar project!
-
-## Goal
-
-The goal of this website is to be a synthesis of useful resources for my Japanese learning adventure. I want to have grammar points next to each other, independently of any "difficulty level", set up in a logical and consistent form. I don't want to have to open 5 pages to compare information, and I don't want a deep dive into a notion. The goal is to be a reminder of the things I learn, rather than a way to learn. I want a few examples to grasp it, but I do not want to have ten of the same kind. And nothing quite fits for me!
-
-## Sources
-
-Of course, since I'm _learning_ the language, I need to borrow what I write from different sources. So this website uses data from the websites listed here. I don't want any recognition of what is here! It's mostly a compilation of what people who are way better in this language have made before.
-
-* [Bunpro](https://bunpro.jp/grammar_points)
-* [JLPT Sensei](https://jlptsensei.com/#jlpt-grammar-lists)
-* [Maggie Sensei](https://maggiesensei.com/)
-* [Try! Series of books](https://2024.ask-books.com/tag/try/)
-* [Hedgehog Japanese](https://hedgehog-japanese.com/category/grammar/)
-* [Wasabi](https://www.wasabi-jpn.com/category/japanese-grammar/)
-* [Japanese StackExchange](https://japanese.stackexchange.com/)
-* [Guide du Japonais](https://guidedujaponais.fr/)
-
-## Other useful resources
-
-In addition to those I cited, here are other resources I find useful.
-
-### Kanjis
-
-* [Remembering the Kanji (RTK)](https://en.wikipedia.org/wiki/Remembering_the_Kanji_and_Remembering_the_Hanzi), a kanji learning method
-* [Kanji Koohii](https://kanji.koohii.com/), a website using the RTK method and spaced repetition
-* [Remember the JLPT](https://git.marchal.dev/keb/remember-the-JLPT), a tool I made to learn kanjis by JLPT levels
-
-### Reading
-
-* [Sakubun](https://sakubun.xyz/)
-* [NHK News Web Easy](https://www3.nhk.or.jp/news/easy/)
-
-### Grammar
-
-* [jtest4you](https://japanesetest4you.com/)
-* [Japanese Conjugation Drill](https://drill.marchal.dev)
-
-### Vocabulary
-
-* [Jisho](https://jisho.org/), an online dictionary
-
-## Any errors?
-
-If you find any error, please do contact me! You can find my website in the footer of any page of this website. Thanks!

custom/build-run.sh

@@ -1,2 +0,0 @@
-docker build -t quartz-jpg .
-cd custom && docker-compose up -d --force-recreate

custom/convert-furigana/LICENSE

@@ -1,9 +0,0 @@
-MIT License
-
-Copyright (c) 2024 keb
-
-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.

custom/convert-furigana/README.md

@@ -1,43 +0,0 @@
-# convert-furigana
-
-## What is it?
-
-There are a few extensions that add [furigana](https://en.wikipedia.org/wiki/Furigana) support to Markdown. I use [Obsidian](https://obsidian.md/), and therefore its furigana extension: [obsidian-markdown-furigana](https://github.com/steven-kraft/obsidian-markdown-furigana). It works well, but by nature is limited by being used within Obsidian.
-
-For that purpose, this python script converts this specific syntax to common, all-platforms HTML ruby tags.
-
-## Process
-
-This specific extension syntax is as following:
-```
-{漢字|かんじ}
-{漢字|かん|じ}
-```
-
-When processed by this script, the result is:
-```
-<ruby>漢字<rt>かんじ</rt></ruby>
-<ruby>漢<rt>かん</rt>字<rt>じ</rt></ruby>
-```
-
-Which leads visually from, by default markdown standards:
-
-> {漢字|かんじ}
->
-> {漢字|かん|じ}
-
-to common HTML ruby syntax:
-
-> <ruby>漢字<rt>かんじ</rt></ruby>
->
-> <ruby>漢<rt>かん</rt>字<rt>じ</rt></ruby>
-
-## Limitations
-
-This has been made for my personal use, which is only kanjis with kanas as furigana. The regexp used do not recognize other inputs. But you can modify them easily for your use if needed.
-
-## Usage
-
-Usage: `python3 convert-furigana.py [root folder]`
-
-Note: Please be careful, this software applies modifications recursively!

custom/convert-furigana/examples/furigana1.md

@@ -1,6 +0,0 @@
-{僕|ボク}の{筆記|ひっ|き}
-
-### ～によるN
-
-* テレビによる{報道|ほうどう}
-* この{地震|じ|しん}による{津波|つ|なみ}の{心配|しんぱい}はありません。

custom/convert-furigana/examples/subfolder/furigana2.md

@@ -1,7 +0,0 @@
-## ふりがなテスト
-
-{漢字|かんじ}
-
-{漢字|かん|じ}
-
-{漢字|カン|ジ}

custom/convert-furigana/program/convert-furigana.py

@@ -1,71 +0,0 @@
-import sys
-import os
-from glob import glob
-import re
-
-### Patterns ###
-
-# https://www.reddit.com/r/learnpython/comments/h0tsaa/regex_expression_for_japanese_extracting/
-re_brace = '{(.+?)}'
-re_kanji = '([㐀-䶵一-鿋豈-頻]+)'
-re_kana = '([ぁ-ゟ゠-ヿ]+)'
-
-### Open file ###
-
-def open_file(filename):
-    with open(filename, 'r', encoding='utf-8-sig') as file:
-        filedata = file.read()
-        return filedata
-
-### Replace ###
-
-def write_ruby_simple(kanji, kana):
-    return f"<ruby>{kanji}<rt>{kana}</rt></ruby>"
-
-def write_ruby_multiple(kanji, kanas):
-    result = f"<ruby>"
-    for idx, kana in enumerate(kanas):
-        result += f"{kanji[idx]}"
-        result += f"<rt>{kana}</rt>"
-    result += f"</ruby>"
-    return result
-
-def convert_to_ruby(content):
-    kanji = re.search(re_kanji, content.group())
-    kana = re.findall(re_kana, content.group())
-
-    if (len(kana) == 1):
-        return write_ruby_simple(kanji.group(), kana[0])
-    else:
-        return write_ruby_multiple(kanji.group(), kana)
-
-def convert_pattern(text):
-    res_text = re.sub(re_brace, convert_to_ruby, text)
-    return res_text
-
-### Write to file ###
-
-def write_file(filename, text):
-    with open(filename, 'w', encoding='utf-8-sig') as file:
-        file.write(text)
-
-
-### Execution ###
-
-file_list = []
-
-if len(sys.argv) > 1:
-    path = sys.argv[1]
-    for filename in glob(path + "/**/*.md", recursive=True):
-        if (os.path.isfile(filename)):
-            file_list.append(filename)
-else:
-    print(f"Usage: python3 {sys.argv[0]} [root folder]")
-    print(f"Note: Please be careful, this software applies modifications recursively!")
-
-for filename in file_list:
-    print(f"Found file {filename}, processing...", end='')
-    data = open_file(filename)
-    text = convert_pattern(data)
-    write_file(filename, text)
-    print(f" done!")

custom/convert-usage/LICENSE

@@ -1,9 +0,0 @@
-MIT License
-
-Copyright (c) 2024 keb
-
-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.

custom/convert-usage/README.md

@@ -1,17 +0,0 @@
-# convert-usage
-
-## Obsidian snippet
-
-For my Japanese Grammar (JPG) project, I have created a style for explanation on the usage of certain grammar points. There is no simple way to make it in Markdown, so I tried to make it with the least amount of HTML possible. You can find it in `examples/sample.md`. However, for it to work, you have to import a custom [CSS snippet](https://help.obsidian.md/Extending+Obsidian/CSS+snippets) to Obsidian, which is located in `obsidian-snippet/usage.css`. But using it, you will have this kind of result:
-
-![Obsidian screenshot](./screenshot.png)
-
-## convert-usage.py
-
-In my Quartz rendering of my markdown data, I want this kind of data to be in a callout. However, it is not possible to combine HTML and Markdown in Obsidian. For that purpose, this script encapsulates it directly in HTML. To make it both compatible in Obsidian and Quartz, and to be still easy to write, it's done with this python script. This is probably super specific and will not be of use for anybody except me!
-
-## Usage
-
-Usage: `python3 convert-usage.py [root folder]`
-
-Note: Please be careful, this software applies modifications recursively!

custom/convert-usage/examples/sample.md

@@ -1,33 +0,0 @@
-# test file
-
-## Lorem ipsum
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Mauris massa eros, feugiat eu dapibus nec, fermentum vel ex. Nulla malesuada luctus pretium. Phasellus ac felis ut nisi lacinia malesuada nec vel odio. Donec tincidunt tincidunt lorem vel tempus. Nullam sed efficitur ligula, a porttitor nibh. Praesent justo dui, venenatis ac mi non, laoreet consequat libero. Aenean ut molestie mauris. Proin mattis volutpat ligula eget tincidunt. Fusce ex eros, condimentum consectetur efficitur vitae, euismod at justo.
-
-**Usage**
-
-<div class="usage">
-<div class="left">
-	<p><span class="box">item1</span></p>
-	<p><span class="box">item2</span></p>
-	<p><span class="box">item3</span></p>
-	<p><span class="box">item4</span></p>
-</div>
-	<p class="right">+ final</p>
-</div>
-
-## Phasellus tristique
-
-Phasellus tristique rutrum enim. Integer vitae ex at turpis convallis posuere nec nec erat. Cras finibus erat mauris. Suspendisse id diam at sapien luctus faucibus. Pellentesque fermentum auctor libero, ut porta orci porttitor quis. In varius at sem sed ultricies. Mauris iaculis convallis erat, congue tincidunt turpis luctus vitae.
-
-**Usage**
-
-<div class="usage">
-<div class="left">
-	<p><span class="box">アイテム１</span></p>
-	<p><span class="box">アイテム２</span></p>
-	<p><span class="box">アイテム３</span></p>
-	<p><span class="box">アイテム４</span></p>
-</div>
-	<p class="right">＋ ファイナル</p>
-</div>

custom/convert-usage/examples/sample2.md

@@ -1,23 +0,0 @@
-# test file
-
-## Lorem ipsum
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Mauris massa eros, feugiat eu dapibus nec, fermentum vel ex. Nulla malesuada luctus pretium. Phasellus ac felis ut nisi lacinia malesuada nec vel odio. Donec tincidunt tincidunt lorem vel tempus. Nullam sed efficitur ligula, a porttitor nibh. Praesent justo dui, venenatis ac mi non, laoreet consequat libero. Aenean ut molestie mauris. Proin mattis volutpat ligula eget tincidunt. Fusce ex eros, condimentum consectetur efficitur vitae, euismod at justo.
-
-**Usage**
-
-<div class="usage">
-<div class="left">
-	<p><span class="box">item1</span></p>
-	<p><span class="box">item2</span></p>
-	<p><span class="box">item3</span></p>
-	<p><span class="box">item4</span></p>
-</div>
-	<p class="right">+ final</p>
-</div>
-
-## Callout
-
-> [!info] Example
-> Callout example
-> Careful with BS4 encoding some characters

custom/convert-usage/obsidian-snippets/usage.css

@@ -1,35 +0,0 @@
-.box {
-    display: inline-block;
-    width: fit-content;
-    margin: 0.2rem;
-    padding: 0.2rem 0.3rem 0.2rem 0.3rem;
-
-    border: 1px solid black;
-    border-radius: 0.5rem;
-}
-
-.usage {
-    display:flex;
-    flex-direction: row;
-    align-items: center;
-}
-
-.left {
-    padding-right: 1.7rem;
-
-    background-image: linear-gradient(black, black), linear-gradient(black, black);
-    background-repeat: no-repeat;
-    background-size: 8px 2px;
-    background-position: top right, bottom right;
-
-    border-right: solid black;
-    border-width: 0 2px;
-}
-
-.left p {
-    margin:0;
-}
-
-.right {
-    padding-left: 1rem;
-}

custom/convert-usage/program/convert-usage.py

@@ -1,66 +0,0 @@
-import sys
-import os
-from glob import glob
-from bs4 import BeautifulSoup
-import re
-
-### Patterns ###
-
-re_usage = r'(^\*\*Usage\*\*$\n\n)'
-callout_title_html = '''
-    <div class="callout-title">
-        <div class="callout-icon"></div>
-        <div class="callout-title-inner"><p>Usage</p></div>
-    </div>'''
-
-### Open file ###
-
-def open_file(filename):
-    with open(filename, 'r', encoding='utf-8-sig') as file:
-        filedata = file.read()
-        return filedata
-
-### Write to file ###
-
-def write_file(filename, text):
-    with open(filename, 'w', encoding='utf-8-sig') as file:
-        file.write(text)
-
-### Replace ###
-
-def convert_pattern(text):
-    text, success = re.subn(re_usage, '', text, flags=re.MULTILINE)
-    if (success == 0):
-        return text
-
-    soup = BeautifulSoup(text, features="html.parser")
-
-    for tag in soup.find_all('div', {"class": "usage"}):
-        new_blockquote = soup.new_tag("blockquote", **{"class": "callout notes", "data-callout": "notes"})
-        tag.wrap(new_blockquote)
-
-        calloutTitle = BeautifulSoup(callout_title_html, features="html.parser")
-        tag.insert_before(calloutTitle)
-
-    return (soup.decode(False, formatter=None))
-
-
-### Execution ###
-
-file_list = []
-
-if len(sys.argv) > 1:
-    path = sys.argv[1]
-    for filename in glob(path + "/**/*.md", recursive=True):
-        if (os.path.isfile(filename)):
-            file_list.append(filename)
-else:
-    print(f"Usage: python3 {sys.argv[0]} [root folder]")
-    print(f"Note: Please be careful, this software applies modifications recursively!")
-
-for filename in file_list:
-    print(f"Found file {filename}, processing...", end='')
-    data = open_file(filename)
-    text = convert_pattern(data)
-    write_file(filename, text)
-    print(f" done!")

custom/docker-compose.yml

@@ -1,14 +0,0 @@
-version: '3.4'
-
-services:
-  quartz:
-    image: quartz-jpg
-    build:
-      context: .
-      dockerfile: Dockerfile
-    environment:
-      NODE_ENV: production
-    container_name: quartz-jpg-container
-    restart: always
-    ports:
-      - 8080:8080

custom/update-repos.sh

@@ -1,8 +0,0 @@
-git fetch convert-furigana main
-git subtree pull --prefix custom/convert-furigana convert-furigana main --squash
-
-git fetch convert-usage main
-git subtree pull --prefix custom/convert-usage convert-usage main --squash
-
-git fetch content main
-git subtree pull --prefix content content main --squash

docs/advanced/creating components.md

@@ -129,11 +129,11 @@ export default (() => {
     return <button id="btn">Click me</button>
   }
 
-  YourComponent.beforeDOM = `
+  YourComponent.beforeDOMLoaded = `
   console.log("hello from before the page loads!")
   `
 
-  YourComponent.afterDOM = `
+  YourComponent.afterDOMLoaded = `
   document.getElementById('btn').onclick = () => {
     alert('button clicked!')
   }
@@ -161,6 +161,18 @@ document.addEventListener("nav", () => {
 })
 ```
 
+You can also add the equivalent of a `beforeunload` event for [[SPA Routing]] via the `prenav` event.
+
+```ts
+document.addEventListener("prenav", () => {
+  // executed after an SPA navigation is triggered but
+  // before the page is replaced
+  // one usage pattern is to store things in sessionStorage
+  // in the prenav and then conditionally load then in the consequent
+  // nav
+})
+```
+
 It is best practice to track any event handlers via `window.addCleanup` to prevent memory leaks.
 This will get called on page navigation.
 
@@ -180,7 +192,7 @@ export default (() => {
     return <button id="btn">Click me</button>
   }
 
-  YourComponent.afterDOM = script
+  YourComponent.afterDOMLoaded = script
   return YourComponent
 }) satisfies QuartzComponentConstructor
 ```

docs/advanced/making plugins.md

@@ -25,10 +25,11 @@ The following sections will go into detail for what methods can be implemented f
 - `BuildCtx` is defined in `quartz/ctx.ts`. It consists of
   - `argv`: The command line arguments passed to the Quartz [[build]] command
   - `cfg`: The full Quartz [[configuration]]
-  - `allSlugs`: a list of all the valid content slugs (see [[paths]] for more information on what a `ServerSlug` is)
+  - `allSlugs`: a list of all the valid content slugs (see [[paths]] for more information on what a slug is)
 - `StaticResources` is defined in `quartz/resources.tsx`. It consists of
-  - `css`: a list of URLs for stylesheets that should be loaded
+  - `css`: a list of CSS style definitions that should be loaded. A CSS style is described with the `CSSResource` type which is also defined in `quartz/resources.tsx`. It accepts either a source URL or the inline content of the stylesheet.
   - `js`: a list of scripts that should be loaded. A script is described with the `JSResource` type which is also defined in `quartz/resources.tsx`. It allows you to define a load time (either before or after the DOM has been loaded), whether it should be a module, and either the source URL or the inline content of the script.
+  - `additionalHead`: a list of JSX elements or functions that return JSX elements to be added to the `<head>` tag of the page. Functions receive the page's data as an argument and can conditionally render elements.
 
 ## Transformers
 
@@ -37,7 +38,7 @@ Transformers **map** over content, taking a Markdown file and outputting modifie
 ```ts
 export type QuartzTransformerPluginInstance = {
   name: string
-  textTransform?: (ctx: BuildCtx, src: string | Buffer) => string | Buffer
+  textTransform?: (ctx: BuildCtx, src: string) => string
   markdownPlugins?: (ctx: BuildCtx) => PluggableList
   htmlPlugins?: (ctx: BuildCtx) => PluggableList
   externalResources?: (ctx: BuildCtx) => Partial<StaticResources>
@@ -85,8 +86,10 @@ export const Latex: QuartzTransformerPlugin<Options> = (opts?: Options) => {
       if (engine === "katex") {
         return {
           css: [
+            {
               // base css
-            "https://cdnjs.cloudflare.com/ajax/libs/KaTeX/0.16.9/katex.min.css",
+              content: "https://cdnjs.cloudflare.com/ajax/libs/KaTeX/0.16.9/katex.min.css",
+            },
           ],
           js: [
             {
@@ -97,8 +100,6 @@ export const Latex: QuartzTransformerPlugin<Options> = (opts?: Options) => {
             },
           ],
         }
-      } else {
-        return {}
       }
     },
   }
@@ -220,12 +221,26 @@ export type QuartzEmitterPlugin<Options extends OptionType = undefined> = (
 
 export type QuartzEmitterPluginInstance = {
   name: string
-  emit(ctx: BuildCtx, content: ProcessedContent[], resources: StaticResources): Promise<FilePath[]>
+  emit(
+    ctx: BuildCtx,
+    content: ProcessedContent[],
+    resources: StaticResources,
+  ): Promise<FilePath[]> | AsyncGenerator<FilePath>
+  partialEmit?(
+    ctx: BuildCtx,
+    content: ProcessedContent[],
+    resources: StaticResources,
+    changeEvents: ChangeEvent[],
+  ): Promise<FilePath[]> | AsyncGenerator<FilePath> | null
   getQuartzComponents(ctx: BuildCtx): QuartzComponent[]
 }
 ```
 
-An emitter plugin must define a `name` field, an `emit` function, and a `getQuartzComponents` function. `emit` is responsible for looking at all the parsed and filtered content and then appropriately creating files and returning a list of paths to files the plugin created.
+An emitter plugin must define a `name` field, an `emit` function, and a `getQuartzComponents` function. It can optionally implement a `partialEmit` function for incremental builds.
+
+- `emit` is responsible for looking at all the parsed and filtered content and then appropriately creating files and returning a list of paths to files the plugin created.
+- `partialEmit` is an optional function that enables incremental builds. It receives information about which files have changed (`changeEvents`) and can selectively rebuild only the necessary files. This is useful for optimizing build times in development mode. If `partialEmit` is undefined, it will default to the `emit` function.
+- `getQuartzComponents` declares which Quartz components the emitter uses to construct its pages.
 
 Creating new files can be done via regular Node [fs module](https://nodejs.org/api/fs.html) (i.e. `fs.cp` or `fs.writeFile`) or via the `write` function in `quartz/plugins/emitters/helpers.ts` if you are creating files that contain text. `write` has the following signature:
 
@@ -234,7 +249,7 @@ export type WriteOptions = (data: {
   // the build context
   ctx: BuildCtx
   // the name of the file to emit (not including the file extension)
-  slug: ServerSlug
+  slug: FullSlug
   // the file extension
   ext: `.${string}` | ""
   // the file content to add
@@ -260,11 +275,11 @@ export const ContentPage: QuartzEmitterPlugin = () => {
     ...defaultContentPageLayout,
     pageBody: Content(),
   }
-  const { head, header, beforeBody, pageBody, left, right, footer } = layout
+  const { head, header, beforeBody, pageBody, afterBody, left, right, footer } = layout
   return {
     name: "ContentPage",
     getQuartzComponents() {
-      return [head, ...header, ...beforeBody, pageBody, ...left, ...right, footer]
+      return [head, ...header, ...beforeBody, pageBody, ...afterBody, ...left, ...right, footer]
     },
     async emit(ctx, content, resources, emit): Promise<FilePath[]> {
       const cfg = ctx.cfg.configuration
@@ -272,7 +287,7 @@ export const ContentPage: QuartzEmitterPlugin = () => {
       const allFiles = content.map((c) => c[1].data)
       for (const [tree, file] of content) {
         const slug = canonicalizeServer(file.data.slug!)
-        const externalResources = pageResources(slug, resources)
+        const externalResources = pageResources(slug, file.data, resources)
         const componentData: QuartzComponentProps = {
           fileData: file.data,
           externalResources,

docs/advanced/paths.md

@@ -48,4 +48,4 @@ Here are the main types of slugs with a rough description of each type of path:
 - `SimpleSlug`: cannot be relative and shouldn't have `/index` as an ending or a file extension. It _can_ however have a trailing slash to indicate a folder path.
 - `RelativeURL`: must start with `.` or `..` to indicate it's a relative URL. Shouldn't have `/index` as an ending or a file extension but can contain a trailing slash.
 
-To get a clearer picture of how these relate to each other, take a look at the path tests in `quartz/path.test.ts`.
+To get a clearer picture of how these relate to each other, take a look at the path tests in `quartz/util/path.test.ts`.

docs/authoring content.md

@@ -29,11 +29,14 @@ Some common frontmatter fields that are natively supported by Quartz:
 
 - `title`: Title of the page. If it isn't provided, Quartz will use the name of the file as the title.
 - `description`: Description of the page used for link previews.
+- `permalink`: A custom URL for the page that will remain constant even if the path to the file changes.
 - `aliases`: Other names for this note. This is a list of strings.
 - `tags`: Tags for this note.
 - `draft`: Whether to publish the page or not. This is one way to make [[private pages|pages private]] in Quartz.
 - `date`: A string representing the day the note was published. Normally uses `YYYY-MM-DD` format.
 
+See [[Frontmatter]] for a complete list of frontmatter.
+
 ## Syncing your Content
 
 When your Quartz is at a point you're happy with, you can save your changes to GitHub.

docs/build.md

@@ -21,3 +21,7 @@ This will start a local web server to run your Quartz on your computer. Open a w
 > - `--serve`: run a local hot-reloading server to preview your Quartz
 > - `--port`: what port to run the local preview server on
 > - `--concurrency`: how many threads to use to parse notes
+
+> [!warning] Not to be used for production
+> Serve mode is intended for local previews only.
+> For production workloads, see the page on [[hosting]].

docs/configuration.md

@@ -21,16 +21,19 @@ const config: QuartzConfig = {
 This part of the configuration concerns anything that can affect the whole site. The following is a list breaking down all the things you can configure:
 
 - `pageTitle`: title of the site. This is also used when generating the [[RSS Feed]] for your site.
+- `pageTitleSuffix`: a string added to the end of the page title. This only applies to the browser tab title, not the title shown at the top of the page.
 - `enableSPA`: whether to enable [[SPA Routing]] on your site.
 - `enablePopovers`: whether to enable [[popover previews]] on your site.
 - `analytics`: what to use for analytics on your site. Values can be
   - `null`: don't use analytics;
   - `{ provider: 'google', tagId: '<your-google-tag>' }`: use Google Analytics;
-  - `{ provider: 'plausible' }` (managed) or `{ provider: 'plausible', host: '<your-plausible-host>' }` (self-hosted): use [Plausible](https://plausible.io/);
+  - `{ provider: 'plausible' }` (managed) or `{ provider: 'plausible', host: 'https://<your-plausible-host>' }` (self-hosted, make sure to include the `https://` protocol prefix): use [Plausible](https://plausible.io/);
   - `{ provider: 'umami', host: '<your-umami-host>', websiteId: '<your-umami-website-id>' }`: use [Umami](https://umami.is/);
   - `{ provider: 'goatcounter', websiteId: 'my-goatcounter-id' }` (managed) or `{ provider: 'goatcounter', websiteId: 'my-goatcounter-id', host: 'my-goatcounter-domain.com', scriptSrc: 'https://my-url.to/counter.js' }` (self-hosted) use [GoatCounter](https://goatcounter.com);
   - `{ provider: 'posthog', apiKey: '<your-posthog-project-apiKey>', host: '<your-posthog-host>' }`: use [Posthog](https://posthog.com/);
   - `{ provider: 'tinylytics', siteId: '<your-site-id>' }`: use [Tinylytics](https://tinylytics.app/);
+  - `{ provider: 'cabin' }` or `{ provider: 'cabin', host: 'https://cabin.example.com' }` (custom domain): use [Cabin](https://withcabin.com);
+  - `{provider: 'clarity', projectId: '<your-clarity-id-code' }`: use [Microsoft clarity](https://clarity.microsoft.com/). The project id can be found on top of the overview page.
 - `locale`: used for [[i18n]] and date formatting
 - `baseUrl`: this is used for sitemaps and RSS feeds that require an absolute URL to know where the canonical 'home' of your site lives. This is normally the deployed URL of your site (e.g. `quartz.jzhao.xyz` for this site). Do not include the protocol (i.e. `https://`) or any leading or trailing slashes.
   - This should also include the subpath if you are [[hosting]] on GitHub pages without a custom domain. For example, if my repository is `jackyzha0/quartz`, GitHub pages would deploy to `https://jackyzha0.github.io/quartz` and the `baseUrl` would be `jackyzha0.github.io/quartz`.
@@ -38,11 +41,12 @@ This part of the configuration concerns anything that can affect the whole site.
 - `ignorePatterns`: a list of [glob](<https://en.wikipedia.org/wiki/Glob_(programming)>) patterns that Quartz should ignore and not search through when looking for files inside the `content` folder. See [[private pages]] for more details.
 - `defaultDateType`: whether to use created, modified, or published as the default date to display on pages and page listings.
 - `theme`: configure how the site looks.
-  - `cdnCaching`: If `true` (default), use Google CDN to cache the fonts. This will generally will be faster. Disable (`false`) this if you want Quartz to download the fonts to be self-contained.
+  - `cdnCaching`: if `true` (default), use Google CDN to cache the fonts. This will generally be faster. Disable (`false`) this if you want Quartz to download the fonts to be self-contained.
   - `typography`: what fonts to use. Any font available on [Google Fonts](https://fonts.google.com/) works here.
-    - `header`: Font to use for headers
-    - `code`: Font for inline and block quotes.
-    - `body`: Font for everything
+    - `title`: font for the title of the site (optional, same as `header` by default)
+    - `header`: font to use for headers
+    - `code`: font for inline and block quotes
+    - `body`: font for everything
   - `colors`: controls the theming of the site.
     - `light`: page background
     - `lightgray`: borders
@@ -52,6 +56,7 @@ This part of the configuration concerns anything that can affect the whole site.
     - `secondary`: link colour, current [[graph view|graph]] node
     - `tertiary`: hover states and visited [[graph view|graph]] nodes
     - `highlight`: internal link background, highlighted text, [[syntax highlighting|highlighted lines of code]]
+    - `textHighlight`: markdown highlighted text background
 
 ## Plugins
 
@@ -99,8 +104,30 @@ transformers: [
 ]
 ```
 
-Some plugins are included by default in the[ `quartz.config.ts`](https://github.com/jackyzha0/quartz/blob/v4/quartz.config.ts), but there are more available.
+Some plugins are included by default in the [`quartz.config.ts`](https://github.com/jackyzha0/quartz/blob/v4/quartz.config.ts), but there are more available.
 
 You can see a list of all plugins and their configuration options [[tags/plugin|here]].
 
 If you'd like to make your own plugins, see the [[making plugins|making custom plugins]] guide.
+
+## Fonts
+
+Fonts can be specified as a `string` or a `FontSpecification`:
+
+```ts
+// string
+typography: {
+  header: "Schibsted Grotesk",
+  ...
+}
+
+// FontSpecification
+typography: {
+  header: {
+    name: "Schibsted Grotesk",
+    weights: [400, 700],
+    includeItalic: true,
+  },
+  ...
+}
+```

docs/features/Citations.md

@@ -0,0 +1,31 @@
+---
+title: Citations
+tags:
+  - feature/transformer
+---
+
+Quartz uses [rehype-citation](https://github.com/timlrx/rehype-citation) to support parsing of a BibTex bibliography file.
+
+Under the default configuration, a citation key `[@templeton2024scaling]` will be exported as `(Templeton et al., 2024)`.
+
+> [!example]- BibTex file
+>
+> ```bib title="bibliography.bib"
+> @article{templeton2024scaling,
+>   title={Scaling Monosemanticity: Extracting Interpretable Features from Claude 3 Sonnet},
+>   author={Templeton, Adly and Conerly, Tom and Marcus, Jonathan and Lindsey, Jack and Bricken, Trenton and Chen, Brian and Pearce, Adam and Citro, Craig and Ameisen, Emmanuel and Jones, Andy and Cunningham, Hoagy and Turner, Nicholas L and McDougall, Callum and MacDiarmid, Monte and Freeman, C. Daniel and Sumers, Theodore R. and Rees, Edward and Batson, Joshua and Jermyn, Adam and Carter, Shan and Olah, Chris and Henighan, Tom},
+>   year={2024},
+>   journal={Transformer Circuits Thread},
+>   url={https://transformer-circuits.pub/2024/scaling-monosemanticity/index.html}
+> }
+> ```
+
+> [!note] Behaviour of references
+>
+> By default, the references will be included at the end of the file. To control where the references to be included, uses `[^ref]`
+>
+> Refer to `rehype-citation` docs for more information.
+
+## Customization
+
+Citation parsing is a functionality of the [[plugins/Citations|Citation]] plugin. **This plugin is not enabled by default**. See the plugin page for customization options.

docs/features/Docker Support.md

@@ -3,5 +3,5 @@ Quartz comes shipped with a Docker image that will allow you to preview your Qua
 You can run the below one-liner to run Quartz in Docker.
 
 ```sh
-docker run --rm -itp 8080:8080 $(docker build -q .)
+docker run --rm -itp 8080:8080 -p 3001:3001 -v ./content:/usr/src/app/content $(docker build -q .)
 ```

docs/features/RSS Feed.md

@@ -1,5 +1,10 @@
 Quartz emits an RSS feed for all the content on your site by generating an `index.xml` file that RSS readers can subscribe to. Because of the RSS spec, this requires the `baseUrl` property in your [[configuration]] to be set properly for RSS readers to pick it up properly.
 
+> [!info]
+> After deploying, the generated RSS link will be available at `https://${baseUrl}/index.xml` by default.
+>
+> The `index.xml` path can be customized by passing the `rssSlug` option to the [[ContentIndex]] plugin.
+
 ## Configuration
 
 This functionality is provided by the [[ContentIndex]] plugin. See the plugin page for customization options.

docs/features/Roam Research compatibility.md

@@ -0,0 +1,28 @@
+---
+title: "Roam Research Compatibility"
+tags:
+  - feature/transformer
+---
+
+[Roam Research](https://roamresearch.com) is a note-taking tool that organizes your knowledge graph in a unique and interconnected way.
+
+Quartz supports transforming the special Markdown syntax from Roam Research (like `{{[[components]]}}` and other formatting) into
+regular Markdown via the [[RoamFlavoredMarkdown]] plugin.
+
+```typescript title="quartz.config.ts"
+plugins: {
+  transformers: [
+    // ...
+    Plugin.RoamFlavoredMarkdown(),
+    Plugin.ObsidianFlavoredMarkdown(),
+    // ...
+  ],
+},
+```
+
+> [!warning]
+> As seen above placement of `Plugin.RoamFlavoredMarkdown()` within `quartz.config.ts` is very important. It must come before `Plugin.ObsidianFlavoredMarkdown()`.
+
+## Customization
+
+This functionality is provided by the [[RoamFlavoredMarkdown]] plugin. See the plugin page for customization options.

docs/features/backlinks.md

@@ -9,6 +9,7 @@ A backlink for a note is a link from another note to that note. Links in the bac
 ## Customization
 
 - Removing backlinks: delete all usages of `Component.Backlinks()` from `quartz.layout.ts`.
+- Hide when empty: hide `Backlinks` if given page doesn't contain any backlinks (default to `true`). To disable this, use `Component.Backlinks({ hideWhenEmpty: false })`.
 - Component: `quartz/components/Backlinks.tsx`
 - Style: `quartz/components/styles/backlinks.scss`
 - Script: `quartz/components/scripts/search.inline.ts`

docs/features/breadcrumbs.md

@@ -19,7 +19,6 @@ Component.Breadcrumbs({
   spacerSymbol: "❯", // symbol between crumbs
   rootName: "Home", // name of first/root element
   resolveFrontmatterTitle: true, // whether to resolve folder names through frontmatter titles
-  hideOnRoot: true, // whether to hide breadcrumbs on root `index.md` page
   showCurrentPage: true, // whether to display the current page in the breadcrumbs
 })
 ```

docs/features/comments.md

@@ -0,0 +1,133 @@
+---
+title: Comments
+tags:
+  - component
+---
+
+Quartz also has the ability to hook into various providers to enable readers to leave comments on your site.
+
+![[giscus-example.png]]
+
+As of today, only [Giscus](https://giscus.app/) is supported out of the box but PRs to support other providers are welcome!
+
+## Providers
+
+### Giscus
+
+First, make sure that the [[setting up your GitHub repository|GitHub]] repository you are using for your Quartz meets the following requirements:
+
+1. The **repository is [public](https://docs.github.com/en/github/administering-a-repository/managing-repository-settings/setting-repository-visibility#making-a-repository-public)**, otherwise visitors will not be able to view the discussion.
+2. The **[giscus](https://github.com/apps/giscus) app is installed**, otherwise visitors will not be able to comment and react.
+3. The **Discussions feature is turned on** by [enabling it for your repository](https://docs.github.com/en/github/administering-a-repository/managing-repository-settings/enabling-or-disabling-github-discussions-for-a-repository).
+
+Then, use the [Giscus site](https://giscus.app/#repository) to figure out what your `repoId` and `categoryId` should be. Make sure you select `Announcements` for the Discussion category.
+
+![[giscus-repo.png]]
+
+![[giscus-discussion.png]]
+
+After entering both your repository and selecting the discussion category, Giscus will compute some IDs that you'll need to provide back to Quartz. You won't need to manually add the script yourself as Quartz will handle that part for you but will need these values in the next step!
+
+![[giscus-results.png]]
+
+Finally, in `quartz.layout.ts`, edit the `afterBody` field of `sharedPageComponents` to include the following options but with the values you got from above:
+
+```ts title="quartz.layout.ts"
+afterBody: [
+  Component.Comments({
+    provider: 'giscus',
+    options: {
+      // from data-repo
+      repo: 'jackyzha0/quartz',
+      // from data-repo-id
+      repoId: 'MDEwOlJlcG9zaXRvcnkzODcyMTMyMDg',
+      // from data-category
+      category: 'Announcements',
+      // from data-category-id
+      categoryId: 'DIC_kwDOFxRnmM4B-Xg6',
+      // from data-lang
+      lang: 'en'
+    }
+  }),
+],
+```
+
+### Customization
+
+Quartz also exposes a few of the other Giscus options as well and you can provide them the same way `repo`, `repoId`, `category`, and `categoryId` are provided.
+
+```ts
+type Options = {
+  provider: "giscus"
+  options: {
+    repo: `${string}/${string}`
+    repoId: string
+    category: string
+    categoryId: string
+
+    // Url to folder with custom themes
+    // defaults to 'https://${cfg.baseUrl}/static/giscus'
+    themeUrl?: string
+
+    // filename for light theme .css file
+    // defaults to 'light'
+    lightTheme?: string
+
+    // filename for dark theme .css file
+    // defaults to 'dark'
+    darkTheme?: string
+
+    // how to map pages -> discussions
+    // defaults to 'url'
+    mapping?: "url" | "title" | "og:title" | "specific" | "number" | "pathname"
+
+    // use strict title matching
+    // defaults to true
+    strict?: boolean
+
+    // whether to enable reactions for the main post
+    // defaults to true
+    reactionsEnabled?: boolean
+
+    // where to put the comment input box relative to the comments
+    // defaults to 'bottom'
+    inputPosition?: "top" | "bottom"
+
+    // set your preference language here
+    // defaults to 'en'
+    lang?: string
+  }
+}
+```
+
+#### Custom CSS theme
+
+Quartz supports custom theme for Giscus. To use a custom CSS theme, place the `.css` file inside the `quartz/static` folder and set the configuration values.
+
+For example, if you have a light theme `light-theme.css`, a dark theme `dark-theme.css`, and your Quartz site is hosted at `https://example.com/`:
+
+```ts
+afterBody: [
+  Component.Comments({
+    provider: 'giscus',
+    options: {
+      // Other options
+
+      themeUrl: "https://example.com/static/giscus", // corresponds to quartz/static/giscus/
+      lightTheme: "light-theme", // corresponds to light-theme.css in quartz/static/giscus/
+      darkTheme: "dark-theme", // corresponds to dark-theme.css quartz/static/giscus/
+    }
+  }),
+],
+```
+
+#### Conditionally display comments
+
+Quartz can conditionally display the comment box based on a field `comments` in the frontmatter. By default, all pages will display comments, to disable it for a specific page, set `comments` to `false`.
+
+```
+---
+title: Comments disabled here!
+comments: false
+---
+```

docs/features/explorer.md

@@ -27,12 +27,10 @@ Component.Explorer({
   folderClickBehavior: "collapse", // what happens when you click a folder ("link" to navigate to folder page on click or "collapse" to collapse folder on click)
   folderDefaultState: "collapsed", // default state of folders ("collapsed" or "open")
   useSavedState: true, // whether to use local storage to save "state" (which folders are opened) of explorer
-  // Sort order: folders first, then files. Sort folders and files alphabetically
-  sortFn: (a, b) => {
-    ... // default implementation shown later
-  },
-  filterFn: filterFn: (node) => node.name !== "tags", // filters out 'tags' folder
-  mapFn: undefined,
+  // omitted but shown later
+  sortFn: ...,
+  filterFn: ...,
+  mapFn: ...,
   // what order to apply functions in
   order: ["filter", "map", "sort"],
 })
@@ -45,26 +43,30 @@ Want to customize it even more?
 - Removing explorer: remove `Component.Explorer()` from `quartz.layout.ts`
   - (optional): After removing the explorer component, you can move the [[table of contents | Table of Contents]] component back to the `left` part of the layout
 - Changing `sort`, `filter` and `map` behavior: explained in [[#Advanced customization]]
-- Component:
-  - Wrapper (Outer component, generates file tree, etc): `quartz/components/Explorer.tsx`
-  - Explorer node (recursive, either a folder or a file): `quartz/components/ExplorerNode.tsx`
+- Component: `quartz/components/Explorer.tsx`
 - Style: `quartz/components/styles/explorer.scss`
 - Script: `quartz/components/scripts/explorer.inline.ts`
 
 ## Advanced customization
 
 This component allows you to fully customize all of its behavior. You can pass a custom `sort`, `filter` and `map` function.
-All functions you can pass work with the `FileNode` class, which has the following properties:
+All functions you can pass work with the `FileTrieNode` class, which has the following properties:
 
-```ts title="quartz/components/ExplorerNode.tsx" {2-5}
-export class FileNode {
-  children: FileNode[]  // children of current node
-  name: string  // last part of slug
-  displayName: string // what actually should be displayed in the explorer
-  file: QuartzPluginData | null // if node is a file, this is the file's metadata. See `QuartzPluginData` for more detail
-  depth: number // depth of current node
+```ts title="quartz/components/Explorer.tsx"
+class FileTrieNode {
+  isFolder: boolean
+  children: Array<FileTrieNode>
+  data: ContentDetails | null
+}
+```
 
-  ... // rest of implementation
+```ts title="quartz/plugins/emitters/contentIndex.tsx"
+export type ContentDetails = {
+  slug: FullSlug
+  title: string
+  links: SimpleSlug[]
+  tags: string[]
+  content: string
 }
 ```
 
@@ -74,15 +76,14 @@ Every function you can pass is optional. By default, only a `sort` function will
 // Sort order: folders first, then files. Sort folders and files alphabetically
 Component.Explorer({
   sortFn: (a, b) => {
-    if ((!a.file && !b.file) || (a.file && b.file)) {
-      // sensitivity: "base": Only strings that differ in base letters compare as unequal. Examples: a ≠ b, a = á, a = A
-      // numeric: true: Whether numeric collation should be used, such that "1" < "2" < "10"
+    if ((!a.isFolder && !b.isFolder) || (a.isFolder && b.isFolder)) {
       return a.displayName.localeCompare(b.displayName, undefined, {
         numeric: true,
         sensitivity: "base",
       })
     }
-    if (a.file && !b.file) {
+
+    if (!a.isFolder && b.isFolder) {
       return 1
     } else {
       return -1
@@ -100,41 +101,23 @@ For more information on how to use `sort`, `filter` and `map`, you can check [Ar
 Type definitions look like this:
 
 ```ts
-sortFn: (a: FileNode, b: FileNode) => number
-filterFn: (node: FileNode) => boolean
-mapFn: (node: FileNode) => void
+type SortFn = (a: FileTrieNode, b: FileTrieNode) => number
+type FilterFn = (node: FileTrieNode) => boolean
+type MapFn = (node: FileTrieNode) => void
 ```
 
-> [!tip]
-> You can check if a `FileNode` is a folder or a file like this:
->
-> ```ts
-> if (node.file) {
->   // node is a file
-> } else {
->   // node is a folder
-> }
-> ```
-
 ## Basic examples
 
 These examples show the basic usage of `sort`, `map` and `filter`.
 
 ### Use `sort` to put files first
 
-Using this example, the explorer will alphabetically sort everything, but put all **files** above all **folders**.
+Using this example, the explorer will alphabetically sort everything.
 
 ```ts title="quartz.layout.ts"
 Component.Explorer({
   sortFn: (a, b) => {
-    if ((!a.file && !b.file) || (a.file && b.file)) {
     return a.displayName.localeCompare(b.displayName)
-    }
-    if (a.file && !b.file) {
-      return -1
-    } else {
-      return 1
-    }
   },
 })
 ```
@@ -147,42 +130,47 @@ Using this example, the display names of all `FileNodes` (folders + files) will
 Component.Explorer({
   mapFn: (node) => {
     node.displayName = node.displayName.toUpperCase()
+    return node
   },
 })
 ```
 
 ### Remove list of elements (`filter`)
 
-Using this example, you can remove elements from your explorer by providing an array of folders/files using the `omit` set.
+Using this example, you can remove elements from your explorer by providing an array of folders/files to exclude.
+Note that this example filters on the title but you can also do it via slug or any other field available on `FileTrieNode`.
 
 ```ts title="quartz.layout.ts"
 Component.Explorer({
   filterFn: (node) => {
     // set containing names of everything you want to filter out
-    const omit = new Set(["authoring content", "tags", "hosting"])
-    return !omit.has(node.name.toLowerCase())
+    const omit = new Set(["authoring content", "tags", "advanced"])
+
+    // can also use node.slug or by anything on node.data
+    // note that node.data is only present for files that exist on disk
+    // (e.g. implicit folder nodes that have no associated index.md)
+    return !omit.has(node.displayName.toLowerCase())
   },
 })
 ```
 
-You can customize this by changing the entries of the `omit` set. Simply add all folder or file names you want to remove.
-
 ### Remove files by tag
 
-You can access the frontmatter of a file by `node.file?.frontmatter?`. This allows you to filter out files based on their frontmatter, for example by their tags.
+You can access the tags of a file by `node.data.tags`.
 
 ```ts title="quartz.layout.ts"
 Component.Explorer({
   filterFn: (node) => {
     // exclude files with the tag "explorerexclude"
-    return node.file?.frontmatter?.tags?.includes("explorerexclude") !== true
+    return node.data.tags?.includes("explorerexclude") !== true
   },
 })
 ```
 
 ### Show every element in explorer
 
-To override the default filter function that removes the `tags` folder from the explorer, you can set the filter function to `undefined`.
+By default, the explorer will filter out the `tags` folder.
+To override the default filter function, you can set the filter function to `undefined`.
 
 ```ts title="quartz.layout.ts"
 Component.Explorer({
@@ -194,10 +182,12 @@ Component.Explorer({
 
 > [!tip]
 > When writing more complicated functions, the `layout` file can start to look very cramped.
-> You can fix this by defining your functions in another file.
+> You can fix this by defining your sort functions outside of the component
+> and passing it in.
+>
+> ```ts title="quartz.layout.ts"
+> import { Options } from "./quartz/components/Explorer"
 >
-> ```ts title="functions.ts"
-> import { Options } from "./quartz/components/ExplorerNode"
 > export const mapFn: Options["mapFn"] = (node) => {
 >   // implement your function here
 > }
@@ -207,16 +197,12 @@ Component.Explorer({
 > export const sortFn: Options["sortFn"] = (a, b) => {
 >   // implement your function here
 > }
-> ```
 >
-> You can then import them like this:
->
-> ```ts title="quartz.layout.ts"
-> import { mapFn, filterFn, sortFn } from "./functions.ts"
 > Component.Explorer({
->   mapFn: mapFn,
->   filterFn: filterFn,
->   sortFn: sortFn,
+>   // ... your other options
+>   mapFn,
+>   filterFn,
+>   sortFn,
 > })
 > ```
 
@@ -227,93 +213,11 @@ To add emoji prefixes (📁 for folders, 📄 for files), you could use a map fu
 ```ts title="quartz.layout.ts"
 Component.Explorer({
   mapFn: (node) => {
-    // dont change name of root node
-    if (node.depth > 0) {
-      // set emoji for file/folder
-      if (node.file) {
-        node.displayName = "📄 " + node.displayName
-      } else {
+    if (node.isFolder) {
       node.displayName = "📁 " + node.displayName
-      }
+    } else {
+      node.displayName = "📄 " + node.displayName
     }
   },
 })
 ```
-
-### Putting it all together
-
-In this example, we're going to customize the explorer by using functions from examples above to [[#Add emoji prefix | add emoji prefixes]], [[#remove-list-of-elements-filter| filter out some folders]] and [[#use-sort-to-put-files-first | sort with files above folders]].
-
-```ts title="quartz.layout.ts"
-Component.Explorer({
-  filterFn: sampleFilterFn,
-  mapFn: sampleMapFn,
-  sortFn: sampleSortFn,
-  order: ["filter", "sort", "map"],
-})
-```
-
-Notice how we customized the `order` array here. This is done because the default order applies the `sort` function last. While this normally works well, it would cause unintended behavior here, since we changed the first characters of all display names. In our example, `sort` would be applied based off the emoji prefix instead of the first _real_ character.
-
-To fix this, we just changed around the order and apply the `sort` function before changing the display names in the `map` function.
-
-### Use `sort` with pre-defined sort order
-
-Here's another example where a map containing file/folder names (as slugs) is used to define the sort order of the explorer in quartz. All files/folders that aren't listed inside of `nameOrderMap` will appear at the top of that folders hierarchy level.
-
-It's also worth mentioning, that the smaller the number set in `nameOrderMap`, the higher up the entry will be in the explorer. Incrementing every folder/file by 100, makes ordering files in their folders a lot easier. Lastly, this example still allows you to use a `mapFn` or frontmatter titles to change display names, as it uses slugs for `nameOrderMap` (which is unaffected by display name changes).
-
-```ts title="quartz.layout.ts"
-Component.Explorer({
-  sortFn: (a, b) => {
-    const nameOrderMap: Record<string, number> = {
-      "poetry-folder": 100,
-      "essay-folder": 200,
-      "research-paper-file": 201,
-      "dinosaur-fossils-file": 300,
-      "other-folder": 400,
-    }
-
-    let orderA = 0
-    let orderB = 0
-
-    if (a.file && a.file.slug) {
-      orderA = nameOrderMap[a.file.slug] || 0
-    } else if (a.name) {
-      orderA = nameOrderMap[a.name] || 0
-    }
-
-    if (b.file && b.file.slug) {
-      orderB = nameOrderMap[b.file.slug] || 0
-    } else if (b.name) {
-      orderB = nameOrderMap[b.name] || 0
-    }
-
-    return orderA - orderB
-  },
-})
-```
-
-For reference, this is how the quartz explorer window would look like with that example:
-
-```
-📖 Poetry Folder
-📑 Essay Folder
-    ⚗️ Research Paper File
-🦴 Dinosaur Fossils File
-🔮 Other Folder
-```
-
-And this is how the file structure would look like:
-
-```
-index.md
-poetry-folder
-    index.md
-essay-folder
-    index.md
-    research-paper-file.md
-dinosaur-fossils-file.md
-other-folder
-    index.md
-```

docs/features/folder and tag listings.md

@@ -30,4 +30,4 @@ As with folder listings, you can also provide a description and title for a tag
 
 ## Customization
 
-The folder listings are a functionality of the [[FolderPage]] plugin, the tag listings of the [[TagPage]] plugin. See the plugin pages for customization options.
+Quartz allows you to define a custom sort ordering for content on both page types. The folder listings are a functionality of the [[FolderPage]] plugin, the tag listings of the [[TagPage]] plugin. See the plugin pages for customization options.

docs/features/graph view.md

@@ -36,6 +36,7 @@ Component.Graph({
     opacityScale: 1, // how quickly do we fade out the labels when zooming out?
     removeTags: [], // what tags to remove from the graph
     showTags: true, // whether to show tags in the graph
+    enableRadial: false, // whether to constrain the graph, similar to Obsidian
   },
   globalGraph: {
     drag: true,
@@ -49,6 +50,7 @@ Component.Graph({
     opacityScale: 1,
     removeTags: [], // what tags to remove from the graph
     showTags: true, // whether to show tags in the graph
+    enableRadial: true, // whether to constrain the graph, similar to Obsidian
   },
 })
 ```

docs/features/private pages.md

@@ -13,9 +13,7 @@ There may be some notes you want to avoid publishing as a website. Quartz suppor
 If you'd like to only publish a select number of notes, you can instead use [[ExplicitPublish]] which will filter out all notes except for any that have `publish: true` in the frontmatter.
 
 > [!warning]
-> Regardless of the filter plugin used, **all non-markdown files will be emitted and available publically in the final build.** This includes files such as images, voice recordings, PDFs, etc. One way to prevent this and still be able to embed local images is to create a folder specifically for public media and add the following two patterns to the ignorePatterns array.
->
-> `"!(PublicMedia)**/!(*.md)", "!(*.md)"`
+> Regardless of the filter plugin used, **all non-markdown files will be emitted and available publically in the final build.** This includes files such as images, voice recordings, PDFs, etc.
 
 ## `ignorePatterns`
 
@@ -28,7 +26,7 @@ Common examples include:
 
 - `some/folder`: exclude the entire of `some/folder`
 - `*.md`: exclude all files with a `.md` extension
-- `!*.md` exclude all files that _don't_ have a `.md` extension
+- `!(*.md)` exclude all files that _don't_ have a `.md` extension. Note that negations _must_ parenthesize the rest of the pattern!
 - `**/private`: exclude any files or folders named `private` at any level of nesting
 
 > [!warning]

docs/features/reader mode.md

@@ -0,0 +1,44 @@
+---
+title: Reader Mode
+tags:
+  - component
+---
+
+Reader Mode is a feature that allows users to focus on the content by hiding the sidebars and other UI elements. When enabled, it provides a clean, distraction-free reading experience.
+
+## Configuration
+
+Reader Mode is enabled by default. To disable it, you can remove the component from your layout configuration in `quartz.layout.ts`:
+
+```ts
+// Remove or comment out this line
+Component.ReaderMode(),
+```
+
+## Usage
+
+The Reader Mode toggle appears as a button with a book icon. When clicked:
+
+- Sidebars are hidden
+- Hovering over the content area reveals the sidebars temporarily
+
+Unlike Dark Mode, Reader Mode state is not persisted between page reloads but is maintained during SPA navigation within the site.
+
+## Customization
+
+You can customize the appearance of Reader Mode through CSS variables and styles. The component uses the following classes:
+
+- `.readermode`: The toggle button
+- `.readerIcon`: The book icon
+- `[reader-mode="on"]`: Applied to the root element when Reader Mode is active
+
+Example customization in your custom CSS:
+
+```scss
+.readermode {
+  // Customize the button
+  svg {
+    stroke: var(--custom-color);
+  }
+}
+```

docs/features/recent notes.md

@@ -9,6 +9,7 @@ Quartz can generate a list of recent notes based on some filtering and sorting c
 
 - Changing the title from "Recent notes": pass in an additional parameter to `Component.RecentNotes({ title: "Recent writing" })`
 - Changing the number of recent notes: pass in an additional parameter to `Component.RecentNotes({ limit: 5 })`
+- Display the note's tags (defaults to true): `Component.RecentNotes({ showTags: false })`
 - Show a 'see more' link: pass in an additional parameter to `Component.RecentNotes({ linkToMore: "tags/components" })`. This field should be a full slug to a page that exists.
 - Customize filtering: pass in an additional parameter to `Component.RecentNotes({ filter: someFilterFunction })`. The filter function should be a function that has the signature `(f: QuartzPluginData) => boolean`.
 - Customize sorting: pass in an additional parameter to `Component.RecentNotes({ sort: someSortFunction })`. By default, Quartz will sort by date and then tie break lexographically. The sort function should be a function that has the signature `(f1: QuartzPluginData, f2: QuartzPluginData) => number`. See `byDateAndAlphabetical` in `quartz/components/PageList.tsx` for an example.

docs/features/social images.md

@@ -0,0 +1,19 @@
+---
+title: "Social Media Preview Cards"
+---
+
+A lot of social media platforms can display a rich preview for your website when sharing a link (most notably, a cover image, a title and a description).
+
+Quartz can also dynamically generate and use new cover images for every page to be used in link previews on social media for you.
+
+## Showcase
+
+After enabling the [[CustomOgImages]] emitter plugin, the social media link preview for [[authoring content | Authoring Content]] looks like this:
+
+| Light                               | Dark                               |
+| ----------------------------------- | ---------------------------------- |
+| ![[social-image-preview-light.png]] | ![[social-image-preview-dark.png]] |
+
+## Configuration
+
+This functionality is provided by the [[CustomOgImages]] plugin. See the plugin page for customization options.

docs/features/syntax highlighting.md

@@ -95,6 +95,16 @@ const [age, setAge] = useState(50)
 const [name, setName] = useState("Taylor")
 ```
 
+### Inline Highlighting
+
+Append {:lang} to the end of inline code to highlight it like a regular code block.
+
+```
+This is an array `[1, 2, 3]{:js}` of numbers 1 through 3.
+```
+
+This is an array `[1, 2, 3]{:js}` of numbers 1 through 3.
+
 ### Line numbers
 
 Syntax highlighting has line numbers configured automatically. If you want to start line numbers at a specific number, use `showLineNumbers{number}`:

docs/features/upcoming features.md

@@ -2,22 +2,11 @@
 draft: true
 ---
 
-## high priority backlog
-
-- static dead link detection
-- block links: https://help.obsidian.md/Linking+notes+and+files/Internal+links#Link+to+a+block+in+a+note
-- note/header/block transcludes: https://help.obsidian.md/Linking+notes+and+files/Embedding+files
-- docker support
-
 ## misc backlog
 
-- breadcrumbs component
+- static dead link detection
 - cursor chat extension
-- https://giscus.app/ extension
 - sidenotes? https://github.com/capnfabs/paperesque
 - direct match in search using double quotes
 - https://help.obsidian.md/Advanced+topics/Using+Obsidian+URI
-- audio/video embed styling
 - Canvas
-- parse all images in page: use this for page lists if applicable?
-- CV mode? with print stylesheet

docs/hosting.md

@@ -57,18 +57,18 @@ jobs:
   build:
     runs-on: ubuntu-22.04
     steps:
-      - uses: actions/checkout@v3
+      - uses: actions/checkout@v4
         with:
           fetch-depth: 0 # Fetch all history for git info
-      - uses: actions/setup-node@v3
+      - uses: actions/setup-node@v4
         with:
-          node-version: 18.14
+          node-version: 22
       - name: Install Dependencies
         run: npm ci
       - name: Build Quartz
         run: npx quartz build
       - name: Upload artifact
-        uses: actions/upload-pages-artifact@v2
+        uses: actions/upload-pages-artifact@v3
         with:
           path: public
 
@@ -81,7 +81,7 @@ jobs:
     steps:
       - name: Deploy to GitHub Pages
         id: deployment
-        uses: actions/deploy-pages@v2
+        uses: actions/deploy-pages@v4
 ```
 
 Then:
@@ -182,37 +182,33 @@ Using `docs.example.com` is an example of a subdomain. They're a simple way of c
 
 ## GitLab Pages
 
-In your local Quartz, create a new file `.gitlab-ci.yaml`.
+In your local Quartz, create a new file `.gitlab-ci.yml`.
 
-```yaml title=".gitlab-ci.yaml"
+```yaml title=".gitlab-ci.yml"
 stages:
   - build
   - deploy
 
-variables:
-  NODE_VERSION: "18.14"
+image: node:22
+cache: # Cache modules in between jobs
+  key: $CI_COMMIT_REF_SLUG
+  paths:
+    - .npm/
 
 build:
   stage: build
   rules:
     - if: '$CI_COMMIT_REF_NAME == "v4"'
   before_script:
-    - apt-get update -q && apt-get install -y nodejs npm
-    - npm install -g n
-    - n $NODE_VERSION
     - hash -r
-    - npm ci
+    - npm ci --cache .npm --prefer-offline
   script:
     - npx quartz build
   artifacts:
     paths:
       - public
-  cache:
-    paths:
-      - ~/.npm/
-    key: "${CI_COMMIT_REF_SLUG}-node-${CI_COMMIT_REF_NAME}"
   tags:
-    - docker
+    - gitlab-org-docker
 
 pages:
   stage: deploy
@@ -251,6 +247,28 @@ server {
 }
 ```
 
+### Using Apache
+
+Here's an example of how to do this with Apache:
+
+```apache title=".htaccess"
+RewriteEngine On
+
+ErrorDocument 404 /404.html
+
+# Rewrite rule for .html extension removal (with directory check)
+RewriteCond %{REQUEST_FILENAME} !-f
+RewriteCond %{REQUEST_FILENAME} !-d
+RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_URI}.html -f
+RewriteRule ^(.*)$ $1.html [L]
+
+# Handle directory requests explicitly
+RewriteCond %{REQUEST_FILENAME} -d
+RewriteRule ^(.*)/$ $1/index.html [L]
+```
+
+Don't forget to activate brotli / gzip compression.
+
 ### Using Caddy
 
 Here's and example of how to do this with Caddy:

docs/index.md

@@ -6,7 +6,7 @@ Quartz is a fast, batteries-included static-site generator that transforms Markd
 
 ## 🪴 Get Started
 
-Quartz requires **at least [Node](https://nodejs.org/) v18.14** and `npm` v9.3.1 to function correctly. Ensure you have this installed on your machine before continuing.
+Quartz requires **at least [Node](https://nodejs.org/) v22** and `npm` v10.9.2 to function correctly. Ensure you have this installed on your machine before continuing.
 
 Then, in your terminal of choice, enter the following commands line by line:
 
@@ -31,13 +31,13 @@ If you prefer instructions in a video format you can try following Nicole van de
 
 ## 🔧 Features
 
-- [[Obsidian compatibility]], [[full-text search]], [[graph view]], note transclusion, [[wikilinks]], [[backlinks]], [[features/Latex|Latex]], [[syntax highlighting]], [[popover previews]], [[Docker Support]], [[i18n|internationalization]] and [many more](./features) right out of the box
-- Hot-reload for both configuration and content
+- [[Obsidian compatibility]], [[full-text search]], [[graph view]], [[wikilinks|wikilinks, transclusions]], [[backlinks]], [[features/Latex|Latex]], [[syntax highlighting]], [[popover previews]], [[Docker Support]], [[i18n|internationalization]], [[comments]] and [many more](./features/) right out of the box
+- Hot-reload on configuration edits and incremental rebuilds for content edits
 - Simple JSX layouts and [[creating components|page components]]
 - [[SPA Routing|Ridiculously fast page loads]] and tiny bundle sizes
 - Fully-customizable parsing, filtering, and page generation through [[making plugins|plugins]]
 
-For a comprehensive list of features, visit the [features page](/features). You can read more about the _why_ behind these features on the [[philosophy]] page and a technical overview on the [[architecture]] page.
+For a comprehensive list of features, visit the [features page](./features/). You can read more about the _why_ behind these features on the [[philosophy]] page and a technical overview on the [[architecture]] page.
 
 ### 🚧 Troubleshooting + Updating
 

docs/layout-components.md

@@ -0,0 +1,102 @@
+---
+title: Higher-Order Layout Components
+---
+
+Quartz provides several higher-order components that help with layout composition and responsive design. These components wrap other components to add additional functionality or modify their behavior.
+
+## `Flex` Component
+
+The `Flex` component creates a [flexible box layout](https://developer.mozilla.org/en-US/docs/Web/CSS/flex) that can arrange child components in various ways. It's particularly useful for creating responsive layouts and organizing components in rows or columns.
+
+```typescript
+type FlexConfig = {
+  components: {
+    Component: QuartzComponent
+    grow?: boolean // whether component should grow to fill space
+    shrink?: boolean // whether component should shrink if needed
+    basis?: string // initial main size of the component
+    order?: number // order in flex container
+    align?: "start" | "end" | "center" | "stretch" // cross-axis alignment
+    justify?: "start" | "end" | "center" | "between" | "around" // main-axis alignment
+  }[]
+  direction?: "row" | "row-reverse" | "column" | "column-reverse"
+  wrap?: "nowrap" | "wrap" | "wrap-reverse"
+  gap?: string
+}
+```
+
+### Example Usage
+
+```typescript
+Component.Flex({
+  components: [
+    {
+      Component: Component.Search(),
+      grow: true, // Search will grow to fill available space
+    },
+    { Component: Component.Darkmode() }, // Darkmode keeps its natural size
+  ],
+  direction: "row",
+  gap: "1rem",
+})
+```
+
+> [!note] Overriding behavior
+> Components inside `Flex` get an additional CSS class `flex-component` that add the `display: flex` property. If you want to override this behavior, you can add a `display` property to the component's CSS class in your custom CSS file.
+>
+> ```scss
+> .flex-component {
+>   display: block; // or any other display type
+> }
+> ```
+
+## `MobileOnly` Component
+
+The `MobileOnly` component is a wrapper that makes its child component only visible on mobile devices. This is useful for creating responsive layouts where certain components should only appear on smaller screens.
+
+### Example Usage
+
+```typescript
+Component.MobileOnly(Component.Spacer())
+```
+
+## `DesktopOnly` Component
+
+The `DesktopOnly` component is the counterpart to `MobileOnly`. It makes its child component only visible on desktop devices. This helps create responsive layouts where certain components should only appear on larger screens.
+
+### Example Usage
+
+```typescript
+Component.DesktopOnly(Component.TableOfContents())
+```
+
+## `ConditionalRender` Component
+
+The `ConditionalRender` component is a wrapper that conditionally renders its child component based on a provided condition function. This is useful for creating dynamic layouts where components should only appear under certain conditions.
+
+```typescript
+type ConditionalRenderConfig = {
+  component: QuartzComponent
+  condition: (props: QuartzComponentProps) => boolean
+}
+```
+
+### Example Usage
+
+```typescript
+Component.ConditionalRender({
+  component: Component.Search(),
+  condition: (props) => props.displayClass !== "fullpage",
+})
+```
+
+The example above would only render the Search component when the page is not in fullpage mode.
+
+```typescript
+Component.ConditionalRender({
+  component: Component.Breadcrumbs(),
+  condition: (page) => page.fileData.slug !== "index",
+})
+```
+
+The example above would hide breadcrumbs on the root `index.md` page.

docs/layout.md

@@ -12,15 +12,20 @@ export interface FullPageLayout {
   header: QuartzComponent[] // laid out horizontally
   beforeBody: QuartzComponent[] // laid out vertically
   pageBody: QuartzComponent // single component
-  left: QuartzComponent[] // vertical on desktop, horizontal on mobile
-  right: QuartzComponent[] // vertical on desktop, horizontal on mobile
+  afterBody: QuartzComponent[] // laid out vertically
+  left: QuartzComponent[] // vertical on desktop and tablet, horizontal on mobile
+  right: QuartzComponent[] // vertical on desktop, horizontal on tablet and mobile
   footer: QuartzComponent // single component
 }
 ```
 
 These correspond to following parts of the page:
 
-![[quartz layout.png|800]]
+| Layout                          | Preview                             |
+| ------------------------------- | ----------------------------------- |
+| Desktop (width > 1200px)        | ![[quartz-layout-desktop.png\|800]] |
+| Tablet (800px < width < 1200px) | ![[quartz-layout-tablet.png\|800]]  |
+| Mobile (width < 800px)          | ![[quartz-layout-mobile.png\|800]]  |
 
 > [!note]
 > There are two additional layout fields that are _not_ shown in the above diagram.
@@ -30,7 +35,26 @@ These correspond to following parts of the page:
 
 Quartz **components**, like plugins, can take in additional properties as configuration options. If you're familiar with React terminology, you can think of them as Higher-order Components.
 
-See [a list of all the components](component.md) for all available components along with their configuration options. You can also checkout the guide on [[creating components]] if you're interested in further customizing the behaviour of Quartz.
+See [a list of all the components](component.md) for all available components along with their configuration options. Additionally, Quartz provides several built-in higher-order components for layout composition - see [[layout-components]] for more details.
+
+You can also checkout the guide on [[creating components]] if you're interested in further customizing the behaviour of Quartz.
+
+### Layout breakpoints
+
+Quartz has different layouts depending on the width the screen viewing the website.
+
+The breakpoints for layouts can be configured in `variables.scss`.
+
+- `mobile`: screen width below this size will use mobile layout.
+- `desktop`: screen width above this size will use desktop layout.
+- Screen width between `mobile` and `desktop` width will use the tablet layout.
+
+```scss
+$breakpoints: (
+  mobile: 800px,
+  desktop: 1200px,
+);
+```
 
 ### Style
 

docs/plugins/Citations.md

@@ -0,0 +1,24 @@
+---
+title: "Citations"
+tags:
+  - plugin/transformer
+---
+
+This plugin adds Citation support to Quartz.
+
+> [!note]
+> For information on how to add, remove or configure plugins, see the [[configuration#Plugins|Configuration]] page.
+
+This plugin accepts the following configuration options:
+
+- `bibliographyFile`: the path to the bibliography file. Defaults to `./bibliography.bib`. This is relative to git source of your vault.
+- `suppressBibliography`: whether to suppress the bibliography at the end of the document. Defaults to `false`.
+- `linkCitations`: whether to link citations to the bibliography. Defaults to `false`.
+- `csl`: the citation style to use. Defaults to `apa`. Reference [rehype-citation](https://rehype-citation.netlify.app/custom-csl) for more options.
+- `prettyLink`: whether to use pretty links for citations. Defaults to `true`.
+
+## API
+
+- Category: Transformer
+- Function name: `Plugin.Citations()`.
+- Source: [`quartz/plugins/transformers/citations.ts`](https://github.com/jackyzha0/quartz/blob/v4/quartz/plugins/transformers/citations.ts).

docs/plugins/ContentIndex.md

@@ -17,6 +17,7 @@ This plugin accepts the following configuration options:
 - `enableRSS`: If `true` (default), produces an RSS feed (`index.xml`) with recent content updates.
 - `rssLimit`: Defines the maximum number of entries to include in the RSS feed, helping to focus on the most recent or relevant content. Defaults to `10`.
 - `rssFullHtml`: If `true`, the RSS feed includes full HTML content. Otherwise it includes just summaries.
+- `rssSlug`: Slug to the generated RSS feed XML file. Defaults to `"index"`.
 - `includeEmptyFiles`: If `true` (default), content files with no body text are included in the generated index and resources.
 
 ## API

docs/plugins/CreatedModifiedDate.md

@@ -11,7 +11,9 @@ This plugin determines the created, modified, and published dates for a document
 
 This plugin accepts the following configuration options:
 
-- `priority`: The data sources to consult for date information. Highest priority first. Possible values are `"frontmatter"`, `"git"`, and `"filesystem"`. Defaults to `"frontmatter", "git", "filesystem"]`.
+- `priority`: The data sources to consult for date information. Highest priority first. Possible values are `"frontmatter"`, `"git"`, and `"filesystem"`. Defaults to `["frontmatter", "git", "filesystem"]`.
+
+When loading the frontmatter, the value of [[Frontmatter#List]] is used.
 
 > [!warning]
 > If you rely on `git` for dates, make sure `defaultDateType` is set to `modified` in `quartz.config.ts`.

docs/plugins/CustomOgImages.md

@@ -0,0 +1,360 @@
+---
+title: Custom OG Images
+tags:
+  - feature/emitter
+---
+
+The Custom OG Images emitter plugin generates social media preview images for your pages. It uses [satori](https://github.com/vercel/satori) to convert HTML/CSS into images, allowing you to create beautiful and consistent social media preview cards for your content.
+
+> [!note]
+> For information on how to add, remove or configure plugins, see the [[configuration#Plugins|Configuration]] page.
+
+## Features
+
+- Automatically generates social media preview images for each page
+- Supports both light and dark mode themes
+- Customizable through frontmatter properties
+- Fallback to default image when needed
+- Full control over image design through custom components
+
+## Configuration
+
+> [!info] Info
+>
+> The `baseUrl` property in your [[configuration]] must be set properly for social images to work correctly, as they require absolute paths.
+
+This plugin accepts the following configuration options:
+
+```typescript title="quartz.config.ts"
+import { CustomOgImages } from "./quartz/plugins/emitters/ogImage"
+
+const config: QuartzConfig = {
+  plugins: {
+    emitters: [
+      CustomOgImages({
+        colorScheme: "lightMode", // what colors to use for generating image, same as theme colors from config, valid values are "darkMode" and "lightMode"
+        width: 1200, // width to generate with (in pixels)
+        height: 630, // height to generate with (in pixels)
+        excludeRoot: false, // wether to exclude "/" index path to be excluded from auto generated images (false = use auto, true = use default og image)
+        imageStructure: defaultImage, // custom image component to use
+      }),
+    ],
+  },
+}
+```
+
+### Configuration Options
+
+| Option           | Type      | Default      | Description                                                       |
+| ---------------- | --------- | ------------ | ----------------------------------------------------------------- |
+| `colorScheme`    | string    | "lightMode"  | Theme to use for generating images ("darkMode" or "lightMode")    |
+| `width`          | number    | 1200         | Width of the generated image in pixels                            |
+| `height`         | number    | 630          | Height of the generated image in pixels                           |
+| `excludeRoot`    | boolean   | false        | Whether to exclude the root index page from auto-generated images |
+| `imageStructure` | component | defaultImage | Custom component to use for image generation                      |
+
+## Frontmatter Properties
+
+The following properties can be used to customize your link previews:
+
+| Property            | Alias            | Summary                             |
+| ------------------- | ---------------- | ----------------------------------- |
+| `socialDescription` | `description`    | Description to be used for preview. |
+| `socialImage`       | `image`, `cover` | Link to preview image.              |
+
+The `socialImage` property should contain a link to an image either relative to `quartz/static`, or a full URL. If you have a folder for all your images in `quartz/static/my-images`, an example for `socialImage` could be `"my-images/cover.png"`. Alternatively, you can use a fully qualified URL like `"https://example.com/cover.png"`.
+
+> [!info] Info
+>
+> The priority for what image will be used for the cover image looks like the following: `frontmatter property > generated image (if enabled) > default image`.
+>
+> The default image (`quartz/static/og-image.png`) will only be used as a fallback if nothing else is set. If the Custom OG Images emitter plugin is enabled, it will be treated as the new default per page, but can be overwritten by setting the `socialImage` frontmatter property for that page.
+
+## Customization
+
+You can fully customize how the images being generated look by passing your own component to `imageStructure`. This component takes JSX + some page metadata/config options and converts it to an image using [satori](https://github.com/vercel/satori). Vercel provides an [online playground](https://og-playground.vercel.app/) that can be used to preview how your JSX looks like as a picture. This is ideal for prototyping your custom design.
+
+### Fonts
+
+You will also be passed an array containing a header and a body font (where the first entry is header and the second is body). The fonts matches the ones selected in `theme.typography.header` and `theme.typography.body` from `quartz.config.ts` and will be passed in the format required by [`satori`](https://github.com/vercel/satori). To use them in CSS, use the `.name` property (e.g. `fontFamily: fonts[1].name` to use the "body" font family).
+
+An example of a component using the header font could look like this:
+
+```tsx title="socialImage.tsx"
+export const myImage: SocialImageOptions["imageStructure"] = (...) => {
+  return <p style={{ fontFamily: fonts[0].name }}>Cool Header!</p>
+}
+```
+
+> [!example]- Local fonts
+>
+> For cases where you use a local fonts under `static` folder, make sure to set the correct `@font-face` in `custom.scss`
+>
+> ```scss title="custom.scss"
+> @font-face {
+>   font-family: "Newsreader";
+>   font-style: normal;
+>   font-weight: normal;
+>   font-display: swap;
+>   src: url("/static/Newsreader.woff2") format("woff2");
+> }
+> ```
+>
+> Then in `quartz/util/og.tsx`, you can load the Satori fonts like so:
+>
+> ```tsx title="quartz/util/og.tsx"
+> import { joinSegments, QUARTZ } from "../path"
+> import fs from "fs"
+> import path from "path"
+>
+> const newsreaderFontPath = joinSegments(QUARTZ, "static", "Newsreader.woff2")
+> export async function getSatoriFonts(headerFont: FontSpecification, bodyFont: FontSpecification) {
+>   // ... rest of implementation remains same
+>   const fonts: SatoriOptions["fonts"] = [
+>     ...headerFontData.map((data, idx) => ({
+>       name: headerFontName,
+>       data,
+>       weight: headerWeights[idx],
+>       style: "normal" as const,
+>     })),
+>     ...bodyFontData.map((data, idx) => ({
+>       name: bodyFontName,
+>       data,
+>       weight: bodyWeights[idx],
+>       style: "normal" as const,
+>     })),
+>     {
+>       name: "Newsreader",
+>       data: await fs.promises.readFile(path.resolve(newsreaderFontPath)),
+>       weight: 400,
+>       style: "normal" as const,
+>     },
+>   ]
+>
+>   return fonts
+> }
+> ```
+>
+> This font then can be used with your custom structure.
+
+## Examples
+
+Here are some example image components you can use as a starting point:
+
+### Basic Example
+
+This example will generate images that look as follows:
+
+| Light                                      | Dark                                      |
+| ------------------------------------------ | ----------------------------------------- |
+| ![[custom-social-image-preview-light.png]] | ![[custom-social-image-preview-dark.png]] |
+
+```tsx
+import { SatoriOptions } from "satori/wasm"
+import { GlobalConfiguration } from "../cfg"
+import { SocialImageOptions, UserOpts } from "./imageHelper"
+import { QuartzPluginData } from "../plugins/vfile"
+
+export const customImage: SocialImageOptions["imageStructure"] = (
+  cfg: GlobalConfiguration,
+  userOpts: UserOpts,
+  title: string,
+  description: string,
+  fonts: SatoriOptions["fonts"],
+  fileData: QuartzPluginData,
+) => {
+  // How many characters are allowed before switching to smaller font
+  const fontBreakPoint = 22
+  const useSmallerFont = title.length > fontBreakPoint
+
+  const { colorScheme } = userOpts
+  return (
+    <div
+      style={{
+        display: "flex",
+        flexDirection: "row",
+        justifyContent: "flex-start",
+        alignItems: "center",
+        height: "100%",
+        width: "100%",
+      }}
+    >
+      <div
+        style={{
+          display: "flex",
+          alignItems: "center",
+          justifyContent: "center",
+          height: "100%",
+          width: "100%",
+          backgroundColor: cfg.theme.colors[colorScheme].light,
+          flexDirection: "column",
+          gap: "2.5rem",
+          paddingTop: "2rem",
+          paddingBottom: "2rem",
+        }}
+      >
+        <p
+          style={{
+            color: cfg.theme.colors[colorScheme].dark,
+            fontSize: useSmallerFont ? 70 : 82,
+            marginLeft: "4rem",
+            textAlign: "center",
+            marginRight: "4rem",
+            fontFamily: fonts[0].name,
+          }}
+        >
+          {title}
+        </p>
+        <p
+          style={{
+            color: cfg.theme.colors[colorScheme].dark,
+            fontSize: 44,
+            marginLeft: "8rem",
+            marginRight: "8rem",
+            lineClamp: 3,
+            fontFamily: fonts[1].name,
+          }}
+        >
+          {description}
+        </p>
+      </div>
+      <div
+        style={{
+          height: "100%",
+          width: "2vw",
+          position: "absolute",
+          backgroundColor: cfg.theme.colors[colorScheme].tertiary,
+          opacity: 0.85,
+        }}
+      />
+    </div>
+  )
+}
+```
+
+### Advanced Example
+
+The following example includes a customized social image with a custom background and formatted date:
+
+```typescript title="custom-og.tsx"
+export const og: SocialImageOptions["Component"] = (
+  cfg: GlobalConfiguration,
+  fileData: QuartzPluginData,
+  { colorScheme }: Options,
+  title: string,
+  description: string,
+  fonts: SatoriOptions["fonts"],
+) => {
+  let created: string | undefined
+  let reading: string | undefined
+  if (fileData.dates) {
+    created = formatDate(getDate(cfg, fileData)!, cfg.locale)
+  }
+  const { minutes, text: _timeTaken, words: _words } = readingTime(fileData.text!)
+  reading = i18n(cfg.locale).components.contentMeta.readingTime({
+    minutes: Math.ceil(minutes),
+  })
+
+  const Li = [created, reading]
+
+  return (
+    <div
+      style={{
+        position: "relative",
+        display: "flex",
+        flexDirection: "row",
+        alignItems: "flex-start",
+        height: "100%",
+        width: "100%",
+        backgroundImage: `url("https://${cfg.baseUrl}/static/og-image.jpeg")`,
+        backgroundSize: "100% 100%",
+      }}
+    >
+      <div
+        style={{
+          position: "absolute",
+          top: 0,
+          left: 0,
+          right: 0,
+          bottom: 0,
+          background: "radial-gradient(circle at center, transparent, rgba(0, 0, 0, 0.4) 70%)",
+        }}
+      />
+      <div
+        style={{
+          display: "flex",
+          height: "100%",
+          width: "100%",
+          flexDirection: "column",
+          justifyContent: "flex-start",
+          alignItems: "flex-start",
+          gap: "1.5rem",
+          paddingTop: "4rem",
+          paddingBottom: "4rem",
+          marginLeft: "4rem",
+        }}
+      >
+        <img
+          src={`"https://${cfg.baseUrl}/static/icon.jpeg"`}
+          style={{
+            position: "relative",
+            backgroundClip: "border-box",
+            borderRadius: "6rem",
+          }}
+          width={80}
+        />
+        <div
+          style={{
+            display: "flex",
+            flexDirection: "column",
+            textAlign: "left",
+            fontFamily: fonts[0].name,
+          }}
+        >
+          <h2
+            style={{
+              color: cfg.theme.colors[colorScheme].light,
+              fontSize: "3rem",
+              fontWeight: 700,
+              marginRight: "4rem",
+              fontFamily: fonts[0].name,
+            }}
+          >
+            {title}
+          </h2>
+          <ul
+            style={{
+              color: cfg.theme.colors[colorScheme].gray,
+              gap: "1rem",
+              fontSize: "1.5rem",
+              fontFamily: fonts[1].name,
+            }}
+          >
+            {Li.map((item, index) => {
+              if (item) {
+                return <li key={index}>{item}</li>
+              }
+            })}
+          </ul>
+        </div>
+        <p
+          style={{
+            color: cfg.theme.colors[colorScheme].light,
+            fontSize: "1.5rem",
+            overflow: "hidden",
+            marginRight: "8rem",
+            textOverflow: "ellipsis",
+            display: "-webkit-box",
+            WebkitLineClamp: 7,
+            WebkitBoxOrient: "vertical",
+            lineClamp: 7,
+            fontFamily: fonts[1].name,
+          }}
+        >
+          {description}
+        </p>
+      </div>
+    </div>
+  )
+}
+```

docs/plugins/Favicon.md

@@ -0,0 +1,19 @@
+---
+title: Favicon
+tags:
+  - plugin/emitter
+---
+
+This plugin emits a `favicon.ico` into the `public` folder. It creates the favicon from `icon.png` located in the `quartz/static` folder.
+The plugin resizes `icon.png` to 48x48px to make it as small as possible.
+
+> [!note]
+> For information on how to add, remove or configure plugins, see the [[configuration#Plugins|Configuration]] page.
+
+This plugin has no configuration options.
+
+## API
+
+- Category: Emitter
+- Function name: `Plugin.Favicon()`.
+- Source: [`quartz/plugins/emitters/favicon.ts`](https://github.com/jackyzha0/quartz/blob/v4/quartz/plugins/emitters/favicon.ts).

docs/plugins/FolderPage.md

@@ -11,10 +11,12 @@ Example: [[advanced/|Advanced]]
 > [!note]
 > For information on how to add, remove or configure plugins, see the [[configuration#Plugins|Configuration]] page.
 
-This plugin has no configuration options.
-
 The pages are displayed using the `defaultListPageLayout` in `quartz.layouts.ts`. For the content, the `FolderContent` component is used. If you want to modify the layout, you must edit it directly (`quartz/components/pages/FolderContent.tsx`).
 
+This plugin accepts the following configuration options:
+
+- `sort`: A function of type `(f1: QuartzPluginData, f2: QuartzPluginData) => number{:ts}` used to sort entries. Defaults to sorting by date and tie-breaking on lexographical order.
+
 ## API
 
 - Category: Emitter

docs/plugins/Frontmatter.md

@@ -17,6 +17,54 @@ This plugin accepts the following configuration options:
 > [!warning]
 > This plugin must not be removed, otherwise Quartz will break.
 
+## List
+
+Quartz supports the following frontmatter:
+
+- title
+  - `title`
+- description
+  - `description`
+- permalink
+  - `permalink`
+- comments
+  - `comments`
+- lang
+  - `lang`
+- publish
+  - `publish`
+- draft
+  - `draft`
+- enableToc
+  - `enableToc`
+- tags
+  - `tags`
+  - `tag`
+- aliases
+  - `aliases`
+  - `alias`
+- cssclasses
+  - `cssclasses`
+  - `cssclass`
+- socialDescription
+  - `socialDescription`
+- socialImage
+  - `socialImage`
+  - `image`
+  - `cover`
+- created
+  - `created`
+  - `date`
+- modified
+  - `modified`
+  - `lastmod`
+  - `updated`
+  - `last-modified`
+- published
+  - `published`
+  - `publishDate`
+  - `date`
+
 ## API
 
 - Category: Transformer

docs/plugins/Latex.md

@@ -11,7 +11,12 @@ This plugin adds LaTeX support to Quartz. See [[features/Latex|Latex]] for more
 
 This plugin accepts the following configuration options:
 
-- `renderEngine`: the engine to use to render LaTeX equations. Can be `"katex"` for [KaTeX](https://katex.org/) or `"mathjax"` for [MathJax](https://www.mathjax.org/) [SVG rendering](https://docs.mathjax.org/en/latest/output/svg.html). Defaults to KaTeX.
+- `renderEngine`: the engine to use to render LaTeX equations. Can be `"katex"` for [KaTeX](https://katex.org/), `"mathjax"` for [MathJax](https://www.mathjax.org/) [SVG rendering](https://docs.mathjax.org/en/latest/output/svg.html), or `"typst"` for [Typst](https://typst.app/) (a new way to compose LaTeX equation). Defaults to KaTeX.
+- `customMacros`: custom macros for all LaTeX blocks. It takes the form of a key-value pair where the key is a new command name and the value is the expansion of the macro. For example: `{"\\R": "\\mathbb{R}"}`
+
+> [!note] Typst support
+>
+> Currently, typst doesn't support inline-math
 
 ## API
 

docs/plugins/ObsidianFlavoredMarkdown.md

@@ -23,6 +23,7 @@ This plugin accepts the following configuration options:
 - `enableYouTubeEmbed`: If `true` (default), enables the embedding of YouTube videos and playlists using external image Markdown syntax.
 - `enableVideoEmbed`: If `true` (default), enables the embedding of video files.
 - `enableCheckbox`: If `true`, adds support for interactive checkboxes in content. Defaults to `false`.
+- `disableBrokenWikilinks`: If `true`, replaces links to non-existent notes with a dimmed, disabled link. Defaults to `false`.
 
 > [!warning]
 > Don't remove this plugin if you're using [[Obsidian compatibility|Obsidian]] to author the content!
@@ -31,4 +32,4 @@ This plugin accepts the following configuration options:
 
 - Category: Transformer
 - Function name: `Plugin.ObsidianFlavoredMarkdown()`.
-- Source: [`quartz/plugins/transformers/toc.ts`](https://github.com/jackyzha0/quartz/blob/v4/quartz/plugins/transformers/toc.ts).
+- Source: [`quartz/plugins/transformers/ofm.ts`](https://github.com/jackyzha0/quartz/blob/v4/quartz/plugins/transformers/ofm.ts)

docs/plugins/RoamFlavoredMarkdown.md

@@ -0,0 +1,26 @@
+---
+title: RoamFlavoredMarkdown
+tags:
+  - plugin/transformer
+---
+
+This plugin provides support for [Roam Research](https://roamresearch.com) compatibility. See [[Roam Research Compatibility]] for more information.
+
+> [!note]
+> For information on how to add, remove or configure plugins, see the [[Configuration#Plugins|Configuration]] page.
+
+This plugin accepts the following configuration options:
+
+- `orComponent`: If `true` (default), converts Roam `{{ or:ONE|TWO|THREE }}` shortcodes into HTML Dropdown options.
+- `TODOComponent`: If `true` (default), converts Roam `{{[[TODO]]}}` shortcodes into HTML check boxes.
+- `DONEComponent`: If `true` (default), converts Roam `{{[[DONE]]}}` shortcodes into checked HTML check boxes.
+- `videoComponent`: If `true` (default), converts Roam `{{[[video]]:URL}}` shortcodes into embeded HTML video.
+- `audioComponent`: If `true` (default), converts Roam `{{[[audio]]:URL}}` shortcodes into embeded HTML audio.
+- `pdfComponent`: If `true` (default), converts Roam `{{[[pdf]]:URL}}` shortcodes into embeded HTML PDF viewer.
+- `blockquoteComponent`: If `true` (default), converts Roam `{{[[>]]}}` shortcodes into Quartz blockquotes.
+
+## API
+
+- Category: Transformer
+- Function name: `Plugin.RoamFlavoredMarkdown()`.
+- Source: [`quartz/plugins/transformers/roam.ts`](https://github.com/jackyzha0/quartz/blob/v4/quartz/plugins/transformers/roam.ts).

docs/plugins/TagPage.md

@@ -9,10 +9,12 @@ This plugin emits dedicated pages for each tag used in the content. See [[folder
 > [!note]
 > For information on how to add, remove or configure plugins, see the [[configuration#Plugins|Configuration]] page.
 
-This plugin has no configuration options.
-
 The pages are displayed using the `defaultListPageLayout` in `quartz.layouts.ts`. For the content, the `TagContent` component is used. If you want to modify the layout, you must edit it directly (`quartz/components/pages/TagContent.tsx`).
 
+This plugin accepts the following configuration options:
+
+- `sort`: A function of type `(f1: QuartzPluginData, f2: QuartzPluginData) => number{:ts}` used to sort entries. Defaults to sorting by date and tie-breaking on lexographical order.
+
 ## API
 
 - Category: Emitter