Find the right public help channel and prepare questions that can be answered clearly.
This page covers common public questions about Tabula and helps you prepare a useful support request. The project’s contact page is the source for current support options. It lists kifuliiru@gmail.com for questions and problem reports.
Use the public information site to learn about the project and participation guidelines. Use the contribution platform through Visit app in this guide’s header when you want account-based access. The first-visit guide explains the distinction.
You can read these public guides without a contribution account. The language references, Academy overview, and portal guides offer other starting points. An account is relevant when participating through the contribution platform.
Available actions depend on your account and the area you are using. Describe the task you want to complete, the page you are on, and what you can see when asking for help. Do not assume every signed-in account has editing or publishing access.
The public sign-in screen offers Google and email/password options. For registration, use the platform’s current sign-up flow rather than assuming that a particular account role is automatically granted.
Interface language and content translation are different kinds of coverage. An English interface does not imply that every entry has an English translation. Two translations may also represent different senses.
Identify the entry, source passage, target language, and meaning you expected. Use dictionary and meanings or review and corrections to prepare the question.
A submission and language review are separate. Follow the outcome shown by the platform and preserve your material until you can identify what was received. If you need an update, refer to the particular contribution and the question that remains; this guide does not promise a review deadline.
Include the page address, device or browser, steps taken, expected result, and actual result. Quote the relevant error message if there is one. For audio, identify the recording and whether the issue is loading, playback, or the content itself.
Use the official contact options. Keep passwords and other private account details out of the report. A screenshot can help explain a layout problem when it does not disclose unrelated private information.
For a language correction, preserve the original form and explain the proposed change. For inappropriate content or a privacy concern, use an available report control or the official contact channel. Include enough information to identify the material without unnecessarily copying private details into a public discussion.
For participation expectations, read community guidelines. For preparing a new entry, use contributing language knowledge.
