Dominic Hargreaves wrote: My personal interest is in disabling the prefixes entirely. I'm running into situations where Category Foo is just a @REDIRECT to Foo, or vice-versa, and the same applies to Locales. I don't see any reason to prefix the node names with "Category" or "Locale" when that information is presented by whether the node is in category "Category" or category "Locale". The node http://manchester.openguides.org/?Category_Hitching indicates that people are confused by the prefixes. Category Hitching is not a category, it's just a node with that name in front. I suspect it's called that because the other links in http://manchester.openguides.org/?Category_Transport all start with "Category" and the user was merely following suit. I don't see that dropping prefixes will do any harm, other than the hassle of refactoring the database for *existing* guides, and I think it will make OpenGuides more usable. However, when it came to implementing it, I saw #53 and decided to make the prefix a customisable string rather than a boolean, since I was mucking around with the code anyway. Dave