Merge pull request #8 from World-Domination-Software/copilot/cleanup-and-connect-documentation

Author: iaretechnician

.github/workflows/wiki-sync.yml

@@ -6,6 +6,7 @@ on:
       - main
     paths:
       - 'docs/**'
+      - 'wiki/**'
       - 'README.md'
       - 'SUPPORT.md'
       - 'CONTRIBUTING.md'
@@ -40,38 +41,45 @@ jobs:
         env:
           WIKI_TOKEN: ${{ secrets.WIKI_TOKEN }}
         run: |
-          git clone "https://x-access-token:${WIKI_TOKEN}@github.com/World-Domination-Software/Projects.wiki.git" wiki
+          git clone "https://x-access-token:${WIKI_TOKEN}@github.com/World-Domination-Software/Projects.wiki.git" wiki-repo
 
       - name: Copy markdown docs into wiki root (flat)
         run: |
           shopt -s nullglob
           # Copy top-level docs/*.md into wiki root
           for file in docs/*.md; do
             base="$(basename "$file")"
-            echo "Copying $file -> wiki/$base"
-            cp "$file" "wiki/$base"
+            echo "Copying $file -> wiki-repo/$base"
+            cp "$file" "wiki-repo/$base"
+          done
+
+          # Copy wiki/*.md files into wiki root (these are the primary wiki page sources)
+          for file in wiki/*.md; do
+            base="$(basename "$file")"
+            echo "Copying $file -> wiki-repo/$base"
+            cp "$file" "wiki-repo/$base"
           done
 
           # Copy key root docs into wiki root
           for file in README.md SUPPORT.md CONTRIBUTING.md; do
             if [ -f "$file" ]; then
-              echo "Copying $file -> wiki/$file"
-              cp "$file" "wiki/$file"
+              echo "Copying $file -> wiki-repo/$file"
+              cp "$file" "wiki-repo/$file"
             fi
           done
 
       - name: Sync documentation images (banner and icons)
         run: |
           if [ -d docs/images ]; then
-            mkdir -p wiki/images
-            echo "Syncing docs/images -> wiki/images"
-            cp -R docs/images/* wiki/images/
+            mkdir -p wiki-repo/images
+            echo "Syncing docs/images -> wiki-repo/images"
+            cp -R docs/images/* wiki-repo/images/
           else
             echo "No docs/images directory to sync."
           fi
 
       - name: Commit and push changes to wiki
-        working-directory: wiki
+        working-directory: wiki-repo
         run: |
           if [ -n "$(git status --porcelain)" ]; then
             git add .

wiki/Bug-Reporting.md

@@ -0,0 +1,60 @@
+# Bug Reporting
+
+A clear, detailed bug report helps us investigate and fix issues faster.
+
+## Choosing the Right Template
+
+When filing an issue in this repository, select the template that best matches your problem:
+
+| Template | Use for |
+|---|---|
+| **Bug report** | Gameplay or UI problems |
+| **Crash report** | Crashes, hard freezes, or forced restarts |
+| **Performance issue** | Low FPS, stuttering, or unusually long load times |
+| **Multiplayer / online issue** | Connection, matchmaking, or sync problems |
+
+➡️ [Open an Issue](https://github.com/World-Domination-Software/Projects/issues/new/choose)
+
+## What to Include
+
+The more detail you provide, the faster we can investigate. Try to include:
+
+- **Platform** – Windows, Linux, macOS, Android, iOS, Steam Deck, or other.
+- **Game version / build** – Shown on the main menu, launcher, or store page.
+- **Steps to reproduce** – Instructions someone else can follow from a fresh start.
+- **Expected vs. actual behavior** – What you thought would happen vs. what did happen.
+- **Frequency** – Does it happen every time, sometimes, or only once?
+- **Logs or error messages** – Short excerpts showing relevant errors (avoid including personal data).
+
+## Example of a Good Bug Report
+
+> **Summary:** Inventory item disappears when dragged onto quickbar.
+>
+> **Steps to reproduce:**
+> 1. Start a new game.
+> 2. Pick up any item.
+> 3. Drag it onto quickbar slot 1.
+>
+> **Expected:** The item appears in slot 1 and remains in inventory.
+>
+> **Actual:** The item disappears from both the inventory and quickbar.
+>
+> **Frequency:** Every time. **Platform:** Windows 11. **Build:** v1.3.2.
+
+## Before Filing
+
+It helps to check first:
+
+- Search [existing issues](https://github.com/World-Domination-Software/Projects/issues) for similar reports — including closed issues.
+- Try the steps in [[Troubleshooting-Index]] to rule out common causes.
+- If you are not sure it is a bug, start a [Support Discussion](https://github.com/World-Domination-Software/Projects/discussions) instead.
+
+## After Filing
+
+- A maintainer will label your issue (`triage`, `needs-info`, `confirmed`, etc.).
+- We may ask for additional details if we cannot reproduce the problem.
+- Once fixed, the issue will be labeled `fixed` and closed when the fix ships.
+
+---
+
+**→ [[Home]] · [[Troubleshooting-Index]] · [[Support]] · [[FAQ]]**

wiki/Community-and-Discussions.md

@@ -0,0 +1,65 @@
+# Community and Discussions
+
+GitHub Discussions is our primary channel for community interaction. This page explains where to ask questions, report bugs, follow the roadmap, and participate in the WDS community.
+
+---
+
+## Where to Ask Questions
+
+Use **Discussions** when you:
+
+- Need troubleshooting help but are not sure it is a bug.
+- Have questions about features, platforms, or settings.
+- Want to share general feedback or ideas.
+
+Before posting:
+- Browse existing topics in the relevant support or Q&A category.
+- Search by keyword — your question may already have an answer.
+- Keep titles descriptive so others can find similar discussions.
+
+➡️ [Browse Discussions](https://github.com/World-Domination-Software/Projects/discussions)
+
+---
+
+## Where to Report Bugs
+
+Use **Issues** when you have a clear, reproducible problem:
+
+- A repeatable gameplay or UI bug.
+- A crash, hard freeze, or save corruption.
+- A multiplayer connectivity problem.
+- Significant performance problems that persist after basic troubleshooting.
+
+If you are unsure whether to open an Issue or a Discussion — start with a Discussion. Maintainers can convert it to an Issue if needed.
+
+➡️ See [[Bug-Reporting]] for templates and guidance.
+
+---
+
+## Where to Follow the Roadmap
+
+Our roadmap lives in the **Roadmap** category of Discussions. This is where we share planned work and where the community can comment and react.
+
+➡️ [Roadmap Discussions](https://github.com/World-Domination-Software/Projects/discussions/categories/roadmap)
+
+To follow updates:
+1. Open the Roadmap category.
+2. Use the **Watch / notification** control on the page to follow new posts and comments.
+3. React with emojis for quick feedback, or comment when you have specific input.
+
+See also [[Roadmap]] for an overview of current focus areas.
+
+---
+
+## How to Participate
+
+We welcome community participation. To keep discussions useful and professional:
+
+- Be specific and constructive — general feedback is helpful; specific examples are better.
+- Stay on topic within categories. Support questions belong in support categories; ideas in the ideas or roadmap categories.
+- Search before posting to avoid duplicate threads.
+- Report bugs with the detail described in [[Bug-Reporting]] so they can be investigated efficiently.
+
+---
+
+**→ [[Home]] · [[Bug-Reporting]] · [[Support]] · [[Roadmap]] · [[FAQ]]**

wiki/FAQ.md

@@ -0,0 +1,76 @@
+# FAQ
+
+Frequently asked questions about WDS projects and this repository.
+
+---
+
+## General
+
+### Where do I report bugs?
+
+Use the issue templates in this repository. Select the template that best matches your problem (bug report, crash report, performance issue, or multiplayer issue). See [[Bug-Reporting]] for guidance on writing a useful report.
+
+➡️ [Open an Issue](https://github.com/World-Domination-Software/Projects/issues/new/choose)
+
+### Which platforms are supported?
+
+We aim to support PC (Windows, Linux, Steam Deck) and mobile platforms (Android, iOS) where possible. Exact support varies by project and release. Check each project's [[Projects|page in the project directory]] for current platform status.
+
+### How do I share feedback or ideas?
+
+Use [GitHub Discussions](https://github.com/World-Domination-Software/Projects/discussions) for ideas, general feedback, and suggestions. For well-defined feature requests, use the **Feature request** issue template.
+
+### Can I contribute code or content?
+
+Yes, in some cases. Please read [CONTRIBUTING.md](https://github.com/World-Domination-Software/Projects/blob/main/CONTRIBUTING.md) before starting work, and open an issue or discussion for larger proposals before implementing.
+
+---
+
+## Bug Reports and Issues
+
+### How do I check if a bug is already known?
+
+- Search existing [issues](https://github.com/World-Domination-Software/Projects/issues) with relevant keywords.
+- Look for issues labeled `known-issue` or `confirmed`.
+- Browse the relevant project's Discussions support category.
+
+### Should I open an Issue or a Discussion?
+
+If you have a clear, reproducible bug — open an Issue using the appropriate template. If you are not sure yet whether it is a bug, or you need help troubleshooting first — start a Discussion. Maintainers can convert a Discussion to an Issue if needed.
+
+---
+
+## Troubleshooting
+
+### Where is the troubleshooting guide?
+
+See [[Troubleshooting-Index]] for a symptom-based guide covering common issues across all projects.
+
+### The troubleshooting guide didn't fix my problem. What next?
+
+1. Check if there is a project-specific troubleshooting page (linked from each project's landing page).
+2. Search existing [issues](https://github.com/World-Domination-Software/Projects/issues) and [discussions](https://github.com/World-Domination-Software/Projects/discussions).
+3. Post in the support Discussions category for the relevant project (see [[Support]]).
+4. If it is a clear bug, file an issue via [[Bug-Reporting]].
+
+---
+
+## Roadmap and Updates
+
+### Where can I see what's planned?
+
+The roadmap is hosted in GitHub Discussions so the community can follow and participate:
+
+➡️ [Roadmap Discussions](https://github.com/World-Domination-Software/Projects/discussions/categories/roadmap)
+
+See also [[Roadmap]] for context on how we use it.
+
+### How do I stay notified about updates?
+
+- Watch the repository (select notification level under **Watch** at the top of the repo page).
+- Subscribe to specific roadmap discussion threads you care about.
+- Follow the Releases section of this repository for published builds.
+
+---
+
+**→ [[Home]] · [[Troubleshooting-Index]] · [[Bug-Reporting]] · [[Support]] · [[Roadmap]]**

wiki/Game-Servers-Panel-FAQ.md

@@ -0,0 +1,67 @@
+# Game Servers Panel – FAQ
+
+← Back to [[Game-Servers-Panel]]
+
+---
+
+## General
+
+### What is Game Servers Panel?
+
+Game Servers Panel is a web-based management interface for game server infrastructure. It lets operators deploy, monitor, configure, and control game server instances from a central dashboard, without needing direct command-line access to the server hosts.
+
+### What types of game servers can be managed?
+
+Game Servers Panel is designed to work with WDS-supported game server types. Support for specific games and server types is documented in the panel itself. Ask in [Game Servers Panel Support Discussions](https://github.com/World-Domination-Software/Projects/discussions/categories/game-servers-panel-support) for specifics.
+
+### Is it cloud-hosted or self-hosted?
+
+Game Servers Panel is self-hosted — you install and run the panel and agents on your own infrastructure. WDS does not manage your panel instance.
+
+---
+
+## Setup and Access
+
+### How do I install the panel?
+
+Installation documentation is included in the panel release package. For the latest guidance, see the [release notes](https://github.com/World-Domination-Software/Projects/releases) or ask in [Game Servers Panel Support Discussions](https://github.com/World-Domination-Software/Projects/discussions/categories/game-servers-panel-support).
+
+### How do I add a new server to the panel?
+
+Install the agent process on the server host, configure it with your panel address and authentication token, then register it in the panel dashboard. Detailed steps are in the panel's documentation.
+
+### Can multiple operators manage the same panel?
+
+Yes. Role-based access control allows you to create accounts with different permission levels (viewer, operator, administrator).
+
+---
+
+## Operations
+
+### Do configuration changes require a server restart?
+
+Most configuration changes require a server restart to take effect. The panel will indicate when a restart is needed after applying changes.
+
+### Can I schedule maintenance windows?
+
+Yes. The panel supports scheduled lifecycle actions including maintenance windows and restarts.
+
+### How do I access server logs?
+
+Server logs are accessible directly from the panel's **Logs and Diagnostics** section for any connected server.
+
+---
+
+## Technical
+
+### How do I report a bug?
+
+See [[Bug-Reporting]] for how to choose the right template and what to include.
+
+### Something is wrong with the agent connection. What should I check?
+
+See [[Game-Servers-Panel-Troubleshooting]] for a step-by-step agent connectivity guide.
+
+---
+
+**→ [[Game-Servers-Panel]] · [[Game-Servers-Panel-Troubleshooting]] · [[Support]] · [[Bug-Reporting]]**

wiki/Game-Servers-Panel-Overview.md

@@ -0,0 +1,55 @@
+# Game Servers Panel – Overview
+
+**Type:** Hosting / Infrastructure | **Developer:** World Domination Software LLC
+
+← Back to [[Game-Servers-Panel]]
+
+---
+
+## What Is Game Servers Panel?
+
+Game Servers Panel is a web-based application for deploying, monitoring, and administering game server instances. It provides a centralized interface that gives operators control over their hosting environment without requiring deep command-line expertise.
+
+## Purpose
+
+Running game servers reliably is operationally complex. Game Servers Panel simplifies this by:
+
+- Providing a single dashboard for all hosted server instances.
+- Reducing the operational burden of manual server administration.
+- Making server management accessible to operators who are not system administrators.
+
+## Features
+
+| Feature | Description |
+|---|---|
+| **Server deployment** | Spin up new server instances quickly from a managed interface. |
+| **Monitoring and status** | View live status, resource usage, and health for each server. |
+| **Configuration management** | Edit and apply server configuration without direct file access. |
+| **Access control** | Role-based permissions for operators and administrators. |
+| **Logs and diagnostics** | Access server logs from the panel for troubleshooting. |
+| **Lifecycle controls** | Start, stop, restart, and schedule server maintenance windows. |
+
+## Architecture
+
+Game Servers Panel is a web-based application with a server-side backend that communicates with lightweight agent processes running on each hosted machine. The panel UI is served from a central host; agents relay commands and telemetry between the panel and the underlying servers.
+
+Key components:
+
+- **Panel web application** – User-facing dashboard and API layer.
+- **Agent process** – Lightweight service installed on each server host, handling lifecycle and telemetry.
+- **Communication layer** – Secure channel between the panel and agents.
+
+## Development Status
+
+| Area | Status |
+|---|---|
+| Core panel and agent | Active development |
+| Monitoring and dashboards | Available |
+| Role-based access control | Available |
+| Extended log analysis | Planned |
+
+For current priorities, see the [Roadmap discussions](https://github.com/World-Domination-Software/Projects/discussions/categories/roadmap).
+
+---
+
+**→ [[Game-Servers-Panel]] · [[Game-Servers-Panel-Troubleshooting]] · [[Game-Servers-Panel-FAQ]]**