markdown-office.github.io valid

Markdown Office

One Markdown document becomes a Word document or a PowerPoint deck. In PHP, with no Office and

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-25T04:54:19.806Z. Cached copy · Source on markdown-office.github.io

# Markdown Office

> One Markdown document becomes a Word document or a PowerPoint deck. In PHP, with no Office and
> no binaries. Both halves read the same directive syntax. One part converts a document back to
> Markdown as well.

This documentation is built from Markdown, and every example in it was produced by the library
it documents at the moment the site was built. The same pages are available as Markdown one page
at a time, and there is a JSON index at https://markdown-office.github.io/pages.json.


## Markdown Word

- [Markdown Word](https://markdown-office.github.io/word/): CommonMark and GitHub Flavored Markdown into .docx, .odt and .rtf — extended with frontmatter and themes, and with two directives — and back out again.
- [Word directives](https://markdown-office.github.io/word/directives/): ::toc and :footnote are drawn. Everything else is written into the document exactly as the author typed it.
- [Configuration](https://markdown-office.github.io/word/configuration/): Every frontmatter key, every option, every style slot and its default — and the parser you have to pass to read any of it.
- [Round trips](https://markdown-office.github.io/word/round-trip/): Markdown to a document and back. What comes out the same, and the five things that do not.
- [Image options](https://markdown-office.github.io/word/images/): The three options that decide what happens to a picture, and the two calls that report what happened to it.
- [Errors](https://markdown-office.github.io/word/errors/): Every exception Markdown Word throws, and what each one means.

## Markdown Presentation

- [Markdown Presentation](https://markdown-office.github.io/presentation/): Slidev-inspired Markdown into .pptx — layouts, themes, click builds and speaker notes, extended with directives. One direction only.
- [Presentation directives](https://markdown-office.github.io/presentation/directives/): ::click, :::click, ::column and ::note — plus the closed set of frontmatter keys, and everything the deck will refuse by name.
- [Themes and layout](https://markdown-office.github.io/presentation/themes/): The twelve colour slots, the thirteen style keys, the eight layout roles, and the four themes that ship with the presentation package.
- [Errors](https://markdown-office.github.io/presentation/errors/): Every exception Markdown Presentation throws, and what each one means.

## In general

- [How directives work](https://markdown-office.github.io/directives/): One syntax, three shapes, and what each half of the suite does with a name it recognises — and with one it does not.
- [The directive syntax](https://markdown-office.github.io/directives/syntax/): Every rule of :name, ::name and :::name — names, labels, attributes, fences, and the four things that look like directives and are not.
- [Images](https://markdown-office.github.io/images/): What is carried, what is converted, what is refused, and the pixel ceiling that makes a 152-byte file expensive.
- [Errors in general](https
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=markdown-office.github.io · GET /v1/domain/markdown-office.github.io · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for markdown-office.github.io:
1. POST https://agentwebmap.com/v1/sites/markdown-office.github.io/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://markdown-office.github.io/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/markdown-office.github.io/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/markdown-office.github.io).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.