Distinguish interface language, translated content, unavailable material, and app-specific help.
Kifuliiru.com provides a multilingual public experience. Kifuliiru, English, French, and Kiswahili appear in its language resources and project scope. Choosing a familiar interface language can help you navigate, but it does not make every resource identical across languages.
Interface language concerns labels and navigation. Content language concerns the actual article, lesson, entry, or explanation. Translation coverage concerns whether that particular material has another-language version. Identify which one is unclear when asking for help.
For example, a lesson title in English does not establish that every attached passage has an English translation. A number with a translation does not guarantee that every number has a speaker recording. Read the options attached to the resource itself.
The portal homepage links to support, contact, and FAQ pages. Use those published options for a portal problem. If you followed a link into Lola, Tabula, Imyazi, or the Store, identify the actual application before contacting its help channel.
A documentation page explains an app; it is not the same as the app’s account or submission screen. Use Visit app in the relevant documentation header when you need the product itself.
| Problem | Include |
|---|---|
| Missing result | Search text, selected language, resource, and expected kind of result |
| Unclear form | Original expression, meaning, and point of uncertainty |
| Playback problem | Recording or value, device, action, and observed result |
| Broken navigation | Starting page, selected link, and destination or error |
| Translation issue | Original passage, target language, and proposed clarification |
Keep the original input before retrying a tool. This helps distinguish an input difference from a display or coverage problem.
Use the language references for explanations, Academy for study pathways, or Tabula’s correction guide to prepare a focused language question. You can continue with nearby reviewed examples without filling the gap with an unsupported answer.
