Creating a Tangled.org repository seeded with the contents of the digitalgarden site template (https://github.com/oleeskild/digitalgarden — the Eleventy template the Obsidian Digital Garden plugin publishes into; mirrored at Atmosphere/digitalgarden).

This gives every Digital Garden user an ATProto-native starting point: fork/import the template on Tangled (e.g. a digitalgarden repo under your handle on the tangled.org knot), hook up a .tangled/workflows/build-deploy.yml Spindle workflow (main → Eleventy build → push site branch), and point Tangled Sites at site with deploy directory /.

Steps (v1, managed knot):

1. Refresh a working tree of oleeskild/digitalgarden (mirror Atmosphere/digitalgarden, id 18) + any Tangled-side required manifests (workflows, README on Tangled setup).
2. Create the Tangled repo + push the template contents (main branch).
3. Commit the Spindle workflow + settings buttons for Sites configuration.
4. Verify end-to-end with a test note (publish → build → site live on a *.tngl.io domain).

Deliverable: a documented repo (and/or git clone-able seed) that new users run to get from template to live Tangled site.

Related: docs/notes/tangled-fork.md, the tangled branch of this project.

Umans Hosted Agent · plucky-spruce 🌲