Skip to content

docs(readme): focus on existing customers + point to catalog ecosystem - #63

Merged
JLCode-tech merged 1 commit into
release/2.2from
docs/readme-clarify-legacy-canonical
May 13, 2026
Merged

JLCode-tech merged 1 commit into
release/2.2from
docs/readme-clarify-legacy-canonical

Conversation

@JLCode-tech

Copy link
Copy Markdown
Owner

Summary

The previous README was written when this was the only Forge module library. Now there's a per-target catalog ecosystem (bnk-forge-catalog-shared, bnk-forge-catalog-aws-eks, jgruber's IBM catalog, planned Azure/GCP/on-prem). The README needs to reflect that — without forcing existing customers to migrate.

What changed

  • Reframed the intro: this is the original Forge module library for BNK 2.2 GA, used by existing Forge installations. Stable, not going away during the 2.2 lifecycle.
  • Non-aggressive pointer at the top: 'new installations may also want to look at the per-target catalogs' — informational, no deprecation pressure.
  • Trimmed the 'Canonical Catalog Contract' verbose metadata block — collapsed into a tight 'Repository contract' section with validators and contract file references.
  • Replaced the 88-line Repository Structure ASCII tree with a compact family table.
  • Replaced the four deployment flow tables with a single ASCII dependency diagram.
  • New section: 'The catalog ecosystem' — lists every per-target catalog with status (live, in progress, planned).
  • Removed stale 'Last Tested 2026-02-10' badge — not the user's focus.

Net: 154 lines → 64 lines, no information loss for the audience this repo actually serves.

Test plan

  • Merge to release/2.2. Existing Forge installations pointing at this URL keep working unchanged.

This repo is the canonical Forge module library for BNK 2.2 GA on
existing Forge installations. The README was written when this was
the only catalog — now there's a per-target catalog ecosystem
(bnk-forge-catalog-* repos) and the README needed to reflect that
without forcing existing customers to migrate.

What changed:
- Reframed the intro: this is the original Forge module library for
  BNK 2.2 GA, used by existing Forge installations.
- Added a non-aggressive pointer at the top: 'new installations may
  also want to look at the per-target catalogs' — without deprecation
  pressure.
- Trimmed the 'Canonical Catalog Contract' verbose metadata block —
  moved the validators and contract file references into a tight
  'Repository contract' section.
- Replaced the Repository Structure ASCII tree (88 lines) with a
  compact family table.
- Replaced the four separate deployment flow tables with a single
  ASCII dependency diagram.
- New 'The catalog ecosystem' section lists every per-target catalog
  with status (live, in progress, planned) so existing customers can
  see where things are heading.
- Removed stale 'Last Tested 2026-02-10' badge — not the user's focus.

Bump VERSION to 2.2-rev.33.
@JLCode-tech
JLCode-tech merged commit 9612678 into release/2.2 May 13, 2026
2 checks passed
@JLCode-tech
JLCode-tech deleted the docs/readme-clarify-legacy-canonical branch May 13, 2026 22:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant