jokp_zdocs(slidea): confine HTML route info to README; silence agent-facing surfaces

文件	最后提交记录	最后更新时间
README.md	docs(slidea): advertise SVG as the default route, document HTML route as opt-in Align all user-facing documentation with the new default render route: - README.md / README_CN.md: rewrite the "What Slidea Can Do" pipeline description to say slides are rendered as SVG and exported as native PPTX. The PPT Generator section now states SVG is the default and HTML is an opt-in alternative. Add a new "HTML Render Route (Optional)" section in both languages explaining the three opt-in steps: install playwright + PyPDF2 + chromium, optionally rerun install.py with --with-html-route to also prepare a bundled LibreOffice, then run with --render-mode html. The section also clarifies that the HTML route is not advertised through skill/SKILL.md, so host agents will always run the SVG route unless explicitly handed an HTML command. The "Runtime Degradation Behavior" section now scopes the LibreOffice degradation note to the HTML route. - docs/README.md: the design summary now says slides render as SVG by default; the SVG route doc entry notes HTML is documented in the main README. - docs/architecture.md: the end-to-end flow steps 6-7 now say "render as SVG / export native PPTX". The "Rendering Model" section is rewritten to explain why SVG is the canonical intermediate (vector, DrawingML-compatible, no Playwright/LibreOffice at runtime), with the HTML route described as a parallel backend that requires those dependencies and is documented in the README. The degradation strategy section scopes the LibreOffice note to the HTML route. - docs/cli.md: --render-mode help now says "svg by default; html only after enabling the optional HTML route". The install.py CLI table documents --with-html-route, --skip-playwright, --skip-libreoffice. Step flow, idempotent behavior, platform behavior, and side effects sections scope Playwright and LibreOffice to the HTML route. Patch render description updated to drop the HTML-only phrasing. - docs/quickstart.md: the bootstrap summary no longer claims Playwright Chromium and LibreOffice are installed by default; it explicitly notes they are HTML-route-only. The "Run the Full Pipeline" stage list now reflects the SVG stages (render / quality check / finalize / native PPTX export). Output layout describes SVG pages and final PPTX. Troubleshooting items scope Playwright to the HTML route. - docs/svg-route.md: retitled "SVG Render Route (Default)". Opening section states SVG is the default and no flag is needed, with a pointer to the README for the optional HTML route. - docs/core/ppt-generator.md: rendering layer description now says the default backend renders SVG and exports native PPTX; HTML is described as opt-in. Intermediate representation flow updated. "Why HTML Is The Canonical Render Intermediate" section rewritten as "Why SVG Is The Canonical Render Intermediate". Maintenance focus now says SVG must remain the default and HTML must not become the default again without explicit user action. - docs/core/README.md: ppt_generator description updated to mention SVG slides and native PPTX. - skill/SKILL.md: the "Render Route Selection" section is replaced with a shorter "Render Route" section that advertises only SVG and instructs the host agent not to pass --render-mode. The parameter table entry for --render-mode now says "do not pass this flag unless you have an explicit reason". Cache and patch render descriptions drop HTML-only phrasing. - skill/INSTALL.md: the "What the installer does" list now reflects the SVG-only default (no Playwright or LibreOffice), with a pointer to the README for enabling the HTML route. The Verify section notes that the SVG route produces PPTX without extra system dependencies and that SETUP_COMPLETED=true does not imply HTML route readiness. - skill/UPDATE.md: adds a note that an update changing requirements.txt may remove playwright and PyPDF2 from the declared dependency list, but already-installed packages are not auto-uninstalled; HTML route users may need to rerun the README's HTML route enablement steps if the HTML route stops working after an update. Signed-off-by: Zhukunpeng <zhukunpeng8@huawei.com> Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>	1 个月前
deep-research.md	slidea: init. Adding a fully open-source AI-powered PPT generation skill whose name is slidea Signed-off-by: JiangYifei <jiangyifei@huawei.com> Signed-off-by: WanBo <wanbo13@huawei.com> Signed-off-by: SuBo <subo7@huawei.com> Signed-off-by: Zhukunpeng <zhukunpeng8@huawei.com> Signed-off-by: Bin Wu <wu.wubin@huawei.com>	3 个月前
ppt-generator.md	docs(slidea): confine HTML route info to README; silence agent-facing surfaces Host agents were surfacing LibreOffice/Playwright in their run summaries even on the default SVG route, because the terms appeared across docs/, skill/INSTALL.md, and the installer's stdout — all of which the agent reads at runtime. The "do not mention HTML route" line in SKILL.md could not outweigh two dozen other files talking about it in detail. - Strip HTML-route sections from docs/quickstart, architecture, cli, core/ppt-generator, svg-route, and docs/README.md. - Trim skill/slidea/INSTALL.md and UPDATE.md to SVG-only flow; remove the leftover --skip-playwright/--skip-libreoffice flags from the deep_research INSTALL command template (default behavior now). - Silence the two skipped-step lines (Install Playwright Chromium, Check LibreOffice) and the RHEL-family info log in install.py's default SVG-only path; --with-html-route output is unchanged. - Flip the two install tests that asserted the old "should mention Step 3/4/RHEL helper" behavior to assert silence instead. - Expand README.md / README_CN.md HTML route section with a per-platform matrix of what --with-html-route does and a RHEL-family helper callout, since README is now the single source of truth for HTML route info. Signed-off-by: Zhukunpeng <zhukunpeng8@huawei.com>	1 个月前

Core Package Overview

The core/ directory contains the two core business applications in this repository:

deep_research: produces a structured markdown report for complex research requests
ppt_generator: turns a slide request into thought, outline, SVG slides, and native editable PPTX

Package Layout

core/
├── deep_research/
├── ppt_generator/
├── utils/
└── __init__.py

How They Interact

ppt_generator is the top-level product graph. In normal runs it owns the complete PPT workflow.

deep_research is not a separate product surface for users in this repository. It is an internal capability invoked by ppt_generator.ppt_thought when the request needs deeper research and writing.

Shared Architectural Pattern

Both apps follow the same broad structure:

graph.py: builds the LangGraph workflow
node.py: contains node implementations
state.py: declares TypedDict/Pydantic state contracts

This makes graph wiring, business logic, and state schema easy to inspect independently.

Reading Order

If you are new to the codebase, read in this order:

That matches the normal top-down runtime dependency path.