The Core Idea
Allow property values to act as triggers. Selecting a specific predetermined value in a property should automatically inject additional, related properties or execute commands (like inserting a dynamic template).
Use case or problem
Currently, managing broad categories requires either massive, cluttered templates or juggling dozens of highly specific ones. For example, I use a general “Software” template that applies to everything from operating systems to audio plugins.
As a second-level classifier, I use a Software Type property (which might be “Audio Effect Plugins,” “DAWs,” or “OS”). Depending on that second-level choice, I need completely different sub-properties injected into the note (e.g., “Plugin Extension” for audio effects, or “OS Family” for an operating system).
Implementing this would automate the use of dynamic templates and adapt perfectly to multi-level classification. It would also pair exceptionally well with existing community requests for multi-level YAML suggestions.
Proposed solution
Implement a cascading, conditional system within the native properties UI.
If I select “Software” in my Categories property, it automatically generates the 3-4 basic properties I need for all software.
If I then set the Software Type property to “Audio Effect Plugins,” it instantly adds another 3-4 properties specifically associated with that type.
UI Suggestion: It would be helpful to have a small visual indicator (like a green dot or distinct symbol) right next to these automated properties so the user knows they were dynamically generated. Additionally, these conditional triggers must be able to support internal wikilinks ([[pages]]) as property values.
Current workaround (optional)
The current workaround is to maintain a huge library of hyper-specific templates and manually insert each one depending on the context of the note, which is slow and disrupts the workflow.