pptz

Quick Reference

Contract

deck-topic/
|-- deck.pptz.toml
|-- pages/
|   |-- cover.page.toml
|   `-- agenda.page.toml
|-- images/
`-- dist/
    `-- deck.pptx

Workflow

1. Create deck.pptz.toml with deck size, theme colors, text/table styles, and ordered page paths.
2. Create pages/*.page.toml with explicit bounds and theme tokens.
3. Put local assets under the deck directory and reference them with relative paths.
4. Compile from the deck directory:

   moon runwasm Milky2018/pptz@0.4.0 deck.pptz.toml --out dist/deck.pptx

   When working inside this repository, use the local package instead:

   moon runwasm . examples/minimal/deck.pptz.toml --out examples/minimal/dist/deck.pptx

5. Deliver the source directory and generated .pptx.

Boundaries

• Use paths relative to the deck directory. Published wasm runs with sandboxed file access.
• Stay inside the documented pptz schema. Unknown fields are rejected before 1.0, and raw OpenXML passthrough is intentionally unsupported.
• Treat writer capability errors as schema boundaries, not TODOs to work around with backend internals.
• Do not rely on letter_spacing, line/connector shape presets, unsupported icon names, unsupported connector kinds, or unsupported shape names.
• font_family must be one PowerPoint typeface name, not a CSS fallback list. Use "Aptos" or one concrete CJK font such as "PingFang SC"; do not write "Aptos, Arial" or "MiSans, PingFang SC, Microsoft YaHei".

Patterns

Style Inheritance

[theme.text_styles.body]
font_size = 22
font_family = "Aptos"
color = "$text"

[theme.text_styles.caption]
extends = "$body"
font_size = 12
color = "$muted"

[theme.table_styles.base]
font_size = 14
font_family = "Aptos"
border = { style = "solid", width = 1, color = "$line" }

[theme.table_styles.compact]
extends = "$base"
header_fill = "$surface_alt"
header_text_color = "$text"
body_text_color = "$text"

Layout Templates

[layouts.content.slots.eyebrow]
bounds = [72, 38, 500, 24]
style = "$caption"

[layouts.content.slots.heading]
bounds = [72, 72, 900, 72]
style = "$title"

[[layouts.content.elements]]
id = "accent"
type = "shape"
bounds = [48, 40, 6, 96]

[layouts.content.elements.content]
shape = "rect"

[layouts.content.elements.content.fill]
type = "solid"
color = "$primary"

layout = "$content"

[slots]
eyebrow = "Risk model"
heading = "风险分析"

Components

[components.stat_card]
bounds = [0, 0, 180, 90]

[[components.stat_card.elements]]
id = "label"
type = "text"
bounds = [16, 14, 148, 24]

[components.stat_card.elements.content]
style = "$caption"
text = "$label"

[[components]]
id = "npm_card"
use = "$stat_card"
bounds = [72, 160, 180, 90]

[components.props]
label = "npm packages"

Diagram Safety

• Do not use spaces to align text across multiple visual objects. Use separate text boxes, table cells, or component instances.
• Treat colored cards, chips, and diagram nodes as semantic objects: each one needs its own label inside the same bounds, or a component that contains both the background shape and label.
• Use empty shapes only as decoration or background chrome. If a shape represents a step, category, state, metric, or concept, bind visible text to that shape.

Rich Text

[elements.content]
style = "$body"
align = ["left", "top"]
wrap = true

[elements.content.body]
auto_fit = "shape"

[elements.content.body.inset]
left = 8
right = 8
top = 4
bottom = 4

[[elements.content.paragraphs]]
text = "Agenda item"
space_after = 6
margin_left = 18
indent = -9

[elements.content.paragraphs.bullet]
kind = "char"
char = "-"

[[elements.content.paragraphs]]

[[elements.content.paragraphs.runs]]
text = "Read "

[[elements.content.paragraphs.runs]]
text = "docs"
style = "$link"
hyperlink = "https://example.com"
tooltip = "Documentation"

Table Style

[theme.table_styles.compact]
font_size = 14
font_family = "Aptos"
header_fill = "$surface_alt"
header_text_color = "$text"
body_text_color = "$text"
border = { style = "solid", width = 1, color = "$muted" }

[elements.content]
style = "$compact"
data = [
  ["Metric", "Q1", "Q2"],
  ["Revenue", "100", "150"],
]

Chart Data

[theme.chart_styles.report_bar]
kind = "bar"
legend = "bottom"
style = 4
data_labels = "outside_end"

[elements.content]
chart_style = "$report_bar"
title = "Revenue"
data = [
  ["", "Q1", "Q2", "Q3"],
  ["Revenue", 100.0, 150.0, 125.0],
]

[elements.content]
kind = "bar"
title = "Revenue"
legend = "bottom"
data = [
  ["", "Q1", "Q2", "Q3"],
  ["Revenue", 100.0, 150.0, 125.0],
]

Images

[elements.content]
path = "images/hero.png"
fit = "cover"

[elements.content.crop]
left = 0.05
right = 0.05
top = 0.0
bottom = 0.0

Delivery Bar

• The PPTX is generated successfully.
• The TOML sources remain editable and are delivered with the PPTX.
• Assets are local to the deck directory and referenced relatively.
• The deck does not assume unsupported schema features.
• Prefer each slide to have a visual structure: image, chart, table, icon, connector, or shape composition.
• Render or preview every deck before delivery; do not leave unreadable table text, clipped text, broken wrapping, empty semantic cards, or labels floating outside their cards.