README

No Clocks Knowledge Vault

Website | GitHub Repo

Curated Knowledge for the Masses

---

support@noclocks.dev | www.noclocks.dev

---

Welcome

Welcome to the Knowledge Vault for No Clocks, LLC.

Inside is a wealth of knowledge curated over our tenure as a business while pursuing and widening our knowledge across the technology sector.

The vault is structured loosely as a Zettelkasten, or a collection of interlinked Atomic Notes about anything that has resonated with our work and was deemed worthy of including.

Consider this a Digital Garden. It is a garden that needs to be maintained and cared for overtime to produce fruitful outcomes.

About

Check out the 05-SYSTEM/Meta Folder for details about this Obsidian Vault and its setup:

• PHILOSOPHY: Vault’s over-arching philosophy.
• TAGS: Tag System
• PLUGINS: Plugin Usage
• THEMES: Custom Vault Themes
• AGENTS: LLM Usage Details

The Changelog is also a good Meta resource.

Launch this vault directly via the Obsidian URI Schema: obsidian://open?vault=NoClocksVault.

Publishing Setup

This repository uses a three-branch workflow with Quartz for publishing:

Branch	Purpose	Trigger
develop	Raw Obsidian content with wikilinks	Local Obsidian Git sync
main	GitHub-viewable content (converted links)	Auto from develop push
gh-pages	Deployed Quartz site	Auto from main push

How it works:

1. develop branch: The actual Obsidian vault content with [[wikilinks]] and index.md files. This is where Obsidian Git syncs to.

2. main branch: Automatically generated from develop via GitHub Actions:

   • [[wikilinks]] converted to standard markdown links using obsidian-export
   • index.md files renamed to README.md for GitHub navigation
   • Force pushed to maintain clean history

3. gh-pages branch: Quartz static site deployed automatically:

   • Triggered after main branch updates
   • Full-text search, graph view, backlinks, and more
   • Published to docs.noclocks.dev/noclocksvault

Check out the GitHub Actions workflows for implementation details.

Vault Philosophy

This vault is a knowledge base, not a task manager. The guiding principle:

Your vault stores YOUR knowledge, not duplicated documentation.

• Link to official docs rather than copying them
• Capture your insights - what you learned, your customizations, your opinions
• Curate references - organized lists with external links
• Connect ideas - liberal use of wikilinks and MOCs

Project documentation stays with projects (in repos, etc.). This vault is for cross-project, transferable knowledge.

Maps of Content

MOCs serve as structural index notes that aggregate related content across the vault. They live in 03-AREAS/ and use Dataview queries to dynamically list related notes.

Current MOCs:

• MOC - Development - General Development
• MOC - R - R programming ecosystem
• MOC - Geospatial - Geographic Information Systems
• MOC - PKM - Personal Knowledge Management

Naming Conventions

Notes use type prefixes for organization, with aliases for clean wikilinks:

Type	Pattern	Example
MOC	MOC - {Topic}.md	MOC - R.md
Code	Code - {Lang} - {Desc}.md	Code - R - Shiny Helpers.md
Definition	Definition - {Term}.md	Definition - API.md
List	List - {Category}.md	List - DevOps Tools.md
Guide	Guide - {Topic}.md	Guide - Local Dev Setup.md
Checklist	Checklist - {Topic}.md	Checklist - Deployment.md

Tag Taxonomy

Tags follow a flat, combinable structure:

• Status/: Complete, WIP, Draft, Ongoing
• Type/: MOC, Code, Definition, List, Guide, Checklist, Daily, etc.
• Topic/: R, Python, GIS, DevOps, Cloud, Business, etc.

See PHILOSOPHY and TAGS for complete documentation

Structure

The vault follows a deliberate structure optimized for knowledge management rather than task management.

NoClocksVaultNew/
  00-INBOX/         # Quick capture entry point
  01-SLIPBOX/       # Atomic, polished permanent notes
  02-JOURNAL/       # Temporal notes (Daily, Weekly, Monthly)
  03-AREAS/         # MOCs - global knowledge indices
  04-RESOURCES/     # Typed reference knowledge
  05-SYSTEM/        # Vault configuration and meta
  99-ARCHIVES/      # Inactive content
  quartz/           # Quartz publishing configuration

Folder	Purpose
00-INBOX	Quick capture, unsorted incoming notes
01-SLIPBOX	Atomic permanent notes (pure ideas, non-typed)
02-JOURNAL	Temporal notes: Daily, Weekly, Monthly, Quarterly, Annual
03-AREAS	MOCs (Maps of Content) - global knowledge indices
04-RESOURCES	Typed knowledge: Code, Definitions, Lists, Guides, Checklists
05-SYSTEM	Vault meta: Templates, Assets, Configuration
99-ARCHIVES	Inactive/deprecated content

Knowledge Flow

CAPTURE → PROCESS → NAVIGATE → REFERENCE

1. Capture: Quick thoughts go to Inbox (or via Daily notes)
2. Process: Route to appropriate location based on type
3. Navigate: MOCs provide global indices across topics
4. Reference: Find what you need when you need it

For detailed philosophy and conventions, see PHILOSOPHY.

Content

The vault has a variety of content including, but not limited to:

• Inbox
• Slipbox
• Journal
  • 2024
  • 2025
• Areas
  • Development Map of Content
  • GIS Map of Content
  • PKM Map of Content
  • R Map of Content
• Resources
  • Checklists
  • Code Snippets
  • Definitions
  • Embedded Websites
  • Guides
  • Lists

Code Snippets

See the Code folder’s README for details on all of the code snippets included inside this vault.

---