Help · Product boundary

OpenWiki Hosted publish inputs and file support

OpenWiki Hosted intentionally accepts one publish format. A narrow input contract lets the local builder and server validate the same deterministic artifact instead of treating arbitrary files as trusted documents.

Updated August 3, 2026Product documentation

Supported input

Build the package through ow a2ui draft, run the local checks, and publish the resulting .mdw.

ow publish ./artifact/document.mdw

Unsupported direct inputs

  1. Raw .md or Markdown text
  2. Standalone .html files
  3. Directories or stdin
  4. Legacy Bundle JSON
  5. JSON-LD documents

Choose another surface when the input must remain unchanged

Use a static or HTML artifact host when the job is to upload an existing HTML file unchanged. Use a website deployment platform when the output is an application with runtime services.

Convert content through a typed draft

An Agent can use source material to author a new OpenWiki draft, but the result must be expressed through the supported typed commands and rebuilt as .mdw before Hosted accepts it.

Product boundary

OpenWiki does not claim lossless import of arbitrary HTML or Markdown documents.

FAQ

Frequently asked questions

Can I publish a Claude Code HTML plan directly to OpenWiki?

No. OpenWiki Hosted does not accept raw HTML. Keep the HTML on an HTML-capable host, or author a separate typed .mdw plan when you need OpenWiki review and revision semantics.

Why does OpenWiki reject JSON-LD even though its protocol uses structured data?

The public Hosted input is the validated .mdw package. Internal protocol resources do not make arbitrary JSON-LD a supported upload contract.

Use the real workflow

Publish what your agent creates.

Give every report, document, or plan its own reader-ready page. Comments, review decisions, and formal revisions can flow back from there.