add results of my research and a roadmap

diff --git a/doc/wishlist/do_not_make_links_backwards.mdwn b/doc/wishlist/do_not_make_links_backwards.mdwn
index f9c3673d937c4c9c3d6d9241b81e967ee0e68771..c63ed7d5553498451e00be4a00b65cf69b79f613 100644 (file)
--- a/doc/wishlist/do_not_make_links_backwards.mdwn
+++ b/doc/wishlist/do_not_make_links_backwards.mdwn
@@ -3,3 +3,14 @@ I understand this may be a bit provocative, but I strongly feel that ikiwiki lin
 Everytime i come back to ikiwiki, i need to bend my mind backwards to create *proper* links. I understand that `\[[description|link]]` is more inline with Markdown's `[description](link)` approach, but in my mind it is too much of a problem for third part plugins to be a proper justification. For example, the [[plugins/creole]] plugin works pretty much as expected *expect* for links, because it can't override ikiwiki's internal link parser. For me that's a huge inconsistency that should be fixed.
 
 If there is an agreement within the community that we can change that, I am ready to work on a migration script or even a configuration variable... -- [[anarcat]]
+
+Dev notes
+---------
+
+I started looking into this, after encouraging words from Joey ("very long term roadmap", AKA "if someone does it"). It turns out it is less deeply rooted than i thought in the core of ikiwiki; everything being a plugin and all, this is also a plugin ([[plugins/link]]).
+
+The following needs to be done:
+
+ 1. the `link_regexp` variable needs to be turned backwards (or frontwards, if you like :P)
+ 2. a config setting need to be added to the `link` plugin so that we can choose if we want backwards links or not
+ 3. a (solid!) parser needs to be written for [[ikiwiki-transition]] to change the actual links (if necessary)