Skip to content

docs: rewrite manifest description as a capability-focused tagline - #19

Merged
aesslinger merged 1 commit into
mainfrom
chore/manifest-description
Aug 14, 2026
Merged

docs: rewrite manifest description as a capability-focused tagline#19
aesslinger merged 1 commit into
mainfrom
chore/manifest-description

Conversation

@aesslinger

Copy link
Copy Markdown
Collaborator

Summary

The manifest's description field ("PostgreSQL plugin driver for Tabularis (parity implementation)") was internal dev-team language left over from the Phase 1 migration — meaningless to an end user browsing the Tabularium registry. Rewrote it as a capability-focused tagline, matching the style of the strongest sibling plugin descriptions already on the registry (mongodb, firestore):

Full-featured PostgreSQL driver for Tabularis: browse schemas, tables, views, routines, and triggers; run queries with EXPLAIN plans; edit rows with type-aware binding for enums, JSON, arrays, UUIDs; generate DDL for tables, columns, indexes, and foreign keys.

260 characters, confirmed under the manifest schema's 280-char cap.

Also synced the GitHub repo's own description field (gh repo edit --description) to match — it was still carrying the old wording, visible on the org page, search results, and clone info.

Context

This plugin is now live on the Tabularium registry at /plugins/postgresql (submitted and confirmed working this session — verified the release webhook via a signed manual replay of the real v1.0.0-beta.5 release event, since GitHub has no built-in way to send a synthetic release event for testing). The registry currently mirrors the old description verbatim, so this change won't take effect there until the next release webhook fires or the manifest is refreshed from the registry's /admin panel.

Verification

  • npx @tabularium/cli validate .tabularium --registry https://registry.tabularis.dev --kind driverok
  • npx markdownlint-cli CHANGELOG.md → clean
  • Confirmed description length (260 chars) against the schema's maxLength: 280
  • Confirmed GitHub repo description now matches via gh repo view --json description

Test plan

  • Manifest validates clean against the live registry schema
  • CHANGELOG markdownlint-clean
  • GitHub repo description synced and confirmed

The old description ("PostgreSQL plugin driver for Tabularis (parity
implementation)") was internal dev-team language that meant nothing to
an end user browsing the registry. Rewrote it to list actual
capabilities (schema browsing, EXPLAIN plans, type-aware row editing,
DDL generation), matching the style of the strongest sibling plugin
descriptions already on the registry (mongodb, firestore). Confirmed
under the manifest schema's 280-char cap (260 chars).

Also synced the GitHub repo's own description field to match, since it
was still carrying the old wording.
@aesslinger aesslinger added the prerelease:beta Version suggestion targets a beta prerelease label Aug 14, 2026
@github-actions

This comment has been minimized.

@aesslinger aesslinger changed the title feat: rewrite manifest description as a capability-focused tagline docs: rewrite manifest description as a capability-focused tagline Aug 14, 2026
@github-actions

Copy link
Copy Markdown

No release needed for this PR (docs).

@aesslinger
aesslinger merged commit a07dcd3 into main Aug 14, 2026
21 checks passed
@aesslinger
aesslinger deleted the chore/manifest-description branch August 14, 2026 15:24
aesslinger added a commit that referenced this pull request Aug 14, 2026
Continuation of the beta line after PR #20 (absolute image URLs in
README, fixing broken images on the Tabularium registry page) and the
carried-forward PR #19 description rewrite. Registry-listed release.

Verified: .tabularium re-validated clean against the live registry
schema; cargo build/test (85/85)/clippy/fmt all pass; markdownlint clean.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

prerelease:beta Version suggestion targets a beta prerelease

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant