We need your help!

FireBoard 1.0.5 is close to being released. We need to update the wiki, readme, changelog, version history, readme, install/upgrade guide, readme, readme, ...

If you are good in writing english based documentation we want your help!
This is your chance to do some cleanup to our documentation that will help the community with the use of FireBoard.

Don't be shy and volunteer. Together we can make this the best release that FireBoard has seen since its inception!

Who knows, maybe you even want to become a full time documentation lead for FireBoard.

Many Thanks to all that have contributed so far.

Come on guys!

Is there really nobody out there willing to contribute?

We have 1.0.5 basically ready to go and need help with documentation. This is a great opportunity to get involved.

Feel free to PM me with questions or respond to this thread.

Looking forward to some great input!

Oliver, I like to help with it but my english is not good enough for writing documentation.
But I am working some knowledgebase/faq/help component for fireboard and firemessage . It will have moderation access too, so you can edit add etc. I personally don't like wiki which is we are using. It is more confusing for members. So I like to keep it simple. Other side, maybe I will make a new site for fireboard documentation, dev blog, help, download etc. separate from bestofjoomla.com then our developers will be have more access.

But right now if we get a word or pdf document will be fine.

So who is willing to jump in here? I will keep the thread on top fo the active threads as long as it takes...

I would propose to not publish any version till the work on the documentation starts.

I will check my schedule and see if I could find few hours to contribute.

ivo.apostolov wrote:
I would propose to not publish any version till the work on the documentation starts.

I will check my schedule and see if I could find few hours to contribute.

We will not publish the version without proper documentation.

OK, let's start with it at least. Shouldn't be that hard.

What we need is shared workspace - i.e. Google docs or SVN (first should be more easy for non-tech users).
We need table of contents, where the key chapters should be covered and afterward, start writing it.

Example of table of contents could be

Fireboard Documentation

Table of contents:
1. Installation
2. Upgrade
3. Configuration
4. Sample data
5. Creation and management of boards
6. Access levels and moderation
7. User Administration
8. Uploaded files
9. Uploaded images
10. Change templates/edit CSS
11. Pruning forums
12. Synchronization of users
13. Smilies management
14. Rank management
15. Statistics
16. Frontend moderation
17. Other frontend features
18. Integration with other extensions
19. Plugins system
20. Fireboard extensions (modules, plugins)
21. Translating Fireboard

We need approximately 20 users, each of them writing ONE CHAPTER. It can not take more than 2-3 hours.

Btw. greatpixels try with quickfaq - very useful.

ivo.apostolov wrote:
OK, let's start with it at least. Shouldn't be that hard.

What we need is shared workspace - i.e. Google docs or SVN (first should be more easy for non-tech users).
We need table of contents, where the key chapters should be covered and afterward, start writing it.

Example of table of contents could be

Fireboard Documentation

Table of contents:
1. Installation
2. Upgrade
3. Configuration
4. Sample data
5. Creation and management of boards
6. Access levels and moderation
7. User Administration
8. Uploaded files
9. Uploaded images
10. Change templates/edit CSS
11. Pruning forums
12. Synchronization of users
13. Smilies management
14. Rank management
15. Statistics
16. Frontend moderation
17. Other frontend features
18. Integration with other extensions
19. Plugins system
20. Fireboard extensions (modules, plugins)
21. Translating Fireboard

We need approximately 20 users, each of them writing ONE CHAPTER. It can not take more than 2-3 hours.

That's a very good start.

We will need to add:

.) Release Notes
.) Maybe something about SEO
.) FAQs

Well, release notes is "your part".
SEO - we have a lot of people dealing with it around, almost anyone can contribute.

FAQs- that's the area where even the people with no time could spend 10 minutes to write one FAQ to be included. Something they suffered, found the solution and could help avoiding the users having the same problem in the future.

I will write now the sample data part in order to show to the X thousand people around, that you can't just demand all the time.