This is mean to be a second brain. An all-in-one personal management system. The goal is to allow one to store notes, todo lists, schedules, thoughts, etc. in a single location. It includes:

• A derivative of markdown which you can visualize in the browser, which utilizes Markdown It.
• Useful functions and shortcuts for managing information in the markdown files.
• Fast file searching through a simple and predictable plain-text format. Currently I have 300 pages, at 38,000 lines, and can still immediately find what I need.

Originally I had set to replicate the zettelkasten technique more closely, where each line was a different thought with a unique id and various tags. You could then query thoughts with certain tags. Although conceptually very interesting, I didn't actually find it useful. It allowed a purely flat layout of all my thoughts. However it had a few flaws:

• It was complicated.
• I was never encouraged to actually think and integrate my thoughts into something more meaningful as I would rely on the tag system to organize my notes.
• It discouraged thinking deeply about concepts.
• By design, it lacks a single source of truth for concepts. I'm limited

I found this new system better:

• Have a couple core files:
  • Structure: is the most importantt. It is a single file that links to all my other notes. Using vim's folding, You can get an overview of the main domains of your wikipedia, or dive down. You can put the same article in multiple locations. This allows you to continue a graph-like knowledge base, while attaching a lot of information, depth, and thought into each thought.
  • Storage: this is a collection of all my old files/thoughts that it will not search through. Good for stuff I will probably never need again, but keep there just in case.
  • Resources:
  • Schedule:
  • Projects:
  • Inbox: a file that somewhat matches the original zettelkasten. Each 'unique' id is the line number. You can add tags to each line.
• Prefix lines with tags such as - #one#two# This is my line text. Provides a natural, intuitive way to organize thoughts that can still be easily searched. Provides a natural, intuitive way to organize thoughts that can still be easily searched.
• To still express the graph knowledge that the zettelkasten provides, I've found a hybrid approach of within your articles, add subheadings that refer to or connect ideas to other articles. Which is exactly what wikipedia does.

However this is not how I think. Overtime, I found my usecase of a note system closely mirrored a personal wikipedia. I would have 10s-100s of articles that I could quickly search.

• Zettelkasten (german for note "zettel" desk "kasten") was a note taking system popularized by Niklas Luhmann, a very prolific sociologist.
• Cortex, latin for bark. Its found in the word "neocortex" and "cerebral cortex". The neocortex is a key component in cognition. The Zortex is meant to be a sort of second brain.

• rsync: transfer local wiki to remote server through SSH
• bat: preview files
• fd: sourcing files

• https://github.com/iamcco/markdown-preview.nvim

  • Integrates with markdown-it and vim to preview markdown-type buffers in the browser
  • Converted class components to functional components
  • Changed variables from "g:mkdp**" to "g:zortex**"

• https://github.com/markdown-it/markdown-it

  • Provides wonderful markdown processing in the browser

• https://github.com/alok/notational-fzf-vim

  • Integrates with fzf to search note system

It only works on vim >= 8.1 and neovim

Preview markdown on your modern browser with synchronised scrolling and flexible configuration

Main features:

• Cross platform (macos/linux/windows)
• Synchronised scrolling
• Fast asynchronous updates
• Katex for typesetting of math
• Plantuml
• Mermaid
• Chart.js
• sequence-diagrams
• flowchart
• dot
• Toc
• Emoji
• Task lists
• Local images
• Flexible configuration

" If you have node.js and yarn
Plug "t-wilkinson/zortex.nvim", { 'do': 'cd app && yarn install' }

• Please take a look at plugin/zortex.vim for config defaults and documentation

Commands:

:ZortexSearch
:ZortexSearchUnique

:ZortexCopyZettelId
:ZortexCopyZettel
:ZortexBranchToOutline
:ZortexBranchToArticle
:ZortexListitemToZettel
:ZortexResourceToZettel
:ZortexOpenStructure

:ZortexStartServer " call this before preview
:ZortexStopServer
:ZortexPreview
:ZortexPreviewStop
:ZortexPreviewToggle

• coc.nvim
• @chemzqm/neovim
• chart.js
• highlight
• neovim/node-client
• next.js
• markdown.css
• markdown-it
• markdown-it-katex
• markdown-it-plantuml
• markdown-it-chart
• mermaid
• opener
• sequence-diagrams
• socket.io

• I like to open a split browser in full screen next to my terminal window.

• Change the FZF title when searching so you don't see that super long shortened path.
• Convert original resource link to tag setup [name]{author=...; ref=...} -> #author=...#[name](ref)
• When searching files, initially populate each file with only the article names for quick searching. it is possible to do some form of multiprocessing

• The left side of search should be either the modified or created article time and the article name.
• Each file should be named a unique article name.
• Searching should be plain text using rg or fzf. rg or fzf should get each article file path and return the name of each match and if possible the matching phrase.
• It might be better to do a custom searching window using a lazyvim plugin.

Better file names: [] Write script to move the article name and remove the article name? We would be limited by os by file names. Also wouldn't ease code if we are still doing aliases.

An enhanced calendar system for Neovim that integrates with your OKR, PARA, and GTD note-taking system.

• Unified Calendar View: Shows tasks from both calendar.zortex and projects.zortex files
• Telescope Integration: Searchable digest view of dates and projects
• Project Task Integration: Automatically displays project tasks with date/time attributes in the calendar
• Header Preservation: Fixed the bug where adding entries would delete file headers
• Multiple Views: Month view with 3-month display and week view
• Smart Task Detection: Recognizes tasks with @due, @at, and time prefixes (HH:MM)

Place the Lua files in your Neovim configuration:

~/.config/nvim/lua/zortex/calendar/
├── init.lua
├── data.lua
├── ui.lua
├── projects.lua
└── telescope.lua

Add to your Neovim configuration:

require('zortex.calendar').setup({
  notes_dir = "~/path/to/your/notes",  -- Directory containing .zortex files
  keymaps = {
    open_calendar = "<leader>zc",       -- Open calendar view
    telescope_digest = "<leader>zd",    -- Open Telescope digest
    today_digest = "<leader>zt",        -- Show today's digest notification
  }
})

• :ZortexCalendar - Open the calendar view
• :ZortexDigest - Open Telescope digest view (calendar + projects)
• :ZortexCalendarTelescope - Calendar-only Telescope view
• :ZortexTodayDigest - Show today's tasks/events as notification
• :ZortexSetupNotifications - Setup system notifications for events

In the calendar view:

• h/l - Navigate days
• j/k - Navigate weeks
• J/K - Navigate months
• H/L - Navigate years
• w - Switch to week view
• m - Switch to month view
• a - Add entry for selected date
• <CR> - Go to selected date in calendar file
• t - Jump to today
• q/<Esc> - Close calendar

The digest view shows:

• Calendar Dates: Searchable by MM-DD-YYYY or long date format
• Projects: Searchable by project name or area (parent heading)

Each project shows:

• Project name with area in brackets
• Number of tasks
• All tasks, resources, and notes in preview

Article Name
tags: #tag1 #tag2

01-15-2024:
  - [ ] Task with no time
  - 10:00 Meeting with team
  - [x] Completed task @due(2024-01-20)
  - [ ] Task with notification @notify(30min)

Article Name
tags: #projects #para

# Work

## Project Alpha
- [ ] Design mockups @due(2024-01-20)
- [ ] 14:00 Client presentation @at(2024-01-18)
- [x] Setup repository
Resources:
- Design guidelines document
- Client feedback form

## Project Beta
- [ ] Code review @due(2024-01-19 15:00)
- [ ] Deploy to staging

Both calendar and project tasks support:

• @due(YYYY-MM-DD) or @due(MM-DD-YYYY) - Due date
• @at(YYYY-MM-DD HH:MM) - Specific date/time
• @from(date) / @to(date) - Date ranges
• @repeat(daily/weekly) - Recurring tasks
• @notify(30min) or @n(1h) - Notifications
• HH:MM prefix - Time for the task
• HH:MM-HH:MM prefix - Time range

• [25] - Selected date
• >15 - Today's date
• .10 - Date with tasks
• ●20 - Date with events
• *5 - Date with notes
• ☐ - Incomplete task
• ☑ - Complete task
• ⚠ - Important task
• ◐ - In progress task
• ⏸ - Paused task

1. Project Tasks in Calendar: Any project task with date/time attributes will automatically appear in the calendar view for that date.

2. Quick Search: Use the Telescope digest to quickly find any date or project. The search works with partial matches.

3. Project Context: When viewing project tasks in the calendar, the project name appears in brackets [Project Name] for context.

4. Notifications: Use @notify(30min) to get system notifications before events. Run :ZortexSetupNotifications to schedule them.

If file headers are being deleted when adding entries:

• The fix has been applied to preserve headers
• Headers are any lines before the first date entry
• Make sure your calendar.zortex has proper date format: MM-DD-YYYY:

For best notification support on macOS, install one of:

1. terminal-notifier (Recommended): brew install terminal-notifier

2. alerter: brew install alerter

Without these, notifications may not appear due to macOS security restrictions on terminal apps.

After installing, restart Neovim and try again.

Alternative: Use :ZortexDigest for buffer view

Files in our zortex:

• vision.zortex: File that doesn't link to anything. Purely conceptual vision of who I want to be and what I want to focus on.
• okr.zortex:
  • Objectives:
    • Objectives have a one to many (usually 1-4) relationship with key results.
    • Each Objective will have the heading of "## YYYY MM Title"
    • Span codes: M, Q, Y, 5Y, 10Y, Y
  • Key results:
    • Will formatted as "- KR-" so KR-1, KR-2, etc.
    • Will link to a project via zortex link starting with "[Projects/...]" or "[P/...]"
  • Current objectives will be under the heading "# Current"
  • Previous objectives will be under the heading "# Previous", sorted by "YYYY MM" with most recent at the top.
• projects.zortex:
  • Projects are the first-class citizens of the XP system. That importance is delegated by connections to the okr system.
  • Projects provide a grouping for tasks, notes, resources.
• for now ignore files like areas.zortex

XP calculation: Total XP = (Base XP * Multipliers) Base XP:

• Connection to OKR: If a project is connected to a key result should increase base XP rewarded. Multipliers:
• Current OKR: Less XP the more distant the temporal colocation
• Priority: Higher priority tasks @p1, @p2, @p3 get an XP multiplier.
• Importance: @i1, @i2, @i3 get an XP multiplier
• Size: tasks that have a size (@xs @sm @md @lg @xl) Larger tasks (@lg, @xl) or larger time estimation @est() or duration @2h are worth more. Let config.yaml specify defaults, but assume tasks to be a certain size/time duration. Let me know what you choose. Have an alignment for each task size to a specific duration.

┌──────────────┐     ┌─────────────┐     ┌──────────────┐     ┌─────────────┐
│ Zortex.nvim  │────▶│ API Gateway │────▶│    Lambda    │────▶│  DynamoDB   │
│   (Client)   │     │   (HTTPS)   │     │  (Manifest   │     │   (State)   │
└──────────────┘     └─────────────┘     │  Processor)  │     └─────────────┘
                                         └──────────────┘              │
                                                   │                   │
                                                   ▼                   ▼
                                          ┌──────────────┐     ┌──────────────┐
                                          │ EventBridge  │────▶│   Lambda     │
                                          │ (Scheduler)  │     │(Notification │
                                          └──────────────┘     │   Sender)    │
                                                               └──────┬───────┘
                                                                      │
                                                                      ▼
                                                              ┌──────────────┐
                                                              │  ntfy.sh     │
                                                              │   (Push)     │
                                                              └──────────────┘

📊 Dual XP System:

1️⃣. Area XP (Long-term Mastery)

• Earned from completing objectives
• Uses exponential level curve (1000 * level^2.5)
• 75% bubbles up to parent areas
• Time horizon multipliers:
  • Daily: 0.1x
  • Weekly: 0.25x
  • Monthly: 0.5x
  • Quarterly: 1.0x
  • Yearly: 3.0x
  • 5-Year: 10.0x

2️⃣. Project XP (Seasonal Momentum)

• Earned from completing tasks
• 3-stage reward structure:
  • Initiation (tasks 1-3): 100 XP with 2x multiplier
  • Execution (middle tasks): 20 XP each
  • Completion (final task): 5x multiplier + 200 XP bonus
• 10% transfers to linked areas
• Seasonal levels: 100 * level^1.2