This document demonstrates all standard Markdown features along with proper sidenote usage. Sidenotes work great with lists to provide additional context for specific items without breaking the list flow. For more information about building effective knowledge bases, check out Building a Personal Knowledge Base. Basic Typography Sidenotes work great with lists to provide additional context for specific items without breaking the list flow. 11. Bold text and italic text are straightforward.

This document demonstrates all standard Markdown features along with proper sidenote usage. This resource is the central reference for all content creators building a Digital Garden or implementing the Zettelkasten Method. Basic Typography Effective typography forms the foundation of digital writing. As explained by 11., consistent formatting improves readability. Recent studies 22. show that proper formatting significantly impacts user engagement. As demonstrated in previous research 2, this approach has been validated multiple times.

Development Tips Serving exampleSite For theme development, use this command to serve the exampleSite with debug options: hugo server \ --source exampleSite \ # Point to exampleSite directory --noHTTPCache \ # Disable HTTP caching --renderToMemory \ # Render to memory --disableFastRender \ # Disable fast render --ignoreCache \ # Ignore cache --gc \ # Run garbage collection --logLevel debug \ # Set debug log level -D # Include draft posts Command Explanation --source exampleSite: Serves the example site instead of the main project --noHTTPCache: Prevents browser caching during development --renderToMemory: Renders pages in memory for faster development --disableFastRender: Forces full re-render of changed pages --ignoreCache: Ignores the cache when rebuilding --gc: Runs garbage collection after builds --logLevel debug: Shows detailed debug information -D: Includes draft content Local Testing For production testing, remove debug flags:

Deploying to GitHub Pages with Hugo This guide explains how to deploy your PKB-theme site to GitHub Pages using Hugo’s built-in capabilities. Prerequisites Hugo Extended version installed Git repository initialized GitHub account PKB-theme installed as a submodule Configuration Steps Update config.toml baseURL = "https://username.github.io/repository-name/" theme = "PKB-theme" publishDir = "docs" # Required for GitHub Pages Create GitHub Workflow Create .github/workflows/hugo.yml: name: Deploy Hugo site on: push: branches: - main jobs: deploy: runs-on: ubuntu-latest steps: - uses: actions/checkout@v3 with: submodules: true fetch-depth: 0 - name: Setup Hugo uses: peaceiris/actions-hugo@v2 with: hugo-version: 'latest' extended: true - name: Build run: hugo --minify - name: Deploy uses: peaceiris/actions-gh-pages@v3 with: github_token: ${{ secrets.

Deploying with exampleSite The PKB-theme includes an exampleSite directory that serves as both a demo and a template for your own site. Quick Start Copy exampleSite Contents cp -r themes/PKB-theme/exampleSite/* . Update Configuration Edit config.toml: baseURL = "https://your-username.github.io/your-site/" title = "Your Site Title" theme = "PKB-theme" Customize Content Modify content in content/ directory Update images in static/ directory Adjust layouts in layouts/ if needed Directory Structure The exampleSite provides a complete structure:

Setting up GitHub Pages with PKB-theme This guide explains how to set up GitHub Pages for your PKB-theme repository. Important Files _config.yml - Main Jekyll configuration file Gemfile - Ruby dependencies for GitHub Pages index.md - Your homepage content _layouts/ - Theme layout files assets/ - Static files like CSS, images, etc. Setup Steps Configure _config.yml Ensure your _config.yml has the correct theme settings: remote_theme: username/PKB-theme Enable GitHub Pages Go to your repository settings Navigate to “Pages” in the sidebar Under “Source”, select: Branch: main (or your preferred branch) Folder: / (root) Click “Save” Verify Gemfile

Analytics Configuration for PKB-theme This document describes how to configure various self-hosted analytics options for your PKB-theme website. Available Analytics Providers PKB-theme supports the following privacy-focused analytics providers: Matomo (formerly Piwik) Plausible Umami Fathom Lite Shynet Configuration Add the following to your config.toml or hugo.toml file: [params.analytics] # Uncomment and configure the analytics system you want to use # Matomo Analytics # matomo = true # matomoSiteId = "1" # matomoURL = "https://analytics.

Matomo Analytics for PKB-theme This guide provides detailed instructions for integrating Matomo Analytics with your PKB-theme. Matomo is a powerful, privacy-focused alternative to Google Analytics that gives you complete control over your data. Why Choose Matomo? Matomo (formerly Piwik) offers several advantages: Full data ownership: All data stays on your server Privacy compliance: Built-in GDPR, CCPA, and cookie law compliance tools Feature parity: Similar features to Google Analytics No data limits: Analyze unlimited websites and users Customizable: Extensive API and plugin system Installation Options Option 1: Docker Installation (Recommended) Create a docker-compose.

Self-Hosted Analytics for PKB-theme This guide helps you implement visitor analytics for your PKB-theme using privacy-respecting, FOSS (Free and Open Source Software) solutions. Unlike commercial analytics platforms that collect excessive data and track users across sites, these tools focus on essential metrics while respecting user privacy. Analytics Solutions Comparison Solution Technologies Size Privacy Features Complexity Key Advantages Limitations Plausible Elixir/PostgreSQL <1KB No cookies, GDPR compliant Easy Lightweight script, simple dashboard Limited segmentation compared to Matomo Umami Next.