Article to Deck

Problem

When an article, iWiki page, KM document, or local file needs to become a quick presentation, manually rebuilding slides often means reorganizing headings, splitting pages, adjusting typography, and restoring visual hierarchy. Article to Deck compresses that workflow into a generation pipeline: fetch the content, plan pages by section, and output a single full-screen HTML deck. It is especially useful for technical write-ups, proposal reviews, weekly meeting material, and ad-hoc presentations, and it can reduce the repeated formatting work between documents and slides.

How It Works

• Source intake: supports iWiki links / docid, KM links, local file paths, and pasted text; iWiki uses mcporter call iwiki.getDocument to fetch the body, while KM first fetches a summary and then extracts the article body.
• Page planning: splits content by top-level headings or major sections, subdivides long sections when needed, targets 6-15 pages, and generates short labels for side navigation.
• HTML generation: fills placeholders such as {{TITLE}}, {{SUBTITLE}}, {{SLIDES_HTML}}, and {{NAV_DATA}} from assets/deck-template.html, using lists, tables, cards, process steps, and code blocks to structure each page.
• Delivery checks: enforces minimum 12px typography, matching navigation data, and valid HTML structure; the result is navigable with the wheel or arrow keys and can be full-screened with F11. It is intended to turn existing articles into presentable decks, not to redesign the source material or replace a design system.