I am increasingly realizing there are some settings I would like to set differently for different Documents. But today, all documents are treated the same.
There is value in that simplicity. But Legend’s flexibility and power mean that I use Legend for many very different functions – and different functions demand different configurations. I believe all of the suggestions below would substantially improve Legend’s power and flexibility. I suggest that users are able, for each of their Documents, to choose:
1) If new items are created at top or bottom of Outline (“first in, first out” workflow vs. “first in, last out”)
2) Default prefix for new items (document for Task-management vs. note-taking vs. content creation)
3) Default sync-to calendar (useful for having separate “work” and “personal” Documents/Boards)
4) #Tag management (longstanding user-requested feature)
5) Agenda pane configuration (relocated from general Settings)
6) Sharing permissions and users (inevitable, collaboration)
7) Which item dates (created, modified, completed, etc.) are user-editable (for Journaling)
For #4, note that #tags are already handled on a per-document basis (the auto-fill menu is different depending on the doc you’re in). So this makes a lot of sense to do in a doc-config dialog. Users (besides me!) have been asking for #tag management (nesting, find/replace, swap/rename, delete all) for quite some time. So long in fact that you can’t even find most of those requests on Slack because they’ve fallen behind the event horizon. A document config dialog would be an excellent place to put such a manager, akin to the existing pane in Settings that controls display of Agenda Panes.
Finally, I suggest the current “Archive” feature gets a major overhaul. Archiving individual items is confusing at best, creates an opening for both perceived and actual data loss, and is difficult to employ meaningfully. Instead, use the document-config dialog to Archive entire documents (they get their own spot in the Overview drawer, above the Trash). This has an immediately relevant use-case, as Documents can then be used as discrete containers for clients, projects, events, etc. which are handled, closed, and then retained.
