> For the complete documentation index, see [llms.txt](https://report.pytogo.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://report.pytogo.org/rapport-de-la-pycon-togo-2025/contexte-de-la-conference/sessions.md).

# Sessions

PyCon Togo 2025 a présenté **13 sessions au total**, conçues pour offrir à la fois un apprentissage technique et un engagement communautaire :

* **Ateliers (2)** : Sessions pratiques animées par Denis Akpagnonité (DevOps) et Serge Koudoro (Ingénierie des systèmes intelligents).
* **Conférences standard (9)** : Couvre un large éventail de sujets tels que l'ingénierie logicielle, la science des données, le machine learning, l'IA/GenAI, la contribution open source, l'éducation et le développement communautaire.
* **Table ronde (1)** : Un échange interactif sur la technologie, l'entrepreneuriat et l'innovation en Afrique.
* **Présentation éclair (1)** : Une présentation courte et percutante sur la HealthTech par Koami Afantchao Aziabou.

Ensemble, ces sessions ont offert aux participants une **expérience complète** , combinant compétences pratiques, profondeur technique et discussions orientées vers l'avenir.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://report.pytogo.org/rapport-de-la-pycon-togo-2025/contexte-de-la-conference/sessions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.