-
Notifications
You must be signed in to change notification settings - Fork 14
Wiki links should use relative addressing #14
Comments
Good idea. To do this would require doing more checking during page rendering. Currently, rendering is very unintelligent. It takes whatever text is there and make a hyperlink out of it. Later, when the hyperlink is clicked, MarkWiki checks if the pages exist to determine whether to show it or show the create page view. Your suggestion would require checking the existence of a page during rendering for this reason: if you add The same kind of issue occurs when you want to create a new page. When you create a new I'll have to think about the implications to the modeling and user experience to see if there is a clean and consistent way to handle this. I'm open to suggestions. |
My intention is that [[baz]] inside [[foo/bar]] always means [[foo/baz]] and never [[baz]], even if [[baz]] already exists. |
ok, that seems like a reasonable answer for viewing. There is still the challenge for page creation. Any ideas for what that would look like? One idea would be if that I add |
That sounds sensible; I think that would be intuitive behaviour. It also might make sense if what you've called "title" was labelled "address" or "identifier" on the edit page since that's what it is. (While we're about talking names, "Create a Wiki" doesn't create a wiki, it creates a page in a wiki, and "Save Wiki" saves a page not a wiki so maybe those names should be changed). |
Consider if I am in page
[[foo/bar]]
and I add a link[[baz]]
. This points to the page/baz.md
not/foo/baz.md
as I would prefer.The advantage of relative addressing is that one could have a whole load of pages in a directory, all pointing to each other, and that directory can be moved anywhere in the wiki directory tree and it would still work.
The text was updated successfully, but these errors were encountered: