docs: update /content user guides to match upload workflow and moderation config

Co-authored-by: PR0M3TH3AN <[email protected]>

content/docs/community/community-guidelines.md

@@ -56,7 +56,7 @@ To maintain a functional and ethical platform, the following types of content ar
 
 bitvid enforces these guidelines through client-side visibility rules that match the current `moreMenuController` and `userBlocks` behavior:
 
-- **Blurred previews:** When trusted NIP-56 `nudity` reports reach the configured blur threshold (`DEFAULT_BLUR_THRESHOLD` in [`config/instance-config.js`](../config/instance-config.js)), thumbnails render blurred and autoplay previews pause. Every blur includes a “show anyway” override. The upstream configuration currently uses three trusted reporters, but adjust the export to match your policy.
+- **Blurred previews:** When trusted NIP-56 `nudity` reports reach the configured blur threshold (`DEFAULT_BLUR_THRESHOLD` in [`config/instance-config.js`](../config/instance-config.js)), thumbnails render blurred and autoplay previews pause. Every blur includes a “show anyway” override. The upstream configuration currently uses one trusted report, but adjust the export to match your policy.
 - **Downranked authors:** Muting a creator adds them to your NIP-51 mute list (kind `10000`). Videos from muted creators are deprioritized but still visible with clear badges so you can reverse the action.
 - **Personal blocks:** Blocking a creator adds them to your private block list (`userBlocks`). Videos from blocked creators are hidden from feeds, carousels, and modals unless you explicitly unblock them.
 - **Admin hard hides:** Moderator-maintained blacklists (NIP-51 kind `30000`) remove creators from default feeds for everyone using the hosted client. Moderators can still review the content through “show anyway” controls when auditing decisions.

content/docs/getting-started.md

@@ -26,9 +26,11 @@ Ready to jump in? Here's everything you need to know to start watching and shari
 ### Step 3: Share on bitvid
 
 1. Click "Share a Video" on bitvid to open the upload modal.
-2. In **Custom** mode, enter your title, paste the hosted HTTPS URL, and (optionally) add the magnet plus any `ws`/`xs` hints. Switch to the experimental **Cloudflare** quick upload mode if you want bitvid to push the file straight to your Cloudflare R2 bucket—have your Account ID, S3 Access Key ID, and Secret Access Key ready (the advanced toggle also accepts an API token, Zone ID, and base domain if you use them).
+2. Choose your upload mode:
+   - **Upload Video**: Select a file from your device to upload directly to your Cloudflare R2 bucket. If you haven't configured storage yet, click **"Configure Storage"** to enter your R2 credentials (Account ID, Access Key ID, Secret Access Key) in your Profile settings.
+   - **External URL**: If you already host your video elsewhere, paste the HTTPS URL and (optionally) a WebTorrent magnet link.
 3. Review the rest of the form: add a description and thumbnail, decide whether to allow comments, and set the NSFW or "For Kids" toggles to match your content. Explore the metadata section to fill in captions, duration, publish time, hashtags, participants, and other fields so first-time viewers have all the context they need.
-4. Click "Post" to publish once everything looks right.
+4. Click "Publish Video" to post your content.
 
 ## Tips for Success
 

content/docs/guides/upload-content.md

@@ -32,18 +32,18 @@ To allow your browser to upload files directly to Cloudflare, you must allow Cro
 [
   {
     "AllowedOrigins": ["http://127.0.0.1:5500", "https://bitvid.network"],
-    "AllowedMethods": ["GET", "PUT", "POST", "DELETE", "HEAD"],
+    "AllowedMethods": ["GET", "PUT", "POST", "DELETE", "HEAD", "OPTIONS"],
     "AllowedHeaders": ["*"],
     "ExposeHeaders": ["ETag", "Content-Length", "Content-Range", "Accept-Ranges"],
     "MaxAgeSeconds": 3600
   }
 ]
 ```
-> **Note:** Replace the `AllowedOrigins` values with the exact origins you use in development and production (the scheme and port must match exactly). Apply this policy on the **bucket’s S3 API endpoint**, not just the public URL or custom domain. Uploads go through the **S3 API endpoint** (`<account>.r2.cloudflarestorage.com`), and Cloudflare’s UI does **not** require adding `OPTIONS` to `AllowedMethods`.
+> **Note:** Replace the `AllowedOrigins` values with the exact origins you use in development and production (the scheme and port must match exactly). Uploads go through the **S3 API endpoint** (`<account>.r2.cloudflarestorage.com`), and browser-based uploads require `OPTIONS` for preflight requests.
 
 5. Click **"Save"**.
 
-### 3. Create an API Token
+### 3. Create an API Token (S3 Credentials)
 
 1. Go back to the **R2 Overview** page.
 2. Click **"Manage R2 API Tokens"** (right sidebar).
@@ -54,17 +54,19 @@ To allow your browser to upload files directly to Cloudflare, you must allow Cro
    - **Specific Bucket(s)**: Select the bucket you created in Step 1.
    - **TTL**: "Forever".
 5. Click **"Create API Token"**.
+6. **Copy the credentials**: You will need the **Access Key ID** and **Secret Access Key**.
 
 ### 4. Configure bitvid
 
 1. Copy the **Access Key ID**, **Secret Access Key**, and your **Account ID** (found on the R2 Overview page).
-2. Return to the **Upload Video** modal in bitvid.
-3. Click **"Configure R2 Storage"**.
-4. Enter your:
+2. In bitvid, open your **Profile** (click your avatar).
+3. Navigate to the **Storage** tab (or click **"Configure R2 Storage"** in the Upload Modal to be redirected there).
+4. Click **"Add Connection"** and select **Cloudflare R2**.
+5. Enter your:
    - **Account ID**
    - **Access Key ID**
    - **Secret Access Key**
    - **Public Bucket URL** (from Step 1)
-5. Click **"Verify & Save"**.
+6. Click **"Save Connection"**.
 
-bitvid will verify your credentials by uploading a small test file. Once verified, you are ready to upload!
+bitvid will verify your credentials by uploading a small test file. Once verified, return to the Upload Modal to start sharing!