Releases

• A previous build's output is no longer copied as assets. Building into the source (-o _site) and then previewing elsewhere (-o /tmp/preview) copied the first site into the second. Discovery now prunes any source directory holding an .orgo-cache.json, which every build writes into its output. On orgo's own docs that is 21 assets down to 2.

• The documentation site moved to https://orgo.krz.sh. homepage and the README links follow it.

Releases are built and published from gitbay CI rather than GitHub Actions; both workflows are gone.

cargo install orgo

The audit stops reporting gaps that are not gaps, and the oracle's skeleton reducer becomes a public module.

The audit reports only real gaps

Five findings, each one a construct the audit called unsupported that orgo handles exactly as org does. On cleberg.net's 180-file corpus the report goes from 99.9% coverage with 8 out-of-scope uses and one ??? to 100.0% coverage, 0 out-of-scope, and no ???.

• Entities are supported (#30). \alpha renders as α in orgo exactly as in Emacs, from a table generated out of org's own org-entities. Every use was counted out-of-scope anyway, and the org-support guide contradicted itself about it.
• Only entity names org knows count (#26). A Windows path (C:\Users\me) and a namespaced identifier (Tumblr\API\Client) are not entity references.
• #+TBLFM: is in scope (#27). Org's HTML exporter does not recalculate formulas either, so both emit the cells as written.
• Special blocks are supported (#28). A block name with no dedicated handling renders as a div carrying that name and holding parsed org, which is what org's exporter emits. VERSE and COMMENT were also mislabelled and now have their own names.
• A construct named inside verbatim is not a use of it (#1). The entity check skipped =verbatim= and ~code~ spans; the other inline checks did not, so a page documenting org syntax reported constructs it does not use.

??? no longer marks working keywords

??? claimed "a name the implementation does not recognize at all" and marked LEDE, which the shipped docs template reads as page.keywords.lede (#2). Reaching templates as page.keywords.<name> is the designed behaviour, so no keyword name is a blind spot. The distinction between dedicated handling and pass-through is still reported, with an honest marker:

KEYWORDS
    DESCRIPTION                            14      14  guide/01-cli.org:2
—   LEDE                                   14      14  guide/01-cli.org:3
    TITLE                                  14      14  guide/01-cli.org:1

??? is now reserved for drawer and link-scheme names, where an unlisted name has no such fallback.

Public skeleton module

The HTML→semantic-skeleton reducer moves out of tests/oracle.rs into src/skeleton.rs, exposing skeleton() and decode_entities(). An examples/skeleton binary renders a fixture to HTML or skeleton — the reference output the org-conformance corpus is built from. tests/conformance.rs verifies orgo still matches the corpus goldens (opt-in via ORG_CONFORMANCE_DIR), so the generated corpus cannot drift from the renderer unnoticed.

Breaking

• Audit::is_known(kind, name) -> bool is replaced by Audit::marker(kind, name) -> &'static str, which returns the report's marker directly.
• The audit report's census marker column is a consistent four columns wide. ??? used to be one wider than the blank it replaced, so flagged rows sat a character right of the rest.

Docs

Ten source comments cited a README section that no longer exists; they now point at docs/guide/05-org-support.org (#29). Two stale claims in parser.rs's header went with them.

cargo install orgo

• A dark syntax highlighting theme, highlight.theme_dark, for readers whose system asks for dark mode. Set it and syntax.css carries both themes, each behind its own prefers-color-scheme query — one stylesheet, no second link tag, no JavaScript.
• minijinja 2.23.0 → 2.24.0.

The two themes are separated rather than stacked. syntect emits a rule per scope its theme names, and two themes name different ones: InspiredGitHub defines .source.python .keyword where base16-ocean.dark defines only .keyword, so a dark theme appended after a light one loses the cascade on some hundred selectors and leaves light colours on tokens sitting over a dark block. Giving each theme its own query costs the browsers too old to know prefers-color-scheme — they match neither and render code unhighlighted — and that cost falls only on sites that opt in.

Only token colours follow the scheme; the surface under them is the page's, so the built-in themes still leave --orgo-code-* to the site. A minor release because it adds a config key: a site that leaves it empty gets exactly the unconditional rules 0.21.0 wrote, and a 199-page site builds byte-identical output under both.

cargo install orgo

• Four built-in site themes — plain, blog, wiki, docs — compiled into the binary and selected with site.theme, which writes the chosen one to the output root as theme.css, exactly as syntax.css is already written from a syntect theme. A zero-config build used to produce correct HTML with no CSS at all: a real site nobody would publish without writing a stylesheet first.
• A theme template variable, linked before stylesheet so the highlighter's colours win over the theme's. A base.html of your own can ignore theme.css entirely.
• Inline code follows the page. --orgo-code-* coloured inline code as well as code blocks, so a site pairing a dark highlight.theme with a theme turned every inline code into a dark pill on a light page. Those three properties now colour blocks only.
• body sets overflow-wrap: break-word in all four themes. A bare URL widened the page to 573px in a 320px viewport.
• The docs favicon is linked again. Resolving #17 against #16 kept style.css in two positions and dropped the favicon line, so every docs page linked its stylesheet twice and none linked the icon.

Opt-in: the default is empty, so a site that names no theme builds exactly what 0.20.2 built, and no site shipping its own CSS finds a second stylesheet competing with it. An unknown name is an error listing the four. orgo init writes theme = "blog". The v0.20.2 documentation tree renders byte-identical output under both versions.

A theme styles only markup orgo already emits — headings, tags, TODO keywords, checkbox lists, footnotes, tables — plus the chrome the layouts put around it. There is no theme-specific HTML, so switching or removing one touches no template. Colours are --orgo-* properties on :root.

cargo install orgo

• audit recognizes orgo's own keywords. SLUG, DRAFT and TEMPLATE were missing from the known-keyword list, so audit filed them under ??? — a name the implementation does not recognize at all.

Upgrade if you run orgo audit. In 0.20.1 and earlier the audit reports the three keywords orgo reads itself as blind spots: SLUG names the output file, DRAFT decides whether a page publishes, and TEMPLATE picks the template. On a real corpus that means the most-used keyword in the site comes back unrecognized. Nothing about how pages build or render changes.

cargo install orgo

• .well-known is published rather than excluded with the other dot-directories.

Upgrade if you deploy with a delete-enabled rsync. In 0.20.0 and earlier, .well-known was excluded from the build alongside .git and .env, so a deploy that mirrors the output directory removes security.txt and any ACME challenges from the server. That is how this was found.

cargo install orgo

• Sitemaps. sitemap.xml listing every page the build emits, written once site.base_url is set. [build] sitemap = false turns it off.
• Published to crates.io from CI, with no stored token.

cargo install orgo

• Footnote back-links carry an accessible name. <a class="footnote-back" href="#fnr-1">↩</a> had that glyph as its entire accessible name, so a screen reader announced "left arrow with hook" once per note and the reader could not tell which reference any of them returned to. Each now carries aria-label="Back to reference N", and the footnote section carries aria-label="Footnotes" — a <hr> is a picture of a section break rather than a section, so the landmark was otherwise announced as an unnamed "section".
• Template partials are documented in the guide. A snippet that is not really layout — an invitation to reply, a licence line — is better as its own file, and the render key follows {% include %}, so editing one re-renders exactly its users.

No visual change, so no stylesheet has to move.

cargo install orgo

The first tagged release, published as org-ssg — the rename to orgo came later, and this version is not on crates.io.

• A native Rust org parser. No Emacs in the build path.
• Multi-file site builds with link resolution. [[file:other.org]] resolves to the page that file becomes.
• Incremental rebuilds keyed on content hashes. A file whose content is unchanged is not re-rendered.