docs(mobile): add Mobile App documentation section (EN + PT-BR)#77
Open
mtlouzada wants to merge 3 commits into
Open
docs(mobile): add Mobile App documentation section (EN + PT-BR)#77mtlouzada wants to merge 3 commits into
mtlouzada wants to merge 3 commits into
Conversation
New section covering the Skatehive iOS/Android app with full Portuguese translation. **Structure (sidebar subcategories):** - FAQ (7 sub-pages): Getting Started, Login & Security, Creating Content, Videos, Wallet & Rewards, Features, Troubleshooting - Creating Content: Creator Guide, App vs Web comparison - Security: Key Security guide - Help: Troubleshooting, Changelog - Reference: Glossary **Config changes:** - sidebars.js: added Mobile App category with nested subcategories - docusaurus.config.js: added docs/Mobile/ to LLM includeOrder and new llms-mobile.txt custom file - i18n/pt-br/current.json: added translated labels for all new sidebar categories
📝 WalkthroughWalkthroughThis PR adds comprehensive user-facing documentation for the Skatehive mobile app across English and Portuguese languages, including creator guides, FAQs, security protocols, and troubleshooting resources. It also introduces an advanced profile customization guide for the web app and updates the Docusaurus documentation infrastructure to support the new Mobile section. ChangesMobile App & Web Profile Documentation
🎯 2 (Simple) | ⏱️ ~12 minutes
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 5
🧹 Nitpick comments (3)
docs/Advance/profile-customization.md (3)
1-1: ⚡ Quick winConsider adding Docusaurus frontmatter.
The document lacks YAML frontmatter, which Docusaurus uses for metadata like
sidebar_position,sidebar_label,description, andtags. This can affect SEO, sidebar ordering, and page discovery.📝 Proposed frontmatter addition
+--- +sidebar_position: 5 +sidebar_label: Profile Customization +description: Learn how to personalize your SkateHive profile with custom images, information, and your own magazine cover. +--- + # Profile Customization Guide🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/Advance/profile-customization.md` at line 1, The markdown page "Profile Customization Guide" is missing Docusaurus YAML frontmatter; add frontmatter at the top of the file including keys like sidebar_position, sidebar_label (e.g., "Profile Customization Guide"), description, and tags so Docusaurus can index and order the page properly; ensure the frontmatter block is the first thing in the file (between --- markers) and contains meaningful values for SEO and sidebar ordering.
113-113: ⚡ Quick winClarify supported image formats for URL method.
The guidance states URLs "must end in .jpg, .png, etc." but line 88 lists WEBP as a supported format, which ends in
.webp. Consider being more explicit about all supported extensions.📝 Proposed clarification
-1. Copy the direct image URL (must end in .jpg, .png, etc.) +1. Copy the direct image URL (must end in .jpg, .jpeg, .png, .gif, or .webp)🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/Advance/profile-customization.md` at line 113, Update the sentence that says "must end in .jpg, .png, etc." to explicitly list all supported image extensions (e.g., .jpg, .jpeg, .png, .gif, .webp, .bmp, .tiff) and/or rephrase to "must end in a supported image extension (e.g., .jpg, .jpeg, .png, .gif, .webp, ...)" so that WEBP (mentioned on line 88) and other formats are clearly covered; adjust the text near the direct image URL guidance to include the full set of supported extensions or a parenthetical example list.
304-304: 💤 Low value"Last updated" date appears to be backdated.
The timestamp shows "December 2025" but this PR was created in June 2026. Consider updating to reflect the actual last modification date.
📅 Proposed fix
-*Last updated: December 2025* +*Last updated: June 2026*🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/Advance/profile-customization.md` at line 304, The markdown shows an outdated "Last updated" timestamp; locate the line containing the literal string "*Last updated: December 2025*" in the profile-customization doc and replace it with the correct current last-modified date (e.g., "*Last updated: June 2026*") ensuring the same formatting/asterisk styling is preserved; commit the change with a clear message like "docs: update last-updated date in profile-customization" so history reflects the fix.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/Advance/profile-customization.md`:
- Line 120: Update the inconsistent file-size guidance so both the "File size"
bullet that currently says "Under 5MB for faster loading" and the
"Troubleshooting" section that says "max 10MB" use a single, consistent limit
and recommendation; decide whether the hard limit is 10MB and the recommended
size is under 5MB (or make both 5MB/10MB as appropriate), then edit the "File
size" bullet text and the "Troubleshooting" entry to match that choice and add a
short clarifier like "max XMB (recommended under YMB)".
- Around line 1-305: The profile-customization doc exists but is not listed in
the Advance sidebar or SUMMARY; update sidebars.js to add
"Advance/profile-customization" into the 🛹 Advance category's items array
(match ordering with other docs/Advance/* entries) and also add an entry
"Advance/profile-customization" (or "Advance/profile-customization.md" if
SUMMARY uses filenames) into docs/SUMMARY.md Advance section so the left-nav and
summary mirror each other; confirm _category_.json remains as generated-index
and does not need changes.
- Around line 259-262: The "Best Practices" section header in
profile-customization.md is empty; either remove the "## Best Practices" header
entirely or populate it with brief guidance (e.g., a short paragraph or bullet
list of recommended practices for profile customization such as privacy tips,
naming conventions, image sizing, and accessibility notes) so the heading is not
left blank; update the content under the "## Best Practices" header accordingly.
In `@docs/Mobile/key-security.md`:
- Line 119: The link in docs/Mobile/key-security.md is broken because it points
to ./faq.md#i-forgot-my-posting-key-what-do-i-do; update the link to the actual
FAQ location docs/Mobile/faq/login-security.md and ensure the anchor follows
Docusaurus conventions (lowercase, hyphens) matching the header for "I forgot my
posting key" so replace the href with
docs/Mobile/faq/login-security.md#i-forgot-my-posting-key-what-do-i-do.
In `@i18n/pt-br/docusaurus-plugin-content-docs/current/Mobile/app-vs-web.md`:
- Line 7: Update the Portuguese text in Mobile/app-vs-web.md to use preferred
pt-BR terms and correct gender/articles: replace instances of "browser" with
"navegador"; change "web app" to "aplicativo web" (and adjust its preceding
article from "o" to the appropriate "o" for aplicativo) wherever used (e.g., the
sentence starting with "O app mobile ..." and occurrences around the phrases
"web app"); and fix "a magazine" to either "o magazine" or better "a revista" to
match intended meaning. Ensure gender and article agreement across the affected
phrases so the sentences read naturally for Brazilian Portuguese readers.
---
Nitpick comments:
In `@docs/Advance/profile-customization.md`:
- Line 1: The markdown page "Profile Customization Guide" is missing Docusaurus
YAML frontmatter; add frontmatter at the top of the file including keys like
sidebar_position, sidebar_label (e.g., "Profile Customization Guide"),
description, and tags so Docusaurus can index and order the page properly;
ensure the frontmatter block is the first thing in the file (between ---
markers) and contains meaningful values for SEO and sidebar ordering.
- Line 113: Update the sentence that says "must end in .jpg, .png, etc." to
explicitly list all supported image extensions (e.g., .jpg, .jpeg, .png, .gif,
.webp, .bmp, .tiff) and/or rephrase to "must end in a supported image extension
(e.g., .jpg, .jpeg, .png, .gif, .webp, ...)" so that WEBP (mentioned on line 88)
and other formats are clearly covered; adjust the text near the direct image URL
guidance to include the full set of supported extensions or a parenthetical
example list.
- Line 304: The markdown shows an outdated "Last updated" timestamp; locate the
line containing the literal string "*Last updated: December 2025*" in the
profile-customization doc and replace it with the correct current last-modified
date (e.g., "*Last updated: June 2026*") ensuring the same formatting/asterisk
styling is preserved; commit the change with a clear message like "docs: update
last-updated date in profile-customization" so history reflects the fix.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 9e3b7f61-ff32-49b4-82ec-ef689a3bbf05
📒 Files selected for processing (32)
docs/Advance/profile-customization.mddocs/Mobile/_category_.jsondocs/Mobile/app-vs-web.mddocs/Mobile/changelog.mddocs/Mobile/creator-guide.mddocs/Mobile/faq/creating-content.mddocs/Mobile/faq/features.mddocs/Mobile/faq/getting-started.mddocs/Mobile/faq/login-security.mddocs/Mobile/faq/troubleshooting-faq.mddocs/Mobile/faq/videos.mddocs/Mobile/faq/wallet-rewards.mddocs/Mobile/glossary.mddocs/Mobile/key-security.mddocs/Mobile/troubleshooting.mddocusaurus.config.jsi18n/pt-br/docusaurus-plugin-content-docs/current.jsoni18n/pt-br/docusaurus-plugin-content-docs/current/Mobile/_category_.jsoni18n/pt-br/docusaurus-plugin-content-docs/current/Mobile/app-vs-web.mdi18n/pt-br/docusaurus-plugin-content-docs/current/Mobile/changelog.mdi18n/pt-br/docusaurus-plugin-content-docs/current/Mobile/creator-guide.mdi18n/pt-br/docusaurus-plugin-content-docs/current/Mobile/faq/creating-content.mdi18n/pt-br/docusaurus-plugin-content-docs/current/Mobile/faq/features.mdi18n/pt-br/docusaurus-plugin-content-docs/current/Mobile/faq/getting-started.mdi18n/pt-br/docusaurus-plugin-content-docs/current/Mobile/faq/login-security.mdi18n/pt-br/docusaurus-plugin-content-docs/current/Mobile/faq/troubleshooting-faq.mdi18n/pt-br/docusaurus-plugin-content-docs/current/Mobile/faq/videos.mdi18n/pt-br/docusaurus-plugin-content-docs/current/Mobile/faq/wallet-rewards.mdi18n/pt-br/docusaurus-plugin-content-docs/current/Mobile/glossary.mdi18n/pt-br/docusaurus-plugin-content-docs/current/Mobile/key-security.mdi18n/pt-br/docusaurus-plugin-content-docs/current/Mobile/troubleshooting.mdsidebars.js
Comment on lines
+1
to
+305
| # Profile Customization Guide | ||
|
|
||
| Learn how to personalize your SkateHive profile with custom images, information, and your own magazine cover. | ||
|
|
||
| ## Table of Contents | ||
|
|
||
| - [Accessing Profile Settings](#accessing-profile-settings) | ||
| - [Basic Profile Information](#basic-profile-information) | ||
| - [Custom Magazine Cover](#custom-magazine-cover) | ||
| - [Profile Images](#profile-images) | ||
| - [Connecting Wallets](#connecting-wallets) | ||
| - [Troubleshooting](#troubleshooting) | ||
|
|
||
| --- | ||
|
|
||
| ## Accessing Profile Settings | ||
|
|
||
| 1. **Navigate to your profile** | ||
| - Click on your avatar in the top navigation bar | ||
| - Or visit `https://skatehive.app/user/[your-username]` | ||
|
|
||
| 2. **Open Edit Profile Modal** | ||
| - Click the **"Edit Profile"** button on your profile page | ||
| - The edit modal will appear with all customization options | ||
|
|
||
| --- | ||
|
|
||
| ## Basic Profile Information | ||
|
|
||
| ### Name (Display Name) | ||
| Your public display name shown throughout SkateHive. | ||
|
|
||
| **To update:** | ||
| - Find the **"Name"** field in the edit modal | ||
| - Enter your preferred display name | ||
| - This appears on your magazine cover and profile | ||
|
|
||
| ### About / Bio | ||
| A short description about yourself or your motto. | ||
|
|
||
| **To update:** | ||
| - Find **"Words to live by? (optional)"** | ||
| - Enter a personal bio or skateboarding motto | ||
| - Maximum recommended length: 200 characters | ||
|
|
||
| ### Location | ||
| Select your country to connect with local skaters. | ||
|
|
||
| **To update:** | ||
| - Click the **"Location"** dropdown | ||
| - Search or scroll to find your country | ||
| - Format: `US - United States`, `BR - Brazil`, etc. | ||
|
|
||
| ### Website | ||
| Link to your personal website, Instagram, or portfolio. | ||
|
|
||
| **To update:** | ||
| - Enter your website URL in the **"Website"** field | ||
| - Must include `https://` or `http://` | ||
| - Example: `https://instagram.com/yourname` | ||
|
|
||
| --- | ||
|
|
||
| ## Custom Magazine Cover | ||
|
|
||
| Create a personalized magazine cover for your profile's flipbook magazine view! This feature gives you a unique, professional-looking magazine with your own cover image. | ||
|
|
||
| ### What is the Magazine Cover? | ||
|
|
||
| When viewers visit your profile and click the **"Magazine"** view, they'll see your posts displayed in an interactive flipbook format. The cover page features: | ||
|
|
||
| - **Your custom cover image** (full-page background) | ||
| - **Your display name** (horizontal text at top left) | ||
| - **Vertical "ZINE" text** (left side, skateboarding magazine style) | ||
| - **Your profile picture** (bottom left corner) | ||
| - **3D page effect** with realistic shadows | ||
|
|
||
| ### Setting Your Magazine Cover | ||
|
|
||
| #### Method 1: Upload and Crop (Recommended) | ||
|
|
||
| 1. **Open Edit Profile modal** | ||
| 2. Scroll to **"Mag Cover (optional)"** | ||
| 3. Click the green **"Upload"** button | ||
| 4. Select an image from your device | ||
| - Recommended: High-resolution photos (1000x1300px or larger) | ||
| - Supported formats: JPG, PNG, GIF, WEBP | ||
| - Best results: Action skateboarding photos, skatepark shots, or lifestyle images | ||
|
|
||
| 5. **Crop your image** | ||
| - The cropper modal will appear | ||
| - Adjust the crop area by dragging | ||
| - Use the **"Zoom"** slider to fine-tune (1x to 3x) | ||
| - The aspect ratio is locked to magazine dimensions (1000x1300px) | ||
| - Preview shows exactly how your cover will look | ||
|
|
||
| 6. **Upload to IPFS** | ||
| - Click **"Crop & Upload"** | ||
| - Wait for upload (shows "Uploading to IPFS...") | ||
| - Success notification appears | ||
| - The cropper closes automatically | ||
| - Your IPFS URL appears in the input field | ||
|
|
||
| 7. **Save your changes** | ||
| - Click the **"Save Changes"** button at the top | ||
| - Confirm the transaction in Keychain | ||
| - Your magazine cover is now live! | ||
|
|
||
| #### Method 2: Paste Image URL | ||
|
|
||
| If you already have an image hosted online: | ||
|
|
||
| 1. Copy the direct image URL (must end in .jpg, .png, etc.) | ||
| 2. Paste it into the **"Mag Cover"** input field | ||
| 3. Click **"Save Changes"** | ||
|
|
||
| **Recommended image specs:** | ||
| - **Dimensions:** 1000px × 1300px (portrait orientation) | ||
| - **Aspect ratio:** 0.77:1 (magazine cover ratio) | ||
| - **File size:** Under 5MB for faster loading | ||
| - **Format:** JPEG (best for photos), PNG (for graphics/text) | ||
|
|
||
| ### Design Tips for Great Magazine Covers | ||
|
|
||
| **Photography:** | ||
| - Use high-quality, well-lit photos | ||
| - Action shots work great (skating, tricks, parks) | ||
| - Lifestyle photos showing personality | ||
| - Street photography with urban vibes | ||
|
|
||
| **Composition:** | ||
| - Leave space at top left for your name | ||
| - Leave space on left side for "ZINE" text | ||
| - Avoid important content in the bottom left (profile picture area) | ||
| - High contrast images work best with the green text overlay | ||
|
|
||
| **Style inspiration:** | ||
| - Classic skateboarding magazines (Thrasher, Transworld) | ||
| - Skateboarder magazine covers (vintage style) | ||
| - Modern skate zines and independent publications | ||
|
|
||
| ### Viewing Your Magazine | ||
|
|
||
| 1. Go to your profile | ||
| 2. Click the **"Magazine"** view tab | ||
| 3. Your custom cover displays on the first page | ||
| 4. Flip through to see your posts in magazine format | ||
| 5. Share your magazine link: `https://skatehive.app/user/[username]?view=magazine` | ||
|
|
||
| ### Updating Your Cover | ||
|
|
||
| You can change your magazine cover anytime: | ||
|
|
||
| 1. Open Edit Profile | ||
| 2. Upload a new image or paste a new URL | ||
| 3. The cropper remembers your preferences | ||
| 4. Save changes to update | ||
|
|
||
| **Pro tip:** Match your cover to seasons, events, or your latest skate video! | ||
|
|
||
| --- | ||
|
|
||
| ## Profile Images | ||
|
|
||
| ### Profile Picture | ||
|
|
||
| Your avatar shown across SkateHive. | ||
|
|
||
| **To update:** | ||
| 1. Find **"Profile Picture"** section | ||
| 2. Click **"Upload"** button or paste image URL | ||
| 3. Recommended size: 400x400px (square) | ||
| 4. Auto-displays in navigation, posts, and comments | ||
|
|
||
| ### Profile Background | ||
|
|
||
| Header image on your profile page. | ||
|
|
||
| **To update:** | ||
| 1. Find **"Profile Background"** section | ||
| 2. Click **"Upload"** button or paste image URL | ||
| 3. Recommended size: 1500x500px (wide banner) | ||
| 4. Appears at the top of your profile | ||
|
|
||
| **Upload options for all images:** | ||
| - **Direct Upload:** Click "Upload" → Select file → Auto-uploads to IPFS | ||
| - **URL Method:** Paste direct image URL from any source | ||
|
|
||
| --- | ||
|
|
||
| ## Connecting Wallets | ||
|
|
||
| ### Ethereum Wallet | ||
|
|
||
| Link your Ethereum address for Web3 features and rewards. | ||
|
|
||
| **To connect:** | ||
| 1. Find **"Ethereum Wallet"** section | ||
| 2. Click **"Connect Ethereum Wallet"** | ||
| 3. Click the RainbowKit "Connect Wallet" button | ||
| 4. Select your wallet provider (MetaMask, Coinbase, etc.) | ||
| 5. Approve the connection | ||
| 6. Click **"Link Address"** to save | ||
| 7. Click **"Save Changes"** | ||
|
|
||
| **Features enabled:** | ||
| - $SKATEHIVE token rewards | ||
| - NFT integration | ||
| - Web3 authentication | ||
| - Cross-chain identity | ||
|
|
||
| --- | ||
|
|
||
| ## Troubleshooting | ||
|
|
||
| ### Magazine Cover Issues | ||
|
|
||
| **❌ "Cropping failed"** | ||
| - Check image file size (max 10MB) | ||
| - Try a different image format | ||
| - Ensure stable internet connection | ||
| - Close and reopen the cropper | ||
|
|
||
| **❌ "Upload failed"** | ||
| - IPFS network might be slow, try again | ||
| - Check browser console for errors | ||
| - Use a different image file | ||
| - Try the URL paste method instead | ||
|
|
||
| **❌ Cover not showing** | ||
| - Clear browser cache | ||
| - Ensure you clicked "Save Changes" | ||
| - Check that the IPFS URL is valid | ||
| - Wait a few minutes for IPFS propagation | ||
|
|
||
| **❌ Text not visible on cover** | ||
| - Choose images with good contrast | ||
| - Avoid very light or very green backgrounds | ||
| - The text has black shadows for readability | ||
| - Test different zoom levels in the cropper | ||
|
|
||
| ### General Profile Issues | ||
|
|
||
| **❌ Changes not saving** | ||
| - Ensure you're logged in with Keychain | ||
| - Check your Hive Resource Credits (RC) | ||
| - Approve the transaction popup | ||
| - Don't close the page during save | ||
|
|
||
| **❌ Images not loading** | ||
| - Wait 30-60 seconds for IPFS upload | ||
| - Check image URL is valid | ||
| - Try a different image host | ||
| - Use IPFS-hosted images for permanence | ||
|
|
||
|
|
||
|
|
||
|
|
||
| ## Best Practices | ||
|
|
||
|
|
||
|
|
||
| ## FAQ | ||
|
|
||
| **Q: How much does it cost to update my profile?** | ||
| A: It uses Hive Resource Credits (RC), which regenerate over time. No monetary cost. | ||
|
|
||
| **Q: Can I change my magazine cover multiple times?** | ||
| A: Yes! Update it as often as you want (respecting RC limits). | ||
|
|
||
| **Q: Are my images stored forever?** | ||
| A: Images uploaded to IPFS are permanent and decentralized. | ||
|
|
||
| **Q: Can others see my magazine?** | ||
| A: Yes! Anyone can view your personalized magazine by visiting your profile. | ||
|
|
||
| **Q: What if I don't set a custom cover?** | ||
| A: Your magazine will use the default SkateHive cover with Matrix effect. | ||
|
|
||
| **Q: Can I remove my magazine cover?** | ||
| A: Yes, clear the URL field and save changes to revert to default. | ||
|
|
||
|
|
||
| --- | ||
|
|
||
| ## Video Tutorial | ||
|
|
||
| 🎥 **Coming Soon:** Watch our step-by-step video guide on YouTube! | ||
|
|
||
| --- | ||
|
|
||
| ## Next Steps | ||
|
|
||
| Now that your profile is customized: | ||
|
|
||
| 1. **Create content** - Share your skate videos and photos | ||
| 2. **Connect with skaters** - Follow and engage with the community | ||
| 3. **Explore features** - Try the magazine view, spot map, and DAO | ||
|
|
||
| **Happy skating!** 🛹 | ||
|
|
||
| --- | ||
|
|
||
| *Last updated: December 2025* | ||
| *SkateHive Team* No newline at end of file |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Check all Advance docs and their sidebar presence
echo "=== Files in docs/Advance/ ==="
fd -e md . docs/Advance/
echo -e "\n=== Sidebar Advance section ==="
rg -A 10 "label: '🛹 Advance'" sidebars.js
echo -e "\n=== SUMMARY.md Advance section ==="
rg -A 10 "^\* \[Advance\]" docs/SUMMARY.mdRepository: SkateHive/skatehive-docs
Length of output: 1132
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "=== sidebars.js: 🛹 Advance block (more context) ==="
rg -n "label: '🛹 Advance'" -n sidebars.js
rg -n -C 5 "label: '🛹 Advance'" sidebars.js
echo -e "\n=== docs/Advance/_category_.json (if present) ==="
if [ -f "docs/Advance/_category_.json" ]; then
echo "Found docs/Advance/_category_.json"
wc -l docs/Advance/_category_.json
cat -n docs/Advance/_category_.json
else
echo "No docs/Advance/_category_.json"
fi
echo -e "\n=== Search for generated-index usage mentioning Advance ==="
rg -n "generated-index" -S docs | head -n 50
echo -e "\n=== Any other navigation config referencing profile-customization ==="
rg -n "profile-customization" -S . | head -n 50Repository: SkateHive/skatehive-docs
Length of output: 1176
Add profile-customization to the 🛹 Advance sidebar and Summary lists for consistency.
docs/Advance/profile-customization.md exists, but it’s missing from the explicit 🛹 Advance category items in sidebars.js and from the Advance section in docs/SUMMARY.md, while other docs/Advance/* pages are listed. Since docs/Advance/_category_.json uses generated-index, it may appear on the category landing page, but the left-nav/summary won’t include it. Add Advance/profile-customization to the 🛹 Advance items in sidebars.js (and to docs/SUMMARY.md if that list is intended to mirror the sidebar).
🧰 Tools
🪛 LanguageTool
[style] ~39-~39: Consider using the synonym “brief” (= concise, using a few words, not lasting long) to strengthen your wording.
Context: ...ne cover and profile ### About / Bio A short description about yourself or your mott...
(QUICK_BRIEF)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/Advance/profile-customization.md` around lines 1 - 305, The
profile-customization doc exists but is not listed in the Advance sidebar or
SUMMARY; update sidebars.js to add "Advance/profile-customization" into the 🛹
Advance category's items array (match ordering with other docs/Advance/*
entries) and also add an entry "Advance/profile-customization" (or
"Advance/profile-customization.md" if SUMMARY uses filenames) into
docs/SUMMARY.md Advance section so the left-nav and summary mirror each other;
confirm _category_.json remains as generated-index and does not need changes.
| **Recommended image specs:** | ||
| - **Dimensions:** 1000px × 1300px (portrait orientation) | ||
| - **Aspect ratio:** 0.77:1 (magazine cover ratio) | ||
| - **File size:** Under 5MB for faster loading |
There was a problem hiding this comment.
Inconsistent file size guidance: 5MB vs 10MB.
Line 120 recommends "Under 5MB for faster loading" but line 219 in the Troubleshooting section states "max 10MB." This creates user confusion about the actual file size limit.
📐 Proposed fix to clarify the limit
-- **File size:** Under 5MB for faster loading
+- **File size:** Under 5MB recommended (10MB maximum)📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| - **File size:** Under 5MB for faster loading | |
| - **File size:** Under 5MB recommended (10MB maximum) |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/Advance/profile-customization.md` at line 120, Update the inconsistent
file-size guidance so both the "File size" bullet that currently says "Under 5MB
for faster loading" and the "Troubleshooting" section that says "max 10MB" use a
single, consistent limit and recommendation; decide whether the hard limit is
10MB and the recommended size is under 5MB (or make both 5MB/10MB as
appropriate), then edit the "File size" bullet text and the "Troubleshooting"
entry to match that choice and add a short clarifier like "max XMB (recommended
under YMB)".
Comment on lines
+259
to
+262
| ## Best Practices | ||
|
|
||
|
|
||
|
|
There was a problem hiding this comment.
Empty section: Best Practices.
The "Best Practices" heading has no content below it, creating a confusing user experience. Either add content or remove the empty section header.
🧹 Proposed fix
Option 1: Remove the empty section entirely
-
-
-
-## Best Practices
-
-
-
## FAQOption 2: Add placeholder content
## Best Practices
+- Use high-quality images (at least 1000px width for covers)
+- Update your profile regularly to keep content fresh
+- Test your magazine cover on different devices
+- Keep your bio concise and engaging
## FAQ📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| ## Best Practices | |
| ## FAQ |
Suggested change
| ## Best Practices | |
| ## Best Practices | |
| - Use high-quality images (at least 1000px width for covers) | |
| - Update your profile regularly to keep content fresh | |
| - Test your magazine cover on different devices | |
| - Keep your bio concise and engaging | |
| ## FAQ |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/Advance/profile-customization.md` around lines 259 - 262, The "Best
Practices" section header in profile-customization.md is empty; either remove
the "## Best Practices" header entirely or populate it with brief guidance
(e.g., a short paragraph or bullet list of recommended practices for profile
customization such as privacy tips, naming conventions, image sizing, and
accessibility notes) so the heading is not left blank; update the content under
the "## Best Practices" header accordingly.
|
|
||
| --- | ||
|
|
||
| **Lost your keys?** See the [FAQ](./faq.md#i-forgot-my-posting-key-what-do-i-do) for recovery steps. |
There was a problem hiding this comment.
Fix broken internal link to FAQ.
The link ./faq.md#i-forgot-my-posting-key-what-do-i-do points to a file that doesn't exist. Based on the file structure, there's no single faq.md file in the Mobile directory. The FAQ section "I forgot my posting key" is located in docs/Mobile/faq/login-security.md (Lines 45-53).
🔗 Proposed fix
-**Lost your keys?** See the [FAQ](./faq.md#i-forgot-my-posting-key-what-do-i-do) for recovery steps.
+**Lost your keys?** See the [FAQ](./faq/login-security.md#i-forgot-my-posting-key-what-do-i-do) for recovery steps. Verify the anchor format matches Docusaurus conventions (headers typically convert to lowercase with hyphens).
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| **Lost your keys?** See the [FAQ](./faq.md#i-forgot-my-posting-key-what-do-i-do) for recovery steps. | |
| **Lost your keys?** See the [FAQ](./faq/login-security.md#i-forgot-my-posting-key-what-do-i-do) for recovery steps. |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/Mobile/key-security.md` at line 119, The link in
docs/Mobile/key-security.md is broken because it points to
./faq.md#i-forgot-my-posting-key-what-do-i-do; update the link to the actual FAQ
location docs/Mobile/faq/login-security.md and ensure the anchor follows
Docusaurus conventions (lowercase, hyphens) matching the header for "I forgot my
posting key" so replace the href with
docs/Mobile/faq/login-security.md#i-forgot-my-posting-key-what-do-i-do.
|
|
||
| # App Mobile vs Web App | ||
|
|
||
| O app mobile do Skatehive e o [web app](https://skatehive.app) compartilham o mesmo backend na blockchain HIVE, mas atendem casos de uso diferentes. O app mobile é feito para interação rápida e portátil — postar clips, navegar o feed, checar notificações. O web app é a plataforma completa com todas as funcionalidades. |
There was a problem hiding this comment.
Consider using preferred Portuguese terminology and fixing grammar for better readability.
The Portuguese documentation contains several language quality issues that affect readability for Brazilian users:
-
"browser" → "navegador": The term "browser" appears multiple times (lines 43, 64, 94, 96). In Portuguese (pt-BR), "navegador" is the preferred term.
-
Gender agreement with "web app": Lines 7, 70, and 94 use "o web app," which creates gender agreement issues in Portuguese. Consider "o aplicativo web" or adjust the phrasing.
-
Article agreement: Line 99 uses "a magazine" which needs correction to "o magazine" or "a revista."
While these don't block functionality, fixing them would improve the professional quality of the Portuguese documentation.
Also applies to: 43-43, 64-64, 70-70, 94-94, 96-96, 99-99
🧰 Tools
🪛 LanguageTool
[grammar] ~7-~7: Possível erro de concordância.
Context: ...s, navegar o feed, checar notificações. O web app é a plataforma completa com todas a...
(ERRO_DE_CONCORDNCIA_DO_GÉNERO_MASCULINO_O)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@i18n/pt-br/docusaurus-plugin-content-docs/current/Mobile/app-vs-web.md` at
line 7, Update the Portuguese text in Mobile/app-vs-web.md to use preferred
pt-BR terms and correct gender/articles: replace instances of "browser" with
"navegador"; change "web app" to "aplicativo web" (and adjust its preceding
article from "o" to the appropriate "o" for aplicativo) wherever used (e.g., the
sentence starting with "O app mobile ..." and occurrences around the phrases
"web app"); and fix "a magazine" to either "o magazine" or better "a revista" to
match intended meaning. Ensure gender and article agreement across the affected
phrases so the sentences read naturally for Brazilian Portuguese readers.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Pages added
FAQ (7 sub-pages)
Creating Content
Security
Help
Reference
Config changes
sidebars.js— Mobile App category with 5 nested subcategoriesdocusaurus.config.js—docs/Mobile/added to LLM includeOrder; newllms-mobile.txtcustom filei18n/pt-br/current.json— translated labels for all 6 new sidebar categoriesTest plan
pnpm buildcompletes without errors/docs/Mobile/faq/getting-startedSummary by CodeRabbit