creation_date: 2024-03-17 modification_date: 2024-03-17 author: Jimmy Briggs jimmy.briggs@jimbrig.com tags:

• Type/Readme
• Topic/Meta
• Status/Ongoing aliases:
• No Clocks Vault
• Vault Readme publish: true permalink: description: image: cssclasses:

• 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.

title: Contents 
style: nestedList # TOC style (nestedList|inlineFirstLevel)
minLevel: 1 # Include headings from the specified level
maxLevel: 4 # Include headings up to the specified level
includeLinks: true # Make headings clickable
debugInConsole: false # Print debug info in Obsidian console

About

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

Some notes:

• [[Obsidian - Setup]]
• [[Obsidian - Folders]]
• [[Obsidian - Scripts]]
• [[Obsidian - Themes]]
• [[Obsidian - CSS Snippets]]
• [[Obsidian - Community Plugins]]

The Changelog is also a good Meta resource.

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

Roadmap

• [ ] TODO

Publishing Setup

• This repository has three main branches: [main], [develop], and [gh-pages].
  • The [main] branch is a representation of the [develop] branch, but with all obsidian wiki-links converted to GitHub markdown links for display on GitHub as well as _README.md files converted to README.md for display on GitHub.
  • The [develop] branch mirrors what I actually work with while inside the Obsidian application and gets sync'd automatically.
  • The [gh-pages] branch is deployed using [MkDocs]() and [GitHub Actions]().
  • Links are converted using the rust library [Obsidian-Export].
  • Links for deployment are converted using the [mkdocs-roamlinks]() plugin.

Check out the various [GitHub Actions] utilized to enable this entire process.

Maps of Content

If this vault serves as my version of [a second brain](), then Maps of Content or MOC's are the underlying mechanism for navigating and connecting the knowledge contained within the vault to form a complex, structured system.

In other words MOC's serve as structural, index notes that list related [Atomic Notes]() in a single location.

Utilize Maps of Content (MOCs) to navigate the vault efficiently.

Some Maps of Content to consider are:

Content

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

• Code Snippets
• Lists of Resources
• Checklists
• Slipbox Atomic Notes
• Guides and How-To's
• Lessons Learned
• Daily Notes
• Templates
• Best Practices
• Documentation
• Tools by Category
• Mindsweeps
• Goals and Learning Notes
• Project Support Notes
• Notes about People and Agendas
• Definitions
• Embedded Websites
• Kanban Boards
• MindMaps
• Highlights from a variety of sources
• Clippings from the Web
• Podcast Notes

And More!

Code Snippets

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