article
Documentation
Help improve FileBrowser documentation using our Hugo-based structure.
Documentation Structure
Static Site Generator: Hugo Theme: Custom FileBrowser Docs Theme Deployment: Auto-generated during releases Format: Markdown with YAML front matter
Repository Structure
Creating New Pages
1. Add Page to Section
Create new markdown file in appropriate folder:
| |
2. Add Front Matter
3. Write Content
No H1 headers - Title comes from front matter. Use H2 (##) for sections.
4. Test Locally
View at: http://localhost:1313/docs/
Front Matter Fields
| Field | Required | Description |
|---|---|---|
title | Yes | Page title (appears in navigation and header) |
description | Yes | Brief description (shows in next/prev cards) |
icon | No | Material Symbol icon name |
Icons
Uses Material Symbols. Search for icon, copy name, add to front matter: icon: "settings"
Content Guidelines
- Clear and concise: Get to the point quickly
- Actionable: Provide steps users can follow
- Examples: Include code examples and configurations
- Accurate: Only document actual features (no speculation)
Code Blocks
Use language-specific syntax highlighting:
Links
Internal links: Use absolute paths from /docs/
External links: Use full URLs
| |
Documentation Best Practices
- Keep descriptions brief: 40-60 characters for navigation cards
- Use consistent icons: Related pages should use related icons
- File structure matters: Order is determined by file system structure
- Cross-reference: Add “Next Steps” section at the end
Local Preview
Always preview changes locally before submitting:
Access at: http://localhost:1313/docs/