Ask a question that gets answered
A short routine for asking in a community forum: search first, make the title the question, say what you tried, and accept the reply that worked.
Most unanswered questions are not hard. They are unclear. Someone reads the title, cannot tell what is being asked, and moves on. A few small habits turn that around, and they cost a minute.
Search first#
Before you post, search the side you are on. Community search works on titles, tags, authors and text of one side at a time, and accepted answers show first. If the question was answered, you are done in seconds, and you spared a helper a repeat. If it was nearly answered, link to that post in yours and say what is different.
Make the title the question#
"Help" is not a title. "How do I export a document as PDF?" is. A good title survives being read in a list, in a search result and in a notification, with nothing around it. If you cannot put your question into one line, you may be asking two questions.
Say what you tried and what happened#
Write what you were doing, what you expected and what you got instead. Add the exact text of an error. On the Developers side, add the versions of what you use, because the answer often depends on them. This is the part most people skip, and it is the part that gets you an answer on the first reply instead of the third.
Pick the right channel#
The channel decides what your post is. A question channel makes a question, with an accepted answer. Help and questions on the Users side is for using Geenius OS and its apps. Dev questions on the Developers side is for building on the kit and the registry. If you are in the wrong side, you will get fewer answers, so switch with one tap.
Accept the reply that worked#
When a reply solves it, open your question and press Accept on that reply. This is the step that makes the community useful later. The accepted answer shows first, and the question is marked answered, so the next person with the same problem finds the fix and does not have to ask. You can change your mind if a better answer arrives.
Say thanks with a reaction#
A reaction such as helpful keeps the thread short. Save replies for things that add something.
What a community cannot promise#
Nobody is obliged to answer, and the community is new, so there are not many members yet. We would rather say that than promise a reply in an hour. If your question is a bug in a Geenius app, a post that says exactly what you did will also help the team find it.
Read the guide to asking, and request access if you are not in yet.