up:: Agorideans - Dashboard
tags:: #agorideans #meta #guide
owner:: @Niko
status:: #status/wip

Collaborator Guide

Welcome to the La Finka Digital Garden ( Obsidian Vault ). This document outlines how to set up your environment, collaborate on content, and follow best practices for contributing to this knowledge base.

Purpose

This vault is version-controlled with Git to allow multiple collaborators to work concurrently. Notes are published to a digital garden by the lead maintainer. Your role is to contribute, edit, and sync notes while maintaining vault structure and standards.

Requirements

Before beginning, install the following:

• Git
• Obsidian
• A GitHub account (read/write access to the repo will be granted)
  • Message Niko at lafinka@pm.me with your account info to get access.

Setup Instructions

Git is best managed through the cmd-line or Terminal

1. Clone the Repository

Clone the vault repository to your local machine using Git:

git clone https://github.com/your-org/your-vault.git
cd your-vault

Open the cloned folder as a vault in Obsidian.

2. Obsidian Configuration

The .obsidian folder is tracked in Git, so your plugins and settings should be automatically configured. If not, install:

• Dataview (required)
• Templater (required)
• Any additional community plugins listed in the vault

Make sure Safe Mode is off (Settings > Community Plugins).

3. Daily Workflow

Before you start working:

git pull

This ensures you’re working from the latest version.

Create or edit notes:

• Follow naming conventions
• Use internal links ([[Page Name]]) liberally
• Use existing tags or consult tag-index.md if available

After you're done:

git add .
git commit -m "Brief summary of changes"
git push

Avoid committing broken links or empty notes. Keep commits meaningful and atomic.

Branching and Publishing

• Work directly on the dev branch unless instructed otherwise.
• Only the lead maintainer publishes the vault to the digital garden.
• The digital garden excludes notes with private: true in the frontmatter.

Frontmatter Standards

Each note should begin with:

ToDo:: Start from a template (Basic Formatting for everything or others)

Dataview Guidelines

• Use standardized tags (e.g., #project, #status/idea, #role/facilitator)
• Avoid using inline fields unless part of a recognized format
• Test queries before committing new dataview blocks

If you're unsure how to structure a Dataview query, refer to dataview-guide.md if available. Or better yet - ask GPT to write what you want in dataviewjs as it behaves better in the digital garden.

Best Practices

• Write clearly and concisely
• Use wikilinks instead of raw markdown links when possible
• Avoid renaming files without checking for existing links
• Do not push large binary files (images should be optimized)

Troubleshooting

Merge Conflicts

If you get a merge conflict:

git pull --rebase

Manually resolve conflicts in Obsidian or a code editor, then:

git add .
git rebase --continue

Sync Issues

If your push is rejected:

git pull --rebase
# resolve any conflicts
git push

Questions

If you're unsure about anything, contact the lead maintainer before pushing. Always pull before editing and push after making changes.

1. Ask GPT
2. Contact Niko

Created: 250516-16:38

Updated: 250516-16:58