Browser-readable Self-editable Agent-ready

OpenWebDoc slide decks are documents first.

A 16:9 presentation surface that still reads as HTML, edits in place, and travels as one safe HTMLX package.

16:9 stage Uniform presentation geometry Semantic HTML Tables and figures stay real Package CSS Layout owned by the document

Native deck surface

Read The deck opens as a normal browser document.

Correct Visible text and objects stay editable on the page.

Package HTML, CSS, metadata, and assets remain together.

Format shift

The starting point moves from page file to browser surface.

HTMLX keeps the presentation readable before any editor chrome appears.

Document model comparison

Question	Page-first deck	HTMLX-native deck
Where is the source?	Buried in a binary or app-specific file.	Visible HTML plus package-owned CSS.
How does it read?	Best inside the authoring app.	Browser-readable, pageless, and portable.
How do agents edit?	Through conversion, screenshots, or fragile exports.	By editing unpacked package files and validating them.

Package anatomy

A deck is just one explicit package.

The presentation profile describes how slides fit and navigate; the document remains the canonical source.

OpenWebDoc slide package

openwebdoc-slide-deck/ index.html styles/document.css metadata/presentation.json metadata/llm.json manifest.json

HTML Slides, tables, figures, and editable text.

CSS 16:9 composition and object placement.

Metadata Reference data for editing, LLMs, provenance, and presentation.

Manifest Entry, resources, security policy, and package identity.

Agent workflow

The agent boundary stays outside the runtime.

Small corrections happen on the document; structural changes move through unpacked files, validation, and a clean package return.

Runtime boundary and external edit loop

Trusted runtime surface

Package files

1 Open Small edits

2 Unpack Edit package files

3 Validate Safety gate

4 Return Portable document

Semantic behavior

A table in a deck stays a table.

Move the object; preserve the table semantics.

The object moves, the table stays semantic

Mode	What changes	What remains semantic
Read	Open it like a browser document.	Rows, headers, captions, and cells.
Edit	Correct text, captions, and placement.	Table elements stay table elements.
Present	Show one centered slide on black.	Metadata guides fit; it never commands.

Trust model

Metadata guides. It never commands.

LLM metadata, presentation metadata, and editing guides are user-visible references, not a hidden instruction channel.

Runtime safety boundary

Reference data LLM and presentation metadata can describe intent, source, and navigation.

source notes
slide navigation
editing guidance

            Validation gate
            A `.htmlx` package is treated as untrusted input until it passes core checks.
            manifest match
resource allowlist
path safety

          

Blocked surface Scripts, inline handlers, remote resources, traversal paths, and unsafe metadata stay out.

script execution
remote resource loads
hidden instruction channels

Documents can become software surfaces without becoming apps.

OpenWebDoc keeps the authoring boundary plain: open the package, correct the document, validate the result, and share one portable file.

Open in the browser Correct on the document Validate package constraints Share the HTMLX file

HTMLX-native presentation, document-native editing