OpenVibe.Publishing

OpenVibe.Publishing holds the "shared publishing packages for the OpenVibe publication products": Wiki, Blog, News, Reviews, Deals, Coupons and Trade. Its README gives the status as alpha, 0.2.0 (roadmap Wave 15). The modules are tested; v0.1.0 is tagged, 0.2.0 is not tagged yet, and no product uses the packages in production yet. OpenVibe.Wiki and Blog are named as the first planned consumers. The package is openvibe-publishing (CommonJS, Node 20 or later) and its license is MIT.

Packages, not an authority

The README states that the repository is "code, never state". It has no runtime, port, domain, database or API of its own. Each product keeps its publication state in its own database: the modules take the product's better-sqlite3 handle and a table prefix and create prefixed tables inside that database, so two products share code but not data.

Modules

• revisions — drafts, immutable revisions, diffs and revert;
• schedule — scheduled publish and unpublish jobs;
• taxonomy — tags, terms and hierarchical categories;
• citations — append-only source references on one revision, by OpenVibe.Sources item id and/or URL;
• media — attachments referenced by OpenVibe.Media object id;
• discussion — references to OpenVibe.Community comment threads;
• seo — a deterministic indexability gate, canonical URLs, redirects, sitemaps and feeds;
• authorship — human, AI, hybrid and imported records; AI content is held as draft and noindex until a person's review;
• index-hooks — search.index-document@1 documents and the events OpenVibe.Search consumes;
• ssr — auto-escaping templates and a safe Markdown subset.

What it does not do

It does not own publication state, run workers or decide editorial rules. It stores references instead of comment content, media bytes or source items. It is not a notification, search or event runtime: it builds the documents and envelopes those services, such as OpenVibe.Events, consume.