Welcome @intrinsical,
Perhaps @jeremyruston would be a good one to answer this?
Recently I learned more on this;
Including for missing tiddlers, which completes the circle. I have already come to the idea of building a cascade for that.
- Here is the next big step in this endeavour Exploring default tiddler links hackability in V5.3.0
However the “low hanging fruit” is to build a macro or template, perhaps with a custom Editor Toolbar button to assist, and design the “link as you desire”; For example<<link-macro "link or tiddler title">>or{{link or tiddler title||link-template}}and you can freely design your link-macro or link-template to do all you dream of. - Within your design you could introduce a cascade for such links.
- The advantage here is you nominate which links these apply to
In time I will share more but my approach includes;
- Do everything to avoid a core change
- If a core change is necessary ask for a minimalist one which empowers hackability whist minimising complexity.
- Until you have a core change or overwrites. invest in good macro or template design, because they can be used once a core hack is found.
Ultimately what you ask for can be very empowering but it also “fiddles with the fundamentals” and thus needs a higher level of rigor than other changes.
- Most of the current link handling was developed in early TiddlyWiki, the cascades are fairly recent.
- A lot of parts use links so if adding features you can get unexpected outcomes. Macros and transclusion templates are more targeted, used when needed, and thus do not have as many unexpected outcomes.
Conclusion
So look around, a lot of people have developed solutions that change link behaviour from popup previews to extra functionality (without JavaScript of any kind). Macros and templates work well and their use can be simplified with custom Editor toolbar buttons.
Perhaps search and ask for the actual solutions to ;