what is easyslides fr?

EasySlides is a Python toolchain that turns academic source material into editable PowerPoint files on your own machine. The README is bilingual, with the same content in Chinese and English. The stated goal is to take papers, reports, web pages, Markdown notes, and similar sources and convert them into decks that have a consistent structure and a consistent visual style, while still being editable in PowerPoint afterwards. The pipeline runs in five stages. Source material goes into a project workspace, the workspace produces a deck plan, the deck plan is rendered through SVG and layout templates, and the result is exported as a PPTX file. The repository groups its code into folders that match that pipeline. The scripts folder holds utilities for conversion, project management, SVG validation, template import, and PPTX export. The templates folder holds academic layouts, style packs, chart modules, and icon libraries. There are also folders for references, optional workflows like preview and audio, and a tests folder with regression tests. To try it, the README asks you to install the Python requirements and run the test suite. From there you initialise a project, import your source files, validate the project, finalise the SVG pages, and then export the deck to PPTX. There are several maintenance commands shown for checking the quality of individual layout templates and rebuilding the template index. The templates section lists two main layout families, defense and literature, with aliases for older template IDs. The acknowledgements section credits five other open-source projects that influenced different layers of EasySlides, covering engineering plumbing, academic communication, narrative flow, style governance, and paper and literature report workflows. The last section is about privacy. Generated decks, source papers, exported PPTX files, previews, and local QA outputs in the projects folder are ignored by Git by default. The README asks contributors to commit only reusable code, templates, tests, and documentation, and to keep API keys in environment variables or a local .env file rather than in the repository.