- Edited
Consolidated Support and Documentation Model for GhostBSD
1. Official Channels
2. Channel Responsibilities
Flarum
All informal support, help, and discussion goes here
Forum categories guide users to post in the right place
Topics that prove valuable can be distilled into documentation or tracked as GitHub issues
GitHub
Only reproducible bugs and clearly scoped feature requests
Use templates to enforce clarity
Flarum threads can be referenced if context helps, but GitHub remains lean and focused
ReadTheDocs
Only high-quality, curated, versioned content
Prominent links back to Flarum for help and GitHub for technical bugs
Every doc page can end with:
> Still have questions? Ask on the forum or open an issue
3. Suggested Flarum Tag Structure
Main Tags:
Support
- Installation
- Hardware Compatibility
- Networking and Wi-Fi
- ZFS and Encryption
- Boot Environments
Tutorials and Guides
- Desktop Customization
- Power Management
- Package Management
- System Recovery
Community and Meta
- Feature Proposals
- Site Feedback
- Contributor Onboarding
4. Interlinking Strategy
- From Flarum → Docs: Curated and validated answers turn into guides
- From Docs → Flarum: “Have questions? Ask here” links after each section
- From GitHub → Docs: Tag issues that require or improve documentation with
docs-needed
- From Flarum → GitHub: Escalate confirmed bugs, tagging with context and link to thread
5. Community Workflow Summary
[User has problem]
↓
[Search Docs at ReadTheDocs]
↓
[If unanswered → Ask on Flarum]
↓
[If verified bug → Maintainer opens GitHub issue]
↓
[Fix merged → Docs updated → Flarum thread closed with summary]