But ... (You just knew there had to be a "but" coming.)

Use the parent nodes for hierarchical ordering.

Hmm, I was about to point out how the dynamically built searches (ala AntiFUD) were easier to do. But that requires new pages to have special formatting within them to work. Proper parent nodes don't take any longer to do. And parent nodes can be nested. Yeah, probably better to do it that way.

BTW that means I'll probably be pulling the IWE prefix entirely from topic names, rather than changing it to IWT.

Damn. Time to ge re-do a couple bunches of files again. This work-in-progress stuff is tedious.

IWE => IWT works for me (this also gives us TWIT, which may also work ;-)

I guess that makes us TWITs.

The whole site is IWeThey. It would be like seeing:
microsoft.com/mswindows
microsoft.com/msaccess
microsoft.com/msexcel
microsoft.com/msoutlook

For trademark purposes they should include MS in the logos and text, but after a while you've pretty much figured out you're on MS's site and the prefix doesn't add any context to the links.

The exception (on TWikIWeThey) is for meta topics. eg: IwtSuggestions, IwtWelcome. But IwtOS? Doesn't convey any information.

Actually, while discovering that you've started putting some stuff in the Know web, I realized I like the way they did the OS names: MacOS, SolarisOS, etc. And the auto-searches and webforms are nice, too. I need to start looking at how they work. BTW they really need better documentation on the search function. There are apparently lots of undocumented switches.

Rejiggering pages and locations in general isn't a good thing to do as it breaks links ... TWiki is about gradualism and incremental change.

Screw backwards compatibility![1]




















[1] ;)