Mimi Yin wrote:
What about a whole family of Chandler Project Wikis
+ Product Wiki
+ Planning Wiki
+ Developer Wiki
+ Teams Wiki
+ Notes Wiki
I'm not entirely sure what you're asking here.
Like, if you have to refer to one of our "silos of content" in copy,
you'd use "Foo Wiki" over "Foo web" or "Foo area"?
Yeah, seems fine. The internal TWiki name is "webs", but it shouldn't
ever expose itself in practice.
For reference, picking a "wiki" name expresses itself it 2 ways:
+ The URL you see for pages in that wiki, ala: /Developer/NeatPage
+ The navigation we're likely to put in the top nav (they should
probably match though technically I can put well-nigh any string into
the nav, independent of the
As a reminder, the impact of creating a new wiki area is essentially:
+ You see it in the URL
+ Search defaults to searching only within the current web
+ Some extra pages need to be kept in sync to make the extra web work
like the others
Most people have probably long-since forgotten the offer, but for
reference, the "big wiki upgrade" a while back also provided us the
ability to do "hierarchical webs" so you could have pages like
"/Notes/JaredRhine/SvkNotes" (and not interfere with any other SvkNotes
pages anyone had created). Nifty, if we find a use for it, where the
URLs are just getting messy/too long :)
-- Jared
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "General" mailing list
http://lists.osafoundation.org/mailman/listinfo/general
