You need to configure an export, but searching for “data” returns too many similar articles. The question makes sense to you yet is too broad for useful results. Describe the next action where you got stuck, rather than the entire project.
Try “view a run error” or “send nested fields in JSON” instead of “nothing works.” These queries point to a more relevant section.
Choose the right section
Akmelo documentation has a searchable home, a user guide, API reference, and SDK reference. The guide explains the interface; the API covers calls from another application; the SDK helps you write collection scenarios.
Start with the first result path if you are new. For a specific issue, go straight to a source, scenario, run, schedule, or export article. You need not read an entire technical reference to understand one setting.
Search covers the published documentation version you selected. Describe an action and an object: “rename an export field” is usually better than “field.” If nothing relevant appears, use a term from the interface or shorten the question.
Read the answer with its conditions
Check a found example in context. An operation may require particular permissions, prepared data, or a mode. A search snippet helps you choose an article but cannot replace its surrounding explanation.
Check the documentation version too. It remains selected when you follow links, so a colleague's link may point to an older edition. Record the article and version when asking why your interface behaves differently.
Use the table of contents to reach a section. A link with an anchor and a short note tells a teammate exactly what you checked, better than sending the documentation home and retelling the answer.
Return to a small test in the application after reading: preview an export, inspect a log, or perform a trial. The editorial pre-export checklist helps with data delivery. If the question remains, note what you did and what appeared instead. That example helps in the next search or discussion.
