Getting Help With Outpost

Welcome & Orientation
1

Use Site Feedback when something in Outpost appears broken, unclear or difficult to use.

Before creating a new Discussion, check whether someone has already reported the same problem. Add useful new information to an existing Discussion when it clearly describes the same issue.

What to include

A useful report usually includes:

  • the Space, Zone or Discussion involved;

  • the page address;

  • what you were trying to do;

  • the steps immediately before the problem;

  • what you expected to happen;

  • what happened instead;

  • the exact error message;

  • whether the problem happens again when you retry;

  • whether it appears limited to your account;

  • your device and browser when they may matter;

  • a screenshot when it helps explain the issue.

Use a specific title such as:

Cannot reply in the Tahoe Trails Rendezvous Zone

or:

Invitation says new account registrations are not allowed

Avoid titles such as Help, Broken or It does not work.

Protect private information

Do not post passwords, login codes, private invitation links, payment information or other sensitive account details.

Describe the problem without exposing private information. Staff may ask to continue privately when account-specific details are necessary.

Use current instructions

The Outpost interface and the software underneath it change over time. Old screenshots, menu paths and troubleshooting instructions may no longer apply.

Technical guidance should be checked against the current Outpost interface and the current underlying software version before anyone treats it as authoritative.

Public help should use Outpost language whenever possible. The name Discourse or an underlying interface term may appear when it is necessary to identify the software, an official help source, a setting or a technical label that cannot be renamed.

Where to report different problems

Use Site Feedback for:

  • interface problems;

  • incorrect or confusing instructions;

  • broken links;

  • unexpected access behavior;

  • feature suggestions;

  • copy corrections;

  • ideas for improving Outpost.

Use the relevant Land & Community Region for changing trail conditions, access information and place-specific resource corrections.

Use flags for harassment, spam, prohibited commercial activity, private information or other conduct problems.

A detailed report makes it easier to distinguish an interface problem, a settings issue, an access boundary and a problem affecting the wider site.