docs: add per-module attribution to the package map and tier tables#311
Merged
Conversation
Now that the split has landed, record which artifact ships each package. - api-stability section 4 gains a Module column and a document.showcase (FontShowcase) row. - package-map gains a Module Layout section mapping the packages onto the 2.0 coordinates. - ROADMAP graduates the "multi-module Maven layout" item — it shipped in 2.0.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The split has landed, but the package-level reference docs still read as a single artifact —
there was no per-package "which module ships this" mapping, and the roadmap still listed the
module split as a future "if there is clear demand" item.
What
com.demcha.compose.document.showcase(FontShowcase) row.coordinates (core / render-pdf / render-docx / render-pptx / templates / testing / wrapper
/ bundle), noting the options-in-core vs pdf-impl-in-render-pdf split.
pointing at the migration guide (and dropping the stale
graph-compose-pdfcoordinate name).Tests
CanonicalSurfaceGuardTest,DocumentationCoverageTest,PackageMapGuardTest,VersionConsistencyGuardTest) — 24 tests, 0 failures. Links resolve.Follow-up (not in this PR): the pre-existing
contributing/extension-guide.mdlink rot(wrong
../depth, relocated test-scaffolding links) is a separate repair pass.