On 3/5/06, Martin Cooper <[EMAIL PROTECTED]> wrote: > On 3/5/06, Niall Pemberton <[EMAIL PROTECTED]> wrote: > > > > On 3/4/06, Rahul Akolkar <[EMAIL PROTECTED]> wrote: <snip/> > > > > > > Perhaps use WikiNames (instead of wikinames)? When the subpage title > > > is a single word, it doesn't help much, but otherwise, that is one of > > > the basic premises of wikis (WikiNames become hyperlinks!) > > > > > > That way when you get to longer URLs, such as (may get fragmented) ... > > > > > > > > http://wiki.apache.org/jakarta-taglibs/ReusableDialogComponents/Tutorials/IntegrateWithXHTML > > > > > > ... the consistency of using WikiNames may help. > > > > Thanks for the comments Rahul. So maybe prefixing everything with > > "Shale" rather than "shale/" would be a better idea i.e. > > "ShaleArticles" rather than "shale/articles" - although the "/" makes > > it looks like its organised in a typicall web hierarchy - I believe in > > the case of the wiki it just means theres a "/" in the page name? > > > How about "Shale/Articles"? The '/' is just a character in the page name, > but always using leading caps makes for consistent page names when we might > have "parent" or "child" page names that are themselves wiki words (e.g. > "WebWork/Migration"). > <snap/>
+1, the '/' gives you the *logical* structure -- a parent-child relationship (a.k.a subpages) -- as you pointed out in the initial post to this thread (manifests itself via the "Show Parent" link at the top left each wiki page). Thats orthogonal to page names being in WikiCase (even if they are single words). -Rahul > -- > Martin Cooper > > > Niall > > > > > FWIW ;-) > > > > > > -Rahul > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
