X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/blobdiff_plain/bcd338531f7fb2f327d0ab12c726113e034dd07f..12f86df239e8a6c1d554d86b5c56e2b8713f6cd8:/doc/todo/toplevel_index.mdwn

diff --git a/doc/todo/toplevel_index.mdwn b/doc/todo/toplevel_index.mdwn
index f5eba96a2..92cef99ac 100644
--- a/doc/todo/toplevel_index.mdwn
+++ b/doc/todo/toplevel_index.mdwn
@@ -1,13 +1,20 @@
 Some inconsistences around the toplevel [[index]] page:
 
 * [[ikiwiki]] is a separate page; links to [[ikiwiki]] should better go to
-  the [[index]] though.
+  the index though.
+
+  > At least for this wiki, I turned out to have a use for [[ikiwiki]]
+  > pointing to a different page, though the general point might still
+  > stand.
+
 * The toplevel [[ikiwiki/Discussion]] page has some weird parentlinks
   behavior. This could be special cased around with the following patch.
   However, I'm unsure if I like the idea of more special cases around this.
   It would be better to find a way to make the toplevel index page not be a
   special case at all.
 
+Here is a patch:
+
 	--- IkiWiki/Render.pm   (revision 1187)
 	+++ IkiWiki/Render.pm   (working copy)
 	@@ -71,6 +71,7 @@
@@ -19,45 +26,12 @@ Some inconsistences around the toplevel [[index]] page:
 	                if (! $skip) {
 	                        $path.="../";
 
+   > Came up with a better patch for this, [[done]] --[[Joey]]
+
 ---
 
 > I would like to suggest another tack, namely a bigger, better special case. 
 > The basic idea is that all indices of the form foo/bar/index get the wiki path foo/bar.
-> This makes some things more elegant:
->
-> * All files having to do with foo/bar are in the foo/bar directory, rather 
->   than the (admittedly minor) wart of having the index be in foo/.
-> * This sort of addresses [[bugs/broken_parentlinks]] in that example/ is 
->   guaranteed to be a valid path. (There might be no index there, though.)
-> * This is more in line with standard HTML practice, as far as I understand it,
->   namely that linking to a/b means a/b/index.html rather than a/b.html.
->
-> This would change the inline plugin in strange ways -- I think if foo/index.html
-> contains \[[inline "* and !*/Discussion"]], it should skip inlining foo/index.html 
-> explicitly, but would inline index pages in child directories 
-> foo/bar/baz/index.html as bar/baz.
->
-> It always bothers me that foo/bar/ files need a foo/bar.html in front of them, 
-> rather than a foo/bar/index.html, as is (to my mind) traditional.
-> 
-> Ethan
->
-> Hmm, now I've had time to think about this, and this does conflict pretty hard with foo.html/Discussion 
-> pages. Well, back to the drawing board.
->
-> Well, it seems unlikely that you'll have both foo/bar.html and foo/bar/index.html, 
-> so why not accept either as foo/bar? This would both preserve backwards
-> compatibility, as well as allow foo/bar/Discussion.
->
-> Ethan
->
-> No, in order for this to work, the wiki path foo/bar/baz could be any of:
->
-> * foo/bar/baz.html
-> * foo/index/bar/index/baz.html
-> * foo/bar/index/baz.html
-> * foo/bar/index/baz/index.html
->
-> Or many others. Which is probably even hackier than having both foo.html and foo/.
->
-> Ethan
\ No newline at end of file
+> You could do this today using [[todo/index.html_allowed]], except that the toplevel 
+> page "index" becomes "", which causes all sorts of chaos. The discussion page would 
+> become /discussion, and the weird parentlinks behavior would go away. --Ethan