Skip to content

DEVELOPERS

Start with the document job. Follow a real technical path.

Choose DeckUse, DeckOps, or DeckHTML, then inspect the version, source, lifecycle, and limitations behind the path you plan to build on.

Choose a Product path
Architecture and paths

Choose by document job.

The three Products have different responsibilities and lifecycle boundaries.

01Current, release-scoped

DeckUse

Create a controlled PowerPoint variant or maintain an existing deck with inspectable changes.

Follow the current existing-PPTX lifecycle: init, inspect or query, apply, validate, then commit.

ExploreView DeckUse source (opens in a new tab)
First technical evidence

Inspect the first technical evidence.

Exact commands are omitted until approved release-bound snippets, fixtures, prerequisites, and limitations are available.

DeckUse

Current, release-scoped

Existing PPTX lifecycle

Version-scoped path
Current, release-scoped
init
inspect/query
apply
validate
commit

Current for existing PPTX work. Creation remains release-scoped. Word and Excel are planned. AGPL-3.0.

DeckOps

Future-state contract

Architecture and status

Grounded explanatory architecture
Future-state contract
document
format-specific IR
RAG / modify / export

The public legacy repository is source and status context only. It does not prove a release, install path, license, Product-contract API, SDK, CLI, or Playground.

DeckHTML

Current at v0.6.4

Current conversion direction

Version-scoped path
Current at v0.6.4
HTML / URL / stdin / SVG
PPTX / PNG

PPTX-to-web is testing. Dedicated DOCX paths are planned. Supported content may remain editable; unsupported content may be simplified or rasterized. MIT.

Contract governance

Lifecycle and limits

Status is part of the technical contract, not a decorative badge.

Current
DeckUse existing-PPTX lifecycle; DeckHTML v0.6.4 web-to-PPTX/PNG; DeckProbe v2.4.0 and DeckRender v0.3.1 supporting source paths.
Testing
DeckHTML PPTX-to-web direction.
Planned
DeckHTML dedicated DOCX paths and DeckUse Word and Excel extensions.
Future-state
DeckOps format-specific IR, RAG, modify, and export Product contract.
Legacy context
The DeckOps public repository may be used as source and status context, not as proof of the future-state Product contract.
Developer Docs handoffs

Continue in maintained technical sources.

Supporting projects appear here only as direct technical handoffs, never as primary Products or website destinations.

DeckUse
Source and quickstart / AGPL-3.0
Open source (opens in a new tab)
DeckOps
Legacy repository context / no release inference
Open context (opens in a new tab)
DeckHTML
v0.6.4 source and quickstart / MIT
Open source (opens in a new tab)
DeckProbe
Supporting project / v2.4.0 / MIT
View DeckProbe source (opens in a new tab)
DeckRender
Supporting project / v0.3.1 / MIT
View DeckRender source (opens in a new tab)
Developer Docs
External documentation / English
Read the Docs (English) (opens in a new tab)
Product-owned technical depth

Keep technical depth with its Product.

DeckUse

Runtime details stay with the DeckUse Product path. Use maintained source and Docs for implementation details.

Product path

DeckOps

IR and Parse details stay with DeckOps Docs. Parse is an internal stage, not a website destination.

Product path

DeckHTML

Conversion directions and format limits stay with the DeckHTML Product path and maintained source.

Product path

Implementation documentation is currently available in English. Read the Docs (English) (opens in a new tab)

Final path

Choose the Product path that owns the work.

DeckUseDeckOpsDeckHTML