Navigation and pages
Navigation
Section titled “Navigation”Admin → Navigation edits three separate navigations — Public site, Admin and Player portal — each with the same tools: rename an entry, reorder it, hide it, group entries into a dropdown section, or add a link of your own.
A fresh site’s public nav is the seeded one: the portal, News, Screenshots, Five on Friday, Newsletter, the wiki, and About. Until you change anything, the nav “renders exactly as coded” — there is no stored copy to drift from the code.
Two properties are worth understanding before you rely on this screen.
It advertises; it does not authorise. Renaming or hiding an entry changes what is listed, never what exists or who may reach it. Hiding Wiki does not close the wiki. Access is decided by roles and by a module’s visibility settings, and this screen “can never show anyone a link their role, or the visibility settings of an installed module, would hide”.
You only edit what you can see. Entries hidden from you — by your role, or by a module’s visibility rules — are not listed, and they keep whatever setting they already had. So an administrator’s view of this screen is not necessarily the whole nav, and editing it cannot damage the parts you cannot see.
Reset to default discards your customisation for that nav and goes back to the coded one. It is per-nav, not global.
Admin → Pages composes standalone pages from blocks. A published page is live at its
slug — /about, /rules, /donate — and a draft is visible only to staff.
This is the right tool for content that is not news and not a wiki article: the pages a navigation entry points at. A page you create is not linked from anywhere until you add it in Navigation — deliberately, because the two are separate decisions.
For everything else — news posts, the newsletter, screenshots, the wiki — see Content.