Dean's site

My personal site

Site Rules

3 min read

Site Rules and Vault System

note

this vault is written as a legacy of mine,
therefore it should be future proof.

1. Integration Plan

(adapted from the princes work ethics)

  • become a finisher
  • make art everyday
  • it doesn’t have to be perfect
  • sleep quality is absolute
  • vault mentality (record everything, store it)
  • design workflows that remain useful and understandable decades from now

2. Format and Compatibility

  • Always use open formats (pandoc?)
  • Prefer .odt over .docx
  • Maintain forward-compatible formats to avoid vendor lock-in
  • Keep metadata in human-readable form

3. System Philosophy

  • System should be self-reinforcing/defending
  • Minimize overhead; vault should maintain itself wherever possible
  • Structure for scalability: multiple projects, multiple contributors, long-term reference
  • Include versioning and 256-hash to confirm vault integrity to future-proof against edits, deletions, or cencoring.

4. Reviews and Automation

  • Schedule monthly and yearly reviews for both content and structure
  • Automate repetitive tasks:
    • spellcheck
    • tag or category validation
    • unresolved link notifications
  • enjoy the doing, dont make it a burden

5. Structure and Publishing Rules

  • Jhony Decibel naming scheme + evergreen/digital garden + memex-style vault
  • Public site contains polished work; 00-raw contains drafts and experimental notes
  • Publishing rules:
    • publish: true → accessible in site

Folder Structure

  • 00-raw

  • 01-projects

  • 02-resources

  • 03-digital_garden

  • Always use underscores _ for spaces

  • Include index.md in each folder for context and information.

6. Vault Philosophy

7. Folder Structure / Sorting System

7.1 Core Rules

  • Use a single vault to centralize all content
  • Reduce folder complexity to simplify navigation and maintainability
  • Migrate external content locally or at least link it
  • when linking an external thing, use an archived version
  • written in standard markdown and sometimes embedded html.
  • Always pluririze tags
  • Heavy use of internal links for interconnectivity

7.2 Folder Organization

Reference Folder

  • 02-resources/02_03-clippings — external content (essays, articles, high-quality wiki pages)

Admin Folder (hidden in navigation)

  • static_files — images, audio, template, PDFs, etc.

Raw Folder (hidden, accessible)

  • 00-raw — drafts, unpolished experiments, ‘unprofesional’ stuff
  • Always link first mentions; unresolved links act as breadcrumbs
  • Capture properties, ratings, and notes in reference files
  • Use Web Clipper for external material
  • Include timestamps or revision history for all notes
  • Maintain consistent frontmatter (tags and modified date)

7.4 Pruning, Random Revisit

  • Periodically review notes to update content, metadata, and structure
  • modified: {{date}} to track edits

Pruning

  • Use Obsidian’s unique note hotkey to log thoughts
  • Weekly compilation, monthly review, yearly meta-review
  • Preserves a fractal web of thought for analysis and historical reference

Random Note Exploration

  • Graph view exploration to find related notes

  • Reconnect older ideas to current projects

  • Opportunity for maintenance: style, metadata, internal links

  • Include script to check for broken links and missing metadata

8. Publishing to the Web

  • Markdown content edited in Obsidian, site code in Zed

  • Quartz static site generator converts Markdown to HTML

  • Deployment via GitHub GUI + GitHub Actions

  • Hosting: GitHub Pages, Neocities (CI/CD available here)

  • archive site via something like waybackmachine

9. Backup and Sync Strategy

  • Mirror site on Neocities
  • Mirror site on Nekoweb
  • Repository mirrored on Codeberg
  • Local + external USB backup via BORG BACKUP
  • Sync across devices with Syncthing
  • Maintain rolling backups for at least 10 days
  • validate backups for via hash

Graph View

Backlinks