Welcome to the Documentation section — help us build the manual ForkBB never had
If you've spent any time digging into ForkBB's official support forum, you've probably noticed the same thing we did: the software itself is solid, but documentation is thin, and what exists is mostly written in Russian. That's fine if you read Russian. Most of you don't.
Rather than try to solve that with a wiki nobody maintains, we're doing something different here: this Documentation section is the manual. It's written by people actually running ForkBB forums on ForkBB.net, based on real configuration problems they've solved and real questions they've had answered.
Why a forum instead of a wiki
A wiki looks great on day one and rots by month three — pages go stale, nobody's sure who's "allowed" to edit what, and it becomes one more thing to administer. A forum section works differently: posts stay attributed to whoever wrote them, discussion and corrections happen right below the original post instead of in some hidden edit history, and it uses the same tool you're already using every day to ask for help. No new login, no new interface, no new habits.
How this works
Ask, and answer. If you figure out how to do something — set up a custom rank ladder, configure image uploads, get search indexing working right, whatever — write it up as a topic here. Even a short, rough post beats no documentation at all.
Search before you post. Chances are decent someone's already run into your question. If they have, reply there instead of starting a duplicate topic — that keeps the good answers consolidated instead of scattered across five threads.
Corrections are welcome, and expected. ForkBB changes over time, and so does ForkBB.net. If you find a post that's outdated or wrong, reply with the fix. We'd rather have documentation that gets corrected in public than documentation nobody trusts.
Title your topic like a question or a task, the way you'd search for it — "How do I change my forum's node URL?" not "Question." It makes the section actually searchable six months from now.
Practical over polished. We're not grading writing style. A clear list of steps that works is worth more than a beautifully worded paragraph that doesn't.
A standing invitation
If you've solved something that took you more than five minutes to figure out, it's worth a post here — the next person shouldn't have to spend those same five minutes. Over time, this section becomes the documentation ForkBB has always needed, written by the people actually using it.
Thanks for helping build this out.