cli + tui to publish to leaflet (wip) & manage tasks, notes & watch/read lists 🍃
desertthunder.dev
charm
leaflet
readability
golang
1---
2title: Article Organization
3sidebar_label: Organization
4description: Filter your archive, add lightweight tags, and keep backups tidy.
5sidebar_position: 3
6---
7
8# Article Organization
9
10## Filter by Author or Title
11
12`noteleaf article list` accepts both a free-form query (matches the title) and dedicated flags:
13
14```sh
15# Anything with "SQLite" in the title
16noteleaf article list SQLite
17
18# Limit to a single author
19noteleaf article list --author "Ada Palmer"
20
21# Cap the output for quick reviews
22noteleaf article list --author "Ada Palmer" --limit 3
23```
24
25Because the database stores created timestamps, results come back with the newest article first, making it easy to run weekly reviews.
26
27## Tagging Articles
28
29There is no first-class tagging UI yet, but Markdown files are yours to edit. Common patterns:
30
31```markdown
32---
33tags: [distributed-systems, reference]
34project: moonshot
35---
36```
37
38Drop that block right after the generated metadata and tools like `rg` or `ripgrep --json` can surface tagged snippets instantly. You can also maintain a separate note that lists article IDs per topic if you prefer not to edit the captured files.
39
40## Read vs Unread
41
42Opening an article in the terminal does not flip a status flag. Use one of these lightweight conventions instead:
43
44- Prefix the Markdown filename with `read-` once you are done.
45- Keep a running checklist note (e.g., “Articles Inbox”) that references IDs and mark them off as you read them.
46- Create a task linked to the article ID (`todo add "Summarize article #14"`), then close the task when you finish.
47
48All three approaches work today and will map cleanly to future built-in read/unread tracking.
49
50## Archiving and Backups
51
52The archive lives under `articles_dir`. By default that is `<data_dir>/articles`, where `<data_dir>` depends on your OS:
53
54| Platform | Default |
55|----------|---------|
56| Linux | `~/.local/share/noteleaf/articles` |
57| macOS | `~/Library/Application Support/noteleaf/articles` |
58| Windows | `%LOCALAPPDATA%\noteleaf\articles` |
59
60You can override the location via the `articles_dir` setting in `~/.config/noteleaf/.noteleaf.conf.toml` (or by pointing `NOTELEAF_DATA_DIR` to a different root before launching the CLI).
61
62Because every import produces Markdown + HTML, the directory is perfect for version control:
63
64```sh
65cd ~/.local/share/noteleaf/articles
66git init
67git add .
68git commit -m "Initial snapshot of article archive"
69```
70
71Pair that with your cloud backup tool of choice and you have a durable, fully-offline knowledge base that still integrates seamlessly with Noteleaf’s search commands.