Okay, so I’m not going to lie.  Documentation isn’t one of my favorite forms of writing.  However, when it comes to creating a new app, especially one like Fellowstream, it’s essential that people have a decent reference point to figure out what’s going on.

So for the last week, I’ve been pouring over our internal Fellowstream account and trying to document every important point I can think of. Here are the major sections so far:

• Creating Work through Tickets:  How to create a ticket of work for yourself and your teammates.
• Accepting/Rejecting Tickets:  How to accept work from others or (equally important) how to let them know you can’t complete a task they requested.
• Managing your Workspace: How to prioritize your Open Tickets stack so that you know what to work on (and so do your teammates).
• Using the Stream:  What kind of information you can use in Fellowstream’s Stream feature, and how you can customize it to be the most useful in your daily work life.
• Using Projects:  How to create a project, including managing milestones and sorting through project tasks.
• Using Groups:  How to create an informal group of people who do the same thing, so that other teammates can assign a ticket to a group (rather than an individual).
• Using Pages:  How to create new Google doc-esque pages inside Fellowstream to share knowledge with others about projects and groups.
• Adjusting your Settings:  Making sure you know all the Fellowstream options available to you.
• Giving Feedback:  How to tell us at Avalon Labs what you like, don’t like, and suggestions for improvement.
• Admin Capabilities:  What options are available to the Fellowstream admins.

Within the next day or two, we’ll ask a few personal friends to start using the site in our first ever closed beta.  It will be interesting to see how useful the Getting Started Doc is and how much I’ll have to rewrite.  (And trust me, there’s always a rewrite!)

– Deborah Fike

Share and Enjoy