Skip to content

docs: clarify Quartz Syncer / dg3 / Netlify public garden path - #126

Draft
oldwinter wants to merge 1 commit into
mainfrom
cursor/clarify-garden-publish-path-503c
Draft

oldwinter wants to merge 1 commit into
mainfrom
cursor/clarify-garden-publish-path-503c

Conversation

@oldwinter

Copy link
Copy Markdown
Owner

Docs-only. Clarifies the live public garden publish path for contributors, without changing deploy config.

Current path (as of this repo + dg3)

  1. This vault (knowledge-garden): set publish: true on a note.
  2. Obsidian Quartz Syncer command Open publication center copies those files into oldwinter/dg3 content/.
  3. Netlify builds Quartz from dg3 (netlify.toml).
  4. Site: https://garden.oldwinter.top (baseUrl in dg3 quartz.config.yaml).

There is still no publish_by_frontmatter.py at the repo root. Quartz Syncer is the only publish path.

Predecessor, not coupled

digital-garden-ai is an archived Vite + React experiment. It is not Quartz, not dg3, and is not on this vault’s publish path. The docs name it only to stop that mix-up.

Stale links / facts fixed

  • Daily web-publish tutorial no longer says dg3 currently deploys on Vercel.
  • Roadmap typo garden.oldwiner.top → garden.oldwinter.top.
  • Gone repo github.com/oldwinter/digital-garden (404) replaced with dg / dg3.
  • Missing wiki targets: obsidian jekyll发布方案, quartz-themes; dropped [[quartz syncer token]].
  • Typo wiki obsidian pubilsh 官方方案 → obsidian publish 发布.

Historical Jekyll (oldwinter/dg, notes.oldwinter.top) and Obsidian Publish (oldwinter.top) remain listed as non-primary.

Verify

node --test scripts/*.mjs — 35 passed, 0 failed.

Open in Web Open in Cursor 

Document the live public garden path for contributors, mark
digital-garden-ai as an uncoupled archived predecessor, and fix
stale publish links (Vercel vs Netlify, garden.oldwiner.top,
missing wiki targets, gone digital-garden repo).

Co-authored-by: oldwinter <cdd2zju@gmail.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants