• Do not register here on develop.twiki.org, login with your twiki.org account.
• Use View topic Item7848 for generic doc work for TWiki-6.1.1. Use View topic Item7851 for doc work on extensions that are not part of a release. More... Close
• Anything you create or change in standard webs (Main, TWiki, Sandbox etc) will be automatically reverted on every SVN update.
Does this site look broken?. Use the LitterTray web for test cases.

Good navigation is essential for large TWiki sites, such as described in TWiki:Codev.HomePageNavigation

The breadcrumb should be changed from:

  • You are here: Bugs > Parent(s) > Item577
  • You are here: Foo Bar home > Bugs web > Parent(s) > Item577

That is, start with WIKITOOLNAME home, and add web to the WEB.

Not all TWiki sites use all webs. Some sites use webs as separate sites, and WIKITOOLNAME home is not communicated.

But if multiple webs are used - I guess in most cases - I agree that the breadcrumb should lead you there.


Most behind firewall customers (TWiki:TWikiMission) have multiple webs, so starting breadcrumb at WIKITOOLNAME home makes sense.

In fact, at large installations it even makes sense to start with the Intranet home, e.g.

  • You are here: Intranet > Foo Bar home > Bugs web > Parent(s) > Item577
but I do not recommend this for the default TWiki distribution.


why does the summary say "needs to include _web_"? it already does include the web name.


The breadcrumb already includes the name of the web, it needs also the text "web". A small change, but consistent terminology helps in reducing the "surprise factor". New content indicated in red:
  • You are here: Foo Bar home > Bugs web > Parent(s) > Item577


How are nested web recognized? Should they be marked with 'web' as well? (I guess so)

While I understand the motivation to put 'web' in the breadcrumb, I've always had mixed feelings towards the name 'web', so I've always downplayed the term. No WebChanges but Changes in links and titles, etc. To put 'web' in the breadcrumb hardcodes the term.


I agree. Web is a confusing term for all manager types. I tend to relabel them areas. Kwiki calls them workspaces.


Arthur: Yes, multiple webs should show text "web" multiple times. If not, user is confused and does not know where is the web / topic parent boundary.

  • OK, let me rephrase: how can this be detected? -- AC
  • Does it need to be detected? The parent topic trail is done with %META{"parent" nowebhome="on" suffix=" >"}%. I do not know how the web trail is done; question for the multi-web implementer -- PTh

Hey guys, just because you do not like an offical term does not justify hiding it. Hiding a term is not consistent and causes confusion for the end user. As long as webs are called webs we should use the term consistently.


SVN 7021. 'Web' is now added to the first %WEB%. If nested webs need the web text too please raise a new bug. AC

Summary Breadcrumb needs to include web
ReportedBy PeterThoeny
AppliesTo Engine
Priority Enhancement
CurrentState Closed

Edit | Attach | Watch | Print version | History: r13 < r12 < r11 < r10 < r9 | Backlinks | Raw View |  Raw edit | More topic actions
Topic revision: r13 - 2005-10-13 - ArthurClemens
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback