Add docs navigation and tighten API request security

docs/gitbook/content-reports.md

@@ -0,0 +1,27 @@
+# Content reports and appeals
+
+If a map or one of its pictures contains a problem, use **Report content**. If a button or the game itself is broken, use **Report a bug** instead.
+
+## Report a map or picture
+
+1. Sign in.
+2. Open the public map page and choose **Report content**. During a game, the same option reports the view you are looking at.
+3. Choose a category and explain what is wrong.
+4. Add a link to evidence if you have one, then send the report.
+
+Be specific and report honestly. You cannot report your own map. If you already have a report waiting on that map, wait for its review rather than sending duplicates.
+
+## What happens next?
+
+An Admin checks the map and the report. Reports do not automatically count against a map. Only confirmed reports add strikes.
+
+Three confirmed strikes from different reporters cause a map to be removed from public play. This affects the map, not the owner's account.
+
+## My map was banned. What can I do?
+
+1. Open **My account** and choose the banned map.
+2. Click **Appeal map ban**.
+3. Explain why it should be reconsidered and include helpful new information.
+4. Wait for the decision. Only one appeal can be waiting at a time.
+
+If approved, the last public version returns and its strike count resets. If rejected, read the feedback before sending another appeal with new information.