From 220811c46f8bbc0e39d032a36612fb8819386f64 Mon Sep 17 00:00:00 2001 From: joey Date: Sun, 25 Feb 2007 21:22:46 +0000 Subject: web commit by http://ethan.betacantrips.com/: clarify -- I think relative pagespecs make more sense to new users --- doc/roadmap/discussion.mdwn | 21 ++++++++++++++++++++- 1 file changed, 20 insertions(+), 1 deletion(-) diff --git a/doc/roadmap/discussion.mdwn b/doc/roadmap/discussion.mdwn index 8b956ae9c..b9ad5d10e 100644 --- a/doc/roadmap/discussion.mdwn +++ b/doc/roadmap/discussion.mdwn @@ -9,4 +9,23 @@ have pagespecs be absolute by default, IMHO. --[[Joey]] I think after you work with ikiwiki for a while, it "makes more sense" for them to be absolute, but I definitely remember tripping over absolute -pagespecs a few times when I was just starting out. --Ethan \ No newline at end of file +pagespecs a few times when I was just starting out. Thus I think we've +learned to accept it as natural, where a new user wouldn't. + +* bugs, todo, news, blog, users, sandbox, and patchqueue + are all at "toplevel", so they are equivalent whether + pagespecs are absolute or relative. +* soc doesn't refer to any pages explicitly so it doesn't matter +* various plugins have pagespecs at plugins/foo.mdwn: map, linkmap, orphans, + pagecount, pagestats + * I'd say most of these make more sense as having abs. pagespecs + * I note that your sitemap is at toplevel, but there's no reason + not to allow putting it in a special meta/ directory. +* examples/blog and examples/software site need to have relative pagespecs, + but they're pretty special cases -- for a real site those things + will probably be toplevel +* plugins/contrib makes more sense to inline relative (though it doesn't + right now) + +Maybe inline should use relative pagespecs by default, and other plugins +don't? --Ethan \ No newline at end of file -- cgit v1.2.3