website

docs/modules/website.md

@@ -93,26 +93,59 @@ name, platform, price, slot range, image status, and location count visible.
 
 ## Navigation
 
-Website footer account links are state-aware:
+The shared header uses one responsive navigation implementation for every public
+page.
 
-- logged out: `Account Login`, `Order a Server`, `Control Panel`
-- logged in: `My Account`, `Order a Server`, `Control Panel`, `My Servers`, `Log Out`
-- staff-only links appear only for Panel admin users and still enforce website staff authorization server-side
+Primary links:
 
-The shared header uses one responsive navigation bar:
+- Home
+- Game Servers
+- Pricing
+- Locations
+- Panel Features
+- Documentation
+- Support
 
-- primary links: Home, Game Servers, Documentation, Support
-- account menu: Login/Create Account/Cart or My Account/My Orders/My Servers/Cart/Staff Dashboard/Logout
-- action links: Custom Projects and Control Panel
+Account area:
 
-Pricing and locations remain available as website pages and footer links, but they
-are summarized on the homepage instead of being prominent main navigation items.
+- logged out: Login, Create Account, Cart
+- logged in: My Account, My Orders, My Servers, Cart, Logout
+- staff-only: Staff Dashboard
+
+Right-side actions:
+
+- Custom Projects
+- Control Panel
+
+`Panel Features` is a website information page that explains the customer
+benefits of the GSP Panel. `Control Panel` is the direct external action that
+opens the operational Panel at the configured Panel URL.
+
+The footer should contain only one modest `Control Panel` link. Public pages,
+especially the homepage, must not repeat Control Panel promotions unnecessarily.
 
 Control Panel links point directly to the configured Panel domain. `My Servers`
 opens a website customer page that summarizes website orders and links to the
 Panel for live server controls. Staff Dashboard opens the website sales/billing
 staff area, not Panel activity logging.
 
+## Public Copy Policy
+
+Public website copy must never repeat developer instructions, prompt wording,
+acceptance criteria, task rationale, or explanations about where content belongs.
+Internal requirements must be translated into polished customer-facing language.
+
+Avoid public wording such as:
+
+- "belongs on"
+- "summarized here"
+- "visitors can get oriented"
+- "another sales page"
+- "as requested"
+- "this section was moved"
+
+Use direct customer-facing language instead.
+
 ## Deployment
 
 Recommended:
@@ -132,6 +165,7 @@ Recommended:
 - `docs.php`
 - `pricing.php`
 - `locations.php`
+- `panel_features.php`
 - `support.php`
 - `login.php`
 - `register.php`