> 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/pycon-togo-2026-report/pycon-togo-2026-report-fr/rapport-pycon-togo-2026/contexte-de-la-conference/pykids.md).

# PyKids

Dans le cadre de PyCon Togo 2026, le programme PyKids a initié environ 20 enfants au monde de la programmation et de la technologie.

Cette initiative a offert aux enfants l’occasion de découvrir les bases de la programmation grâce à des activités accessibles et adaptées aux débutants, utilisant Python, les algorithmes, l’IA et Scratch. Grâce à cette introduction, les participants ont exploré des concepts de programmation fondamentaux et ont fait leurs premiers pas vers la compréhension de la création de logiciels.

PyKids a reflété l’engagement de PyCon Togo à promouvoir un premier contact avec la technologie, à encourager la curiosité et à rendre l’enseignement de la programmation plus accessible aux jeunes générations.

En initiant les enfants à la programmation dans un environnement d’apprentissage accueillant, le programme visait à susciter leur intérêt pour la technologie et à les encourager à continuer d’explorer les compétences numériques au-delà de la conférence.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://report.pytogo.org/pycon-togo-2026-report/pycon-togo-2026-report-fr/rapport-pycon-togo-2026/contexte-de-la-conference/pykids.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.