Zettelkasten workflow in my note-taking app Flowtelic

Flowtelic’s latest workflow update turns note-taking into a guided pipeline—capturing ideas, turning reading into study notes, processing those notes into permanent “slip box” cards, and then using the results to drive writing and publishing. The core change is that notes now carry both a **note type** (what they are) and a **workflow state** (where they are in the process), with navigation updated to reflect that structure. Instead of letting useful material sit indefinitely, the system is designed to nudge users through small, repeatable steps so knowledge compounds over time.

At the center is a Zettelkasten-inspired model. Users start with an **inbox-style capture**: “idea” notes and “study notes” (literature notes derived from reading). When an item is ready, it moves through workflow states—such as **draft** and **ready to process**—until it reaches **complete**, representing a finalized permanent note stored in the app’s “slip box.” Flowtelic frames this as a practical adaptation of the Zettelkasten method: ideas and literature notes are processed into evergreen permanent notes that are meant to be linked and reused.

Flowtelic also introduces a clearer separation of roles inside the knowledge base. **Index notes** act like a map of content (similar to MOCs in Zettelkasten terms), organized alphabetically for fast browsing and linking to related notes. **Permanent notes** represent final, evergreen thoughts—“cards” intended to connect with other cards to form a durable knowledge system. **Reference notes** are treated differently: they store reusable citations (links to blog posts, books, or pages) without workflow states, functioning as lightweight bibliographic anchors.

To connect knowledge to output, the update adds **projects** as a work layer. Projects behave like “index cards for your work,” with their own navigation and lifecycle—backlog, in progress, and completion. Study notes can be linked directly into project notes, letting reading material feed specific writing tasks. The workflow supports iterative creation: a project can be worked on in short sessions, with effort increasing as the project becomes more complete. This is positioned as the mechanism for turning non-evergreen material into publishable artifacts.

Finally, Flowtelic expands organization beyond notes and projects with **books** and **people** collections. Books let users track what they’re reading and see what study notes and outputs connect to each book. People (such as authors and public speakers) provide another linking hub—e.g., connecting articles, TED talks, and books to a single figure to trace how ideas formed and how they later show up in content.

The update is presented as a testable prototype with local storage—no server syncing, no registration—and export/import to Markdown that preserves workflow states. Upcoming features focus on workflow tooling: visualization of progress and reminders to spend time on small steps (like studying an article, generating study notes, and organizing them into the permanent store). The overall aim is consistency—keeping users moving through the pipeline rather than losing momentum for months at a time.