Skip to content

AI turns documents or topics into real, native PowerPoint decks—with native shapes, transitions and animations, data-backed charts and tables on demand, audio narration from speaker notes, and support for your own .pptx templates. · by Hugo He

docs(contributing): state that only Microsoft PowerPoint rendering is in scope

hugohe395b3f18e3713
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index ac249cda..181b8958 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -68,6 +68,7 @@ AI assistance is welcome — this project is itself AI-driven. But an AI-drafted
- "Drive-by" cosmetic reformatting unrelated to a real fix
- Pure translations or wording-only edits that were not requested or discussed first
- Changing a foundational setting — the MIT license, or DrawingML component reuse / template-fill in place of AI-generated shapes. These are deliberate founding choices and won't change midway
+- Fixes whose only effect is in a renderer other than Microsoft PowerPoint — PPT Master targets PowerPoint and nothing else; Keynote, WPS, LibreOffice and Google Slides can open the output, but their rendering differences (ignored `wrap="none"`, their own script-spacing rules, remapped effects) are outside the contract. If the deck is correct in PowerPoint, it is correct. Such reports are closed as not planned, and PRs for them are closed unmerged even when the change looks harmless, because the affected code paths (width estimation, the quality checker, export) also drive PowerPoint output
- Fixed numeric quotas to constrain generation (`max_cards` / `max_bullets` / `max_table_rows` and similar) — density is governed by narrative rhythm and one primary focus per page, not hard caps
- Post-processing that is quality smoothing rather than compatibility — we fix things that are broken/unusable if not done (e.g. AI-image size/format/alpha); "nicer if done" polish (loudness normalization, kerning) stays out. If a model or service falls short, the fix is to switch it, not to make the project adapt to it
- A new backend, path, or option that duplicates a capability the repo already provides — check current behavior first (e.g. OpenAI-compatible providers already run under `IMAGE_BACKEND=openai`)
@@ -110,6 +111,7 @@ Open an issue on [GitHub Issues](https://github.com/hugohe3/ppt-master/issues) a
- Steps to reproduce
- Expected vs. actual behavior
- Environment details (OS, Python version, AI editor used)
+- Confirmation that the problem shows in Microsoft PowerPoint — a deck that renders correctly there but differently in another app is not a bug for this project (see above)
## Code of Conduct