🧭 what this is

this is not a strict plan.

it is a direction map for where the chaos garden is going, what needs more structure, and which areas are starting to form paths.

the goal is not to finish everything. the goal is to make the garden easier to use, easier to return to, and easier to grow without turning into a drawer full of haunted cables.

🌱 core idea

the garden is becoming a connected system for:

  • daily life
  • patterns
  • creative experiments
  • faith notes
  • second life notes
  • tools and workflows
  • archives and scraps
  • things that help me function

🧱 foundation

core pages that explain what the garden is and how it works:

🗺️ main maps

these are the main navigation hubs.

🌿 making it usable

current usability goals:

  • connect related notes with markdown backlinks
  • keep yaml useful but not overloaded
  • add “go here next” links where helpful
  • reduce dead-end pages
  • make map pages clear and skimmable
  • keep pages useful before making them elegant
  • avoid creating too many almost-identical pages

🧠 patterns system / live mode

pattern pages are for recurring life/weather/brain/work/creative patterns. live mode is for quick “where am i and what do i do next?” navigation.

possible areas:

pattern goal

make repeated experiences easier to recognize and route through.

not every pattern needs a solution. sometimes naming it is already a small lantern.

live mode goal

reduce thinking while using the system.

when energy is low, the garden should offer paths, not demand architecture.

🎨 creative expansion

creative pages can hold art experiments, prompt systems, visual thinking, and process notes.

possible pages:

🙏 faith expansion

faith pages can collect prayer, spiritual reading, saints, and grounding practices.

possible pages:

🌍 second life expansion

second life pages can document identity play, places, social notes, venue notes, style, and online experience.

possible pages:

🧺 archive expansion

archive pages are for things worth saving that do not need to become polished notes yet.

possible collections:

  • jokes
  • screenshots
  • comment responses
  • strange phrases
  • cursed lists
  • unfinished ideas
  • tiny observations
  • scraps that might become notes later

main page:

🧩 current priorities

a. build the core map layer

  • create pages that are repeatedly linked
  • remove links that do not need to exist yet
  • turn repeated dead links into “possible future notes” sections

c. improve navigation

  • add connections sections to important notes
  • keep map pages short enough to scan
  • add “main paths” near the top of maps
  • use consistent page names

d. polish public-facing pages

  • check tone
  • avoid private details
  • remove actual local paths
  • keep public explanations clear
  • add affiliate disclosure where needed

e. improve system support

  • build quick state-routing notes
  • create low-energy fallback pages
  • make task/life patterns easier to find
  • keep useful notes from vanishing into the compost fog

🪴 garden stages

seed

rough capture. useful because it exists.

growing

has structure and can be revisited.

evergreen

stable, useful, and worth linking often.

compost

old, messy, abandoned, or partially useful material that can feed future notes.

🧭 naming / structure rules

  • lowercase filenames
  • kebab-case filenames
  • no spaces in filenames
  • expressive page titles are fine
  • use markdown links for relationships
  • keep yaml light
  • use map pages for navigation
  • use archive pages for loose collections
  • do not delete useful mess too quickly

🧭 connections

🧺 loose scraps

  • not a plan, a compass
  • build paths before palaces
  • maps reduce friction
  • useful before elegant
  • fewer perfect systems, more returnable trails
  • the garden should help when the brain is foggy