My personal public notes managed with Logseq.

Logseq Version: 0.10.14

This repository contains the source for my personal knowledge garden.

• assets/: Contains static assets like images and PDFs referenced in the notes.
• journals/: Daily notes and journal entries.
• logseq/: Logseq configuration files and metadata.
• pages/: The main content of the knowledge base, containing individual notes and pages.

This project uses GitHub Actions for continuous integration and deployment.

• CI (.github/workflows/main.yml): This workflow is triggered on pushes to the main branch. It uses the official logseq/publish-spa action (v0.3.0) with Logseq version 0.10.14 to build the static site and then deploys it to GitHub Pages (the gh-pages branch).
• Test (.github/workflows/test.yml): This workflow allows for manual triggering (workflow_dispatch). It builds the site with the same action and version, then copies a custom CSS file, useful for testing build integrity and style changes.

• Adding Notes: Notes are added by creating Markdown files in the pages/ or journals/ directories.
• Deployment: Changes pushed to the main branch are automatically built and deployed to https://pengx17.github.io/knowledge-garden/#/all-journals.

This repository uses pixi for Python dependency management and task execution.

Install pixi (if not already installed):

curl -fsSL https://pixi.sh/install.sh | bash

Install project dependencies:

pixi install

• Fix Hierarchy: Validates and fixes the type field in all markdown files to ensure they reference their immediate parent folder:

  pixi run fix-hierarchy

• Cleanup Metadata: Removes redundant metadata fields (feature:, **Parent:** lines):

  pixi run cleanup-metadata

See the specs/002-update-architecture/ directory for detailed architecture documentation:

• categories_structure.md: Complete hierarchical structure of all 17 domains
• hierarchy_principle.md: Explains the "Immediate Parent Principle" for type fields
• cleanup_summary.md: Summary of metadata cleanup (removed 65 feature: fields and 117 **Parent:** lines)
• structured_architecture.md: Core architectural principles and navigation rules
• tasks.md: Implementation task tracking