As a Wagneer, I want to be able to designate a reference site with a card, then do something like 'reference site+page name' or 'page name+reference site' and get an external link with 'page name' as the link text.
Ideally we can find a wagneering solution that doesn't require any development level changes or custom mods.
I think the wagn way has to be with using the reference site card as a tag. So 'page name+wikipedia' and wikipedia+*right+*structure and other rules to implement it.
Thinking about this more. I think what I really want is to have a related feature integrated into the link editor. Or a plugin that work like some of the link editor features.
I guess I need to understand what is planned for the link editor a little. It has to work with the content editor (tinyMCE unless we change that too), but does in need to work with any other editors?
So, if tinyMCE, I imagine at least one new button on the toolbar for links. This would look just like the same button for the tinyMCE link editor, but add ours. Or is the solution likely to be very different from this?
Whatever the solution for links generally, this would be a subcase of external links where maybe it uses a search API on the referenced site to get choices based for an autocomplete UI. The page name from the selected completion would go in the link text where you could change it further without further changing the link target.
Do you think I should revamp this ticket for that and connect it to the link editor work?
this is about nests/view syntax, not link syntax. Link syntax doesn't involve card content.
I think I explained and named it badly (again). What would work for me is easily creating [[http://some.site/prefix/Name|Name]] in content, which is why I'm thinking link editor. If you have a different useful idea based on mine ...
A solution that involves automagically creating a URI card named Name, or SomeTrunk+Name linked to http://some.site/prefix/Name seems fine too. But, the output syntax might need tweaking to see Name for SomeTrunk+Name when desired.
+discussed in support tickets+relevant user stories