Grow a Garden 2 Wiki

Community

Grow a Garden 2 Wiki Community

Send source-backed corrections, track open reviews and prepare live stock or weather reports without turning the site into an unmoderated forum.

Community input is useful only when it feeds the review workflow. Fast reports still need evidence before data changes.

active

Structured corrections

Use the correction form when a crop value, mutation multiplier, code, weather event, pet, gear, prop or live snapshot needs source-backed review.

  • Wrong or stale values
  • New source-backed entities
  • Live stock or weather reports
  • Copyright or source concerns

Reports must include a source URL, screenshot note or reproducible in-game observation before data changes.

Open
active

Review queue

Track known gaps before they become published database changes.

  • Checking whether a report is already known
  • Prioritizing high-risk data
  • Seeing which pages a change affects

High-impact reports stay in review until evidence and affected pages are both clear.

Open
needs setup

Discord entry

Discord should be launched only after rules, source requirements and moderation ownership are ready.

  • Fast weather sightings
  • Stock screenshots
  • Community testing sessions

Do not publish a public invite until spam handling and data-verification rules exist.

Open
active

GitHub issue intake

Open a structured GitHub issue when a source-backed correction should enter the public review trail.

  • Structured correction reports
  • Source-backed data patches
  • Audit trail before deployment

Issue intake needs a public repository URL before the site can link users to a real destination.

Open

Discord readiness

Discord should be a fast reporting lane, not the source of truth. Launch it only with pinned rules for screenshots, source URLs, event timestamps and no-copy policy.

  • Create channels for weather, stock, corrections and moderator review.
  • Require evidence before any report becomes data.
  • Route accepted reports into the review queue and changelog.

GitHub issue intake

Because this site is statically exported, a public GitHub issue template is the cleanest first backend. The repository now includes .github/ISSUE_TEMPLATE/data-correction.yml, and the correction form creates report text that can be pasted into an issue. The email draft uses support@growa-garden2.wiki as the intended domain mailbox; configure it before relying on email intake.

Create reportData processOpen GitHub issue