My input is that expanding tag and interactive tag related graph functionality in general would make obsidian much more useful and differentiated for use with real world projects and content management workflows.
In addition to supporting graph color options ― I would request and suggest adding shape-icon, and graph visualization options and functionality that support how tags are used, visualized and navigated to provides a more generalized and complete solution for managing and interacting visually with our knowledge graph and use of tags.
Below are an image and explanation to help communicate these points:
IMAGE
EXPLANATION:
A. On the left is an example panel for (1) selecting tags by pre-configured types, classes, etc. and (2) selecting graph visualization by types (just 2 here, but there are several other types commonly used by mind-mapping type apps)
B. On the main graph in the center are examples of how these visualizations might look by example. Note they are imagined as foldable visualizations and iconic on the main graph to reduce clutter. This would allow fast visual confirmation of the type of tag organization type or class is being used by the underlying content
C. On the right is an example of the pane showing the iconic visualization un-folded in the main graph showing it in full detail, color matched when the node is expanded in the main graph.
D. To provide maximum flexibility is it would be best if these selections are FILTER type selections, which could stored as views, to give the underlying content and tags and visualizations maximum flexibility depending on how the user wants to slice and dice their content in different ways to match different workflow needs. And, perhaps subsets locked into a particular style differently for each particular stored view. NOTION does this multi-view store quite well.
SAMPLE USE CASE EXAMPLES
Vault contains CONTENT user wants to partly organize and at times visualize as structured and part unstructured.
- One part or at one time visualizing KBASE to discover related concepts as a result of tagging over time
- Managing the same content but visualizing it based on different projects within the whole KBASE GRAPH or graph subsets larger than themselves see and manage: (1) hierarchies of pages, categories, tags and content for a website, (2) book, chapter, pages of a book ― and for these providing a way to (3) turning on and off different types of tags that would show concepts linked to nodes in (1), (2) while they remain visualized in a their structured form.
This type of approach might enable a very high degree of visualization and content management capability and flexibility, while being easy to use.