Skip to content

docs: make catalog versioning easier to understand#117

Merged
Reefact merged 8 commits into
mainfrom
agent/improve-catalog-versioning-docs
Jul 14, 2026
Merged

docs: make catalog versioning easier to understand#117
Reefact merged 8 commits into
mainfrom
agent/improve-catalog-versioning-docs

Conversation

@Reefact

@Reefact Reefact commented Jul 14, 2026

Copy link
Copy Markdown
Owner

Summary

Restructure the catalog versioning documentation from one long page into a short guide plus dedicated reference and CI/CD pages (English and French), so a reader meets the mental model and the everyday workflow first and reaches implementation detail only when needed. The entry-point filenames are unchanged, so existing links stay valid.

Type of change

  • Bug fix
  • New feature
  • Breaking change
  • Refactoring
  • Analyzer / diagnostic change
  • Tests
  • Documentation
  • Build / CI / tooling

Changes

  • Reorganized CatalogVersioning.{en,fr}.md around the mental model and the daily workflow: snapshot vs committed baseline, what catalog update actually means, a concrete errors-baseline.json example, and the rename scenario.
  • Extracted a bilingual referenceCatalogVersioningReference.{en,fr}.md: commands, options, exit codes, --fail-on / --report / --against, snapshot & baseline format, schema behavior, and fce.json configuration.
  • Extracted a bilingual CI/CD guide — CatalogVersioningCI.{en,fr}.md: GitHub Actions and GitLab CI examples, baseline seeding, label-based acceptance, and release-diff scenarios.
  • Standardized the example error codes in the versioning guide on UPPER_SNAKE_CASE (PAYMENT_DECLINED), matching the errors-baseline.json example shown on the same page.
  • Linked the three pages into one linear navigation spine (operational integration → guide → reference → CI/CD → architecture) with a consistent "up to the table of contents" link, and grouped them under a Catalog versioning sub-section in the English and French tables of contents.

Testing

  • dotnet build FirstClassErrors.sln
  • dotnet test FirstClassErrors.sln
  • Analyzer tests pass (FirstClassErrors.Analyzers.UnitTests)

Documentation-only change; no source code was modified, so the build and test commands do not apply. Verified instead that every cross-page and table-of-contents link resolves, that the footer navigation spine is acyclic in both languages, and that all commits pass the repository commit-lint (--ci).

Documentation

  • Public API / error documentation updated
  • README / doc/ updated
  • French translation (doc/README.fr.md) updated if user-facing behavior changed
  • No documentation change required

Every page exists in English and French and was updated together; the French README table of contents was updated alongside the English one. No user-facing behavior changed.

Related issues

None.

Reefact and others added 7 commits July 14, 2026 09:32
The rename example used dotted error codes (PAYMENT.DECLINED) while the
baseline JSON example in the same guide, and the FCE004 UPPER_SNAKE_CASE
convention the library enforces, use underscores. Align the example on
that convention in both the English and French guides.
Make the three catalog versioning pages navigable as one unit. The footer
links now form a single linear path (operational integration -> guide ->
reference -> CI/CD -> architecture) instead of the guide skipping its own
sub-pages and the reference and CI/CD footers pointing at each other; every
page also gains the "up to the table of contents" link.

The README table of contents (English and French) groups the guide,
reference, and CI/CD pages under a "Catalog versioning" sub-section, so the
three are discoverable and the "table of contents" links land where the
pages are actually listed.
@Reefact Reefact marked this pull request as ready for review July 14, 2026 08:40
@Reefact Reefact merged commit b401fb6 into main Jul 14, 2026
12 checks passed
@Reefact Reefact deleted the agent/improve-catalog-versioning-docs branch July 14, 2026 08:50
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.

2 participants