Filled example · OpenCatalogi

opencatalogi(7) Conduction · v2026.04 · NL

OpenCatalogi.

De catalogus. Vind, installeer en update apps uit een gefedereerd register van vertrouwde uitgevers.

Stable Cobalt · canonical v2.4.1

What it does

OpenCatalogi is a federated catalogue for Nextcloud apps and public registers. You publish your own apps, or consume those of others, with a uniform metadata spec.

Publish and retract apps via a simple UI or the API.
Federated discovery, see what other municipalities run.
Audit trail per publication, suitable for WOO.
Schema validation against the Conduction app spec.
Works with OpenRegister for structured records under the catalogue.

For whom

Municipalities and joint arrangements that want to surface their own apps and registers without vendor lock-in. Also suitable for MKB IT leads who want an internal catalogue for team tools.

Status

Production stable. Deployed at 7 municipalities and 2 joint arrangements. Weekly releases, breaking changes only between majors.

Works with

OpenCatalogithis app

OpenRegisterdata underneath

OpenConnectorexternal APIs

DocuDeskdocuments

LaunchPadstart page

Cobalt border = this fact sheet · cobalt-50 border = direct compatibility.

Known limitations

Federation between instances is best-effort, not 100% real-time consistent.
Schema validation is strict; old apps without the Conduction app spec aren't auto-adopted.
No CSV import in the UI, that flow goes via OpenConnector.

Install

conduction install OpenCatalogi

Or via the Nextcloud app store · AGPL-3.0 · source: codeberg.org/Conduction/opencatalogi

conduction.nl/apps/opencatalogi · docs.conduction.nl/opencatalogi v2026.04 · EN

Empty template · placeholders only

{{ app-slug }}(7) Conduction · {{ version }} · {{ lang }}

{{ AppName }}.

What it does

{{ Concrete capability 1 }}
{{ Concrete capability 2 }}
{{ Concrete capability 3 }}
{{ Concrete capability 4 }}

For whom

{{ Audience tier and the problem they have. Not a persona, a situation. }}

Status

Works with

{{ App }}this app

Known limitations

{{ Limitation 1 }}
{{ Limitation 2 }}
{{ Limitation 3 }}

Install

conduction install {{ AppName }}

Or via the Nextcloud app store · {{ licence }} · source: codeberg.org/Conduction/{{ slug }}

conduction.nl/apps/{{ slug }}{{ version }} · {{ lang }}

Why we built it this way

Each app is a chapter, not a brochure

Marketing one-pagers list features and lose context. Ours are paginated like a manpage entry: one app per A4, with the same structure across the family. Stack five fact-sheets, you have the book.

App glyph hex top-left, big. 22mm hex with the app's canonical icon. Recognisable from across a desk; the glyph is the primary identifier, not the wordmark.
Tagline ends with a period. "OpenCatalogi." with a period turns the title into a finished thought. The tagline below names the verb and the noun: "Vind, installeer, update."
Works-with compat-grid. Five small hexes showing siblings; the current app is cobalt-filled, the rest are tinted. Tells the reader "this is part of a family" without a paragraph.
"Known limitations" panel in vermillion. Honest disclosure of what doesn't work, on the front of the page, not buried. Builds trust with engineers who would find it anyway.
Install strip in cobalt-900. Dark band at the bottom with a CLI command. Turns the install into a copyable artefact, not a sales hand-off.
"$ man opencatalogi(7)" running header. Plex Mono running header treats the fact-sheet as a manpage entry. Section number 7, "miscellaneous", reading developers smile.
Three pills, three signals. Status (stable/beta), colour family, version. Visible at a glance, no walls of text needed.

Uses

tokens.css · app glyphs · hex-bullet icon · status badges · .paper--A4 · Plex Mono for running header

Download .odtLibreOffice / Word →

Open in your editor, fill the {{ placeholders }}, export to PDF.

App fact-sheet

OpenCatalogi.

What it does

For whom

Status

Works with

{{ AppName }}.

What it does

For whom

Status

Works with